Distributed monitoring
βοΈ Monitors
Track uptime, incidents, latency, and node coverage from one place.
How monitoring worksβΌ
Monitors check a target on a fixed interval and record whether it is reachable. Use HTTP checks for websites and APIs, TCP checks for open ports, DNS checks for name resolution, ping checks for basic reachability, and TLS checks for certificate visibility.
A monitor becomes useful after it has a few checks: the dashboard shows recent success, 24-hour uptime, latency, and open incidents. Failed checks create incidents so you can quickly see what needs attention.
Pick intervals that match the service. Critical public endpoints can be checked frequently; internal or low-priority systems should use a slower interval to reduce noise and avoid unnecessary traffic.
Total Monitors
0
Avg Uptime
β
Open Incidents
0
Γ Latency
β
Monitors
Loadingβ¦