HTTP Monitor

Periodically sends HTTP requests to websites and API endpoints, verifying the response status code and body.

Configuration

Field	Description	Required	Default
URL	Target URL (HTTP/HTTPS)	Yes	-
Method	HTTP method	No	GET
Expected Status Code	Status code considered healthy (100-599)	No	200
Timeout	Maximum time to wait for a response	No	10 seconds
Keyword Check	String that should be present in the response body	No	-
Headers	Custom headers to add to the request	No	-

HTTP Methods

Method	Use Case
GET	General web page and API checks (default)
HEAD	When you only need the status without the body. Reduces bandwidth
POST	Checking API endpoints that require a request body

Keyword Check

Verify that the response body contains a specific string. Even if the status code is healthy, the monitor will detect a failure if the page content differs from expectations.

For example, this can detect when a maintenance page is served while still returning a 200 status code, indicating the actual content is not being displayed.

Custom Headers

Add arbitrary headers to the request. Header names may only contain alphanumeric characters and hyphens.

The following headers cannot be set for security reasons:

Host
Authorization
Cookie / Set-Cookie
Transfer-Encoding
Content-Length

Incident Detection

A failure is detected when any of the following conditions are met:

The response status code differs from the expected value
The response does not return within the timeout period
Keyword check is configured and the keyword is not found in the response body
Connection error (DNS resolution failure, connection refused, etc.)