Endpoint monitoring, explained through evidence.
Learn how PointWarden observes public HTTP Endpoints, confirms Availability changes from Scheduled Check evidence, and delivers Incident and Recovery Notification Events to eligible Notifiers in your Workspace.
Open PointWardenUnderstand the evidence path
PointWarden turns what a Scheduled Check observed into a confirmed Availability change, then carries that evidence into Delivery.
Observe
Run Scheduled Checks against public HTTP Endpoints.
Example Check EvidenceObserve- Endpoint
- https://api.example.com/health
- Observed
- 18 May 2024 · 10:18:12 UTC
- Final status
- 200 · 112 ms · 0 redirects
- Example only
- Replace with an Endpoint you control.
Checks run from the public internet against the Endpoint you configured, so the evidence reflects real reachability.
Scheduled Checks can affect Availability. Manual Checks cannot.
Confirm
Use consecutive Check Evidence before changing Availability.
Confirmation sequenceConfirm- Incident DetectionFailing Check 1 · Suspected Failure
- Suspected FailureFailing Check 2
- Incident ConfirmationFailing Check 3 · Incident opens
- RecoveringPassing Check 1
- Recovery confirmedPassing Check 2 · Incident closes
Incident Detection starts observed impact. Incident Confirmation opens the Incident after the third consecutive Failing Check. Two consecutive Passing Checks confirm Recovery.
Incident Detection and Incident Confirmation are separate moments.
Notify
Deliver Incident and Recovery Notification Events to verified Notifiers.
Notifier readinessNotify- Subscription
- Incident and Recovery
- Verification
- Verified
- Lifecycle
- Enabled
A successful Test Delivery verifies a Notifier. Enabled decides whether it can receive new subscribed events.
Verification and enablement are separate decisions.
Availability is an observation, not a promise
PointWarden reports what it observed from the public internet at a moment in time. It does not measure your internal systems or guarantee an Endpoint's complete service health.