PointWarden Docs
Open PointWarden

Quickstart

Create an active Monitor, confirm its first Scheduled Check evidence, and prepare a subscribed, Verified, and Enabled Notifier.

Before you start

This path begins with you acting as the Owner of an empty Personal Workspace. It ends when PointWarden has current Scheduled Check evidence for one Monitor and a subscribed Notifier is Verified and Enabled.

Create a Monitor

Open Monitors, choose Create a Monitor, and use these settings for the first Monitor.

Only an Owner or Admin can create or change Monitors. You are following this guide as Owner; review the Workspace role permissions if your access differs. During the free beta, a Workspace may save 10 Monitors and keep five active; see the free-beta limits.

SettingValue
NameCustomer API
Endpointhttps://api.example.com/healthReplace this placeholder with your public Endpoint. Use public HTTP on port 80 or HTTPS on port 443. The path remains visible; keep secrets out of it. Query values, headers, and bodies are encrypted and hidden after saving.
MethodGET
Accepted statuses200 through 399
Interval5 minutes
Timeout10 seconds
LifecycleActive

  1. Run the diagnostic request

    Keep Start this Monitor after saving selected, then choose Test Request. A Test Request is diagnostic and does not change Availability, Incidents, Availability Rollups, or notifications.

    Expected result: PointWarden shows the immediate Test Request outcome while the Monitor remains unsaved.

  2. Save the active Monitor

    Choose Create Monitor. PointWarden saves Customer API as active and makes a Scheduled Check due immediately.

    Expected result: Customer API opens as Pending because no Scheduled Check evidence exists yet for this Monitor Revision.

Confirm Scheduled Check evidence

Wait for the first Scheduled Check and refresh Customer API. A passing Scheduled Check changes the Monitor from Pending to Available. The earlier Test Request cannot make this change.

Expected result: The Monitor shows Available, and its latest Check Evidence identifies a Scheduled Check with a passing outcome.

If Pending persists, use the persistent Pending path before continuing. If Scheduled Check evidence exists but is not Passing, troubleshoot the Endpoint evidence.

Create a Notifier

Open Notifiers and choose Create a Notifier. Bring an existing receiver target; this guide keeps provider-specific setup outside the shared PointWarden path.

Only an Owner or Admin can create or change Notifiers. During the free beta, a Workspace may save 10 Notifiers and keep three Enabled; see the Workspace role permissions and free-beta limits.

SettingValue
NamePrimary operations
Receiver URLhttps://hooks.example.com/pointwardenThis is a non-runnable placeholder. Replace it with an existing public HTTPS target you control. PointWarden has no demo receiver; the complete URL is encrypted and hidden after saving.
Destination typeGeneric, Slack, Discord, or Microsoft TeamsConfirm the type PointWarden detects for your receiver.
Operational eventsIncident opening and Recovery
Monitor selectionCustomer API

  1. Name and confirm the receiver

    Enter the settings above and confirm the detected Destination type. Only public HTTPS targets are accepted.

    Expected result: PointWarden shows the matching Destination type as confirmed while Primary operations remains an unsaved draft.

  2. Test the unsaved configuration

    Choose Test Notifier. Test Notifier does not send a live Test Delivery; it validates the configuration and public DNS before the Notifier exists.

    Expected result: PointWarden confirms whether the unsaved receiver configuration can be accepted. The Notifier is still unsaved and Unverified.

  3. Connect the subscriptions

    Review Operational events and Monitor selection against the settings above. A Verified and Enabled Notifier receives nothing when its event or Monitor subscriptions are empty.

    Expected result: Incident opening, Recovery, and Customer API are selected in the unsaved draft.

  4. Save Primary operations

    Choose Create Notifier. If you chose Generic, store the one-time signing secret, then choose Continue to Notifier. PointWarden does not reveal that secret again. Provider Notifiers open the detail page directly.

    Expected result: Primary operations is saved as Unverified and Paused with the Incident opening, Recovery, and Customer API subscriptions saved; its complete receiver URL is hidden.

Verify and enable

Verification and enablement are separate. Verification proves that the saved receiver accepted a Test Delivery; it never enables production delivery automatically.

  1. Send the saved Test Delivery

    Choose Verify Notifier. Unlike Test Notifier, this sends a live Test Delivery in the saved Destination type's format.

    Expected result: After the target accepts the Test Delivery, Primary operations is Verified and Paused.

  2. Enable production delivery

    Choose Enable. This makes the Notifier eligible for new subscribed Incident and Recovery Notification Events; it does not backfill earlier events.

    Expected result: Primary operations is Verified and Enabled.

  1. After Create NotifierUnverified and Paused
  2. After a successful Test DeliveryVerified and Paused
  3. After EnableVerified and Enabled

If the Test Delivery fails, use Test Delivery troubleshooting. If the Notifier cannot be enabled, check verification and lifecycle troubleshooting.