Alerts
Get notified when something goes wrong with your application.
Alert Types
Performance Alerts
- Method response time exceeds threshold
- Error rate exceeds threshold
- Throughput drops below threshold
System Alerts
- CPU usage exceeds threshold
- Memory usage exceeds threshold
- Event loop lag exceeds threshold
Error Alerts
- New error type detected
- Error count exceeds threshold
- Specific error pattern matches
Creating Alerts
- Navigate to Site Settings > Alerts
- Click "Create Alert"
- Configure the alert:
Name: High Response Time
Condition: avg(method.responseTime) > 1000ms
For: 5 minutes
Severity: warning
Alert Configuration
Conditions
Define when the alert triggers:
| Metric | Operators | Example |
|---|---|---|
method.responseTime | greater, less, equals | greater than 1000ms |
method.errorRate | greater, less, equals | greater than 5% |
system.cpuUsage | greater, less, equals | greater than 80% |
system.memoryUsage | greater, less, equals | greater than 90% |
error.count | greater, less, equals | greater than 100 |
Duration
How long the condition must be true:
- Instant - Alert immediately
- 1 minute - Sustained for 1 minute
- 5 minutes - Sustained for 5 minutes
- 15 minutes - Sustained for 15 minutes
Severity
- Info - Informational, no action needed
- Warning - Should investigate
- Critical - Requires immediate attention
Notification Channels
Email
Default notification method. Alerts sent to:
- Account owner
- Team members (configurable)
Email notifications include:
- Alert name and severity
- Current value vs threshold
- Direct link to affected resource
- Quick investigation steps
Alert Examples
Slow Method Alert
Name: Slow API Methods
Condition: p95(method.responseTime) > 2000ms
For: 5 minutes
Severity: warning
Filter: methodName matches "api.*"
Error Spike Alert
Name: Error Rate Spike
Condition: errorRate > 5%
For: 1 minute
Severity: critical
Memory Alert
Name: High Memory Usage
Condition: system.memoryUsage > 85%
For: 10 minutes
Severity: warning
New Error Alert
Name: New Error Type
Condition: newErrorType = true
Severity: warning
Managing Alerts
Alert States
- OK - Condition not met
- Pending - Condition met, waiting for duration
- Firing - Alert active, notifications sent
- Resolved - Was firing, now OK
Silencing Alerts
Temporarily disable alerts during maintenance:
- Go to Alerts
- Click "Silence"
- Set duration (1h, 4h, 24h, custom)
- Add reason (optional)
Alert History
View past alerts:
- When it fired
- Duration
- Resolution
- Related metrics
Best Practices
1. Start Conservative
Begin with loose thresholds, tighten over time:
# Start here
Condition: responseTime > 5000ms
# Tighten after baseline
Condition: responseTime > 2000ms
2. Use Duration
Avoid alert fatigue with duration requirements:
# Bad: Alerts on every spike
For: instant
# Better: Sustained issues only
For: 5 minutes
3. Set Appropriate Severity
- Info: Awareness, no action
- Warning: Investigate when convenient
- Critical: Wake someone up
4. Group Related Alerts
Consolidate similar alerts to reduce noise:
- Group by service or feature area
- Use composite conditions when possible
Next Steps
- Error Tracking - Configure error capture
- System Metrics - Monitor system health
- Troubleshooting - Common issues