better-stack-monitors

# Better Stack Uptime Monitors ## Overview Uptime monitors are the core of Better Stack's monitoring platform. They periodically check URLs, ports, or heartbeats to detect downtime and performance degradation. Monitors can be grouped, paused, and configured with custom check intervals, expected status codes, and alerting thresholds. ## Anti-triggers - **An internal or RFC1918 target** — checks run from Better Stack's public regions and cannot reach a private LAN. Reachability from inside the site is `domotz-network`, which polls from a collector on the LAN. Note it answers a different question: Domotz reports device and interface state, not synthetic HTTP/TCP probes, so there is no in-LAN equivalent of a Better Stack check. - **Azure Monitor** — same word, different product. Azure metrics, KQL, and alert rules are `azure-mcp-observability`. - **Whether a piece of infrastructure is up** — SNMP and ICMP polling of switches, firewalls, and APs is `auvik-devices`; a workstation or server under RMM is `atera` or `ncentral`. - **Who gets woken when a check fails** — the monitor holds the check; the routing and rotation are `betterstack-oncall`. ## Key Concepts ### Monitor Types - **HTTP/HTTPS** - Check a URL for expected status code and response - **Ping (ICMP)** - Ping a host to verify reachability - **TCP** - Check if a TCP port is open and responding - **UDP** - Check UDP port connectivity - **Heartbeat** - Expect periodic check-ins from cron jobs or ser...