HTTP(S) monitor

For web and API endpoints — status codes, keywords, JSON paths, redirect chains.

What it checks

Teravor sends an HTTP request from a probe region and asserts on the response. You can pin status codes, match text or JSON in the body, check response headers, and cap latency.

When to use it

• Public API endpoints (`GET /health`, `GET /api/v1/status`).
• Public marketing pages (assert on a keyword you control).
• Authenticated endpoints using a bearer token or custom header.
• Endpoints behind Cloudflare (we follow redirects and send a real UA).

Config fields

Fields marked * are required.

Example config

{
  "name": "api.example.com health",
  "type": "http",
  "config": {
    "url": "https://api.example.com/health",
    "method": "GET",
    "expected_status": [200],
    "keyword_match": { "pattern": "\"status\":\"ok\"" },
    "max_response_ms": 2000
  },
  "interval_sec": 60
}

Notes

• The probe sends a real User-Agent and honors robots.txt only for discovery, not for monitor checks.
• TLS verification is on by default. To monitor a cert you expect to be broken, disable via `tls_insecure: true`.