HTTP Checks
Checks & Monitoring
Updated Apr 2, 2026
HTTP checks are the most common check type. They verify that a web endpoint responds correctly by making an HTTP request and validating the response.
Configuration
| Field | Description |
|---|---|
| URL | The full URL to monitor (must start with http:// or https://). |
| HTTP Method | GET, POST, PUT, DELETE, PATCH, or HEAD. |
| Expected Status | A specific code (e.g. 200) or a range (2xx, 3xx). |
| Expected Body | Optional text that must appear in the response body. |
| Request Headers | Custom headers sent with the request (JSON key/value format). |
| Request Body | Payload for POST/PUT/PATCH requests. |
| Interval | 30s, 60s, 2m, 5m, 10m, 30m or 1h. |
How it works
- At each interval, every assigned agent sends the configured HTTP request to your URL.
- The response status code is compared against the expected value.
- If an expected body is configured, the response body is scanned for the string.
- Response time, SSL certificate details, and any errors are recorded.
Response time tracking
Chglog records the response time for every check execution. You can view response-time graphs on the check detail page — showing average, minimum and maximum values over a configurable time range.
SSL certificate monitoring
For HTTPS URLs, Chglog automatically captures SSL certificate details (issuer, expiration date). You can opt into SSL expiration alerts via your notification preferences.
Tips
- Use
HEADrequests to save bandwidth when you only care about status codes. - Set an expected body pattern like
"status":"ok"to catch cases where a server returns 200 but with error content. - If your server rate-limits requests, use a longer interval (5m or 10m).