On this page

A monitor checks one service on a schedule and records whether it is up.

Shared settings

Every monitor has these settings:

  • Interval: how often it's checked, in seconds.
  • Timeout: how long a check may take before it counts as down.
  • Retries and retry interval: how many failed checks in a row are retried, and how far apart, before the service is marked down. While retrying, the service shows as Pending and no alert is sent.
  • Invert: treat success as down and failure as up, for things that should not be reachable.
  • Tags: labels for grouping and finding services.
  • Alert channels: where alerts go (see Alerts).

Uptime and statistics

Each service's page shows its uptime over the last 24 hours, 7 days and 30 days, its average response time over 24 hours and 7 days, the number of checks in 30 days, and how long it has been in its current status. The dashboard shows how many services are up, down or failing, and recent incidents.

Uptime is the share of up results among up and down ones; see how uptime is calculated. Use tags to group services and find them quickly.

Check types

TypeUp when
HTTP(S)The response status matches and every body assertion passes
PingThe host answers an ICMP echo
TCP portA TCP connection to the port succeeds
DNSThe name resolves, and the answers include every expected value
TLS certificateThe certificate is valid for longer than the warning period
Docker containerThe container is running and not reported unhealthy
DatabasePostgreSQL, MySQL/MariaDB or Redis accepts a connection and answers a trivial query
PushThe service sent a heartbeat within the interval