HTTP Monitoring

An HTTP monitor (kind http) issues a GET or HEAD request to a public HTTPS/HTTP URL you configure. Pass/fail is derived from the probe outcome — expected status, timeouts, and network errors — not from synthetic uptime.

Same walkthrough as the Monitoring overview— create from /app/monitoring.

1. 1

   Step 1: Open the create form

   From Monitoring, click Add monitor or Create monitor. You land on the New monitor form for the selected project.

   

2. 2

   Step 2: Fill required fields

   • URL — public http:// or https:// target.
   • Success when the response status is — default 200.
   • Check every — Free at most every 10 minutes.

   Click Create monitor. The first check starts right after saving.

3. 3

   Step 3: Confirm a result

   Open the monitor detail. After the probe runs, pass/fail and timing come from the real response. Linked daily SSL and DNS checks for the hostname are described on the create form.

• url — target URL (SSRF-safe hostnames only; private / link-local targets are rejected).
• method — GET (default) or HEAD.
• expectedStatus — HTTP status code to treat as success (default 200).
• timeoutMs — probe budget (default 10000, max 60s).
• followRedirects — default true.

Create and edit monitors under the project Monitoring UI, or via the REST API when Enterprise api_access is enabled.

Each scheduled run stores a check result. Failures (wrong status, timeout, network error) contribute to health and can open alerts. Continuous runs require Trigger workers — see Monitoring overview.

HTTP monitoring is available on Free and all paid plans (feature gate http_monitor). Project and schedule limits still apply per plan.

• Monitoring overview
• SSL Monitoring
• Alerts