Alert Rules#
An alert rule runs a monitoring query on a schedule and notifies you when the result meets a condition — and again when it resolves. Open Monitoring → Alert Rules.
How it works#
At each evaluation interval, the query runs on the selected connections.
The result is reduced to one value (Last value, Average or Count).
The value is compared with the condition, for example
CPU > 90.Condition met → Firing and a notification. Condition cleared → OK and a resolution notification.
State |
Meaning |
|---|---|
Unknown |
Not evaluated yet |
OK |
Condition not met |
Firing |
Condition met |
No Data |
The query returned nothing |
Error |
Query or evaluation failed — check the rule and the connection |
Create a rule#
Click New Rule, or use Setup alert rule from this widget on a dashboard widget to pre-fill the query.
Basics
Field |
Description |
|---|---|
Name |
Up to 64 characters |
Description |
Optional, up to 200 characters |
Connections |
One or more connections to query |
Evaluation interval |
How often to run, minimum 1 minute |
Query — the same query types as dashboard widgets (Azure Metrics, Log Analytics, Resource Graph, Alerts; AWS CloudWatch Metrics, Logs, Alarms; GCP Monitoring Metrics, Alert Policies).
Condition
Field |
Description |
|---|---|
Evaluation target |
Last value (latest point), Average (over the window) or Count (rows or points) |
Operator |
|
Threshold |
Value to compare (not used by Any Result) |
Evaluation window |
Minutes of data to evaluate |
Any Result fires whenever the query returns at least one result (for example an active provider alert) and resolves when it returns none.
Notifications
Setting |
Description |
|---|---|
In-app |
Notification in Reply CMP (on by default) |
Send to the listed recipients |
|
Webhooks |
Teams, PagerDuty or HTTP channels from Webhooks |
Cooldown |
Minimum time between repeated notifications while firing (default 30 minutes; from none to 24 hours) |
Select Create Alert Rule.
Manage rules#
Enabled switch — pause or resume evaluation.
Evaluate now — run the rule immediately, useful to test it.
Edit / Delete — deletion is permanent and removes the history.
History#
Open Evaluation history on a rule (or select an alert on Home) to see its latest state, last evaluation and the most recent state changes, with values and messages. Refreshing only reloads the data: it does not evaluate the rule or send notifications.
Notification content#
Emails include rule name, state (FIRED / RESOLVED), value, condition, time (UTC) and suggested next steps. Teams receives a message card; other webhooks receive an HTTP POST.
Limits and permissions#
Up to 50 alert rules per tenant by default (see Quotas).
Action |
Permission |
|---|---|
View rules and history |
|
Create, edit, evaluate |
|
Delete |
|
Having trouble? See Troubleshooting → Monitoring.