View resolved alerts

Review alerts that are no longer active, measure resolution performance, and investigate recurring issues.

The Resolved alerts tab enables you to review the alerts that are no longer active. It lists the alert events that resolve during the selected time period. The default period is Last 8 days, and you can also select a custom period.

Note: In the Controlled Availability release stage, Splunk products may have limitations on customer access, features, maturity, and regional availability. For additional information on Controlled Availability please contact your Splunk representative.

Why resolved alerts matter

Active alerts display what needs attention now. Resolved alerts display what happened, how long it lasted, and whether response patterns are improving.

Review resolved alerts to:

  • Reconstruct incident history: See which detector or SLO fired, when the alert cleared, and which signal properties were involved.

  • Measure response performance: Track resolved alert counts, mean time to resolution (MTTR), and the percentage of alerts resolved within 30 minutes.

  • Compare services and teams: Filter and group by dimensions such as service, team, detector, and severity.

  • Identify noisy or flapping detectors: Look for repeated short-duration alerts that might indicate thresholds or detector settings need tuning.

  • Support operational reviews: Use resolved-alert history for post-incident review, reliability analysis, and detector optimization.

Supported regions

This feature is currently available in the following realms:

  • us0

  • us1

  • au0

  • jp0

  • eu0

  • eu1

  • eu2

How to access Resolved alerts

Go to Alerting > Alerts and select the Resolved alerts tab.

Page details

The Resolved alerts page provides the options to filter and view the resolved alerts.

Resolved alert tab

Filters and search

Use the filter options to narrow the list of resolved alerts. You can filter by the time range and inventory filters such as duration, severity, team, detector, metric, and log type. APM filters include service or endpoint and business transaction.

You can search resolved alerts by rule name, which includes the detector, display name, and detect label.

You can group resolved alerts by supported dimensions, with up to two group-by levels.

Summary cards

The summary cards display the following metrics based on the selected time range and applied filters:

Card Definition
Resolved / total alerts Resolved alerts divided by resolved alerts and currently active alerts whose last state update falls in the selected time range.
Resolved within 30 mins Resolved alerts with duration under 30 minutes divided by all resolved alerts.
Mean time to resolution Average duration of the resolved alerts.

The trend in each card compares the current range with the immediately previous equal-length period.

Resolved alert list

The table lists individual resolved alerts, with the default sort displaying the newest cleared alerts first.

Column Description
Rule name The detector rule that triggered the alert. You cannot configure this column.
Signal properties Key properties that identify the signal involved in the alert.
Detector or SLO The detector or Service Level Objectives (SLO) associated with the alert. Links the respective detector and SLO.
Tags Tags associated with the alert or detector.
Duration How long the alert was active. This sortable column uses the same duration format as MTTR.
Cleared When the alert resolved. This column is sortable.
Mute status Whether the alert was muted when it resolved. A dash means that the alert was not muted.
Triggered When the alert triggered. This optional column is sortable.
Teams Team associated with the alert.
Resolution type

Resolution context of the alerts. Types include:

  • Cleared: The alert condition returned to normal, or the detector’s clear condition was met.

  • Stopped: The alert ended because its detector became inactive, such as when someone edited or deleted the detector.

  • Manually Resolved: A user marked the alert as resolved in the UI or through the API.

  • Auto cleared: Splunk Observability Cloud automatically cleared the alert after the detector’s configured timeout elapsed because it was unable to evaluate the signal, for example, because the metric stopped reporting.

Resolved alert details

Select an alert from the list of resolved alerts to view its details. A resolved alert provides the same details as an active alert. See View alert details.

Resolved alert details