Displaying metric details for an alert
This task describes how to view an alert's metric information obtained by the metric anomaly detection capability.
About this task
Procedure
- Click the alert that you are interested in from the Alerts page.
-
If there is metric data that is associated with the alert, an extra tab Metrics
anomaly details is present on the preview pane, under the Actions
and Information tabs.
Note: If you want to directly identify which are the alerts that present Metrics anomaly details, you can use the search bar in the Events page by looking up the string Anomaly.
-
Click the Metrics anomaly details to see the metric data, the associated
baseline data for that metric, and any anomalous intervals for the metric. It is possible to view a
maximum of two days of data in this preview chart. By default the chart shows the two days preceding
the
LastOccurrenceof the alert.Complete either of following steps to disable the baseline from the graph:- Click Baseline. If it is already selected by default, then click it again to deselect the Baseline. Deselecting the Baseline removes the baseline in the graph, or
- Select the metrics anomaly checkbox in the Related alerts table to include the metric anomaly in the Metrics anomaly details graph. Clear the selection to remove the metrics anomaly from the Metrics anomaly details graph.
-
Click the drop-down icon to use a calendar and show data for different days in a graph. The
graph shows the value of the metric over time. If the metric strays outside the baseline, then it
becomes anomalous and is marked by a red bar.
Note: By default, metric data is removed from the system 30 days after the data are inserted.
-
You can zoom in the graph in two different ways:
- Click and drag action on the main chart
- Adjusting the slider bar in the spark-line
They are represented as a single value at 15:00, with the averaged value of 10.66.15:00 - 10.6 15:01 - 11.0 15:02 - 10.2 15:03 - 10.7 15:04 - 10.8Note: It is possible for you to see overlapping anomalous red shading in the UI, leading to a darker red.The following example shows how the overlapping occurs and its resolution.
- The first datapoint is seen at 6:23. This datapoint is aggregated and aligned to 6:20, as the
METRIC_SPARK_AGGREGATION_INTERVALis set to its default of 5 minutes. The red anomalous area for this datapoint is then drawn for the time range from 6:20 to 6:35. - Then, in the following interval, the datapoint is seen at 6:32. This datapoint is aggregated and aligned to 6:30. The red anomalous area for this datapoint is drawn for the time range from 6:30 to 6:45. Thus, an overlap is seen in the red anomalous area from 6:30 to 6:35.
In this example, to avoid this overlap, change the value of
METRIC_SPARK_AGGREGATION_INTERVALto 15 minutes.Edit the deployment as follows:
oc edit deployment ${RELEASE}-metric-spark-service-metricsparkserviceWhere
${RELEASE}is the custom resource release name of your deployment.Search
METRIC_SPARK_AGGREGATION_INTERVAL, and change the value to the minimum aggregation interval for your data.