Alerts#

Alerts turn Monitor from a passive dashboard into an active notification system. An alert rule watches a metric or query and fires when the result crosses a threshold you define. Fired alerts are delivered to the contact channels configured on the workspace.

Creating an Alert Rule#

Alert rules are created from Monitor → Alerting → Alert rules → New rule. A rule consists of:

1. Name — a short descriptive label that appears in notifications
2. Query — the metric expression to evaluate
3. Condition — the threshold and comparator that determines when the alert fires (e.g., “p95 API latency is above 500 ms for 5 minutes”)
4. Evaluation interval — how often the condition is checked
5. For duration — how long the condition must be true before the alert transitions to firing (prevents flapping on brief spikes)
6. Severity label — informational tag used for routing and display (e.g., warning, critical)

Notification Channels#

Monitor delivers alert notifications over email. When an alert fires, an email is sent to every address configured on the workspace’s alerting contact list. The email contains the alert name, the current metric value, the threshold that was crossed, a link back to the relevant dashboard, and the severity label.

Alert States#

An alert rule moves between these states:

• Normal — the condition is not satisfied
• Pending — the condition is satisfied but has not yet been true for the full “for duration” window
• Firing — the condition has been satisfied for the full window; notifications have been sent
• Resolved — the condition is no longer satisfied; a resolution notification is sent

Silencing#

If you need to suppress notifications temporarily — for example, during planned maintenance — you can create a silence that matches one or more alert rules for a specified time window. Silenced alerts continue to evaluate but do not generate notifications.