FRÅGAN
Why does the same outage keep recurring?
Har det ena betydande inverkan på det andra? Tre fjärdedelar av de avgivna rösterna avgör.
stängt · tillbaka till fasen Åtgärder
Du tittar som gäst. Ange ett användarnamn för att gå med och delta.
Frågorna fördelas mellan grupperna, så du får dem som din grupp tilldelades — inte alla 180.
176 / 180 avgjorda 0 för dig att besvara varför
Ingen skulle kunna svara på flera hundra par. Varje par går till en grupp; ett par som blir delat skickas sedan vidare till andra grupper, så det kan dyka upp i din lista senare trots att det började någon annanstans. Antalet avgjorda omfattar varje grupps arbete, och därför stiger det snabbare än din egen lista krymper.
Senaste sammanräkning: avgjorda 176 · skickade vidare till paneler över grupperna 1 · omstridda 0 · under kvorum 3 — paneler behöver minst max(2, 75 % av panelen) avgivna röster; din minsta panel har 15 medlemmar.
Rollbacks take longer than the outage they are meant to end → påverkar? → Reliability has no budget line of its own
Inget sagt än.
Avslutad fas — protokollet över par och röster står ovan.Kontrollera logiken ↗
| Reliability has no budget line of its own | → | Feature flags are never cleaned up, so nobody knows which paths are live | öppen | diskutera |
| The same three services cause most of the pages | → | … | öppen | diskutera |
| The incident channel fills with people asking for status instead of giving it | → | The service map in the wiki is two years old | öppen | diskutera |
| The staging environment does not resemble production | → | Rollbacks take longer than the outage they are meant to end | öppen vidareskickat | diskutera |
| Tests that fail intermittently are retried until green | → | Customers report outages before monitoring does | ✓ ja | diskutera |
| Alerts fire so often that on-call mutes them | → | Customers report outages before monitoring does | ✓ ja | diskutera |
| Alerts fire so often that on-call mutes them | → | Every team has its own logging format | ✓ ja | diskutera |
| Every team has its own logging format | → | Customers report outages before monitoring does | ✓ ja | diskutera |
| The on-call rota has the same two people on it most weeks | → | Alerts fire so often that on-call mutes them | ✓ ja | diskutera |
| Feature work always outranks reliability work in planning | → | Post-mortem actions are written up and then never scheduled | ✓ ja | diskutera |
| One engineer knows how the payment path actually works | → | The on-call rota has the same two people on it most weeks | ✓ ja | diskutera |
| The on-call rota has the same two people on it most weeks | → | Post-mortem actions are written up and then never scheduled | ✓ ja | diskutera |
| Post-mortems assign actions to people who were not in the room | → | Post-mortem actions are written up and then never scheduled | ✓ ja | diskutera |
| The service map in the wiki is two years old | → | The staging environment does not resemble production | ✓ ja | diskutera |
| Rollbacks take longer than the outage they are meant to end | → | Reliability has no budget line of its own | ✓ ja | i fokus ↑ · stäng ✕ |
| Reliability has no budget line of its own | → | The staging environment does not resemble production | ✓ ja | diskutera |
| Retries are unbounded, so a slow dependency becomes a flood | → | The same three services cause most of the pages | ✓ ja | diskutera |
| Reliability has no budget line of its own | → | The incident channel fills with people asking for status instead of giving it | ✓ ja | diskutera |
| The same three services cause most of the pages | → | The staging environment does not resemble production | ✓ ja | diskutera |
| The service map in the wiki is two years old | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✓ ja | diskutera |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | Rollbacks take longer than the outage they are meant to end | ✓ ja | diskutera |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | The same three services cause most of the pages | ✓ ja | diskutera |
| The on-call rota has the same two people on it most weeks | → | Customers report outages before monitoring does | ✓ härledd | diskutera |
| Retries are unbounded, so a slow dependency becomes a flood | → | The staging environment does not resemble production | ✓ härledd | diskutera |
| Post-mortem actions are written up and then never scheduled | → | Every team has its own logging format | ✗ nej | diskutera |
| Every team has its own logging format | → | Error budgets exist on a slide and nowhere else | ✗ nej | diskutera |
| Feature work always outranks reliability work in planning | → | Customers report outages before monitoring does | ✗ nej | diskutera |
| Error budgets exist on a slide and nowhere else | → | Tests that fail intermittently are retried until green | ✗ nej | diskutera |
| Error budgets exist on a slide and nowhere else | → | One engineer knows how the payment path actually works | ✗ nej | diskutera |
| Error budgets exist on a slide and nowhere else | → | Post-mortems assign actions to people who were not in the room | ✗ nej | diskutera |
| Customers report outages before monitoring does | → | Post-mortems assign actions to people who were not in the room | ✗ nej | diskutera |
| Post-mortem actions are written up and then never scheduled | → | Alerts fire so often that on-call mutes them | ✗ nej | diskutera |
| Post-mortems assign actions to people who were not in the room | → | Alerts fire so often that on-call mutes them | ✗ nej | diskutera |
| Error budgets exist on a slide and nowhere else | → | Customers report outages before monitoring does | ✗ nej | diskutera |
| Customers report outages before monitoring does | → | The on-call rota has the same two people on it most weeks | ✗ nej | diskutera |
| Post-mortem actions are written up and then never scheduled | → | Post-mortems assign actions to people who were not in the room | ✗ nej | diskutera |
| Feature work always outranks reliability work in planning | → | Tests that fail intermittently are retried until green | ✗ nej | diskutera |
| Tests that fail intermittently are retried until green | → | The on-call rota has the same two people on it most weeks | ✗ nej | diskutera |
| Post-mortem actions are written up and then never scheduled | → | The on-call rota has the same two people on it most weeks | ✗ nej | diskutera |
| Feature work always outranks reliability work in planning | → | Error budgets exist on a slide and nowhere else | ✗ nej | diskutera |
| Tests that fail intermittently are retried until green | → | Every team has its own logging format | ✗ nej | diskutera |
| The on-call rota has the same two people on it most weeks | → | Tests that fail intermittently are retried until green | ✗ nej | diskutera |
| Post-mortems assign actions to people who were not in the room | → | Every team has its own logging format | ✗ nej | diskutera |
| Feature work always outranks reliability work in planning | → | Post-mortems assign actions to people who were not in the room | ✗ nej | diskutera |
| Tests that fail intermittently are retried until green | → | Alerts fire so often that on-call mutes them | ✗ nej | diskutera |
| Post-mortems assign actions to people who were not in the room | → | Error budgets exist on a slide and nowhere else | ✗ nej | diskutera |
| Alerts fire so often that on-call mutes them | → | One engineer knows how the payment path actually works | ✗ nej | diskutera |
| Customers report outages before monitoring does | → | One engineer knows how the payment path actually works | ✗ nej | diskutera |
| Alerts fire so often that on-call mutes them | → | Post-mortem actions are written up and then never scheduled | ✗ nej | diskutera |
| 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 | ✗ nej | diskutera |
| One engineer knows how the payment path actually works | → | Alerts fire so often that on-call mutes them | ✗ nej | diskutera |
| Customers report outages before monitoring does | → | Alerts fire so often that on-call mutes them | ✗ nej | diskutera |
| Error budgets exist on a slide and nowhere else | → | The on-call rota has the same two people on it most weeks | ✗ nej | diskutera |
| Feature work always outranks reliability work in planning | → | Every team has its own logging format | ✗ nej | diskutera |
| Customers report outages before monitoring does | → | Post-mortem actions are written up and then never scheduled | ✗ nej | diskutera |
| Customers report outages before monitoring does | → | Every team has its own logging format | ✗ nej | diskutera |
| Customers report outages before monitoring does | → | Error budgets exist on a slide and nowhere else | ✗ nej | diskutera |
| Post-mortem actions are written up and then never scheduled | → | One engineer knows how the payment path actually works | ✗ nej | diskutera |
| Customers report outages before monitoring does | → | Tests that fail intermittently are retried until green | ✗ nej | diskutera |
| Every team has its own logging format | → | The on-call rota has the same two people on it most weeks | ✗ nej | diskutera |
| Every team has its own logging format | → | Post-mortems assign actions to people who were not in the room | ✗ nej | diskutera |
| Every team has its own logging format | → | Post-mortem actions are written up and then never scheduled | ✗ nej | diskutera |
| Post-mortem actions are written up and then never scheduled | → | Tests that fail intermittently are retried until green | ✗ nej | diskutera |
| The on-call rota has the same two people on it most weeks | → | Error budgets exist on a slide and nowhere else | ✗ nej | diskutera |
| Alerts fire so often that on-call mutes them | → | The on-call rota has the same two people on it most weeks | ✗ nej | diskutera |
| One engineer knows how the payment path actually works | → | Tests that fail intermittently are retried until green | ✗ nej | diskutera |
| Tests that fail intermittently are retried until green | → | Post-mortems assign actions to people who were not in the room | ✗ nej | diskutera |
| Feature work always outranks reliability work in planning | → | Alerts fire so often that on-call mutes them | ✗ nej | diskutera |
| Customers report outages before monitoring does | → | Feature work always outranks reliability work in planning | ✗ nej | diskutera |
| One engineer knows how the payment path actually works | → | Customers report outages before monitoring does | ✗ nej | diskutera |
| Post-mortems assign actions to people who were not in the room | → | Customers report outages before monitoring does | ✗ nej | diskutera |
| Error budgets exist on a slide and nowhere else | → | Feature work always outranks reliability work in planning | ✗ nej | diskutera |
| Alerts fire so often that on-call mutes them | → | Post-mortems assign actions to people who were not in the room | ✗ nej | diskutera |
| One engineer knows how the payment path actually works | → | Post-mortem actions are written up and then never scheduled | ✗ nej | diskutera |
| The on-call rota has the same two people on it most weeks | → | One engineer knows how the payment path actually works | ✗ nej | diskutera |
| Tests that fail intermittently are retried until green | → | One engineer knows how the payment path actually works | ✗ nej | diskutera |
| The on-call rota has the same two people on it most weeks | → | Every team has its own logging format | ✗ nej | diskutera |
| Alerts fire so often that on-call mutes them | → | Tests that fail intermittently are retried until green | ✗ nej | diskutera |
| Every team has its own logging format | → | One engineer knows how the payment path actually works | ✗ nej | diskutera |
| 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 | ✗ nej | diskutera |
| Post-mortems assign actions to people who were not in the room | → | Tests that fail intermittently are retried until green | ✗ nej | diskutera |
| Every team has its own logging format | → | Alerts fire so often that on-call mutes them | ✗ nej | diskutera |
| The on-call rota has the same two people on it most weeks | → | Feature work always outranks reliability work in planning | ✗ nej | diskutera |
| Tests that fail intermittently are retried until green | → | Feature work always outranks reliability work in planning | ✗ nej | diskutera |
| Tests that fail intermittently are retried until green | → | Post-mortem actions are written up and then never scheduled | ✗ nej | diskutera |
| Error budgets exist on a slide and nowhere else | → | Alerts fire so often that on-call mutes them | ✗ nej | diskutera |
| Error budgets exist on a slide and nowhere else | → | Post-mortem actions are written up and then never scheduled | ✗ nej | diskutera |
| Post-mortems assign actions to people who were not in the room | → | Feature work always outranks reliability work in planning | ✗ nej | diskutera |
| One engineer knows how the payment path actually works | → | Feature work always outranks reliability work in planning | ✗ nej | diskutera |
| Error budgets exist on a slide and nowhere else | → | Every team has its own logging format | ✗ nej | diskutera |
| Tests that fail intermittently are retried until green | → | Error budgets exist on a slide and nowhere else | ✗ nej | diskutera |
| Post-mortem actions are written up and then never scheduled | → | Error budgets exist on a slide and nowhere else | ✗ nej | diskutera |
| Post-mortem actions are written up and then never scheduled | → | Customers report outages before monitoring does | ✗ nej | diskutera |
| Every team has its own logging format | → | Tests that fail intermittently are retried until green | ✗ nej | diskutera |
| One engineer knows how the payment path actually works | → | Post-mortems assign actions to people who were not in the room | ✗ nej | diskutera |
| Feature work always outranks reliability work in planning | → | One engineer knows how the payment path actually works | ✗ nej | diskutera |
| Every team has its own logging format | → | Feature work always outranks reliability work in planning | ✗ nej | diskutera |
| One engineer knows how the payment path actually works | → | Error budgets exist on a slide and nowhere else | ✗ nej | diskutera |
| Alerts fire so often that on-call mutes them | → | Error budgets exist on a slide and nowhere else | ✗ nej | diskutera |
| Post-mortems assign actions to people who were not in the room | → | One engineer knows how the payment path actually works | ✗ nej | diskutera |
| Alerts fire so often that on-call mutes them | → | Feature work always outranks reliability work in planning | ✗ nej | diskutera |
| One engineer knows how the payment path actually works | → | Every team has its own logging format | ✗ nej | diskutera |
| Feature work always outranks reliability work in planning | → | The on-call rota has the same two people on it most weeks | ✗ nej | diskutera |
| Post-mortem actions are written up and then never scheduled | → | Feature work always outranks reliability work in planning | ✗ nej | diskutera |
| The same three services cause most of the pages | → | The service map in the wiki is two years old | ✗ nej | diskutera |
| Rollbacks take longer than the outage they are meant to end | → | The same three services cause most of the pages | ✗ nej | diskutera |
| Config lives in five places and drifts between them | → | Rollbacks take longer than the outage they are meant to end | ✗ nej | diskutera |
| … | → | The staging environment does not resemble production | ✗ nej | diskutera |
| The incident channel fills with people asking for status instead of giving it | → | Config lives in five places and drifts between them | ✗ nej | diskutera |
| Reliability has no budget line of its own | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ nej | diskutera |
| The incident channel fills with people asking for status instead of giving it | → | Rollbacks take longer than the outage they are meant to end | ✗ nej | diskutera |
| The same three services cause most of the pages | → | The incident channel fills with people asking for status instead of giving it | ✗ nej | diskutera |
| The service map in the wiki is two years old | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ nej | diskutera |
| Config lives in five places and drifts between them | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✗ nej | diskutera |
| 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 | ✗ nej | diskutera |
| Retries are unbounded, so a slow dependency becomes a flood | → | The service map in the wiki is two years old | ✗ nej | diskutera |
| … | → | Reliability has no budget line of its own | ✗ nej | diskutera |
| The service map in the wiki is two years old | → | Rollbacks take longer than the outage they are meant to end | ✗ nej | diskutera |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | Reliability has no budget line of its own | ✗ nej | diskutera |
| 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 | ✗ nej | diskutera |
| Rollbacks take longer than the outage they are meant to end | → | … | ✗ nej | diskutera |
| The incident channel fills with people asking for status instead of giving it | → | Reliability has no budget line of its own | ✗ nej | diskutera |
| Config lives in five places and drifts between them | → | The staging environment does not resemble production | ✗ nej | diskutera |
| … | → | Config lives in five places and drifts between them | ✗ nej | diskutera |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | … | ✗ nej | diskutera |
| Reliability has no budget line of its own | → | Config lives in five places and drifts between them | ✗ nej | diskutera |
| The incident channel fills with people asking for status instead of giving it | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ nej | diskutera |
| Rollbacks take longer than the outage they are meant to end | → | The incident channel fills with people asking for status instead of giving it | ✗ nej | diskutera |
| The same three services cause most of the pages | → | Reliability has no budget line of its own | ✗ nej | diskutera |
| … | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✗ nej | diskutera |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | The service map in the wiki is two years old | ✗ nej | diskutera |
| Config lives in five places and drifts between them | → | Reliability has no budget line of its own | ✗ nej | diskutera |
| The staging environment does not resemble production | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✗ nej | diskutera |
| Rollbacks take longer than the outage they are meant to end | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✗ nej | diskutera |
| Retries are unbounded, so a slow dependency becomes a flood | → | Config lives in five places and drifts between them | ✗ nej | diskutera |
| The service map in the wiki is two years old | → | Reliability has no budget line of its own | ✗ nej | diskutera |
| The service map in the wiki is two years old | → | Config lives in five places and drifts between them | ✗ nej | diskutera |
| The staging environment does not resemble production | → | Config lives in five places and drifts between them | ✗ nej | diskutera |
| Rollbacks take longer than the outage they are meant to end | → | The service map in the wiki is two years old | ✗ nej | diskutera |
| The staging environment does not resemble production | → | The service map in the wiki is two years old | ✗ nej | diskutera |
| The staging environment does not resemble production | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ nej | diskutera |
| … | → | The same three services cause most of the pages | ✗ nej | diskutera |
| Retries are unbounded, so a slow dependency becomes a flood | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✗ nej | diskutera |
| … | → | The service map in the wiki is two years old | ✗ nej | diskutera |
| Config lives in five places and drifts between them | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ nej | diskutera |
| The staging environment does not resemble production | → | … | ✗ nej | diskutera |
| Reliability has no budget line of its own | → | … | ✗ nej | diskutera |
| The same three services cause most of the pages | → | Config lives in five places and drifts between them | ✗ nej | diskutera |
| … | → | The incident channel fills with people asking for status instead of giving it | ✗ nej | diskutera |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | The staging environment does not resemble production | ✗ nej | diskutera |
| Retries are unbounded, so a slow dependency becomes a flood | → | The incident channel fills with people asking for status instead of giving it | ✗ nej | diskutera |
| Config lives in five places and drifts between them | → | … | ✗ nej | diskutera |
| The staging environment does not resemble production | → | The same three services cause most of the pages | ✗ nej | diskutera |
| Reliability has no budget line of its own | → | Rollbacks take longer than the outage they are meant to end | ✗ nej | diskutera |
| Config lives in five places and drifts between them | → | The same three services cause most of the pages | ✗ nej | diskutera |
| The staging environment does not resemble production | → | The incident channel fills with people asking for status instead of giving it | ✗ nej | diskutera |
| Rollbacks take longer than the outage they are meant to end | → | The staging environment does not resemble production | ✗ nej | diskutera |
| … | → | Rollbacks take longer than the outage they are meant to end | ✗ nej | diskutera |
| Config lives in five places and drifts between them | → | The service map in the wiki is two years old | ✗ nej | diskutera |
| The same three services cause most of the pages | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ nej | diskutera |
| Rollbacks take longer than the outage they are meant to end | → | Config lives in five places and drifts between them | ✗ nej | diskutera |
| Reliability has no budget line of its own | → | The service map in the wiki is two years old | ✗ nej | diskutera |
| Retries are unbounded, so a slow dependency becomes a flood | → | … | ✗ nej | diskutera |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | Config lives in five places and drifts between them | ✗ nej | diskutera |
| Config lives in five places and drifts between them | → | The incident channel fills with people asking for status instead of giving it | ✗ nej | diskutera |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ nej | diskutera |
| The service map in the wiki is two years old | → | … | ✗ nej | diskutera |
| The incident channel fills with people asking for status instead of giving it | → | The same three services cause most of the pages | ✗ nej | diskutera |
| Rollbacks take longer than the outage they are meant to end | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ nej | diskutera |
| Reliability has no budget line of its own | → | The same three services cause most of the pages | ✗ nej | diskutera |
| Retries are unbounded, so a slow dependency becomes a flood | → | Rollbacks take longer than the outage they are meant to end | ✗ nej | diskutera |
| The same three services cause most of the pages | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✗ nej | diskutera |
| The service map in the wiki is two years old | → | The incident channel fills with people asking for status instead of giving it | ✗ nej | diskutera |
| The service map in the wiki is two years old | → | The same three services cause most of the pages | ✗ nej | diskutera |
| The incident channel fills with people asking for status instead of giving it | → | … | ✗ nej | diskutera |
| The staging environment does not resemble production | → | Reliability has no budget line of its own | ✗ nej | diskutera |
| The incident channel fills with people asking for status instead of giving it | → | The staging environment does not resemble production | ✗ nej | diskutera |
| The same three services cause most of the pages | → | Rollbacks take longer than the outage they are meant to end | ✗ nej | diskutera |
| … | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ nej | diskutera |
| Retries are unbounded, so a slow dependency becomes a flood | → | Reliability has no budget line of its own | ✗ nej | diskutera |