How Website Monitoring Works
Learn how external checks, confirmation and recovery turn website failures into actionable incidents.
Login2Cloud product team · Published 2026-10-01
Start with a public endpoint
A monitor makes a bounded request to the public URL you choose and evaluates status, timing and optional content assertions. Choose an endpoint that reflects the service visitors need, rather than assuming the homepage represents every workflow.
Separate failure and confirmation
A timeout, DNS error or rejected assertion is a failed observation. Confirmation settings determine when repeated failures become a measured incident. Recovery follows a successful observation; the exact time between checks remains uncertain.
Diagnose before changing thresholds
Compare the safe failure category with application logs, deployment time and DNS or certificate changes. Reproduce the request from an external connection. Increasing a timeout can hide a real slowdown, so understand the failure first.
Build a small useful set
Start with a website check, certificate expiry and an API readiness endpoint. Add job heartbeats for scheduled work. Test a notification channel and document who responds before expanding coverage.
Common questions
Where should I start?
Use the related tool to inspect the current signal, then configure the matching monitor and verify its first result.