Creating an alert
Open Alerts from the sidebar and click Create Alert. Give the alert a name and optional description, then configure what it watches, where it applies, and how it notifies your team.What to alert on
Where to apply the alert
Conditions
Available conditions depend on the Watch setting:
Numeric metrics support
> >= < <= = and !=. String metrics support exact, not exact, contains, not contains, and case-insensitive matching.
Channels
Enable any combination of notification channels:Advanced settings
- Cooldown (seconds) sets the minimum time between notifications, from 0 to 86400 seconds (24 hours). Matches during the cooldown are recorded but not notified, including when several results finish at the same moment. The cooldown starts once a notification is delivered; if every enabled channel fails, the next match can still notify.
- Custom Message Template overrides the notification text. Without a template, the notification includes the alert name, outcome, condition summary, and a link to the run or conversation.
Template variables
When the first triggered condition is a Baseline deviation, these are also available:
{{baseline_display_name}}, {{baseline_ulid}}, {{sigma_threshold}}, {{direction}}, {{average_observed}}, {{average_z_score}}, {{flagged_count}}, {{total_count}}, and {{anomaly_fraction}}.
Number formatting in templates
Computed metric values use up to two decimal places by default. To choose a different precision, add:.Nf to a numeric variable, where N is from 0 to 10:
0.9285714285714286, {{actual_value:.3f}} displays 0.929, while {{actual_value:.6f}} displays 0.928571. Formatting uses the original value, rounds halfway values away from zero, and keeps the requested number of decimal places (5 with :.2f becomes 5.00). It only changes the notification text; alert conditions and stored results use the original values.
Formatting applies to individual numeric variables, including actual_value, threshold, and numeric baseline variables. Summary variables such as condition_summary and metric_values are text and retain their default formatting. Unknown variables, unsupported formats, and numeric formats applied to text remain unchanged in the rendered message.
Links in templates
Use{{resource_label}}: {{resource_url}} for templates that handle both uploaded and simulated conversations. Uploaded conversation alerts display Conversation and link to the uploaded conversation result. Simulation alerts display Run and link to the simulation run. Links include the workspace when the result has one.
The existing {{run_url}} and {{run_link}} variables point to the same destination as {{resource_url}}, including for uploaded conversations. If an older custom template contains the literal text Run:, replace that label with {{resource_label}} to let it follow the conversation source automatically.
API access
Use the Alerts API to create and manage alerts programmatically. New integrations should use the canonical/v1/alerts endpoints. The existing /v1/monitors endpoints remain supported for compatibility.