HTTP Monitors

An HTTP monitor sends a request to your URL and evaluates the response. Use an endpoint that is safe to call repeatedly.

Configure the request

Set the URL, method, optional headers, and optional body. For a JSON endpoint, choose the appropriate method and set Content-Type: application/json when sending JSON. Keep authentication values in the monitor configuration; never include them in public reports.

Redirect following is enabled by default. Disable it when you need to check the first redirect response itself. When enabled, assertions evaluate the final response.

Evaluate the response

Use status-code, response-header, and text-body assertions offered by the editor. For example, assert status 200 and a body containing your health marker. A response arriving successfully is not sufficient if its content indicates failure.

Choose a timeout, optional degraded threshold, schedule, and locations. The timeout is capped at 60 seconds. The attempts setting represents the total number of attempts, capped at three, rather than three additional retries.

See Create your first monitor and Check locations.