--- title: Anomaly insights description: The reference topic gives additional information for anomaly charts. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/impact/addl-inf-io-anomaly.html release: australia topic_type: reference last_updated: "2026-03-30" reading_time_minutes: 6 keywords: [Anomaly details] breadcrumb: [Instance monitoring and performance metrics, Monitor instance performance, Platform Health, Using Impact, Impact] --- # Anomaly insights The reference topic gives additional information for anomaly charts. ## Additional information for anomaly - In Anomaly charts, the x axis represents time series and the y-axis represents the actual metrics per date range you select. Anomalies are denoted by red color code on the chart. Each red point represents the occurrence of an anomaly in the data. The specific placement of the red mark depend on the criteria or algorithm used to detect anomalies. - In case of node level performance chart \(like semaphore and node memory\), you must select the common grain for x axis \(1 minute roll up\) if you must tally the data between default and anomaly tab. Performance chart is represented at the node level, however, anomalies are aggregated at an instance level. - The anomalous points are selectable for semaphore and Node Memory max metrics in Anomaly chart that will be enabled with node metadata beyond the normal range. You must select **View detail** for the same. This Information will not reflect for non-anomalous points. In case of 10-min grain data, the anomaly is calculated based on 15-min average data point. Therefore, this will list all nodes beyond the range in the last 15 minutes. ## Aggregation level of each metric

Metric Name	Aggregation LevelDefault Chart	Aggregation LevelAnomaly Chart	Aggregation TypeDefault Chart	Aggregation TypeAnomaly Chart
User Transaction Count	Instance	Instance	Sum	Sum
Average Server Response Time	Instance	Instance	Weighted Average	Weighted Average
SQL Response Time	Instance	Instance	Average	Weighted Average
Semaphore Default Mean	Node	Instance	Max	Max
Node Memory Max	Node	Instance	Max	Max
Semaphore Default Queue Depth	Node	Instance	Max	Max
Semaphore API Int In Use	Node	Instance	Max	Max
Semaphore API Int Queue Depth	Node	Instance	Max	Max
Semaphore AMB Send Queue Depth	Node	Instance	Max	Max
Garbage Collection	Instance	Instance	Max	Max
CPU Time	Instance	Instance	Sum	Sum
Threads Running	Instance	Instance	Max	Max
InnoDBrowLock	Instance	Instance	Max	Max
Slow Queries	Instance	Instance	Max	Max

## Roll up logic - **User Transaction Count \| Average Server Response Time \| SQL Response Time** - When selected date range is **less than or equal to 7 days**, metric values are rolled up at the 1-minute level. - When selected date range is **greater than 7 days but less than 30 days**, metric values are rolled up at the 10-minute level. - When selected date range is **greater than 30 days**, metric values are rolled up at the 1-hour level. - Default chart metric values will **not match** with the anomaly chart metric values when data is rolled up at the 10-minute level, because the default chart uses a 10-minute metric value average whereas the anomaly chart uses a 15-minute moving average. - Default chart metric values will **match** with the anomaly chart metric values when aggregation is at the 1-minute level for **User Transaction Count** and **Average Server Response Time**. Values will not match for **SQL Response Time** because the default chart uses **Average** aggregation whereas the anomaly chart uses **Weighted Average**. - Anomaly chart data is available for a **maximum of 28 days** from the current date. - **Other metrics** - When selected date range is **less than or equal to 24 hours**, metric values are rolled up at the 1-minute level. - When selected date range is **greater than 1 day but less than 7 days**, metric values are rolled up at the 5-minute level. - When selected date range is **greater than 7 days but less than 30 days**, metric values are rolled up at the 10-minute level. - When selected date range is **greater than 30 days but less than 60 days**, metric values are rolled up at the 1-hour level. - When selected date range is **greater than 60 days but less than 90 days**, metric values are rolled up at the 2-hour level. - When selected date range is **greater than 90 days but less than 120 days**, metric values are rolled up at the 4-hour level. - When selected date range is **greater than 120 days but less than 150 days**, metric values are rolled up at the 8-hour level. - When selected date range is **greater than 150 days but less than 180 days**, metric values are rolled up at the 12-hour level. - Default chart metric values will not match with anomaly chart metric values for node-level metrics, because the default chart aggregates at the node level whereas the anomaly chart aggregates at the instance level. Note that the aggregation type \(Max\) remains the same across both charts for these metrics. - Anomaly chart data is available for a maximum of 28 days from the current date. **Parent Topic:**[Instance monitoring and performance metrics](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/impact/instance-observer-ovr-metric.md) **Related topics** [Feature availability based on package]() [Auriga Intelligent Alert report]() [Transaction or response metrics]() [Database performance metrics]() [Semaphores performance metrics]() [Event queues performance metrics]() [ECC Queue performance metrics]() [Email performance metrics]() [Scheduler performance metrics]() [Job details performance metrics]() [Node health performance metrics]() [Host health performance metrics]() [Standby replication Lag]() [Pool Replication Lag]() [Chat details performance metrics]() [Cluster details performance metrics]() [Load balancer performance metrics]() [User information metrics]() [Instance Data Replication]()