Xray
daily rollups 1h 6h 24h 48h 3d 5d 7d 14d 30d ‹
Last 5 days▾
Ends now. Anything up to this cluster's 30-day retention.
Start and end times
Cancel
Interpreted in UTC (change it at the right of this bar). Earliest available: 2026-10-19 07:50:14.
› →|
updated 21h ago
Sample data. This database was generated by scripts/seed_dev_db.py — every service, deploy, person and figure on this page is synthetic. Names are sample.*@seed.invalid and image tags are prefixed SEED-. Nothing here happened.

Error budgets 18

stored 21h ago all 18objectives derived from history

Every service on master over the last 5d, 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.
These objectives are derived, not agreed. Nothing in the fleet declares a target, so each service is measured against twice its own normal failure rate over the last 7 days. That answers “is this worse than this service usually is”, which is usually what people mean — but it is not a promise to anyone, and a service that has always been unreliable gets an unambitious objective. Declaring real targets is an upstream change; when they exist they replace this and the column below will say declared.
Columns
Views
Export CSV
Error budget, burn rate and verdict per service on master
Service Verdict Objective Achieved Budget left Burn 1h Burn 6h Calls Bad p95 p99
execsvc below objective 95.0%der 88.88% 0% n/a n/a 7k 790 1.64 s 4.76 s
studiosvc healthy 99.0%der 99.74% 74% n/a n/a 28k 72 2.0 min 409.5 min
docsvc healthy 99.5%der 99.78% 56% n/a n/a 8k 18 1.39 s 4.13 s
docproc healthy 99.0%der 99.62% 62% n/a n/a 2k 6 483 ms 1.65 s
workplansvc healthy 99.9%der 99.95% 50% n/a n/a 10k 5 34.24 s 55.06 s
dashql healthy 99.5%der 99.89% 78% n/a n/a 2k 2 3.90 s 4.84 s
chat-agent healthy 99.9%der 100.00% 100% n/a n/a 557 0 265 ms 39.90 s
enrollsvc healthy 99.9%der 100.00% 100% n/a n/a 2k 0 446 ms 2.32 s
feedsvc healthy 99.9%der 100.00% 100% n/a n/a 89k 0 53 ms 353 ms
notifsvc healthy 99.9%der 100.00% 100% n/a n/a 2k 0 — —
onboardingsvc healthy 99.9%der 100.00% 100% n/a n/a 27k 0 156 ms 476 ms
ontologysvc healthy 99.9%der 100.00% 100% n/a n/a 147 0 428 ms 2.80 s
patientsvc healthy 99.9%der 100.00% 100% n/a n/a 290 0 1.81 s 3.76 s
regsvc healthy 99.9%der 100.00% 100% n/a n/a 41 0 397 ms 479 ms
schedsvc healthy 99.9%der 100.00% 100% n/a n/a 184 0 882 ms 1.72 s
swaggersvc healthy 99.9%der 100.00% 100% n/a n/a 4 0 180 ms 196 ms
tusker healthy 99.9%der 100.00% 100% n/a n/a 509 0 1.91 s 4.58 s
virtual-assistant healthy 99.9%der 100.00% 100% n/a n/a 3k 0 1.72 s 10.67 s