A monitor is one thing you want watched: a URL, an endpoint, a certificate. Tallwatch runs the check from each region you pick, on the interval you set, and opens an incident when more than one region agrees it’s down.Documentation Index
Fetch the complete documentation index at: https://docs.tallwatch.com/llms.txt
Use this file to discover all available pages before exploring further.
In this section
Monitor types
What each check does, and which run end-to-end today.
Creating monitors
Fill in the form: URL, request options, assertions, regions, intervals.
Dependencies
Silence symptom alerts when an upstream monitor is already down.
Maintenance windows
Plan downtime so it doesn’t open incidents.
Settings every monitor shares
Whatever the type, each monitor carries the same core settings:- Regions it checks from. Pick at least three so an incident needs agreement, not one bad data point.
- Interval between checks, from 30 seconds up. The probers run about once a minute, so 60s is the practical floor.
- Sensitivity, how long failures must persist before an incident opens. Shorter alerts faster; longer tolerates more noise.
- Status,
activeorpaused. A paused monitor keeps its history but stops checking and never alerts.