问题
Why does the same outage keep recurring?
把你的贴纸用在最重要的内容上。有证据支持的想法可以占用一个保留席位。
已关闭 · 返回行动阶段
正以访客身份查看。输入用户名即可加入并参与。
你的贴纸额度
每个想法最多一张，共 5 张。至少投一票。
有 5 个席位为被忽视的想法保留——附上链接提名一个，当 2 人认同来源相关时就会计入。
为什么
阶段结束时，一名被提名者通过随机抽签入选，其余按提名数入选，每个利益相关方类别最多一个。模型只检查页面是否关于同一主题——从不检查它是否证明了这个主张。那要由房间来判断；没有其他人支持的提名不能占用席位。
Alerts fire so often that on-call mutes them
I mean the pattern over the last two quarters, not a single incident.
类别 5
还没有人发言。
类别 1
The on-call rota has the same two people on it most weeks
7 票讨论
The same three services cause most of the pages
14 票讨论
类别 2
Post-mortem actions are written up and then never scheduled
4 票讨论
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.
7 票讨论
类别 3
Migrations are run by hand from a laptop
2 票讨论
Config lives in five places and drifts between them
I mean the pattern over the last two quarters, not a single incident.
3 票讨论
类别 4
Reliability has no budget line of its own
To be precise: this is about the process, not the person on call that night.
11 票讨论
Every team has its own logging format
3 票讨论
类别 5
Customers report outages before monitoring does
I mean the pattern over the last two quarters, not a single incident.
10 票讨论
Alerts fire so often that on-call mutes them
I mean the pattern over the last two quarters, not a single incident.
类别 6
The service map in the wiki is two years old
5 票讨论
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.
2 票讨论中（1）
未归类
Tests that fail intermittently are retried until green
10 票讨论
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.
1 票讨论
Success is measured in features shipped per quarter
1 票讨论
Dependencies are upgraded only when something breaks
Meaning the repeat outages, not the one-off hardware failure in March.
0 票讨论
Deploys go out on Friday afternoons because that is when the sprint ends
2 票讨论
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.
3 票讨论
Post-mortems assign actions to people who were not in the room
Scope: the services this team runs, not the whole platform.
8 票讨论中（1）
Feature work always outranks reliability work in planning
Scope: the services this team runs, not the whole platform.
4 票讨论
There is no time set aside after an incident, so the write-up is done at midnight
2 票讨论
Incidents are declared late because declaring one feels like blame
1 票讨论
Load tests were last run before the customer base doubled
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
8 票讨论
The staging environment does not resemble production
7 票讨论
The incident channel fills with people asking for status instead of giving it
3 票讨论
Nobody owns the shared database schema
To be precise: this is about the process, not the person on call that night.
2 票讨论
Retries are unbounded, so a slow dependency becomes a flood
6 票讨论
Capacity is added after the outage, never before
0 票讨论