Product Guides
Alerts
Use Alerts to understand rule evaluation, SLO status, and the response workflow for active conditions.
Overview
Use Alerts to respond to configured rules. Alerts tell you which condition crossed a threshold, whether it is still firing, and which evidence should be checked before acknowledging or tuning it.
Use this page after you know the approximate symptom and need to decide which evidence should come next. Keep the service, environment, and time range consistent as you move from summary pages to request-level detail.
How to read this page
Separate policy-driven Alerts from detected Issues: alerts represent configured rules. Use status, evaluation window, and affected target before escalating. Open the related service, trace, log, or release context before changing alert state.
- Rule target
- A useful alert points to a service, route, SLO, or operational target.
- State
- Firing, recovered, muted, and healthy states determine whether the task is response or cleanup.
- Evaluation window
- The window explains whether the alert is a sustained problem or a short spike.
Investigation workflow
Use this sequence when you need to move from a broad symptom to evidence you can share with another teammate.
- 1
Open the firing alert and confirm target, threshold, and evaluation window.
- 2
Open the related service, traces, logs, and releases for that exact window.
- 3
Acknowledge or tune the rule only after the evidence explains the alert state.
Interpretation note
Do not tune a noisy alert while the service is still unhealthy. Do not treat recovered as solved until you know why it recovered. Do not create alerts for symptoms nobody will act on.