Creating a Health Check
- Go to Health Checks in the dashboard
- Click Add
- Configure:
| Field | Description |
|---|---|
| Name | Display name |
| URL | Full URL to monitor |
| Method | GET, POST, HEAD |
| Interval | Check frequency (seconds) |
| Timeout | Max wait time (seconds) |
- Click Create
How Checks Work
Every interval, Hub:- Sends HTTP request to the URL
- Records response time and status
- Marks UP if 2xx status code
- Marks DOWN if timeout or non-2xx
- Sends alert on status change
Expected Status Codes
By default, any 2xx (200-299) is considered healthy. To accept only specific codes:200- Only 200 is OK200,201,204- Accept these specific codes
Retry Logic
Before alerting, Hub retries failed checks:| Setting | Default |
|---|---|
| Retries | 3 |
| Retry interval | 10s |
| Confirmation delay | 30s |
Alerts
Configure where to send alerts:- Go to Settings → Notifications
- Set up Telegram or email
- New health check alerts go to configured channels
Viewing History
Click any health check to see:- Uptime percentage (24h, 7d, 30d)
- Response time graph
- Recent checks (last 100)
- Incident history
Limits
| Plan | Health Checks |
|---|---|
| Personal | 10 |
| PRO | Unlimited |
Internal vs External URLs
Hub can monitor:- External URLs: Public websites, APIs
- Internal URLs: Services on your network (localhost, private IPs)
Troubleshooting
All checks show DOWN
All checks show DOWN
- Check Hub has internet access
- Verify DNS resolution:
- Check firewall allows outbound HTTPS
Intermittent false alerts
Intermittent false alerts
Increase retry count or confirmation delay in check settings.
Response times too high
Response times too high
Hub measures from server location. High latency is normal for geographically distant services.