Drill Into a Suspected Cause

Click More Details for the Suspected Cause to review:

  • Simplified timeline
  • Metrics graphed over time

Two types of graphed metrics display:

  • Top Deviating Metrics for the Business Transaction
  • Suspected Cause Metrics

Examine Top Deviating Metrics for the Business Transaction

Deviating Business Transaction metrics can indicate why an anomaly was important enough to surface. (The system does not surface anomalies for every transitory or slight deviation in metrics. Such anomalies would be of dubious value, since their customer impact is minimal. For the same reason, anomalies are surfaced for Business Transactions which have a CPM of under 20.)

Each deviating metric is shown as a thin blue line (the metric's value) against a wide gray band (the metric's Expected Range).

You can:

  • Scroll along the graph to compare a metric’s value with its Expected Range at any time point.
  • Hover over a time point to view the metric's value and Expected Range in numerical form.
Note: Hovering to view values in numerical form is essential when the Expected Range is so much smaller than the deviating metric values that the gray band “disappears” into the X axis.

In this example:

  • The deviating metric's (errors per minutes) spike remained elevated for about 50 minutes (7:45 AM - 8:35 AM), then subsided back into Expected Range.
  • Six minutes after the metric returned to its Expected Range, the Severity Level changed from Critical to Warning, and twelve minutes after that, to Normal.

Hovering over time points display the period of deviation: the Errors per Minutes was around 16 and above, while its Expected Range was from 0 to 13.5. With a key metric elevated by this large amount, it made sense for the system to surface this anomaly.

Note: Because Top Deviating Metrics are at the Business Transaction level, they are the same for all Suspected Causes.

The Top Deviating Metrics timeline also displays the evaluation period of an anomaly in the grey color. The evaluation time period is the duration in which the data is analyzed to detect the anomaly. This timeline helps you to precisely identify the time when the issue started. The following images displays the evaluation period:

Examine Suspected Cause Metrics

You view, scroll through, and hover over Suspected Cause Metrics similar to Top Deviating Metrics.

Note: Top Deviating Metrics describe the Business Transaction, while Suspected Cause Metrics describe tiers or nodes further down in the entity tree. This means that if you have ART as a Top Deviating Metric and as a Suspected Cause Metric, those are two different metrics. Likewise, EPM as a Top Deviating Metric and as a Suspected Cause Metric are also two different metrics.While the Suspected Cause Metric likely contributes to the way the Top Deviating Metric behaves, the values of the two metrics will differ.

For example, the suspected cause metric is displayed for frontend15novauto. The expected range of the MemoryUsed% metric is 0 to 4.5%, but the value is 8%, which is above the expected range. This is the root cause of the anomaly.

Suspected Cause Metric