Uptime Monitoring
Automatically monitor your services and get alerted when something goes wrong. Optionally create incidents automatically when monitors fail.
Creating a Monitor
Navigate to Monitors and click Add Monitor. Configure the following:
- Name - A descriptive name for the monitor
- Type - The protocol to use for checking (HTTP, TCP, ICMP, DNS, SSL)
- Target - The URL, hostname, or IP address to monitor
- Check Interval - How often to run checks (1, 5, 10, 15, 30, or 60 minutes)
- Timeout - How long to wait before considering a check failed (1-60 seconds)
- Linked Component - Optionally link to a component for status updates
Monitor Types
Monitor web endpoints. Checks that the URL returns an expected status code (default: 200). Optionally verify that the response contains a specific keyword.
Configuration options:
- Expected status code (100-599)
- Expected keyword in response body
Check if a TCP port is open and accepting connections. Useful for databases, mail servers, and other non-HTTP services.
Configuration options:
- Port number (1-65535)
Send ICMP ping requests to check if a host is reachable. Good for monitoring network connectivity and server availability.
Verify that a domain resolves correctly. Optionally check that it resolves to a specific IP address.
Configuration options:
- Expected IP address (optional)
Monitor SSL certificate validity and expiration. Get alerted before your certificates expire.
Configuration options:
- Expiry threshold in days (default: 14 days)
Automatic Incident Creation
Enable Auto-create incident to automatically create an incident when a monitor fails. This is useful for:
- Immediately notifying subscribers when an outage is detected
- Updating component status without manual intervention
- Creating an audit trail of all outages
You can customise the incident title using a template. Use {name} as a placeholder for the monitor name.
Example templates:
{name} is down→ "API Server is down"Outage detected: {name}→ "Outage detected: API Server"
Check Intervals
Choose how frequently your monitors run checks:
| Interval | Best For |
|---|---|
| 1 minute | Critical services requiring immediate detection |
| 5 minutes | Important production services (recommended default) |
| 10-15 minutes | Standard services, internal tools |
| 30-60 minutes | Low-priority services, SSL certificate checks |
Uptime Statistics
Each monitor tracks detailed statistics:
- Uptime percentage - Calculated over 24h, 7d, 30d, and 90d periods
- Response time - Average response time with historical graphs
- Check history - Last 100 check results with timestamps
- Incident history - All incidents created by this monitor
Uptime history is displayed on your public status page as a 90-day graph for each component linked to a monitor.
Pausing Monitors
You can pause a monitor to temporarily stop checks without deleting it. This is useful during planned maintenance or when you know a service will be unavailable.
Paused monitors display a yellow "Paused" badge and don't affect uptime calculations while paused.