PASOŠ · ŠTA JE OVA SOBA URADILA
Why does the same outage keep recurring?
Svaki red je iz zapisa. Ništa se ne izračunava za ovu stranicu i ništa se ne ulepšava: kratak spisak neslaganja znači sobu koja se složila, a ne sobu čija su neslaganja sklonjena.
| strukturira | prepreke |
| otvorena | 08 Sep 2026 |
| ko je odgovarao | ljudi: 30, grupa: 2 · učesnik: 30 |
| pisali naslepo | nije zabeleženo |
| tvrdnje | napisano: 30, strukturirano: 20 |
| potvrđene veze | 20 |
| sobe o ovom pitanju | 1 · ne računa se u zajedničkoj mapi |
| prag odluke | 75% datih glasova |
| zapečaćeno | da, članovi su zaboravljeni |
Na čemu počiva- The service map in the wiki is two years old
- One engineer knows how the payment path actually works
- Feature flags are never cleaned up, so nobody knows which paths are live
- The on-call rota has the same two people on it most weeks
- Rollbacks take longer than the outage they are meant to end
- Alerts fire so often that on-call mutes them
Šta soba nije mogla da rešiObjavljeno kao sporno, nikad zabeleženo kao „ne”.
- nema: svaki par do kog je soba stigla je rešen
Šta je predviđeno da uslediNapisano pošto je mapa rešena. Niko nije glasao o tome.
- No production deploy after 14:00 on Fridays unless the on-call engineer agrees — očekuje se: the same cause stops coming back once fixing it is in the sprint — rok: 23 Jan 2027
Šta bi soba uradilaSvaka akcija ocenjena prema svakom osnovnom uzroku, sa tri četvrtine datih glasova.
- No production deploy after 14:00 on Fridays unless the on-call engineer agrees
podeljeno: One engineer knows how the payment path actually works - Give the shared schema one named owner and a migration tool with rollback
smanjuje: One engineer knows how the payment path actually works - Reserve one engineer-week per sprint for post-mortem actions, first in the sprint, not last
ne smanjuje nijedan osnovni uzrok
← dijalog