SPØRGSMÅLET
Why does the same outage keep recurring?
Saml sedler, du synes ligner hinanden. Klynger gør væggen lettere at læse; de afgør intet.
lukket · tilbage til fasen Handlinger
Du ser med som gæst. Vælg et brugernavn for at komme med og deltage.
Klynger dannes ud fra lighed, navnene kommer sidst
Fast rækkefølge: kobl par af idéer, du synes ligner hinanden — koblinger er symmetriske (A~B er B~A; retningen betyder aldrig noget), og en kobling holder, når 2 medlemmer har lavet den.
hvorfor
Koblinger er symmetriske — A~B er B~A. Klynger er de grupper, der opstår af koblinger, der holder, og kun en dannet klynge kan navngives, af et menneske. Dine egne koblinger har et ✕, så du kan trække dem tilbage; du kan ikke fjerne andres. Klynger ordner væggen og spærrer aldrig for afstemningen — to sedler, der fremsætter samme PÅSTAND, skal lægges sammen i fasen Præcisering.
Koblinger og navne laves, mens fasen Sortering er åben; tovholderens ← genåbner den.
unavngiven klynge — navngiv den, hvis sedlerne har en fælles tråd, eller lad den være unavngiven (2)
Alerts fire so often that on-call mutes them
~ Customers report outa…Customers report outages before monitoring does (12)
Customers report outages before monitoring does
~ Alerts fire so often …Alerts fire so often that on-call mutes them (12)
unavngiven klynge — navngiv den, hvis sedlerne har en fælles tråd, eller lad den være unavngiven (2)
The same three services cause most of the pages
~ The on-call rota has …The on-call rota has the same two people on it most weeks (20)
The on-call rota has the same two people on it most weeks
~ The same three servic…The same three services cause most of the pages (20)
unavngiven klynge — navngiv den, hvis sedlerne har en fælles tråd, eller lad den være unavngiven (2)
Every team has its own logging format
~ Reliability has no bu…Reliability has no budget line of its own (15)
Reliability has no budget line of its own
~ Every team has its ow…Every team has its own logging format (15)
unavngiven klynge — navngiv den, hvis sedlerne har en fælles tråd, eller lad den være unavngiven (2)
Runbooks are out of date within a month of being written
~ The service map in th…The service map in the wiki is two years old (16)
The service map in the wiki is two years old
~ Runbooks are out of d…Runbooks are out of date within a month of being written (16)
unavngiven klynge — navngiv den, hvis sedlerne har en fælles tråd, eller lad den være unavngiven (2)
Post-mortem actions are written up and then never scheduled
~ Post-mortems assign a…Post-mortems assign actions to people who were not in the room (9)
~ Feature flags are nev…Feature flags are never cleaned up, so nobody knows which paths are live (14)
Feature flags are never cleaned up, so nobody knows which paths are live
~ Post-mortem actions a…Post-mortem actions are written up and then never scheduled (14)
unavngiven klynge — navngiv den, hvis sedlerne har en fælles tråd, eller lad den være unavngiven (2)
Config lives in five places and drifts between them
~ Migrations are run by…Migrations are run by hand from a laptop (21)
Migrations are run by hand from a laptop
~ Config lives in five …Config lives in five places and drifts between them (21)
· endnu ikke i en klynge (18)
Tests that fail intermittently are retried until green
Leadership asks for a root cause within the hour, so the first plausible one wins
Success is measured in features shipped per quarter
Dependencies are upgraded only when something breaks
Deploys go out on Friday afternoons because that is when the sprint ends
Rollbacks take longer than the outage they are meant to end
Post-mortems assign actions to people who were not in the room
~ Post-mortem actions a…Post-mortem actions are written up and then never scheduled (9)
Feature work always outranks reliability work in planning
There is no time set aside after an incident, so the write-up is done at midnight
Incidents are declared late because declaring one feels like blame
Load tests were last run before the customer base doubled
One engineer knows how the payment path actually works
Error budgets exist on a slide and nowhere else
The staging environment does not resemble production
The incident channel fills with people asking for status instead of giving it
Nobody owns the shared database schema
Retries are unbounded, so a slow dependency becomes a flood