Alerting
Configure alert rules and notification channels for your infrastructure.
SMLL lets you define alert rules that fire when your infrastructure metrics cross thresholds. Alerts are sent to notification channels you configure.
Default alerts
Every VPC comes with 7 pre-configured alert rules:
| Alert | Metric | Condition | Severity |
|---|---|---|---|
| OOM Killed Detection | Container OOM kills | > 0 for 60s | Critical |
| Container Restart Loop | Restart count | > 5 in 5min | Warning |
| High CPU Usage | CPU usage | > 90% for 5min | Warning |
| High Memory Usage | Memory usage | > 90% for 5min | Warning |
| Disk Usage Critical | Disk usage | > 80% for 5min | Critical |
| DB Replication Lag | Replication lag | > 30s for 2min | Warning |
| Connection Pool Exhaustion | Pool usage | > 80% for 5min | Warning |
Default alerts can be customized or disabled.
Creating custom alerts
- Go to your VPC's Alerting section
- Click Create Alert
- Configure:
- Metric — what to monitor
- Condition — above, below, or equals
- Threshold — the numeric value to compare against
- Duration — how long the condition must hold before firing (in seconds)
- Severity — info, warning, or critical
- Channels — where to send notifications
Available metrics
| Metric | Description |
|---|---|
cpu_usage_percent | CPU usage percentage |
memory_usage_percent | Memory usage percentage |
disk_usage_percent | Disk usage percentage |
container_oom_killed | OOM kill events |
container_restart_count | Container restart count |
db_replication_lag | Database replication lag (seconds) |
db_connections_percent | Connection pool usage percentage |
network_egress_bytes | Network egress bytes |
http_error_rate | HTTP error rate |
http_latency_p99 | HTTP p99 latency |
Notification channels
Send alerts to any email address. Configure in the Channels tab:
- Click Add Channel
- Choose Email
- Enter the email address
Webhook
Send alerts as HTTP POST requests to any URL:
- Click Add Channel
- Choose Webhook
- Enter the URL
- Optionally set a signing secret
Webhook payloads are signed with HMAC-SHA256. The signature is sent in the X-SMLL-Signature header, so you can verify that alerts are genuine.
Testing channels
After creating a channel, click Test to send a sample notification and verify it's working.
Alert history
The alerting page shows a log of all fired alerts, including:
- When the alert fired and resolved
- Which metric and threshold triggered it
- The severity level
- Which channels were notified