Alert Rules
Alert rules monitor your infrastructure and notify you when defined conditions are met. Configure thresholds for costs, resource state changes, and sync health.
How Alerts Work
Each alert rule defines a condition to watch and a notification channel to use when that condition is triggered. Rules are evaluated on an ongoing basis as resources are synced and cost data is ingested.
Alert Types
Cost Threshold Alerts
Trigger when spend exceeds a configured amount over a given period. Monitor daily, weekly, or monthly costs per provider or project.
- Daily spend β alert if AWS costs exceed $200/day
- Monthly budget β alert if total cloud spend exceeds $10,000/month
- Per-service β alert if RDS spend jumps 50% week-over-week
Resource Change Alerts
Trigger when resources are created, modified, or deleted. Useful for detecting unexpected infrastructure changes.
- New EC2 instance launched outside of auto-scaling groups
- S3 bucket policy changed to public
- DNS record modified or deleted
Sync Health Alerts
Trigger when a provider sync fails, stalls, or returns inconsistent data. Helps catch credential expiration and API quota issues before they impact monitoring.
Configuring Alert Rules
- Navigate to Alerts in the dashboard navigation
- Click New Alert Rule
- Choose the alert type and configure the condition
- Select notification channels β email is always available; Slack and webhook require configuration (see Notification Channels)
- Set a cooldown period to avoid alert storms (default: 15 minutes)
Managing Alerts
The alerts dashboard shows all triggered alerts with severity, status (active/acknowledged/resolved), and the resource or condition that caused them. Use bulk actions to acknowledge or resolve multiple alerts at once.