Website Change Monitoring Without Raw-Alert Overload

A monitor captures a selected section, validates the response, normalizes configured noise, compares it with the last good snapshot, and schedules the next check. A change is an event; Healthy, Delayed, Failing, Paused, and Baseline pending describe monitor health.

Stable job identities and database leases prevent overlapping work from creating duplicate change records. Rejected captures never replace the last valid baseline.

Checks occur at the cadence shown by the selected plan, so a short-lived edit between checks may not be observed. Authenticated, blocked, or highly dynamic pages may require the browser extension or a clearer public section.