Monitor overview
Learn how a Monitor turns Scheduled Checks against one public Endpoint into Check Evidence, Availability, and confirmed Incidents or Recovery.
A Monitor defines how PointWarden sends Checks to one public HTTP or HTTPS Endpoint and uses Scheduled Check Evidence to determine observed Availability.
How a Monitor produces evidence
Monitor configuration, Checks, evidence, and confirmation form one connected path. The request fields are inputs to that path, so read them together.
Define the observation
The public Endpoint, request method, accepted statuses, interval, and timeout define what PointWarden sends and how it evaluates the response. HTTP uses port 80 and HTTPS uses port 443.
Run Scheduled Checks
Regular Scheduled Checks observe the public Endpoint on its interval. Short confirmation Checks follow when evidence begins an Incident or Recovery sequence.
Retain and interpret Check Evidence
Each Check records safe outcome and timing evidence. Executed regular Scheduled Checks contribute to Availability, while Coverage shows how much expected evidence PointWarden produced.
Confirm Incidents and Recovery
Three consecutive Failing Checks open an Incident. Two consecutive Passing Checks confirm Recovery and close it. Each confirmed change creates its eligible Notification Event.
Read a Monitor
Start with the current claim, then check the evidence behind it and whether that evidence is complete enough for the time range.
| Question | Evidence to read |
|---|---|
| What is PointWarden claiming now? | Current Monitor state. |
| What happened in the latest observation? | Latest Check Evidence, final status, and latency. |
| Is the evidence current? | Freshness, Pending, or No Data. |
| How often did executed regular Checks pass? | Availability. |
| How much expected evidence exists? | Coverage. |
Configuration and lifecycle
Availability-affecting changes create a new Monitor Revision. An active revised Monitor returns to Pending until it produces new Scheduled Check Evidence. Pausing stops Scheduled Checks and the current Availability claim; resuming returns the Monitor to Pending. Deleting it prevents future Checks while retained evidence follows its normal retention period.
Choose the next task
Follow the Owner quickstart for the shortest complete setup, or Create a Monitor for every required field. Use advanced configuration and the Monitor lifecycle when you need to change how it runs.
To interpret the result, Compare Check types, read Availability and Coverage, then follow the Incident and Recovery sequence.