問い
Why does the same outage keep recurring?
何を言いたかったのかを説明します。2枚のカードは、両方の書き手が同意した場合にだけ統合されます。
終了 · 対策に戻る
ゲストとして閲覧中。参加するにはユーザー名を入力してください。
重複を統合
同じ主張をしている2枚のカードの場合だけです。
理由
統合は両方の書き手が同意したときにだけ行われます。統合する前に、カードの横のチャットで意味について議論してください。
統合済み "Action items from incident rev…" → "Post-mortem actions are writte…"
Config lives in five places and drifts between them
I mean the pattern over the last two quarters, not a single incident.
まとまり 3
まだ発言はありません。
Tests that fail intermittently are retried until green
Customers report outages before monitoring does
I mean the pattern over the last two quarters, not a single incident.
まとまり 5議論する
The on-call rota has the same two people on it most weeks
まとまり 1議論する
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.
Reliability has no budget line of its own
To be precise: this is about the process, not the person on call that night.
まとまり 4議論する
Every team has its own logging format
まとまり 4議論する
Success is measured in features shipped per quarter
Dependencies are upgraded only when something breaks
Meaning the repeat outages, not the one-off hardware failure in March.
The service map in the wiki is two years old
まとまり 6議論する
Deploys go out on Friday afternoons because that is when the sprint ends
Post-mortem actions are written up and then never scheduled
まとまり 2議論中（1）
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.
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.
まとまり 6議論中（1）
Migrations are run by hand from a laptop
まとまり 3議論する
Post-mortems assign actions to people who were not in the room
Scope: the services this team runs, not the whole platform.
Feature work always outranks reliability work in planning
Scope: the services this team runs, not the whole platform.
There is no time set aside after an incident, so the write-up is done at midnight
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.
まとまり 2議論する
Config lives in five places and drifts between them
I mean the pattern over the last two quarters, not a single incident.
Incidents are declared late because declaring one feels like blame
Load tests were last run before the customer base doubled
The same three services cause most of the pages
まとまり 1議論する
One engineer knows how the payment path actually works
Scope: the services this team runs, not the whole platform.
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
To be precise: this is about the process, not the person on call that night.
Retries are unbounded, so a slow dependency becomes a flood
Alerts fire so often that on-call mutes them
I mean the pattern over the last two quarters, not a single incident.
まとまり 5議論する
Capacity is added after the outage, never before