The Anomalies score represents how abnormal the behavior of the object is, based on its historical metrics data.

vRealize Operations Manager calculates dynamic thresholds for each metric that is collected for an object. vRealize Operations Manager also analyses the number of metrics that are violating their dynamic thresholds to determine trends and normal levels of threshold violations. Based on these trends, the Anomalies score is calculated using the total number of threshold violations for all metrics for the selected object and its child objects.

A low Anomalies score indicates that an object is behaving in accordance with its established historical parameters. Most or all of the object metrics, especially its KPIs, are within their thresholds. Because changes in behavior often indicate developing problems, if the metrics of an object go outside the calculated thresholds, the anomalies score for the object grows. As more metrics breach the thresholds, anomalies continue to increase. Violations by KPI metrics increase the Anomalies score more than violations by non-KPI metrics. A high number of anomalies usually indicates a problem or at least a situation that requires your attention.

Anomalies and Workload differ in that workload is computing an absolute measurement of how hard an object is working while anomalies is computing how different from normal the object is behaving. Both Workload and Anomalies are useful when searching for and troubleshooting performance problems.

The Anomalies score ranges between 0 (good) and 100 (bad). The badge changes its color based on the badge score thresholds that are set by the vRealize Operations Manager administrator.

Table 1. Object Anomalies States
Badge Icon Description User Action
Icon for normal score of Anomalies. The Anomalies score is normal. No attention required.
Icon for medium level of Anomalies. The Anomalies score exceeds the normal range.
Icon for partially high level of anomalies. The Anomalies score is very high.
Icon for excessive level of anomalies. Most of the metrics are beyond their thresholds. This object might not be working properly or might stop working soon.
Icon for unknown level of anomalies. No data is available or the object is offline.

A vRealize Operations Manager administrator can change the badge score thresholds. For example, a green Anomalies badge can indicate a score below 60 instead of 50, as set be default.