StackState Self-hosted v5.0.x
StackState reports a health state for elements in the topology based on the health state reported by checks and monitors attached to the element. Checks and monitors have a similar function in StackState, but work very differently under the hood.
This page describes what StackState checks are and how they work.
Checks are a feature of StackState that provides health state information bound to the topology elements. StackState calculates the health state of a check based on the telemetry and log streams attached to an element and a set of customizable validation rules expressed in the form of Check Functions. It also possible to use anomaly events generated by the Autonomous Anomaly Detector (AAD) for anomaly health checks.
Unlike monitors, checks are defined on a per-topology element basis and rely on the telemetry streams present on the topology element to which they are attached. In this sense, each instance of a check is directly connected to the specific topology element for which it will produce health state information. This means that multiple instances of checks need to be created to serve the whole topology - one for each topology element that is to be covered by monitoring.
Check results are displayed in the StackState UI right panel Selection details tab under Health when information about a topology element is displayed:
Check result panel
Each check result displays among other information:
- A health state produced by this check, along with the time it was updated
- A metric chart of the data that resulted in this health state being generated
- The check function configuration utilized by this check
The context menu of each check result (...) contains several useful shortcuts:
- Edit - change the configuration of a specific check.
- Delete - remove the Check associated with this result panel.
Note that both of the options above are disabled when in time-travelling mode - topology elements cannot be modified in the past.