Service Level Objectives From User Journeys
Define SLIs, SLOs and error budgets for a service.
Added October 15, 2026. Written with AI assistance and checked for clarity and placeholders; not reviewed by a lawyer, accountant, clinician or other professional. How these prompts are made
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Define service level objectives for [SERVICE_NAME]. Describe the top three user journeys in my words: [USER_JOURNEYS]. Traffic volume and peak hours: [TRAFFIC]. Current monitoring data I can pull (latency percentiles, error rates, availability): [CURRENT_METRICS]. Business tolerance for downtime and slowness: [TOLERANCE]. For each journey, propose one or two service level indicators defined precisely: what counts as a good event, what counts as a valid event, and where the measurement is taken (server, load balancer, synthetic probe). Set a target SLO for each with a rationale tied to my tolerance, and compute the error budget in minutes or requests per 28 days, showing the arithmetic. Provide a burn-rate alert design with fast and slow windows using concrete example thresholds I can edit. Add an error budget policy: what the team does when the budget is spent, who decides, and how exceptions are recorded. Flag any indicator that I cannot measure with my current data and the cheapest way to start measuring it. End with a one-page review template for the monthly SLO meeting. Add a worked example for one journey using invented numbers: a checkout journey with 1,200,000 valid requests in 28 days and a 99.9 percent target. Show the error budget as 1,200 failed requests, the minutes-equivalent if the service were fully down, and a burn-rate table with a fast window (for example, 14.4 times the budget rate over one hour paging someone) and a slow window (for example, 6 times over six hours opening a ticket). Say clearly that these thresholds are examples for me to edit. Add a short section on choosing the target: compare the target with what the service achieved over the last three months, and warn against setting a target the service already misses or one far better than users can notice. Close with the questions to ask the business before agreeing the SLO.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.