Alert Types
| Alert | Trigger |
|---|---|
| High CPU | CPU usage > threshold |
| High Memory | Memory usage > threshold |
| High Disk | Disk usage > threshold |
| Health Check Down | Endpoint unreachable |
| Container Stopped | Docker container exits |
Setting Up Telegram
Create Bot
Open @BotFather in Telegram
Send
/newbot and follow instructions
Copy the API tokenGet Chat ID
Start a chat with your new bot
Send any message
Visit:
https://api.telegram.org/bot<TOKEN>/getUpdates
Find your chat_id in the responseConfiguring Thresholds
In Settings → Alerts:| Metric | Default | Recommended |
|---|---|---|
| CPU | 80% | 80-90% |
| Memory | 85% | 80-90% |
| Disk | 90% | 85-95% |
Alert Delay
Set how long a condition must persist before alerting:- Instant: Alert immediately
- 1 minute: Must stay high for 1 min
- 5 minutes: Must stay high for 5 min
Alert History
View past alerts in Alerts tab:- Timestamp
- Type
- Severity
- Resolution status
Muting Alerts
During maintenance:- Go to the server or health check
- Click “Mute”
- Choose duration
- Alerts pause until unmute
Alert Rules (PRO)
PRO users can create custom rules:Quiet Hours
Coming soon: Disable alerts during specified hours.Troubleshooting
Not receiving Telegram alerts
Not receiving Telegram alerts
- Verify bot token is correct
- Ensure you’ve sent a message to the bot first
- Check chat_id matches your chat
- Try “Send Test” button
Too many alerts
Too many alerts
- Increase thresholds (e.g., CPU 80% → 90%)
- Add alert delay (5 minutes)
- Use mute during known high-usage periods
Alert not resolving
Alert not resolving
Alerts auto-resolve when condition clears. If stuck:
- Check current metric values
- Manually clear in Alert History