Try it free

View topology

  • Latest Dynatrace
  • Explanation
  • 2-min read

The Smartscape Smartscape in-context topology view allows you to visualize the topology of a selected entity from other Dynatrace apps across the platform. Because it's closely integrated into existing workflows, it can help you to get a deeper understanding of both vertical and horizontal relationships between entities in your environment.

Using the in-context topology view, you can:

  • Access drill-downs and actionable information for all displayed entities.
  • Explore Smartscape Smartscape's rich insights from within another app or a particular view, such as Kubernetes overview or Infrastructure overview, without leaving the current context.

View topology support in Dynatrace apps

You can open an in-context topology view from the entity details in any Dynatrace application that supports this feature, such as Smartscape Smartscape, Notebooks Notebooks, or Threats & Exploits Threats & Exploits, either via an explicitly labeled button or menu item, or through the Open with option after selecting the entity.

Some nodes might not have any edges to other nodes in your environment. If no edges exist in Smartscape on Grail, the topology perspective will only contain the selected node.

The following are some examples of where you can open an in-context topology view:

  • Smartscape Smartscape: from any entity in any Smartscape view by selecting View topology action in the tooltip.
  • Notebooks Notebooks: from a Smartscape node by selecting the Show topology action in the tooltip.
  • Threats & Exploits Threats & Exploits: from the Affected object details within the app.

Overview

The View topology in-context view offers two different perspectives on the selected node's topology:

  • Vertical topology:
    • Provides a complete hierarchical visualization of all related entities for a selected node.
    • Usually used to understand the underlying infrastructure of the target entity.
  • Horizontal topology:
    • Focuses on directly connected upstream and downstream nodes.
    • Usually used to understand the upstream and downstream dependencies of the target entity.

The in-context topology view allows you to switch between perspectives to gain a complete understanding of an entity's context. Both perspectives consist of the following components:

  • Groups
  • Nodes
  • Edges

Components represent different relationships and node types depending on the view.

Vertical topology

The vertical topology perspective shows a complete hierarchical visualization of all related entities for the trigger node. It allows you to view relationships between the nodes, such as runs_on or part_of. You can use vertical topology to understand the underlying infrastructure of the target entity.

Group

In the vertical topology perspective, each group contains entities of the same type, such as hosts and Kubernetes nodes.

Nodes

In the vertical topology, nodes can be categorized into the following types:

  • Trigger node: the node from which you triggered the view. It's highlighted and displayed at the center of the graph.
  • Upstream nodes: entities the trigger node is connected to by a runs_on or a part_of relationship. By default, these entities are displayed above the trigger node.
  • Downstream nodes: entities that are connected to the trigger node by a runs_on or a part_of relationship. By default, these entities are displayed below the trigger node.

Edges

Edges in vertical topology perspective represent different relationship types between nodes, based on the trigger node type. The runs_on relationship is the most commonly displayed type, but other relationship types, such as part_of or is_attached_to, may also appear in this perspective.

Horizontal topology

The horizontal topology perspective focuses on calls relationships between nodes, and showcases one level of relationship in either direction. You can use this perspective to view the upstream and downstream dependencies of the target entity.

Group

In the horizontal topology perspective, entities are divided into logical source and target groups:

  • Source group: entities that call the trigger node (calls relationship), displayed to the left.
  • Target group: entities that the trigger node calls (calls relationship), displayed to the right.

Nodes

In the horizontal topology, nodes can be categorized into the following types:

  • Trigger node: the node from which you triggered the view. It's highlighted and displayed at the center of the graph.
  • Source nodes: entities calling the trigger node, displayed to the left of the trigger node.
  • Target nodes: entities called by the trigger node, displayed to the right of the trigger node.

Edges

All edges shown in the horizontal topology represent the calls relationship type. You can use them to get insights about communication pathways.

Use cases

You can use the topology view to:

  • Understand the entity context and relationship between your services.
  • Identify dependencies between entities in your environment.

Best practice tips

For efficient use of the Smartscape Smartscape in-context topology view:

  • Reference the legend to quickly view a summary of nodes and their types in the current topology.
  • Drill down into any displayed entity directly from the topology perspective to analyze performance metrics, troubleshoot errors, or resolve failures.
  • Use both vertical and horizontal topology perspectives as a combined perspective to gain complete understanding of an entity's context and dependencies between your services.
  • Trigger additional topology perspectives from within the current view to continue exploring related entities and better understand the full scope of dependencies.
  • Use the Recent views section in the left menu to quickly navigate between your most recent investigations.

Related topics

  • Smartscape
  • Smartscape views
Related tags
Application ObservabilitySmartscapeSmartscape