Derived health
Availability and performance are separate signals.
For every monitor type, WebGuard derives availability from raw check evidence—such as the HTTP response, transport outcome, connection result, observed DNS values, heartbeat, or server metrics. HTTP and Keyword monitors can additionally define a response-time threshold and consecutive-check confirmation count.
- A slow but successful check creates a separate degraded-performance alert; it does not become a public availability incident.
- The configured consecutive-check count confirms a latency change before WebGuard alerts.
- When response time returns below the threshold, WebGuard sends a recovery notification through the selected channels.
At a glance
- URL checks for websites and APIs
- HTTP method, headers, body, timeout, and Basic Auth support
- Response time and status history for investigation
How it helps
Use HTTP monitors for login pages, API health endpoints, landing pages, and SaaS product routes that must stay reachable.
Checks can validate the request shape and expected response status, making the monitor useful for operational readiness and not only network reachability.
Response history feeds dashboard cards, uptime summaries, recent checks, incidents, and public status displays when enabled.