Alerting
Alert Rules
Create and manage alert rules in Argus.
Creating an Alert Rule
- Navigate to Alerts > Rules
- Click Create Rule
- Configure the rule:
Rule Configuration
| Field | Description | Example |
|---|---|---|
| Name | Descriptive name | "High CPU Alert" |
| Metric | The metric to monitor | cpu_percent |
| Condition | Comparison operator | Greater than |
| Threshold | Trigger value | 90 |
| Duration | How long before triggering | 5 minutes |
| Severity | Alert severity level | Critical |
| Services | Which services to apply to | All / specific |
Rule Types
- Threshold — Triggers when a metric crosses a defined value
- Anomaly — AI-detected deviation from baseline patterns
- Absence — Triggers when a metric stops being reported
Managing Rules
- Enable/Disable — Toggle rules without deleting them
- Edit — Modify any rule configuration
- Clone — Duplicate a rule as a starting point
- Delete — Remove a rule permanently
Best Practices
- Start with critical alerts (CPU, memory, disk full)
- Use appropriate durations to avoid flapping
- Set meaningful severity levels for escalation routing
- Combine with suppression windows for maintenance periods