Success Criteria
Configure what counts as a passing check for each endpoint type.
Each check evaluates one or more conditions to determine whether an endpoint is healthy. If all conditions pass, the check is recorded as a success. If any condition fails, the check is a failure and the failure counter increments toward the alert threshold.
HTTP / HTTPS
- Status code — default: any 2xx or 3xx response is a pass. You can require an exact code (e.g., 200) or a range (e.g., 200–299).
- Response time — optionally fail if the response takes longer than N milliseconds.
- Body contains — fail if the response body does not contain a specific string (e.g.,
"status":"ok"). - Body does not contain — fail if the response body contains an error string (e.g.,
"error"). - TLS certificate — for HTTPS, optionally alert when the certificate expires within N days.
TCP
A TCP check succeeds when a connection is established to the host and port within the timeout period. There are no additional conditions to configure — connection established equals success.
DNS
- Query type — A, AAAA, CNAME, MX, TXT, NS, or SOA.
- Expected answer — optionally specify an IP or value the DNS response must include.
ICMP (Ping)
A ping check sends ICMP echo requests and measures round-trip time. The check succeeds when the host responds. You can optionally set a maximum response time threshold.
SSH
- Connection — authentication (password or private key) must succeed.
- Command output — optionally run a shell command and check that the output contains an expected string.
Note: All conditions within a single check use AND logic — every configured condition must pass for the check to be considered successful.