Error budgets 19
Every service on test27 over the last 30d, against an
objective — with how much of the budget is gone and how fast it is going.
?A budget is the failures an objective permits. Burn rate is how fast you are
spending it: 1 spends exactly the window's budget over the window, 14.4 spends
2% of a 30-day budget in an hour. Two windows are shown because they answer
different questions — the 1h catches something breaking now, the 6h catches a
slow leak the 1h would dismiss as noise.
How to read this page — error budgets
An objective turns a latency or error number into a verdict, and a burn rate turns the verdict into a schedule: not "we are at 99.3%" but "at this rate the budget is gone by Thursday".
- objective
- The share of requests allowed to fail. `der` means DERIVED from this service's own history — see the banner — and `dec` would mean a declared target, which nothing in the fleet has yet.
- achieved
- The share that actually succeeded in this window. Red when it is under the objective.
- budget left
- How much of the permitted failure is unspent. 100% means nothing has failed; 0% means the objective is already missed for this window.
- burn 1h / 6h
- How fast the budget is being spent, relative to spending it exactly over the window. 1x is on-pace; 14.4x spends 2% of a 30-day budget in an hour. Two windows, because the 1h catches something breaking now and the 6h catches a slow leak the 1h dismisses as noise.
- n/a
- Fewer than 20 requests in that window. A burn rate from ten calls is noise, so none is shown.
- bad
- 5xx responses, plus — in `availability + slow` mode — requests slower than 1.5x this service's own baseline p95. 4xx is deliberately excluded: a client asking for something that does not exist is not the service failing.
What this page will not tell you
- Whether users are happy. A derived objective measures a service against its own past, not against what its callers need. Only a declared target can do that.
- Anything about a service with no traffic: it is absent rather than shown as perfect.
- A comparison between services. Two services with different derived objectives are being held to different bars, on purpose.
declared.
| Service | Verdict | Objective | Achieved | Budget left | Burn 1h | Burn 6h | Calls | Bad | p95 | p99 |
|---|---|---|---|---|---|---|---|---|---|---|
| onboardingsvc | healthy | 98.5%der | 99.41% | 61% | n/a | n/a | 19k | 110 | 271 ms | 987 ms |
| studiosvc | healthy | 99.5%der | 99.93% | 85% | n/a | n/a | 25k | 18 | 7.16 s | 1.9 min |
| docsvc | healthy | 99.0%der | 99.73% | 73% | n/a | n/a | 4k | 10 | 2.11 s | 4.58 s |
| execsvc | healthy | 99.9%der | 99.99% | 90% | n/a | n/a | 10k | 1 | 494 ms | 1.78 s |
| chat-agent | healthy | 99.9%der | 100.00% | 100% | n/a | n/a | 367 | 0 | 9.87 s | 19.76 s |
| dashql | healthy | 99.9%der | 100.00% | 100% | n/a | n/a | 155 | 0 | 4.81 s | 8.89 s |
| docproc | healthy | 99.9%der | 100.00% | 100% | n/a | n/a | 902 | 0 | 2.86 s | 4.94 s |
| enrollsvc | healthy | 99.9%der | 100.00% | 100% | n/a | n/a | 813 | 0 | 1.20 s | 4.21 s |
| feedsvc | healthy | 99.9%der | 100.00% | 100% | n/a | n/a | 628 | 0 | 245 ms | 972 ms |
| notifsvc | healthy | 99.9%der | 100.00% | 100% | n/a | n/a | 501 | 0 | — | — |
| ontologysvc | healthy | 99.9%der | 100.00% | 100% | n/a | n/a | 245 | 0 | 4.12 s | 4.83 s |
| patientsvc | healthy | 99.9%der | 100.00% | 100% | n/a | n/a | 117 | 0 | 8.96 s | 9.79 s |
| regsvc | healthy | 99.9%der | 100.00% | 100% | n/a | n/a | 34 | 0 | 2.45 s | 4.49 s |
| schedsvc | healthy | 99.9%der | 100.00% | 100% | n/a | n/a | 52 | 0 | 3.05 s | 4.61 s |
| swaggersvc | healthy | 99.9%der | 100.00% | 100% | n/a | n/a | 13 | 0 | 13 ms | 19 ms |
| tmfsync | healthy | 99.9%der | 100.00% | 100% | n/a | n/a | 86k | 0 | 20 ms | 47 ms |
| tusker | healthy | 99.9%der | 100.00% | 100% | n/a | n/a | 87 | 0 | 1.32 s | 5.65 s |
| virtual-assistant | healthy | 99.9%der | 100.00% | 100% | n/a | n/a | 340 | 0 | 4.24 s | 7.74 s |
| workplansvc | healthy | 99.9%der | 100.00% | 100% | n/a | n/a | 465 | 0 | 934 ms | 3.03 s |