Incidents & SLOs
m0nitor opens incidents automatically on monitor failure, routes them through workflows, and tracks availability and latency SLOs with error-budget burn-rate alerts.
Yes - when a monitor fails consensus across regions, m0nitor creates an incident automatically and ties it to the affected monitor.
Minor, major and critical; severity drives workflow conditions.
On your status page and its RSS and JSON feeds, and to email subscribers; visibility is toggleable per incident.
The remaining allowed downtime within an SLO window; burn-rate policies warn when you spend it too quickly.
Rolling 7-, 30- and 90-day windows for availability and p95 latency targets.
Yes - SLA reports export to CSV, and maintenance windows suppress alerts and stay out of the error budget.