ПИТАННЯ
Why does the same outage keep recurring?
Чи суттєво одне впливає на інше? Вирішують три чверті поданих голосів.
закрито · назад до етапу Дії
Ви переглядаєте як гість. Введіть ім’я користувача, щоб приєднатися й брати участь.
Питання розподіляються між групами, тож ви отримуєте ті, що дісталися вашій групі, — а не всі 180.
вирішено: 176 / 180 чекають вашої відповіді: 0 чому
Ніхто не зміг би відповісти на кілька сотень пар. Кожна пара дістається одній групі; пару, у якій думки розділилися, потім передають іншим групам, тож вона може пізніше з’явитися у вашому списку, хоча почалася деінде. Кількість вирішених охоплює роботу всіх груп, тому вона росте швидше, ніж скорочується ваш список.
Останній підрахунок: вирішено: 176 · передано міжгруповим панелям: 1 · спірно: 0 · нижче кворуму: 3 — панелям потрібно щонайменше max(2, 75% панелі) поданих голосів; у вашій найменшій панелі 15 учасників.
Config lives in five places and drifts between them → впливає на? → The service map in the wiki is two years old
Ще нічого не сказано.
Етап завершено — запис пар і голосів наведено вище.Перевірити логіку ↗
| Reliability has no budget line of its own | → | Feature flags are never cleaned up, so nobody knows which paths are live | відкрито | обговорити |
| The same three services cause most of the pages | → | … | відкрито | обговорити |
| The incident channel fills with people asking for status instead of giving it | → | The service map in the wiki is two years old | відкрито | обговорити |
| The staging environment does not resemble production | → | Rollbacks take longer than the outage they are meant to end | відкрито передано далі | обговорити |
| Tests that fail intermittently are retried until green | → | Customers report outages before monitoring does | ✓ так | обговорити |
| Alerts fire so often that on-call mutes them | → | Customers report outages before monitoring does | ✓ так | обговорити |
| Alerts fire so often that on-call mutes them | → | Every team has its own logging format | ✓ так | обговорити |
| Every team has its own logging format | → | Customers report outages before monitoring does | ✓ так | обговорити |
| The on-call rota has the same two people on it most weeks | → | Alerts fire so often that on-call mutes them | ✓ так | обговорити |
| Feature work always outranks reliability work in planning | → | Post-mortem actions are written up and then never scheduled | ✓ так | обговорити |
| One engineer knows how the payment path actually works | → | The on-call rota has the same two people on it most weeks | ✓ так | обговорити |
| The on-call rota has the same two people on it most weeks | → | Post-mortem actions are written up and then never scheduled | ✓ так | обговорити |
| Post-mortems assign actions to people who were not in the room | → | Post-mortem actions are written up and then never scheduled | ✓ так | обговорити |
| The service map in the wiki is two years old | → | The staging environment does not resemble production | ✓ так | обговорити |
| Rollbacks take longer than the outage they are meant to end | → | Reliability has no budget line of its own | ✓ так | обговорити |
| Reliability has no budget line of its own | → | The staging environment does not resemble production | ✓ так | обговорити |
| Retries are unbounded, so a slow dependency becomes a flood | → | The same three services cause most of the pages | ✓ так | обговорити |
| Reliability has no budget line of its own | → | The incident channel fills with people asking for status instead of giving it | ✓ так | обговорити |
| The same three services cause most of the pages | → | The staging environment does not resemble production | ✓ так | обговорити |
| The service map in the wiki is two years old | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✓ так | обговорити |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | Rollbacks take longer than the outage they are meant to end | ✓ так | обговорити |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | The same three services cause most of the pages | ✓ так | обговорити |
| The on-call rota has the same two people on it most weeks | → | Customers report outages before monitoring does | ✓ виведено | обговорити |
| Retries are unbounded, so a slow dependency becomes a flood | → | The staging environment does not resemble production | ✓ виведено | обговорити |
| Post-mortem actions are written up and then never scheduled | → | Every team has its own logging format | ✗ ні | обговорити |
| Every team has its own logging format | → | Error budgets exist on a slide and nowhere else | ✗ ні | обговорити |
| Feature work always outranks reliability work in planning | → | Customers report outages before monitoring does | ✗ ні | обговорити |
| Error budgets exist on a slide and nowhere else | → | Tests that fail intermittently are retried until green | ✗ ні | обговорити |
| Error budgets exist on a slide and nowhere else | → | One engineer knows how the payment path actually works | ✗ ні | обговорити |
| Error budgets exist on a slide and nowhere else | → | Post-mortems assign actions to people who were not in the room | ✗ ні | обговорити |
| Customers report outages before monitoring does | → | Post-mortems assign actions to people who were not in the room | ✗ ні | обговорити |
| Post-mortem actions are written up and then never scheduled | → | Alerts fire so often that on-call mutes them | ✗ ні | обговорити |
| Post-mortems assign actions to people who were not in the room | → | Alerts fire so often that on-call mutes them | ✗ ні | обговорити |
| Error budgets exist on a slide and nowhere else | → | Customers report outages before monitoring does | ✗ ні | обговорити |
| Customers report outages before monitoring does | → | The on-call rota has the same two people on it most weeks | ✗ ні | обговорити |
| Post-mortem actions are written up and then never scheduled | → | Post-mortems assign actions to people who were not in the room | ✗ ні | обговорити |
| Feature work always outranks reliability work in planning | → | Tests that fail intermittently are retried until green | ✗ ні | обговорити |
| Tests that fail intermittently are retried until green | → | The on-call rota has the same two people on it most weeks | ✗ ні | обговорити |
| Post-mortem actions are written up and then never scheduled | → | The on-call rota has the same two people on it most weeks | ✗ ні | обговорити |
| Feature work always outranks reliability work in planning | → | Error budgets exist on a slide and nowhere else | ✗ ні | обговорити |
| Tests that fail intermittently are retried until green | → | Every team has its own logging format | ✗ ні | обговорити |
| The on-call rota has the same two people on it most weeks | → | Tests that fail intermittently are retried until green | ✗ ні | обговорити |
| Post-mortems assign actions to people who were not in the room | → | Every team has its own logging format | ✗ ні | обговорити |
| Feature work always outranks reliability work in planning | → | Post-mortems assign actions to people who were not in the room | ✗ ні | обговорити |
| Tests that fail intermittently are retried until green | → | Alerts fire so often that on-call mutes them | ✗ ні | обговорити |
| Post-mortems assign actions to people who were not in the room | → | Error budgets exist on a slide and nowhere else | ✗ ні | обговорити |
| Alerts fire so often that on-call mutes them | → | One engineer knows how the payment path actually works | ✗ ні | обговорити |
| Customers report outages before monitoring does | → | One engineer knows how the payment path actually works | ✗ ні | обговорити |
| Alerts fire so often that on-call mutes them | → | Post-mortem actions are written up and then never scheduled | ✗ ні | обговорити |
| 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 | ✗ ні | обговорити |
| One engineer knows how the payment path actually works | → | Alerts fire so often that on-call mutes them | ✗ ні | обговорити |
| Customers report outages before monitoring does | → | Alerts fire so often that on-call mutes them | ✗ ні | обговорити |
| Error budgets exist on a slide and nowhere else | → | The on-call rota has the same two people on it most weeks | ✗ ні | обговорити |
| Feature work always outranks reliability work in planning | → | Every team has its own logging format | ✗ ні | обговорити |
| Customers report outages before monitoring does | → | Post-mortem actions are written up and then never scheduled | ✗ ні | обговорити |
| Customers report outages before monitoring does | → | Every team has its own logging format | ✗ ні | обговорити |
| Customers report outages before monitoring does | → | Error budgets exist on a slide and nowhere else | ✗ ні | обговорити |
| Post-mortem actions are written up and then never scheduled | → | One engineer knows how the payment path actually works | ✗ ні | обговорити |
| Customers report outages before monitoring does | → | Tests that fail intermittently are retried until green | ✗ ні | обговорити |
| Every team has its own logging format | → | The on-call rota has the same two people on it most weeks | ✗ ні | обговорити |
| Every team has its own logging format | → | Post-mortems assign actions to people who were not in the room | ✗ ні | обговорити |
| Every team has its own logging format | → | Post-mortem actions are written up and then never scheduled | ✗ ні | обговорити |
| Post-mortem actions are written up and then never scheduled | → | Tests that fail intermittently are retried until green | ✗ ні | обговорити |
| The on-call rota has the same two people on it most weeks | → | Error budgets exist on a slide and nowhere else | ✗ ні | обговорити |
| Alerts fire so often that on-call mutes them | → | The on-call rota has the same two people on it most weeks | ✗ ні | обговорити |
| One engineer knows how the payment path actually works | → | Tests that fail intermittently are retried until green | ✗ ні | обговорити |
| Tests that fail intermittently are retried until green | → | Post-mortems assign actions to people who were not in the room | ✗ ні | обговорити |
| Feature work always outranks reliability work in planning | → | Alerts fire so often that on-call mutes them | ✗ ні | обговорити |
| Customers report outages before monitoring does | → | Feature work always outranks reliability work in planning | ✗ ні | обговорити |
| One engineer knows how the payment path actually works | → | Customers report outages before monitoring does | ✗ ні | обговорити |
| Post-mortems assign actions to people who were not in the room | → | Customers report outages before monitoring does | ✗ ні | обговорити |
| Error budgets exist on a slide and nowhere else | → | Feature work always outranks reliability work in planning | ✗ ні | обговорити |
| Alerts fire so often that on-call mutes them | → | Post-mortems assign actions to people who were not in the room | ✗ ні | обговорити |
| One engineer knows how the payment path actually works | → | Post-mortem actions are written up and then never scheduled | ✗ ні | обговорити |
| The on-call rota has the same two people on it most weeks | → | One engineer knows how the payment path actually works | ✗ ні | обговорити |
| Tests that fail intermittently are retried until green | → | One engineer knows how the payment path actually works | ✗ ні | обговорити |
| The on-call rota has the same two people on it most weeks | → | Every team has its own logging format | ✗ ні | обговорити |
| Alerts fire so often that on-call mutes them | → | Tests that fail intermittently are retried until green | ✗ ні | обговорити |
| Every team has its own logging format | → | One engineer knows how the payment path actually works | ✗ ні | обговорити |
| 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 | ✗ ні | обговорити |
| Post-mortems assign actions to people who were not in the room | → | Tests that fail intermittently are retried until green | ✗ ні | обговорити |
| Every team has its own logging format | → | Alerts fire so often that on-call mutes them | ✗ ні | обговорити |
| The on-call rota has the same two people on it most weeks | → | Feature work always outranks reliability work in planning | ✗ ні | обговорити |
| Tests that fail intermittently are retried until green | → | Feature work always outranks reliability work in planning | ✗ ні | обговорити |
| Tests that fail intermittently are retried until green | → | Post-mortem actions are written up and then never scheduled | ✗ ні | обговорити |
| Error budgets exist on a slide and nowhere else | → | Alerts fire so often that on-call mutes them | ✗ ні | обговорити |
| Error budgets exist on a slide and nowhere else | → | Post-mortem actions are written up and then never scheduled | ✗ ні | обговорити |
| Post-mortems assign actions to people who were not in the room | → | Feature work always outranks reliability work in planning | ✗ ні | обговорити |
| One engineer knows how the payment path actually works | → | Feature work always outranks reliability work in planning | ✗ ні | обговорити |
| Error budgets exist on a slide and nowhere else | → | Every team has its own logging format | ✗ ні | обговорити |
| Tests that fail intermittently are retried until green | → | Error budgets exist on a slide and nowhere else | ✗ ні | обговорити |
| Post-mortem actions are written up and then never scheduled | → | Error budgets exist on a slide and nowhere else | ✗ ні | обговорити |
| Post-mortem actions are written up and then never scheduled | → | Customers report outages before monitoring does | ✗ ні | обговорити |
| Every team has its own logging format | → | Tests that fail intermittently are retried until green | ✗ ні | обговорити |
| One engineer knows how the payment path actually works | → | Post-mortems assign actions to people who were not in the room | ✗ ні | обговорити |
| Feature work always outranks reliability work in planning | → | One engineer knows how the payment path actually works | ✗ ні | обговорити |
| Every team has its own logging format | → | Feature work always outranks reliability work in planning | ✗ ні | обговорити |
| One engineer knows how the payment path actually works | → | Error budgets exist on a slide and nowhere else | ✗ ні | обговорити |
| Alerts fire so often that on-call mutes them | → | Error budgets exist on a slide and nowhere else | ✗ ні | обговорити |
| Post-mortems assign actions to people who were not in the room | → | One engineer knows how the payment path actually works | ✗ ні | обговорити |
| Alerts fire so often that on-call mutes them | → | Feature work always outranks reliability work in planning | ✗ ні | обговорити |
| One engineer knows how the payment path actually works | → | Every team has its own logging format | ✗ ні | обговорити |
| Feature work always outranks reliability work in planning | → | The on-call rota has the same two people on it most weeks | ✗ ні | обговорити |
| Post-mortem actions are written up and then never scheduled | → | Feature work always outranks reliability work in planning | ✗ ні | обговорити |
| The same three services cause most of the pages | → | The service map in the wiki is two years old | ✗ ні | обговорити |
| Rollbacks take longer than the outage they are meant to end | → | The same three services cause most of the pages | ✗ ні | обговорити |
| Config lives in five places and drifts between them | → | Rollbacks take longer than the outage they are meant to end | ✗ ні | обговорити |
| … | → | The staging environment does not resemble production | ✗ ні | обговорити |
| The incident channel fills with people asking for status instead of giving it | → | Config lives in five places and drifts between them | ✗ ні | обговорити |
| Reliability has no budget line of its own | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ ні | обговорити |
| The incident channel fills with people asking for status instead of giving it | → | Rollbacks take longer than the outage they are meant to end | ✗ ні | обговорити |
| The same three services cause most of the pages | → | The incident channel fills with people asking for status instead of giving it | ✗ ні | обговорити |
| The service map in the wiki is two years old | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ ні | обговорити |
| Config lives in five places and drifts between them | → | 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 | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✗ ні | обговорити |
| Retries are unbounded, so a slow dependency becomes a flood | → | The service map in the wiki is two years old | ✗ ні | обговорити |
| … | → | Reliability has no budget line of its own | ✗ ні | обговорити |
| The service map in the wiki is two years old | → | Rollbacks take longer than the outage they are meant to end | ✗ ні | обговорити |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | Reliability has no budget line of its own | ✗ ні | обговорити |
| 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 | ✗ ні | обговорити |
| Rollbacks take longer than the outage they are meant to end | → | … | ✗ ні | обговорити |
| The incident channel fills with people asking for status instead of giving it | → | Reliability has no budget line of its own | ✗ ні | обговорити |
| Config lives in five places and drifts between them | → | The staging environment does not resemble production | ✗ ні | обговорити |
| … | → | Config lives in five places and drifts between them | ✗ ні | обговорити |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | … | ✗ ні | обговорити |
| Reliability has no budget line of its own | → | Config lives in five places and drifts between them | ✗ ні | обговорити |
| The incident channel fills with people asking for status instead of giving it | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ ні | обговорити |
| Rollbacks take longer than the outage they are meant to end | → | The incident channel fills with people asking for status instead of giving it | ✗ ні | обговорити |
| The same three services cause most of the pages | → | Reliability has no budget line of its own | ✗ ні | обговорити |
| … | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✗ ні | обговорити |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | The service map in the wiki is two years old | ✗ ні | обговорити |
| Config lives in five places and drifts between them | → | Reliability has no budget line of its own | ✗ ні | обговорити |
| The staging environment does not resemble production | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✗ ні | обговорити |
| Rollbacks take longer than the outage they are meant to end | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✗ ні | обговорити |
| Retries are unbounded, so a slow dependency becomes a flood | → | Config lives in five places and drifts between them | ✗ ні | обговорити |
| The service map in the wiki is two years old | → | Reliability has no budget line of its own | ✗ ні | обговорити |
| The service map in the wiki is two years old | → | Config lives in five places and drifts between them | ✗ ні | обговорити |
| The staging environment does not resemble production | → | Config lives in five places and drifts between them | ✗ ні | обговорити |
| Rollbacks take longer than the outage they are meant to end | → | The service map in the wiki is two years old | ✗ ні | обговорити |
| The staging environment does not resemble production | → | The service map in the wiki is two years old | ✗ ні | обговорити |
| The staging environment does not resemble production | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ ні | обговорити |
| … | → | The same three services cause most of the pages | ✗ ні | обговорити |
| Retries are unbounded, so a slow dependency becomes a flood | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✗ ні | обговорити |
| … | → | The service map in the wiki is two years old | ✗ ні | обговорити |
| Config lives in five places and drifts between them | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ ні | обговорити |
| The staging environment does not resemble production | → | … | ✗ ні | обговорити |
| Reliability has no budget line of its own | → | … | ✗ ні | обговорити |
| The same three services cause most of the pages | → | Config lives in five places and drifts between them | ✗ ні | обговорити |
| … | → | 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 | → | The staging environment does not resemble production | ✗ ні | обговорити |
| Retries are unbounded, so a slow dependency becomes a flood | → | The incident channel fills with people asking for status instead of giving it | ✗ ні | обговорити |
| Config lives in five places and drifts between them | → | … | ✗ ні | обговорити |
| The staging environment does not resemble production | → | The same three services cause most of the pages | ✗ ні | обговорити |
| Reliability has no budget line of its own | → | Rollbacks take longer than the outage they are meant to end | ✗ ні | обговорити |
| Config lives in five places and drifts between them | → | The same three services cause most of the pages | ✗ ні | обговорити |
| The staging environment does not resemble production | → | The incident channel fills with people asking for status instead of giving it | ✗ ні | обговорити |
| Rollbacks take longer than the outage they are meant to end | → | The staging environment does not resemble production | ✗ ні | обговорити |
| … | → | Rollbacks take longer than the outage they are meant to end | ✗ ні | обговорити |
| Config lives in five places and drifts between them | → | The service map in the wiki is two years old | ✗ ні | у фокусі ↑ · закрити ✕ |
| The same three services cause most of the pages | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ ні | обговорити |
| Rollbacks take longer than the outage they are meant to end | → | Config lives in five places and drifts between them | ✗ ні | обговорити |
| Reliability has no budget line of its own | → | The service map in the wiki is two years old | ✗ ні | обговорити |
| Retries are unbounded, so a slow dependency becomes a flood | → | … | ✗ ні | обговорити |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | Config lives in five places and drifts between them | ✗ ні | обговорити |
| Config lives in five places and drifts between them | → | 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 | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ ні | обговорити |
| The service map in the wiki is two years old | → | … | ✗ ні | обговорити |
| The incident channel fills with people asking for status instead of giving it | → | The same three services cause most of the pages | ✗ ні | обговорити |
| Rollbacks take longer than the outage they are meant to end | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ ні | обговорити |
| Reliability has no budget line of its own | → | The same three services cause most of the pages | ✗ ні | обговорити |
| Retries are unbounded, so a slow dependency becomes a flood | → | Rollbacks take longer than the outage they are meant to end | ✗ ні | обговорити |
| The same three services cause most of the pages | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✗ ні | обговорити |
| The service map in the wiki is two years old | → | The incident channel fills with people asking for status instead of giving it | ✗ ні | обговорити |
| The service map in the wiki is two years old | → | The same three services cause most of the pages | ✗ ні | обговорити |
| The incident channel fills with people asking for status instead of giving it | → | … | ✗ ні | обговорити |
| The staging environment does not resemble production | → | Reliability has no budget line of its own | ✗ ні | обговорити |
| The incident channel fills with people asking for status instead of giving it | → | The staging environment does not resemble production | ✗ ні | обговорити |
| The same three services cause most of the pages | → | Rollbacks take longer than the outage they are meant to end | ✗ ні | обговорити |
| … | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ ні | обговорити |
| Retries are unbounded, so a slow dependency becomes a flood | → | Reliability has no budget line of its own | ✗ ні | обговорити |