Topology Perspective
See the real time state of your IT landscape
Last updated
See the real time state of your IT landscape
Last updated
This page describes StackState version 4.1.
The StackState 4.1 version range is End of Life (EOL) and no longer supported. We encourage customers still running the 4.1 version range to upgrade to a more recent release.
The Topology Perspective displays the components in your IT landscape and their relationships.
The Topology Perspective shows components and relations in the selected view. Components that have one or more checks configured will have a calculated health state.
When a component is selected by clicking on it, the Component Details pane is shown on the right hand side. This panel displays detailed information of the component:
metadata such as the component's name, type and labels
The View Filters pane on the left side of the screen in any View allows you to filter the topology components displayed. Read more about Topology Filters
The topology can also be navigated interactively. Hover over any component to bring up the component navigation menu. The available options allow tyou to change your view respective to the selected component.
Hover over any component to bring up the component navigation menu. Select Quick actions to expand the topology selection in one of the following ways:
Show all dependencies -- shows all dependencies for selected component
Show dependencies, 1 level, both directions -- limits displayed dependencies to one level from selected component
Show Root Cause -- if the selected component is in a non-clear state, adds the root cause tree
Show Root Cause only -- limits displayed components to the root cause elements
You can extend this list with component actions that are pre-defined in a StackPack or configure your own actions.
Hover over any component to bring up the component navigation menu. Select Dependencies to isolate the selected component (show only that component) and expand the topology selection in one of the following ways:
Direction -- choose between Both, Up, and Down
Depth -- choose between All, 1 level, and 2 levels
If you require more flexibility in selecting topology, check out the StackState Query Language (STQL).
Hover over any component to bring up the component navigation menu. Select Root Cause Analysis to isolate the selected non clear (e.g. deviating or critical) and expand the topology selection in one of the following ways:
Root cause only -- only show the probable causing component
Full root cause tree -- show the entire root cause tree
You can also show root cause outside the current view
Locate a specific component in the view by typing the first few letters of it's name in the Topology Perspective. Alternatively, you can select the Component finder icon magnifying glass in the bottom right corner of the topology visualizer.
There are zoom buttons located in the bottom right corner of the topology visualizer. The plus button zooms in on the topology, the minus button zooms out. In between both buttons is the fit to screen button which zooms out so the complete topology becomes visible.
If one or more components have a critical state, StackState will show the related components and their states as a Problem Cluster in the View Overview pane.
If there are components with telemetry streams and health checks in your view, the Topology Perspective will calculate a health state and propagate this state throughout the graph. The propagated health state will help you to see the risk of affecting other components.
It is possible that your view can contain components that have a deviating propagated health state caused by a component that is outside your view. The Topology Perspective allows you to configure whether to show a root cause even when it is outside of the currently displayed view:
Don't show root cause -- do not show the root cause
Show root cause only -- only show the root cause component
Show full root cause tree -- show the entire root cause tree
The components in the topology visualization can also be shown in a list instead of a graph:
