Aternity health event metrics

The Unique Critical Health Events and Unique Major Health Events metrics A measurement or data point that is monitored and analyzed to detect anomalies and generate incidents. track health event counts from Aternity. Aternity tracks the counts of health events by application An entity type representing software applications deployed in the customer environment that are monitored for performance and anomalies., location An entity type representing physical or logical locations in the customer environment where entities are deployed and monitored., and severity once per hour. IQ Ops streams this data and monitors these counts, creating incidents A collection of one or more related triggers. Relationships that cause triggers to be combined into incidents include application, location, operating system, or a trigger by itself. when either the critical or major health event counts for a particular application and location exceed the expected baseline by a significant amount.

Both metrics use baseline-based anomaly An unexpected event or measurement that does not match the expected model. detection One or more indicators that are correlated and may act as a trigger for incident creation or runbook execution.. You can enable or disable these policies as desired, but like other baseline policies, they cannot be edited. For more information about how these incidents are created and how to use runbooks An automated workflow that executes a series of steps or tasks in response to a triggered event, such as the detection of anomalous behavior generating an incident, a lifecycle event, or a manually executed runbook. to investigate them, see Aternity Health Event Incident Automation.