True Causes
SR
← početna
7/7 · Akcije · pregled: Izbor
osoba: 30 · ideja: 30
probni prolaz · ne računa se
prepreke · svako sa linkom · na javnom spisku · federacija uključena
vodi: njen voditelj (zapečaćeno)
osoba: 30 · ideja: 30 · 2 grupe
Pasoš → · Logika → · zapis
↗ podeli ovu mapu
Na drugom sajtu, kao živa mapa:
Kao slika: https://truecauses.org/d/6708d57/map.svg
Kao podaci: svi ocenjeni parovi u ovoj sobi (CSV). Svaka tvrdnja ima svoju adresu, /c/6708d57/<card>, navedenu ispod mape.
Navedite izvor kada objavljujete: Causal map: True Causes, https://truecauses.org/d/6708d57
PITANJE

Why does the same outage keep recurring?

Potrošite nalepnice na ono što je najvažnije. Ideja sa dokazom može da zauzme rezervisano mesto.

Gledate kao gost. Unesite korisničko ime da biste se pridružili i učestvovali.
Vaš broj nalepnica
Jedna po ideji, ukupno 5. Najmanje jedan glas.
Rezervisana mesta za previđene ideje: 5 — nominujte jednu uz link, i ona se računa kada se dovoljno ljudi (2) složi da je izvor relevantan.
zašto
Kada se faza zatvori, jedan nominovani ulazi slučajnim izvlačenjem, a ostali po broju nominacija, najviše jedan po klasi zainteresovanih strana. Model proverava samo da li stranica govori o istoj temi — nikad da li dokazuje tvrdnju. Ta procena pripada sobi, a nominacija iza koje niko drugi ne stoji ne dobija mesto.
zatvori ✕
Error budgets exist on a slide and nowhere else
Još ništa nije rečeno.
KLASTER 1
The on-call rota has the same two people on it most weeks
glasova: 7diskutuj
The same three services cause most of the pages
glasova: 14diskutuj
KLASTER 2
Post-mortem actions are written up and then never scheduled
glasova: 4diskutuj
Feature flags are never cleaned up, so nobody knows which paths are live
Meaning the repeat outages, not the one-off hardware failure in March.
glasova: 7diskutuj
KLASTER 3
Migrations are run by hand from a laptop
glasova: 2diskutuj
Config lives in five places and drifts between them
I mean the pattern over the last two quarters, not a single incident.
glasova: 3diskutuj
KLASTER 4
Reliability has no budget line of its own
To be precise: this is about the process, not the person on call that night.
glasova: 11diskutuj
Every team has its own logging format
glasova: 3diskutuj
KLASTER 5
Customers report outages before monitoring does
I mean the pattern over the last two quarters, not a single incident.
glasova: 10diskutuj
Alerts fire so often that on-call mutes them
I mean the pattern over the last two quarters, not a single incident.
glasova: 6diskutuj
KLASTER 6
The service map in the wiki is two years old
glasova: 5diskutuj
Runbooks are out of date within a month of being written
To be precise: this is about the process, not the person on call that night.
glasova: 2diskusija (1)
VAN KLASTERA
Tests that fail intermittently are retried until green
glasova: 10diskutuj
Leadership asks for a root cause within the hour, so the first plausible one wins
I mean the pattern over the last two quarters, not a single incident.
glasova: 1diskutuj
Success is measured in features shipped per quarter
glasova: 1diskutuj
Dependencies are upgraded only when something breaks
Meaning the repeat outages, not the one-off hardware failure in March.
glasova: 0diskutuj
Deploys go out on Friday afternoons because that is when the sprint ends
glasova: 2diskutuj
Rollbacks take longer than the outage they are meant to end
To be precise: this is about the process, not the person on call that night.
glasova: 3diskutuj
Post-mortems assign actions to people who were not in the room
Scope: the services this team runs, not the whole platform.
glasova: 8diskusija (1)
Feature work always outranks reliability work in planning
Scope: the services this team runs, not the whole platform.
glasova: 4diskutuj
There is no time set aside after an incident, so the write-up is done at midnight
glasova: 2diskutuj
Incidents are declared late because declaring one feels like blame
glasova: 1diskutuj
Load tests were last run before the customer base doubled
glasova: 1diskutuj
One engineer knows how the payment path actually works
Scope: the services this team runs, not the whole platform.
glasova: 5
↳ nominovano za rezervisano mesto: https://example.org/ops-incident-review.pdf could not read it (HTTPError) podrška: 1 od 2
diskutuj
Error budgets exist on a slide and nowhere else
The staging environment does not resemble production
glasova: 7diskutuj
The incident channel fills with people asking for status instead of giving it
glasova: 3diskutuj
Nobody owns the shared database schema
To be precise: this is about the process, not the person on call that night.
glasova: 2diskutuj
Retries are unbounded, so a slow dependency becomes a flood
glasova: 6diskutuj
Capacity is added after the outage, never before
glasova: 0diskutuj