The Autonomous Anomaly Detector (AAD) looks for deviations in metric streams. It annotates the metric streams with anomalies and generates corresponding anomaly events. The anomaly events can be viewed in the event perspective and also serve as an input for health checks. Health checks can react to anomaly events and set the component health state to the
DEVIATING (orange). Without a health check responding to generated anomaly events, a component would not change its health state based on found anomalies.
Anomaly health checks are either automatically placed on components by the StackPacks or can be manually created. After manual creation, you can of course automate the creation of such checks, like any other checks, using the component templates.
Follow the instructions below to add an anomaly health check to a component.
In the StackState UI Topology Perspective, select the component that you want to add an anomaly health check to.
Click on the the + ADD button under the Health section in the component details pane on the right of the screen.
Select the Check function Autonomous metric stream anomaly detection.
Add the following arguments:
anomalyDirection - the direction the found anomaly must have for the check to go to a
DEVIATING (orange) health state. You can choose from:
Rise - to detect peaks, for example in a latency metric stream.
Drop - to detect sudden drops, for example in the number of threads free in a thread pool.
Any - to detect both rises and drops, for example when detecting both hot and cold deviations in data center temperature.
metricStream - a metric stream that is available on the component to detect the anomalies on.
event - leave unchanged. This is an instance of an anomaly event that the check will react to.
Click CREATE to activate the check.
When enabled, the autonomous metric stream anomaly detection check function will behave as follows:
Autonomous metric stream anomaly detection check will remain in an
UNKNOWN (gray) health state unless an anomaly is found.
When an anomaly is found, the check will go to a
DEVIATING (orange) health state.
HIGH severity anomalies change the health status of the check to
It can take between 5 to 25 minutes before an anomaly is detected, depending on the granularity of the metric stream and the size of the anomaly. Only anomalies lasting for several minutes are considered to be
HIGH severity anomalies.
Once an anomaly is found, the
DEVIATING health state will remain for at least 8 minutes.
Optionally, advanced users of StackState can create their own custom anomaly check functions. More information on custom anomaly check functions, parameters and available fields can be found in the anomaly check functions developer guide. Note that you have to adjust an identifier of a custom anomaly check function such that it is recognized by the Autonomous Anomaly Detector. If you would you like to know more, contact StackState support.