Review detected anomalies

Triage unusual metric behavior, confirm impact, and close findings without mistaking detection for cause.

Open Explore → Anomalies to review statistically unusual metric behavior. Findings can be open, acknowledged, or resolved.

Triage a finding

Confirm the project, environment, metric, service, and time window.
Compare the observed value with the expected band and surrounding baseline.
Check related service health, traces, logs, Issues, releases, and alerts.
Determine whether customers were affected or whether the change was expected.
Acknowledge when someone owns the investigation; Resolve when the finding no longer needs action.

A detection says the series departed from its learned behavior. It does not establish a root cause and may reflect a deployment, traffic shift, seasonality, instrumentation change, or real failure.

Avoid noisy conclusions

Use a time window that includes the baseline and the deviation.
Check for changed metric labels or cardinality before blaming application behavior.
Compare the anomaly with a release or feature rollout.
Do not delete a finding merely because it is inconvenient; resolve it with the reason recorded in the team’s incident workflow.

If no findings appear, confirm metrics have enough consistent history for detection and that the selected status filter includes open findings.