
What it is
An alert is created when a built-in trigger condition is met. It carries a severity (low, medium, high, critical), a trigger type, and a link to the affected resource. Alerts stay open until a human acknowledges or resolves them. Duplicate alerts within a suppression window collapse into a single entry with an increasing occurrence count.
When to use it
- Get paged when a certificate tagged
prodis within 7 days of expiry. - Route renewal failures to the platform team’s Slack channel.
- Escalate an unacknowledged alert to a secondary on-call if nobody acts within 15 minutes.
- Suppress low-severity alerts for certificates in a planned-decommission workflow.
- Raise an alert any time a Certificate Transparency mis-issuance is detected.
Built-in triggers
| Trigger | Default threshold | Default severity |
|---|---|---|
certificate.expiring | 30 / 14 / 7 / 1 days | low to critical |
certificate.expired | On expiry | critical |
renewal.failed | On failure | high |
deployment.failed | On failure | high |
policy.violation | On violation | medium to high |
anomaly.detected | Scored automatically | low to critical |
ct.misissuance | New entry outside your CA allow-list | high |
agent.offline | No heartbeat for 5 minutes | medium |
ca.certificate.expiring | 180 / 90 days | critical |
crl.stale | NextUpdate minus 24 hours | high |
Set it up
Choose a trigger
Select one of the built-in triggers from the dropdown. The trigger determines which alerts the rule evaluates.
Add conditions
Build a condition tree to narrow the rule — for example, severity equals
critical and certificate tags contains prod. Use All of (AND) or Any of (OR) wrappers.Set the notification channel
Pick one or more channels configured under Settings > Notifications. Optionally attach a custom message template.
What you’ll see
Active alerts appear on Monitoring > Alerts with severity badges. Click Acknowledge to claim ownership or Resolve to close. Each alert row expands to show the matched condition and the channels that were notified.Alert states
| Status | Meaning |
|---|---|
open | Fired, no action yet |
acknowledged | Someone owns it |
resolved | Condition cleared or manually closed |
suppressed | Collapsed inside the suppression window |
Tips
- Assign escalation policies to rules so overdue alerts automatically re-notify a secondary on-call.
- Any Workflow step can raise an alert with a custom type, letting you create organization-specific triggers beyond the built-in set.
- Deleting an alert is permanent and removes it from history. Use Resolve for real incidents so the audit trail is preserved.
Related
Alert rules
Build condition trees with a visual editor and a live rule tester.
Notifications
Channels, templates, and escalation policies.
Audit logs
Every alert acknowledgement and resolution is captured.
Analytics
Alert trends and anomaly detections over time.