Yapılandırma · Why does the same outage keep recurring?

SORU

Why does the same outage keep recurring?

Biri diğerini önemli ölçüde etkiler mi? Kullanılan oyların dörtte üçü karar verir.

Misafir olarak görüntülüyorsunuz. Katılmak için bir kullanıcı adı girin.

Sorular gruplar arasında paylaştırılır; bu yüzden sorulardan (180) hepsini değil, grubunuza verilenleri alırsınız.

neden

Kimse birkaç yüz çifti yanıtlayamaz. Her çift bir gruba gider; bölünen bir çift sonra diğer gruplara yönlendirilir, bu yüzden başka yerde başlamış olsa bile daha sonra listenizde görünebilir. Karara bağlananların sayısı her grubun çalışmasını içerir; bu yüzden kendi listenizin kısalmasından daha hızlı artar.

176 / 180 karara bağlandı yanıtlamanız gereken: 0

Son sayım: 176 karara bağlandı · 1 gruplar arası panellere aktarıldı · 0 tartışmalı · 3 yeter sayının altında — panellerde en az max(2, panelin %75’i) oy kullanılmalıdır; en küçük panelinizdeki üye sayısı: 15.

kapat ✕

Tests that fail intermittently are retried until green → etkiler mi? → One engineer knows how the payment path actually works

Henüz bir şey söylenmedi.

Tamamlanmış aşama — çiftlerin ve oyların kaydı yukarıda duruyor.Mantığı denetle ↗

Reliability has no budget line of its own	→	Feature flags are never cleaned up, so nobody knows which paths are live	açık	tartış
The same three services cause most of the pages	→	…	açık	tartış
The incident channel fills with people asking for status instead of giving it	→	The service map in the wiki is two years old	açık	tartış
The staging environment does not resemble production	→	Rollbacks take longer than the outage they are meant to end	açık aktarıldı	tartış
Tests that fail intermittently are retried until green	→	Customers report outages before monitoring does	✓ evet	tartış
Alerts fire so often that on-call mutes them	→	Customers report outages before monitoring does	✓ evet	tartış
Alerts fire so often that on-call mutes them	→	Every team has its own logging format	✓ evet	tartış
Every team has its own logging format	→	Customers report outages before monitoring does	✓ evet	tartış
The on-call rota has the same two people on it most weeks	→	Alerts fire so often that on-call mutes them	✓ evet	tartış
Feature work always outranks reliability work in planning	→	Post-mortem actions are written up and then never scheduled	✓ evet	tartış
One engineer knows how the payment path actually works	→	The on-call rota has the same two people on it most weeks	✓ evet	tartış
The on-call rota has the same two people on it most weeks	→	Post-mortem actions are written up and then never scheduled	✓ evet	tartış
Post-mortems assign actions to people who were not in the room	→	Post-mortem actions are written up and then never scheduled	✓ evet	tartış
The service map in the wiki is two years old	→	The staging environment does not resemble production	✓ evet	tartış
Rollbacks take longer than the outage they are meant to end	→	Reliability has no budget line of its own	✓ evet	tartış
Reliability has no budget line of its own	→	The staging environment does not resemble production	✓ evet	tartış
Retries are unbounded, so a slow dependency becomes a flood	→	The same three services cause most of the pages	✓ evet	tartış
Reliability has no budget line of its own	→	The incident channel fills with people asking for status instead of giving it	✓ evet	tartış
The same three services cause most of the pages	→	The staging environment does not resemble production	✓ evet	tartış
The service map in the wiki is two years old	→	Feature flags are never cleaned up, so nobody knows which paths are live	✓ evet	tartış
Feature flags are never cleaned up, so nobody knows which paths are live	→	Rollbacks take longer than the outage they are meant to end	✓ evet	tartış
Feature flags are never cleaned up, so nobody knows which paths are live	→	The same three services cause most of the pages	✓ evet	tartış
The on-call rota has the same two people on it most weeks	→	Customers report outages before monitoring does	✓ çıkarsandı	tartış
Retries are unbounded, so a slow dependency becomes a flood	→	The staging environment does not resemble production	✓ çıkarsandı	tartış
Post-mortem actions are written up and then never scheduled	→	Every team has its own logging format	✗ hayır	tartış
Every team has its own logging format	→	Error budgets exist on a slide and nowhere else	✗ hayır	tartış
Feature work always outranks reliability work in planning	→	Customers report outages before monitoring does	✗ hayır	tartış
Error budgets exist on a slide and nowhere else	→	Tests that fail intermittently are retried until green	✗ hayır	tartış
Error budgets exist on a slide and nowhere else	→	One engineer knows how the payment path actually works	✗ hayır	tartış
Error budgets exist on a slide and nowhere else	→	Post-mortems assign actions to people who were not in the room	✗ hayır	tartış
Customers report outages before monitoring does	→	Post-mortems assign actions to people who were not in the room	✗ hayır	tartış
Post-mortem actions are written up and then never scheduled	→	Alerts fire so often that on-call mutes them	✗ hayır	tartış
Post-mortems assign actions to people who were not in the room	→	Alerts fire so often that on-call mutes them	✗ hayır	tartış
Error budgets exist on a slide and nowhere else	→	Customers report outages before monitoring does	✗ hayır	tartış
Customers report outages before monitoring does	→	The on-call rota has the same two people on it most weeks	✗ hayır	tartış
Post-mortem actions are written up and then never scheduled	→	Post-mortems assign actions to people who were not in the room	✗ hayır	tartış
Feature work always outranks reliability work in planning	→	Tests that fail intermittently are retried until green	✗ hayır	tartış
Tests that fail intermittently are retried until green	→	The on-call rota has the same two people on it most weeks	✗ hayır	tartış
Post-mortem actions are written up and then never scheduled	→	The on-call rota has the same two people on it most weeks	✗ hayır	tartış
Feature work always outranks reliability work in planning	→	Error budgets exist on a slide and nowhere else	✗ hayır	tartış
Tests that fail intermittently are retried until green	→	Every team has its own logging format	✗ hayır	tartış
The on-call rota has the same two people on it most weeks	→	Tests that fail intermittently are retried until green	✗ hayır	tartış
Post-mortems assign actions to people who were not in the room	→	Every team has its own logging format	✗ hayır	tartış
Feature work always outranks reliability work in planning	→	Post-mortems assign actions to people who were not in the room	✗ hayır	tartış
Tests that fail intermittently are retried until green	→	Alerts fire so often that on-call mutes them	✗ hayır	tartış
Post-mortems assign actions to people who were not in the room	→	Error budgets exist on a slide and nowhere else	✗ hayır	tartış
Alerts fire so often that on-call mutes them	→	One engineer knows how the payment path actually works	✗ hayır	tartış
Customers report outages before monitoring does	→	One engineer knows how the payment path actually works	✗ hayır	tartış
Alerts fire so often that on-call mutes them	→	Post-mortem actions are written up and then never scheduled	✗ hayır	tartış
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	✗ hayır	tartış
One engineer knows how the payment path actually works	→	Alerts fire so often that on-call mutes them	✗ hayır	tartış
Customers report outages before monitoring does	→	Alerts fire so often that on-call mutes them	✗ hayır	tartış
Error budgets exist on a slide and nowhere else	→	The on-call rota has the same two people on it most weeks	✗ hayır	tartış
Feature work always outranks reliability work in planning	→	Every team has its own logging format	✗ hayır	tartış
Customers report outages before monitoring does	→	Post-mortem actions are written up and then never scheduled	✗ hayır	tartış
Customers report outages before monitoring does	→	Every team has its own logging format	✗ hayır	tartış
Customers report outages before monitoring does	→	Error budgets exist on a slide and nowhere else	✗ hayır	tartış
Post-mortem actions are written up and then never scheduled	→	One engineer knows how the payment path actually works	✗ hayır	tartış
Customers report outages before monitoring does	→	Tests that fail intermittently are retried until green	✗ hayır	tartış
Every team has its own logging format	→	The on-call rota has the same two people on it most weeks	✗ hayır	tartış
Every team has its own logging format	→	Post-mortems assign actions to people who were not in the room	✗ hayır	tartış
Every team has its own logging format	→	Post-mortem actions are written up and then never scheduled	✗ hayır	tartış
Post-mortem actions are written up and then never scheduled	→	Tests that fail intermittently are retried until green	✗ hayır	tartış
The on-call rota has the same two people on it most weeks	→	Error budgets exist on a slide and nowhere else	✗ hayır	tartış
Alerts fire so often that on-call mutes them	→	The on-call rota has the same two people on it most weeks	✗ hayır	tartış
One engineer knows how the payment path actually works	→	Tests that fail intermittently are retried until green	✗ hayır	tartış
Tests that fail intermittently are retried until green	→	Post-mortems assign actions to people who were not in the room	✗ hayır	tartış
Feature work always outranks reliability work in planning	→	Alerts fire so often that on-call mutes them	✗ hayır	tartış
Customers report outages before monitoring does	→	Feature work always outranks reliability work in planning	✗ hayır	tartış
One engineer knows how the payment path actually works	→	Customers report outages before monitoring does	✗ hayır	tartış
Post-mortems assign actions to people who were not in the room	→	Customers report outages before monitoring does	✗ hayır	tartış
Error budgets exist on a slide and nowhere else	→	Feature work always outranks reliability work in planning	✗ hayır	tartış
Alerts fire so often that on-call mutes them	→	Post-mortems assign actions to people who were not in the room	✗ hayır	tartış
One engineer knows how the payment path actually works	→	Post-mortem actions are written up and then never scheduled	✗ hayır	tartış
The on-call rota has the same two people on it most weeks	→	One engineer knows how the payment path actually works	✗ hayır	tartış
Tests that fail intermittently are retried until green	→	One engineer knows how the payment path actually works	✗ hayır	odakta ↑ · kapat ✕
The on-call rota has the same two people on it most weeks	→	Every team has its own logging format	✗ hayır	tartış
Alerts fire so often that on-call mutes them	→	Tests that fail intermittently are retried until green	✗ hayır	tartış
Every team has its own logging format	→	One engineer knows how the payment path actually works	✗ hayır	tartış
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	✗ hayır	tartış
Post-mortems assign actions to people who were not in the room	→	Tests that fail intermittently are retried until green	✗ hayır	tartış
Every team has its own logging format	→	Alerts fire so often that on-call mutes them	✗ hayır	tartış
The on-call rota has the same two people on it most weeks	→	Feature work always outranks reliability work in planning	✗ hayır	tartış
Tests that fail intermittently are retried until green	→	Feature work always outranks reliability work in planning	✗ hayır	tartış
Tests that fail intermittently are retried until green	→	Post-mortem actions are written up and then never scheduled	✗ hayır	tartış
Error budgets exist on a slide and nowhere else	→	Alerts fire so often that on-call mutes them	✗ hayır	tartış
Error budgets exist on a slide and nowhere else	→	Post-mortem actions are written up and then never scheduled	✗ hayır	tartış
Post-mortems assign actions to people who were not in the room	→	Feature work always outranks reliability work in planning	✗ hayır	tartış
One engineer knows how the payment path actually works	→	Feature work always outranks reliability work in planning	✗ hayır	tartış
Error budgets exist on a slide and nowhere else	→	Every team has its own logging format	✗ hayır	tartış
Tests that fail intermittently are retried until green	→	Error budgets exist on a slide and nowhere else	✗ hayır	tartış
Post-mortem actions are written up and then never scheduled	→	Error budgets exist on a slide and nowhere else	✗ hayır	tartış
Post-mortem actions are written up and then never scheduled	→	Customers report outages before monitoring does	✗ hayır	tartış
Every team has its own logging format	→	Tests that fail intermittently are retried until green	✗ hayır	tartış
One engineer knows how the payment path actually works	→	Post-mortems assign actions to people who were not in the room	✗ hayır	tartış
Feature work always outranks reliability work in planning	→	One engineer knows how the payment path actually works	✗ hayır	tartış
Every team has its own logging format	→	Feature work always outranks reliability work in planning	✗ hayır	tartış
One engineer knows how the payment path actually works	→	Error budgets exist on a slide and nowhere else	✗ hayır	tartış
Alerts fire so often that on-call mutes them	→	Error budgets exist on a slide and nowhere else	✗ hayır	tartış
Post-mortems assign actions to people who were not in the room	→	One engineer knows how the payment path actually works	✗ hayır	tartış
Alerts fire so often that on-call mutes them	→	Feature work always outranks reliability work in planning	✗ hayır	tartış
One engineer knows how the payment path actually works	→	Every team has its own logging format	✗ hayır	tartış
Feature work always outranks reliability work in planning	→	The on-call rota has the same two people on it most weeks	✗ hayır	tartış
Post-mortem actions are written up and then never scheduled	→	Feature work always outranks reliability work in planning	✗ hayır	tartış
The same three services cause most of the pages	→	The service map in the wiki is two years old	✗ hayır	tartış
Rollbacks take longer than the outage they are meant to end	→	The same three services cause most of the pages	✗ hayır	tartış
Config lives in five places and drifts between them	→	Rollbacks take longer than the outage they are meant to end	✗ hayır	tartış
…	→	The staging environment does not resemble production	✗ hayır	tartış
The incident channel fills with people asking for status instead of giving it	→	Config lives in five places and drifts between them	✗ hayır	tartış
Reliability has no budget line of its own	→	Retries are unbounded, so a slow dependency becomes a flood	✗ hayır	tartış
The incident channel fills with people asking for status instead of giving it	→	Rollbacks take longer than the outage they are meant to end	✗ hayır	tartış
The same three services cause most of the pages	→	The incident channel fills with people asking for status instead of giving it	✗ hayır	tartış
The service map in the wiki is two years old	→	Retries are unbounded, so a slow dependency becomes a flood	✗ hayır	tartış
Config lives in five places and drifts between them	→	Feature flags are never cleaned up, so nobody knows which paths are live	✗ hayır	tartış
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	✗ hayır	tartış
Retries are unbounded, so a slow dependency becomes a flood	→	The service map in the wiki is two years old	✗ hayır	tartış
…	→	Reliability has no budget line of its own	✗ hayır	tartış
The service map in the wiki is two years old	→	Rollbacks take longer than the outage they are meant to end	✗ hayır	tartış
Feature flags are never cleaned up, so nobody knows which paths are live	→	Reliability has no budget line of its own	✗ hayır	tartış
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	✗ hayır	tartış
Rollbacks take longer than the outage they are meant to end	→	…	✗ hayır	tartış
The incident channel fills with people asking for status instead of giving it	→	Reliability has no budget line of its own	✗ hayır	tartış
Config lives in five places and drifts between them	→	The staging environment does not resemble production	✗ hayır	tartış
…	→	Config lives in five places and drifts between them	✗ hayır	tartış
Feature flags are never cleaned up, so nobody knows which paths are live	→	…	✗ hayır	tartış
Reliability has no budget line of its own	→	Config lives in five places and drifts between them	✗ hayır	tartış
The incident channel fills with people asking for status instead of giving it	→	Retries are unbounded, so a slow dependency becomes a flood	✗ hayır	tartış
Rollbacks take longer than the outage they are meant to end	→	The incident channel fills with people asking for status instead of giving it	✗ hayır	tartış
The same three services cause most of the pages	→	Reliability has no budget line of its own	✗ hayır	tartış
…	→	Feature flags are never cleaned up, so nobody knows which paths are live	✗ hayır	tartış
Feature flags are never cleaned up, so nobody knows which paths are live	→	The service map in the wiki is two years old	✗ hayır	tartış
Config lives in five places and drifts between them	→	Reliability has no budget line of its own	✗ hayır	tartış
The staging environment does not resemble production	→	Feature flags are never cleaned up, so nobody knows which paths are live	✗ hayır	tartış
Rollbacks take longer than the outage they are meant to end	→	Feature flags are never cleaned up, so nobody knows which paths are live	✗ hayır	tartış
Retries are unbounded, so a slow dependency becomes a flood	→	Config lives in five places and drifts between them	✗ hayır	tartış
The service map in the wiki is two years old	→	Reliability has no budget line of its own	✗ hayır	tartış
The service map in the wiki is two years old	→	Config lives in five places and drifts between them	✗ hayır	tartış
The staging environment does not resemble production	→	Config lives in five places and drifts between them	✗ hayır	tartış
Rollbacks take longer than the outage they are meant to end	→	The service map in the wiki is two years old	✗ hayır	tartış
The staging environment does not resemble production	→	The service map in the wiki is two years old	✗ hayır	tartış
The staging environment does not resemble production	→	Retries are unbounded, so a slow dependency becomes a flood	✗ hayır	tartış
…	→	The same three services cause most of the pages	✗ hayır	tartış
Retries are unbounded, so a slow dependency becomes a flood	→	Feature flags are never cleaned up, so nobody knows which paths are live	✗ hayır	tartış
…	→	The service map in the wiki is two years old	✗ hayır	tartış
Config lives in five places and drifts between them	→	Retries are unbounded, so a slow dependency becomes a flood	✗ hayır	tartış
The staging environment does not resemble production	→	…	✗ hayır	tartış
Reliability has no budget line of its own	→	…	✗ hayır	tartış
The same three services cause most of the pages	→	Config lives in five places and drifts between them	✗ hayır	tartış
…	→	The incident channel fills with people asking for status instead of giving it	✗ hayır	tartış
Feature flags are never cleaned up, so nobody knows which paths are live	→	The staging environment does not resemble production	✗ hayır	tartış
Retries are unbounded, so a slow dependency becomes a flood	→	The incident channel fills with people asking for status instead of giving it	✗ hayır	tartış
Config lives in five places and drifts between them	→	…	✗ hayır	tartış
The staging environment does not resemble production	→	The same three services cause most of the pages	✗ hayır	tartış
Reliability has no budget line of its own	→	Rollbacks take longer than the outage they are meant to end	✗ hayır	tartış
Config lives in five places and drifts between them	→	The same three services cause most of the pages	✗ hayır	tartış
The staging environment does not resemble production	→	The incident channel fills with people asking for status instead of giving it	✗ hayır	tartış
Rollbacks take longer than the outage they are meant to end	→	The staging environment does not resemble production	✗ hayır	tartış
…	→	Rollbacks take longer than the outage they are meant to end	✗ hayır	tartış
Config lives in five places and drifts between them	→	The service map in the wiki is two years old	✗ hayır	tartış
The same three services cause most of the pages	→	Retries are unbounded, so a slow dependency becomes a flood	✗ hayır	tartış
Rollbacks take longer than the outage they are meant to end	→	Config lives in five places and drifts between them	✗ hayır	tartış
Reliability has no budget line of its own	→	The service map in the wiki is two years old	✗ hayır	tartış
Retries are unbounded, so a slow dependency becomes a flood	→	…	✗ hayır	tartış
Feature flags are never cleaned up, so nobody knows which paths are live	→	Config lives in five places and drifts between them	✗ hayır	tartış
Config lives in five places and drifts between them	→	The incident channel fills with people asking for status instead of giving it	✗ hayır	tartış
Feature flags are never cleaned up, so nobody knows which paths are live	→	Retries are unbounded, so a slow dependency becomes a flood	✗ hayır	tartış
The service map in the wiki is two years old	→	…	✗ hayır	tartış
The incident channel fills with people asking for status instead of giving it	→	The same three services cause most of the pages	✗ hayır	tartış
Rollbacks take longer than the outage they are meant to end	→	Retries are unbounded, so a slow dependency becomes a flood	✗ hayır	tartış
Reliability has no budget line of its own	→	The same three services cause most of the pages	✗ hayır	tartış
Retries are unbounded, so a slow dependency becomes a flood	→	Rollbacks take longer than the outage they are meant to end	✗ hayır	tartış
The same three services cause most of the pages	→	Feature flags are never cleaned up, so nobody knows which paths are live	✗ hayır	tartış
The service map in the wiki is two years old	→	The incident channel fills with people asking for status instead of giving it	✗ hayır	tartış
The service map in the wiki is two years old	→	The same three services cause most of the pages	✗ hayır	tartış
The incident channel fills with people asking for status instead of giving it	→	…	✗ hayır	tartış
The staging environment does not resemble production	→	Reliability has no budget line of its own	✗ hayır	tartış
The incident channel fills with people asking for status instead of giving it	→	The staging environment does not resemble production	✗ hayır	tartış
The same three services cause most of the pages	→	Rollbacks take longer than the outage they are meant to end	✗ hayır	tartış
…	→	Retries are unbounded, so a slow dependency becomes a flood	✗ hayır	tartış
Retries are unbounded, so a slow dependency becomes a flood	→	Reliability has no budget line of its own	✗ hayır	tartış