SRE maturity self-assessment
Ten questions, about two minutes. Nothing leaves your browser.
Answer for the team and services you know best. There are no wrong answers: the result points to where a small change would help most, it is not a grade.
Your result
Where to start
- Pick one critical service and write down one SLI and one SLO for it. The wizard can generate the rules.
- Move from resource metrics to request-based ratios: successful requests divided by total requests.
- Agree with product on one rule for when the budget is exhausted, for example a freeze on risky changes.
- Replace the noisiest cause-based pages with multi-window burn-rate alerts on the SLO.
- Write a short runbook for your three most frequent pages and link it from the alert.
- Hold a blameless review after the next significant incident and track every action to completion.
- Count pages per shift for a month; if many are not actionable, fix or delete those alerts first.
- List your top dependencies and their published SLAs: your SLO cannot realistically exceed them.
- Track the hours spent on manual, repetitive operations for a month, then automate the biggest item.
- Make sure each alert links to a dashboard that holds the matching logs and traces.