HTTP/HTTPS Monitoring

Monitor web endpoints with HTTP and HTTPS checks

Monitoring

HTTP/HTTPS monitors are the most common type of uptime check. They verify that your web services are responding correctly by making requests and validating the responses.

Configuration Options

URL

The full URL to monitor, including protocol (http:// or https://).

https://api.example.com/health

Request Method

HTTP method to use for the request.

GET

POST

HEAD

PUT

DELETE

Expected Status Code

The HTTP status code that indicates success (default: 200).

200 OK201 Created204 No Content

Timeout

Maximum time to wait for a response (in seconds). Default is 30 seconds.

Check Interval

How often to run the check. Options range from 30 seconds to 24 hours.

Advanced Options

Custom Headers

Add custom HTTP headers to the request (e.g., Authorization, API keys).

{
  "Authorization": "Bearer token123",
  "X-API-Key": "your-api-key"
}

Request Body

For POST/PUT requests, include a JSON body.

{
  "ping": true
}

Response Body Validation

Optionally check if the response body contains a specific string or matches a pattern.

SSL Certificate Verification

Verify SSL certificates are valid and not expired. Can be disabled for self-signed certs.

Best Practices

Use dedicated health check endpoints (e.g., /health or /status)
Set reasonable timeouts based on expected response times
Monitor critical endpoints more frequently than non-critical ones
Use HEAD requests for simple availability checks to reduce load