When to use HTTP monitors
- Health check endpoints — verify
/healthor/statusreturns 200 - API availability — check that key API endpoints respond within latency budgets
- Website uptime — confirm marketing pages, app frontends, and landing pages load
- SSL certificate expiry — get alerts before certificates expire using the
ssl_expiryassertion - Content validation — verify response bodies contain expected data using
body_contains,json_path, orregex - Redirect chains — track redirect behavior with
redirect_countandredirect_targetassertions
How it works
- DevHelm sends an HTTP request from each configured probe region at the set frequency
- The response is evaluated against all configured assertions
- Each assertion records pass/fail with the configured severity (
failorwarn) - If any
fail-severity assertion fails, the check is marked as failed - Failed checks flow into the incident policy engine
Supported methods
| Method | Typical use |
|---|---|
GET | Health checks, page monitoring, API reads |
POST | API endpoint testing with request bodies |
PUT | API update endpoint testing |
PATCH | Partial update endpoint testing |
DELETE | Deletion endpoint testing |
HEAD | Lightweight availability checks (no response body) |
Quick example
Next steps
Configuration
Every HTTP monitor field — URL, method, headers, body, TLS, auth.
Assertions
All 11 HTTP assertion types with examples.
First HTTP monitor
Step-by-step tutorial.
SSL monitoring
Monitor certificate expiration dates.