Skip to content
Website Toolkit DEV

DOCUMENTATION & HELP

Understand a monitor alert

Separate scheduling, observed health and notification delivery.

Monitoring · concept · public

Checked against v1.241.1 on 2026-11-02 · Source reviewed

Identify the measurement

DNS Watcher checks DNS conditions. Site Monitor samples website responses. Domain Watch tracks registration information. An active schedule and a successful condition are different states.

Read the observation

Review the latest event time, target, condition, expected values and actual observation. An old match does not establish the current state. A blocked request can describe treatment of the probe rather than every visitor's experience.

Alerts and maintenance

Maintenance and notification suppression affect delivery policy; they do not by themselves prove checks stopped. Email has separate opt-in and readiness requirements. In-app and email delivery are different channels. A scheduling state alone does not confirm either delivery.

Registration and advanced sources

A registry expiry observation does not confirm registrar auto-renew. Ask the registrar account owner when action is needed. A private agent heartbeat is not proof that an internal website is healthy. Missing data remains unknown.

Next action

Use the exact event link or workspace to inspect current evidence and settings. Do not create duplicate jobs merely because a notification is absent. New jobs, alert lifecycles, mail delivery and private integrations require their own acceptance; none was activated by this help work.

Verification scope: Current form labels, registry and source reviewed; live provider, mailbox, saved-work lifecycle and host acceptance remain separate.