True Causes
SV
Reliability has no budget line of its own
a walkthrough with stand-ins — a demonstration, not a finding · sealed
It significantly influences
The incident channel fills with people asking for status instead of giving it
certified · 9 yes · 3 no · 2 abstained
The staging environment does not resemble production
certified · 13 yes · 1 no
What significantly influences it
Rollbacks take longer than the outage they are meant to end
certified · 12 yes · 1 no · 1 abstained
Judged not to be linked
The same three services cause most of the pages
judged not to · 2 yes · 11 no · 1 abstained
Rollbacks take longer than the outage they are meant to end
judged not to · 1 yes · 13 no
Config lives in five places and drifts between them
judged not to · 0 yes · 13 no · 1 abstained
Customers report outages before monitoring does
judged not to · 0 yes · 13 no · 1 abstained
Retries are unbounded, so a slow dependency becomes a flood
judged not to · 1 yes · 13 no
The service map in the wiki is two years old
judged not to · 3 yes · 11 no
The same three services cause most of the pages
judged not to · 2 yes · 10 no · 2 abstained
Config lives in five places and drifts between them
judged not to · 2 yes · 10 no · 2 abstained
Customers report outages before monitoring does
judged not to · 3 yes · 10 no · 1 abstained
The incident channel fills with people asking for status instead of giving it
judged not to · 1 yes · 13 no
Retries are unbounded, so a slow dependency becomes a flood
judged not to · 1 yes · 13 no
The staging environment does not resemble production
judged not to · 1 yes · 13 no
Feature flags are never cleaned up, so nobody knows which paths are live
judged not to · 0 yes · 12 no · 2 abstained
The service map in the wiki is two years old
judged not to · 1 yes · 13 no
A group’s judgement, not a measurement. Demo room. On the atlas.
↗ cite or embed this claim
Link: https://truecauses.org/c/6708d57/1ccb9e7-reliability-budget
As data: https://truecauses.org/c/6708d57/1ccb9e7.json