Uptime checks and SLOs
Checks from outside your cloud, SLOs with error budgets, and burn-rate alerts that open incidents.
Operate · Runs automatically in your portal
The problem
Dashboards nobody reads, alerts that fire all night, and outages you hear about from customers first.
What you get
- Know when a user-facing endpoint is down or slow
- Availability and latency SLOs with error budgets
- Burn-rate alerts on the Google SRE Workbook thresholds
- A monthly reliability report
Deliverables
- HTTP checks every 30 seconds to 5 minutes with status and keyword assertions
- SLOs and error budgets in your portal
- Burn-rate alerts that open incidents
- Monthly reliability report
How it runs
- 1Add checks
Sign-up, checkout, API health: the URLs your users depend on.
- 2Define SLOs
Availability or latency targets over a rolling window.
- 3Alert
Fast and slow burn alerts become incidents under your response policy.
- 4Report
Attainment and incidents summarized every month.
The quality bar for this service
Every uptime checks and slos deliverable is reviewed against this checklist (version 1.0) before it is released. Items marked required must be fully met; an item that is not is flagged on the report.
- Lists every service's SLO, the measured attainment for the period and the error budget remaining.Required
- Summarizes incidents and alerts with links to postmortems.Required
- Reports alert volume and noise (alerts without action) with tuning actions taken.
- Shows month-over-month trends for latency, errors and saturation of key services.Required
- Lists reliability improvements for next period with owners.Required