Every operation of the Monitoring API, under /monitoring/api. Sign requests with an access key (Authorization: EWS-ACCESS-KEY <id>:<secret>). A successful JSON response is { "success": true, "data": … }.
CPU, disk and network of every machine, and database volume usage
Series an application publishes itself, charted and alarmed on like built-ins
Thresholds on a metric that notify by email or webhook
Uptime checks: a URL requested on a schedule, with response times and outages
What a deployed app printed, shipped by the agent on its machine
Public status pages at {slug}.status.{root}, built from uptime checks
Incidents posted on a status page, with their timeline of updates
Who a status page emails or calls about incidents and components going down
Generated from the API description, the same one the API checks requests against and the CLI is built from.