What is WebCheck — core concepts in 5 minutes
WebCheck keeps an eye on your websites: Monitoring runs on a fixed interval, and when something won't open, gets slow, shows wrong content, or has a certificate about to expire, it notifies you by email, DingTalk, webhook, or browser push.
#Four core concepts
| Concept | In one sentence |
|---|---|
| Site | A URL (homepage or any page). Checked every few minutes for status code, response time, and page content. |
| Content watch | Watches one small part of a page — a price, stock level, version number, announcement — and tells you when it changes. |
| Vantage point | Where the check is sent from. The platform runs shared nodes in several regions; you can also attach your own nodes or proxies. |
| Check | One real HTTP request. Records the status code, per-stage timings (DNS/TCP/TLS/TTFB), and a response digest. |
#Site states
Up recent checks succeeded; Incident failures hit the threshold — judged an incident and alerted; Abnormal, confirming failing but not enough times yet, still being confirmed; Paused you paused it manually; Not checked never checked yet.
Why alerts need "consecutive failures"
Flapping is common — a single timeout is usually a false alarm. By default, 3 consecutive failures are required before an incident is declared; you can tune this per site in the Monitoring defaults section of Settings (System settings).
#Next up
- Add your first site — see Add your first site in 5 minutes
- Set up alerts — see Set up your first alert
- Tour the interface — see Interface tour