Getting Started
StackState Self-hosted v5.1.x
Last updated
StackState v5.1
StackState Self-hosted v5.1.x
Last updated
Hi! So, you've just installed StackState and you are ready to get started.
The first step to take is integrating StackState with your IT systems. This can be done by installing one or more .
StackState visualizes components in the Topology Perspective by the layer and domain that they're placed in. These are logical groupings of components. Layers are displayed on the vertical axis. Domains are displayed on the horizontal axis.
A topology consists of components and relations combined with their health state. Because topologies can get very large, StackState automatically groups the components.
The health state of a component is indicated by two colors:
The component color indicates the health state calculated for the component itself.
The outer color indicates there is potential impact from unhealthy components or relations that this component depends upon.
The direction of a relation's arrow indicates dependency. For example, app -> db means: app depends on db. Health propagates in the opposite direction to the arrows. So if the db component turns red, the outer color of the app component will turn red too.
Select a component or a relation to display detailed information about it in the right panel details tab - the tab will be named according to the element type that you selected. For example, Component details when you select a component or Direct relation details when you select a relation that links two components with no hidden components in between. Click SHOW ALL PROPERTIES to open a popup with all details of a component or direct relation.
Both components and relations can have one or multiple telemetry streams. The most common type is a metric stream also known as time series. If you click on a metric stream, you can see the metric stream in a popup.
If you click on a log stream, you can see the log stream in a popup. Again, there are a number of drill-down capabilities available on the left of the popup.
To quickly find the cause of any DEVIATING component, head to the right panel in the StackState UI where you can find the Problems section. It provides an immediate understanding of ongoing problems in your IT environment clustered by their root cause and will show you the probable cause of current problems.
The View summary and Subview summary tabs give an overview of problems based on the components impacted in the current view or subview.
The Component details lists all problems that involve the selected component.
The Direct relation details tab lists all problems that involve the selected direct relation, its source component or its target component.
Problems and issues are displayed in order of the last problem update with the most recently updated problem at the top of the list and the oldest update at the bottom. Within each problem, component-specific issues are displayed in order of the timestamp of the last health state change, from the most recent at the top of the list to the oldest at the bottom.
Note that some components listed in the problem panel might not be visible in the current topology view. You can open a dedicated problem subview to focus on all of the topology elements involved in a specific problem.
The Events Perspective isn't the only place you can find events; you can find the latest events in the Events section in the right panel View summary tab and in the details tabs - Component details and Direct relation details.
After setting up an , you can go to the to explore your IT landscape or visit a specific from your installed StackPacks.
You can change which part of the landscape you are viewing (for example, layers and domains) with the on the left bar, or by .
➡️
➡️ Learn more about , and
The at the bottom of the screen gives you the ability to go to any point in time. All the information that you see (component details, metric streams, etc.) is relative to the topology that existed at the currently selected topology time. Normally, StackState is in live mode, this means that StackState automatically displays the latest state of the stack.
➡️
➡️
To show all events for the selected Topology, select the Events Perspective from the top of the screen. Examples of important events that may appear here are health state changes and changes to the components themselves, like version changes. With , you can configure StackState to react to any events, for example, by automatically creating a ticket or triggering some automation.
➡️
