Cấu trúc · Why does the same outage keep recurring?

CÂU HỎI

Why does the same outage keep recurring?

Liệu cái này có ảnh hưởng đáng kể đến cái kia không? Ba phần tư số phiếu đã bỏ sẽ quyết định.

Đang xem với tư cách khách. Nhập tên người dùng để vào và tham gia.

Các câu hỏi được chia cho các nhóm, nên bạn nhận những câu được giao cho nhóm mình — không phải cả 180 câu.

vì sao

Không ai trả lời nổi vài trăm cặp thẻ. Mỗi cặp được giao cho một nhóm; cặp nào bị chia rẽ sẽ được chuyển sang các nhóm khác, nên nó có thể xuất hiện trong danh sách của bạn sau này dù bắt đầu ở nơi khác. Số đã ngã ngũ tính cả công việc của mọi nhóm, vì vậy nó tăng nhanh hơn tốc độ danh sách của bạn ngắn lại.

176 / 180 đã ngã ngũ 0 câu chờ bạn trả lời

Lần kiểm phiếu gần nhất: 176 đã quyết · 1 chuyển lên hội đồng liên nhóm · 0 còn tranh cãi · 3 chưa đủ số người tối thiểu — hội đồng cần ít nhất max(2, 75% hội đồng) phiếu đã bỏ; hội đồng nhỏ nhất của bạn có 15 thành viên.

đóng ✕

Feature flags are never cleaned up, so nobody knows which paths are live → ảnh hưởng? → The incident channel fills with people asking for status instead of giving it

Chưa ai nói gì.

Giai đoạn đã xong — hồ sơ các cặp thẻ và phiếu bầu nằm ở trên.Kiểm tra lập luận ↗

Reliability has no budget line of its own	→	Feature flags are never cleaned up, so nobody knows which paths are live	đang mở	thảo luận
The same three services cause most of the pages	→	…	đang mở	thảo luận
The incident channel fills with people asking for status instead of giving it	→	The service map in the wiki is two years old	đang mở	thảo luận
The staging environment does not resemble production	→	Rollbacks take longer than the outage they are meant to end	đang mở đã chuyển lên	thảo luận
Tests that fail intermittently are retried until green	→	Customers report outages before monitoring does	✓ có	thảo luận
Alerts fire so often that on-call mutes them	→	Customers report outages before monitoring does	✓ có	thảo luận
Alerts fire so often that on-call mutes them	→	Every team has its own logging format	✓ có	thảo luận
Every team has its own logging format	→	Customers report outages before monitoring does	✓ có	thảo luận
The on-call rota has the same two people on it most weeks	→	Alerts fire so often that on-call mutes them	✓ có	thảo luận
Feature work always outranks reliability work in planning	→	Post-mortem actions are written up and then never scheduled	✓ có	thảo luận
One engineer knows how the payment path actually works	→	The on-call rota has the same two people on it most weeks	✓ có	thảo luận
The on-call rota has the same two people on it most weeks	→	Post-mortem actions are written up and then never scheduled	✓ có	thảo luận
Post-mortems assign actions to people who were not in the room	→	Post-mortem actions are written up and then never scheduled	✓ có	thảo luận
The service map in the wiki is two years old	→	The staging environment does not resemble production	✓ có	thảo luận
Rollbacks take longer than the outage they are meant to end	→	Reliability has no budget line of its own	✓ có	thảo luận
Reliability has no budget line of its own	→	The staging environment does not resemble production	✓ có	thảo luận
Retries are unbounded, so a slow dependency becomes a flood	→	The same three services cause most of the pages	✓ có	thảo luận
Reliability has no budget line of its own	→	The incident channel fills with people asking for status instead of giving it	✓ có	thảo luận
The same three services cause most of the pages	→	The staging environment does not resemble production	✓ có	thảo luận
The service map in the wiki is two years old	→	Feature flags are never cleaned up, so nobody knows which paths are live	✓ có	thảo luận
Feature flags are never cleaned up, so nobody knows which paths are live	→	Rollbacks take longer than the outage they are meant to end	✓ có	thảo luận
Feature flags are never cleaned up, so nobody knows which paths are live	→	The same three services cause most of the pages	✓ có	thảo luận
The on-call rota has the same two people on it most weeks	→	Customers report outages before monitoring does	✓ suy ra	thảo luận
Retries are unbounded, so a slow dependency becomes a flood	→	The staging environment does not resemble production	✓ suy ra	thảo luận
Post-mortem actions are written up and then never scheduled	→	Every team has its own logging format	✗ không	thảo luận
Every team has its own logging format	→	Error budgets exist on a slide and nowhere else	✗ không	thảo luận
Feature work always outranks reliability work in planning	→	Customers report outages before monitoring does	✗ không	thảo luận
Error budgets exist on a slide and nowhere else	→	Tests that fail intermittently are retried until green	✗ không	thảo luận
Error budgets exist on a slide and nowhere else	→	One engineer knows how the payment path actually works	✗ không	thảo luận
Error budgets exist on a slide and nowhere else	→	Post-mortems assign actions to people who were not in the room	✗ không	thảo luận
Customers report outages before monitoring does	→	Post-mortems assign actions to people who were not in the room	✗ không	thảo luận
Post-mortem actions are written up and then never scheduled	→	Alerts fire so often that on-call mutes them	✗ không	thảo luận
Post-mortems assign actions to people who were not in the room	→	Alerts fire so often that on-call mutes them	✗ không	thảo luận
Error budgets exist on a slide and nowhere else	→	Customers report outages before monitoring does	✗ không	thảo luận
Customers report outages before monitoring does	→	The on-call rota has the same two people on it most weeks	✗ không	thảo luận
Post-mortem actions are written up and then never scheduled	→	Post-mortems assign actions to people who were not in the room	✗ không	thảo luận
Feature work always outranks reliability work in planning	→	Tests that fail intermittently are retried until green	✗ không	thảo luận
Tests that fail intermittently are retried until green	→	The on-call rota has the same two people on it most weeks	✗ không	thảo luận
Post-mortem actions are written up and then never scheduled	→	The on-call rota has the same two people on it most weeks	✗ không	thảo luận
Feature work always outranks reliability work in planning	→	Error budgets exist on a slide and nowhere else	✗ không	thảo luận
Tests that fail intermittently are retried until green	→	Every team has its own logging format	✗ không	thảo luận
The on-call rota has the same two people on it most weeks	→	Tests that fail intermittently are retried until green	✗ không	thảo luận
Post-mortems assign actions to people who were not in the room	→	Every team has its own logging format	✗ không	thảo luận
Feature work always outranks reliability work in planning	→	Post-mortems assign actions to people who were not in the room	✗ không	thảo luận
Tests that fail intermittently are retried until green	→	Alerts fire so often that on-call mutes them	✗ không	thảo luận
Post-mortems assign actions to people who were not in the room	→	Error budgets exist on a slide and nowhere else	✗ không	thảo luận
Alerts fire so often that on-call mutes them	→	One engineer knows how the payment path actually works	✗ không	thảo luận
Customers report outages before monitoring does	→	One engineer knows how the payment path actually works	✗ không	thảo luận
Alerts fire so often that on-call mutes them	→	Post-mortem actions are written up and then never scheduled	✗ không	thảo luận
Post-mortems assign actions to people who were not in the room	→	The on-call rota has the same two people on it most weeks	✗ không	thảo luận
One engineer knows how the payment path actually works	→	Alerts fire so often that on-call mutes them	✗ không	thảo luận
Customers report outages before monitoring does	→	Alerts fire so often that on-call mutes them	✗ không	thảo luận
Error budgets exist on a slide and nowhere else	→	The on-call rota has the same two people on it most weeks	✗ không	thảo luận
Feature work always outranks reliability work in planning	→	Every team has its own logging format	✗ không	thảo luận
Customers report outages before monitoring does	→	Post-mortem actions are written up and then never scheduled	✗ không	thảo luận
Customers report outages before monitoring does	→	Every team has its own logging format	✗ không	thảo luận
Customers report outages before monitoring does	→	Error budgets exist on a slide and nowhere else	✗ không	thảo luận
Post-mortem actions are written up and then never scheduled	→	One engineer knows how the payment path actually works	✗ không	thảo luận
Customers report outages before monitoring does	→	Tests that fail intermittently are retried until green	✗ không	thảo luận
Every team has its own logging format	→	The on-call rota has the same two people on it most weeks	✗ không	thảo luận
Every team has its own logging format	→	Post-mortems assign actions to people who were not in the room	✗ không	thảo luận
Every team has its own logging format	→	Post-mortem actions are written up and then never scheduled	✗ không	thảo luận
Post-mortem actions are written up and then never scheduled	→	Tests that fail intermittently are retried until green	✗ không	thảo luận
The on-call rota has the same two people on it most weeks	→	Error budgets exist on a slide and nowhere else	✗ không	thảo luận
Alerts fire so often that on-call mutes them	→	The on-call rota has the same two people on it most weeks	✗ không	thảo luận
One engineer knows how the payment path actually works	→	Tests that fail intermittently are retried until green	✗ không	thảo luận
Tests that fail intermittently are retried until green	→	Post-mortems assign actions to people who were not in the room	✗ không	thảo luận
Feature work always outranks reliability work in planning	→	Alerts fire so often that on-call mutes them	✗ không	thảo luận
Customers report outages before monitoring does	→	Feature work always outranks reliability work in planning	✗ không	thảo luận
One engineer knows how the payment path actually works	→	Customers report outages before monitoring does	✗ không	thảo luận
Post-mortems assign actions to people who were not in the room	→	Customers report outages before monitoring does	✗ không	thảo luận
Error budgets exist on a slide and nowhere else	→	Feature work always outranks reliability work in planning	✗ không	thảo luận
Alerts fire so often that on-call mutes them	→	Post-mortems assign actions to people who were not in the room	✗ không	thảo luận
One engineer knows how the payment path actually works	→	Post-mortem actions are written up and then never scheduled	✗ không	thảo luận
The on-call rota has the same two people on it most weeks	→	One engineer knows how the payment path actually works	✗ không	thảo luận
Tests that fail intermittently are retried until green	→	One engineer knows how the payment path actually works	✗ không	thảo luận
The on-call rota has the same two people on it most weeks	→	Every team has its own logging format	✗ không	thảo luận
Alerts fire so often that on-call mutes them	→	Tests that fail intermittently are retried until green	✗ không	thảo luận
Every team has its own logging format	→	One engineer knows how the payment path actually works	✗ không	thảo luận
The on-call rota has the same two people on it most weeks	→	Post-mortems assign actions to people who were not in the room	✗ không	thảo luận
Post-mortems assign actions to people who were not in the room	→	Tests that fail intermittently are retried until green	✗ không	thảo luận
Every team has its own logging format	→	Alerts fire so often that on-call mutes them	✗ không	thảo luận
The on-call rota has the same two people on it most weeks	→	Feature work always outranks reliability work in planning	✗ không	thảo luận
Tests that fail intermittently are retried until green	→	Feature work always outranks reliability work in planning	✗ không	thảo luận
Tests that fail intermittently are retried until green	→	Post-mortem actions are written up and then never scheduled	✗ không	thảo luận
Error budgets exist on a slide and nowhere else	→	Alerts fire so often that on-call mutes them	✗ không	thảo luận
Error budgets exist on a slide and nowhere else	→	Post-mortem actions are written up and then never scheduled	✗ không	thảo luận
Post-mortems assign actions to people who were not in the room	→	Feature work always outranks reliability work in planning	✗ không	thảo luận
One engineer knows how the payment path actually works	→	Feature work always outranks reliability work in planning	✗ không	thảo luận
Error budgets exist on a slide and nowhere else	→	Every team has its own logging format	✗ không	thảo luận
Tests that fail intermittently are retried until green	→	Error budgets exist on a slide and nowhere else	✗ không	thảo luận
Post-mortem actions are written up and then never scheduled	→	Error budgets exist on a slide and nowhere else	✗ không	thảo luận
Post-mortem actions are written up and then never scheduled	→	Customers report outages before monitoring does	✗ không	thảo luận
Every team has its own logging format	→	Tests that fail intermittently are retried until green	✗ không	thảo luận
One engineer knows how the payment path actually works	→	Post-mortems assign actions to people who were not in the room	✗ không	thảo luận
Feature work always outranks reliability work in planning	→	One engineer knows how the payment path actually works	✗ không	thảo luận
Every team has its own logging format	→	Feature work always outranks reliability work in planning	✗ không	thảo luận
One engineer knows how the payment path actually works	→	Error budgets exist on a slide and nowhere else	✗ không	thảo luận
Alerts fire so often that on-call mutes them	→	Error budgets exist on a slide and nowhere else	✗ không	thảo luận
Post-mortems assign actions to people who were not in the room	→	One engineer knows how the payment path actually works	✗ không	thảo luận
Alerts fire so often that on-call mutes them	→	Feature work always outranks reliability work in planning	✗ không	thảo luận
One engineer knows how the payment path actually works	→	Every team has its own logging format	✗ không	thảo luận
Feature work always outranks reliability work in planning	→	The on-call rota has the same two people on it most weeks	✗ không	thảo luận
Post-mortem actions are written up and then never scheduled	→	Feature work always outranks reliability work in planning	✗ không	thảo luận
The same three services cause most of the pages	→	The service map in the wiki is two years old	✗ không	thảo luận
Rollbacks take longer than the outage they are meant to end	→	The same three services cause most of the pages	✗ không	thảo luận
Config lives in five places and drifts between them	→	Rollbacks take longer than the outage they are meant to end	✗ không	thảo luận
…	→	The staging environment does not resemble production	✗ không	thảo luận
The incident channel fills with people asking for status instead of giving it	→	Config lives in five places and drifts between them	✗ không	thảo luận
Reliability has no budget line of its own	→	Retries are unbounded, so a slow dependency becomes a flood	✗ không	thảo luận
The incident channel fills with people asking for status instead of giving it	→	Rollbacks take longer than the outage they are meant to end	✗ không	thảo luận
The same three services cause most of the pages	→	The incident channel fills with people asking for status instead of giving it	✗ không	thảo luận
The service map in the wiki is two years old	→	Retries are unbounded, so a slow dependency becomes a flood	✗ không	thảo luận
Config lives in five places and drifts between them	→	Feature flags are never cleaned up, so nobody knows which paths are live	✗ không	thảo luận
The incident channel fills with people asking for status instead of giving it	→	Feature flags are never cleaned up, so nobody knows which paths are live	✗ không	thảo luận
Retries are unbounded, so a slow dependency becomes a flood	→	The service map in the wiki is two years old	✗ không	thảo luận
…	→	Reliability has no budget line of its own	✗ không	thảo luận
The service map in the wiki is two years old	→	Rollbacks take longer than the outage they are meant to end	✗ không	thảo luận
Feature flags are never cleaned up, so nobody knows which paths are live	→	Reliability has no budget line of its own	✗ không	thảo luận
Feature flags are never cleaned up, so nobody knows which paths are live	→	The incident channel fills with people asking for status instead of giving it	✗ không	đang mở ↑ · đóng ✕
Rollbacks take longer than the outage they are meant to end	→	…	✗ không	thảo luận
The incident channel fills with people asking for status instead of giving it	→	Reliability has no budget line of its own	✗ không	thảo luận
Config lives in five places and drifts between them	→	The staging environment does not resemble production	✗ không	thảo luận
…	→	Config lives in five places and drifts between them	✗ không	thảo luận
Feature flags are never cleaned up, so nobody knows which paths are live	→	…	✗ không	thảo luận
Reliability has no budget line of its own	→	Config lives in five places and drifts between them	✗ không	thảo luận
The incident channel fills with people asking for status instead of giving it	→	Retries are unbounded, so a slow dependency becomes a flood	✗ không	thảo luận
Rollbacks take longer than the outage they are meant to end	→	The incident channel fills with people asking for status instead of giving it	✗ không	thảo luận
The same three services cause most of the pages	→	Reliability has no budget line of its own	✗ không	thảo luận
…	→	Feature flags are never cleaned up, so nobody knows which paths are live	✗ không	thảo luận
Feature flags are never cleaned up, so nobody knows which paths are live	→	The service map in the wiki is two years old	✗ không	thảo luận
Config lives in five places and drifts between them	→	Reliability has no budget line of its own	✗ không	thảo luận
The staging environment does not resemble production	→	Feature flags are never cleaned up, so nobody knows which paths are live	✗ không	thảo luận
Rollbacks take longer than the outage they are meant to end	→	Feature flags are never cleaned up, so nobody knows which paths are live	✗ không	thảo luận
Retries are unbounded, so a slow dependency becomes a flood	→	Config lives in five places and drifts between them	✗ không	thảo luận
The service map in the wiki is two years old	→	Reliability has no budget line of its own	✗ không	thảo luận
The service map in the wiki is two years old	→	Config lives in five places and drifts between them	✗ không	thảo luận
The staging environment does not resemble production	→	Config lives in five places and drifts between them	✗ không	thảo luận
Rollbacks take longer than the outage they are meant to end	→	The service map in the wiki is two years old	✗ không	thảo luận
The staging environment does not resemble production	→	The service map in the wiki is two years old	✗ không	thảo luận
The staging environment does not resemble production	→	Retries are unbounded, so a slow dependency becomes a flood	✗ không	thảo luận
…	→	The same three services cause most of the pages	✗ không	thảo luận
Retries are unbounded, so a slow dependency becomes a flood	→	Feature flags are never cleaned up, so nobody knows which paths are live	✗ không	thảo luận
…	→	The service map in the wiki is two years old	✗ không	thảo luận
Config lives in five places and drifts between them	→	Retries are unbounded, so a slow dependency becomes a flood	✗ không	thảo luận
The staging environment does not resemble production	→	…	✗ không	thảo luận
Reliability has no budget line of its own	→	…	✗ không	thảo luận
The same three services cause most of the pages	→	Config lives in five places and drifts between them	✗ không	thảo luận
…	→	The incident channel fills with people asking for status instead of giving it	✗ không	thảo luận
Feature flags are never cleaned up, so nobody knows which paths are live	→	The staging environment does not resemble production	✗ không	thảo luận
Retries are unbounded, so a slow dependency becomes a flood	→	The incident channel fills with people asking for status instead of giving it	✗ không	thảo luận
Config lives in five places and drifts between them	→	…	✗ không	thảo luận
The staging environment does not resemble production	→	The same three services cause most of the pages	✗ không	thảo luận
Reliability has no budget line of its own	→	Rollbacks take longer than the outage they are meant to end	✗ không	thảo luận
Config lives in five places and drifts between them	→	The same three services cause most of the pages	✗ không	thảo luận
The staging environment does not resemble production	→	The incident channel fills with people asking for status instead of giving it	✗ không	thảo luận
Rollbacks take longer than the outage they are meant to end	→	The staging environment does not resemble production	✗ không	thảo luận
…	→	Rollbacks take longer than the outage they are meant to end	✗ không	thảo luận
Config lives in five places and drifts between them	→	The service map in the wiki is two years old	✗ không	thảo luận
The same three services cause most of the pages	→	Retries are unbounded, so a slow dependency becomes a flood	✗ không	thảo luận
Rollbacks take longer than the outage they are meant to end	→	Config lives in five places and drifts between them	✗ không	thảo luận
Reliability has no budget line of its own	→	The service map in the wiki is two years old	✗ không	thảo luận
Retries are unbounded, so a slow dependency becomes a flood	→	…	✗ không	thảo luận
Feature flags are never cleaned up, so nobody knows which paths are live	→	Config lives in five places and drifts between them	✗ không	thảo luận
Config lives in five places and drifts between them	→	The incident channel fills with people asking for status instead of giving it	✗ không	thảo luận
Feature flags are never cleaned up, so nobody knows which paths are live	→	Retries are unbounded, so a slow dependency becomes a flood	✗ không	thảo luận
The service map in the wiki is two years old	→	…	✗ không	thảo luận
The incident channel fills with people asking for status instead of giving it	→	The same three services cause most of the pages	✗ không	thảo luận
Rollbacks take longer than the outage they are meant to end	→	Retries are unbounded, so a slow dependency becomes a flood	✗ không	thảo luận
Reliability has no budget line of its own	→	The same three services cause most of the pages	✗ không	thảo luận
Retries are unbounded, so a slow dependency becomes a flood	→	Rollbacks take longer than the outage they are meant to end	✗ không	thảo luận
The same three services cause most of the pages	→	Feature flags are never cleaned up, so nobody knows which paths are live	✗ không	thảo luận
The service map in the wiki is two years old	→	The incident channel fills with people asking for status instead of giving it	✗ không	thảo luận
The service map in the wiki is two years old	→	The same three services cause most of the pages	✗ không	thảo luận
The incident channel fills with people asking for status instead of giving it	→	…	✗ không	thảo luận
The staging environment does not resemble production	→	Reliability has no budget line of its own	✗ không	thảo luận
The incident channel fills with people asking for status instead of giving it	→	The staging environment does not resemble production	✗ không	thảo luận
The same three services cause most of the pages	→	Rollbacks take longer than the outage they are meant to end	✗ không	thảo luận
…	→	Retries are unbounded, so a slow dependency becomes a flood	✗ không	thảo luận
Retries are unbounded, so a slow dependency becomes a flood	→	Reliability has no budget line of its own	✗ không	thảo luận