Service Level Objectives

User flows turned into SLIs, SLO targets set from real data, error budgets with an agreed policy, burn-rate alerts and the review rhythm that turns reliability into a planning input.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Service Level Objectives, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

200

Starter tasks

⚙️ Software Engineering

Service Level Objectives

Defining reliability targets, error budgets and the indicators behind them, and using them to balance shipping features against stability work.

  1. Critical user flow inventory for one service
  2. Shared SLO glossary for the team
  3. First availability SLI from request logs
  4. First latency SLI with a percentile threshold
  5. Ninety-day SLI baseline before setting targets
  6. Choosing the first SLO target from evidence
  7. SLO document for the first service
  8. Rolling or calendar compliance window decision
  9. Error budget policy agreed with product
  10. Per-service SLO dashboard
  11. Monday error budget check
  12. Monthly SLO review with product
  13. Burn-rate alerts on the error budget
  14. Quarterly SLO target recalibration
  15. Error budget spend ledger by cause
  16. Release freeze when the budget is exhausted
  17. SLI data quality checks
  18. Planned maintenance and the error budget
  19. Feature and reliability work split from budget status
  20. SLO coverage tracker across services
  21. Error budget arithmetic and the nines
  22. Burn rate and multiwindow alerting maths
  23. Latency SLIs with histograms done properly
  24. Request-based versus time-window SLIs
  25. Client-side SLIs from probes and real-user data
  26. SLOs for data pipelines and freshness
  27. SLOs for low-traffic services
  28. SLO reading list from the SRE literature
  29. SLO tooling choice, build or buy
  30. SLOs as code in the service repository
  31. Retiring vanity uptime figures
  32. Dependency SLOs and the call graph
  33. Internal SLOs alongside customer SLA terms
  34. Tightening an SLO users have outgrown
  35. Loosening an SLO that costs too much
  36. Per-tenant SLIs for large customers
  37. SLO kick-off workshop with product and engineering
  38. Budget exhaustion retrospective
  39. Launch SLOs for a new service
  40. Annual reliability target review with leadership
  41. Error budget policy tabletop exercise
  42. SLOs for a small team without SRE specialists
  43. Introducing SLOs to a team used to uptime targets
  44. Inheriting a service with untrusted SLOs
  45. SLOs for an internal platform team
  46. SLOs for a mobile app
  47. SLOs for batch jobs and scheduled work
  48. SLO hierarchy from components to user flows
  49. Error budget gate in the deploy pipeline
  50. Reliability investment case from SLO data

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Critical user flow inventory for one service

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Every SLO is only as useful as the user experience it measures, and most teams start by measuring whatever their metrics system already exports.

First tasks

  • Write down every action a user can take against the service in one sitting
  • Pull the last quarter of support tickets that mention this service
  • Rank each flow by impact and frequency with the product owner
  • Commit the ranked flow list to the service repository

Shared SLO glossary for the team

Teams argue for weeks when one person means uptime, another means success rate and a third means the contractual SLA. A one-page glossary defining SLI, SLO, SLA, error budget, burn rate, compliance window and good event versus valid event settles the vocabulary before any target is set. New joiners then read one page instead of three books.

First tasks

  • List the reliability terms the team already uses inconsistently
  • Write one definition and one local example per term
  • Ask a product manager to check the glossary reads clearly to them
  • Link the glossary from the handbook and onboarding checklist

First availability SLI from request logs

Availability is the natural first SLI, but the definition hides real choices: which requests count, whether a 4xx is the user's fault or yours, and where you measure. Writing the SLI as good requests divided by valid requests, with each term defined precisely and the query saved, gives the team one number everyone computes the same way.

First tasks

  • Choose the measurement point for the service's highest-ranked flow
  • Write the good and valid event filters in plain words first
  • Translate the filters into a saved query or recording rule
  • Hand-check 50 raw requests against the query's classification

Make it yours.

Install Service Level Objectives, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.