ПИТАЊЕ
Why does the same outage keep recurring?
Да ли једно значајно утиче на друго? Одлучују три четвртине датих гласова.
затворено · назад на фазу Акције
Гледате као гост. Унесите корисничко име да бисте се придружили и учествовали.
Питања се расподељују између група, па добијате она која су дата вашој групи — не свих 180.
решено: 176 / 180 за ваш одговор: 0 зашто
Нико не би могао да одговори на неколико стотина парова. Сваки пар иде једној групи; пар на коме се панел подели затим се упућује другим групама, па може касније да се појави на вашем списку иако је почео негде другде. Број решених укључује рад свих група, зато расте брже него што се ваш списак смањује.
Последње пребројавање: решено: 176 · прослеђено панелима више група: 1 · спорно: 0 · испод кворума: 3 — панелима треба најмање max(2, 75% панела) датих гласова; ваш најмањи панел има 15 чланова.
The staging environment does not resemble production → утиче на? → 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 | отворено | дискутуј |
| 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 | ✗ не | дискутуј |