DIE FRAGE
Why does the same outage keep recurring?
Beeinflusst das eine das andere maßgeblich? Es entscheiden drei Viertel der abgegebenen Stimmen.
geschlossen · zurück zu Maßnahmen
Ansicht als Gast. Benutzernamen eingeben, um beizutreten und mitzumachen.
Die Fragen werden auf die Gruppen verteilt, daher bekommen Sie die, die Ihre Gruppe erhalten hat — nicht alle 180.
176 / 180 entschieden 0 für Sie zu beantworten warum
Niemand könnte mehrere hundert Paare beantworten. Jedes Paar geht an eine Gruppe; ist sie uneinig, wird das Paar an andere Gruppen weitergegeben, daher kann es später in Ihrer Liste auftauchen, obwohl es woanders begonnen hat. Die Zahl der entschiedenen Fragen enthält die Arbeit aller Gruppen, deshalb steigt sie schneller, als Ihre eigene Liste schrumpft.
Letzte Auszählung: 176 entschieden · 1 an gruppenübergreifende Panels weitergegeben · 0 umstritten · 3 unter dem Quorum — Panels brauchen mindestens max(2, 75 % des Panels) abgegebene Stimmen; Ihr kleinstes Panel hat 15 Mitglieder.
Reliability has no budget line of its own → beeinflusst? → Feature flags are never cleaned up, so nobody knows which paths are live
Noch nichts gesagt.
Abgeschlossene Phase — das Protokoll der Paare und Stimmen steht oben.Logik prüfen ↗
| Reliability has no budget line of its own | → | Feature flags are never cleaned up, so nobody knows which paths are live | offen | im Fokus ↑ · schließen ✕ |
| The same three services cause most of the pages | → | … | offen | diskutieren |
| The incident channel fills with people asking for status instead of giving it | → | The service map in the wiki is two years old | offen | diskutieren |
| The staging environment does not resemble production | → | Rollbacks take longer than the outage they are meant to end | offen weitergegeben | diskutieren |
| Tests that fail intermittently are retried until green | → | Customers report outages before monitoring does | ✓ ja | diskutieren |
| Alerts fire so often that on-call mutes them | → | Customers report outages before monitoring does | ✓ ja | diskutieren |
| Alerts fire so often that on-call mutes them | → | Every team has its own logging format | ✓ ja | diskutieren |
| Every team has its own logging format | → | Customers report outages before monitoring does | ✓ ja | diskutieren |
| The on-call rota has the same two people on it most weeks | → | Alerts fire so often that on-call mutes them | ✓ ja | diskutieren |
| Feature work always outranks reliability work in planning | → | Post-mortem actions are written up and then never scheduled | ✓ ja | diskutieren |
| One engineer knows how the payment path actually works | → | The on-call rota has the same two people on it most weeks | ✓ ja | diskutieren |
| The on-call rota has the same two people on it most weeks | → | Post-mortem actions are written up and then never scheduled | ✓ ja | diskutieren |
| Post-mortems assign actions to people who were not in the room | → | Post-mortem actions are written up and then never scheduled | ✓ ja | diskutieren |
| The service map in the wiki is two years old | → | The staging environment does not resemble production | ✓ ja | diskutieren |
| Rollbacks take longer than the outage they are meant to end | → | Reliability has no budget line of its own | ✓ ja | diskutieren |
| Reliability has no budget line of its own | → | The staging environment does not resemble production | ✓ ja | diskutieren |
| Retries are unbounded, so a slow dependency becomes a flood | → | The same three services cause most of the pages | ✓ ja | diskutieren |
| Reliability has no budget line of its own | → | The incident channel fills with people asking for status instead of giving it | ✓ ja | diskutieren |
| The same three services cause most of the pages | → | The staging environment does not resemble production | ✓ ja | diskutieren |
| The service map in the wiki is two years old | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✓ ja | diskutieren |
| 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 | diskutieren |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | The same three services cause most of the pages | ✓ ja | diskutieren |
| The on-call rota has the same two people on it most weeks | → | Customers report outages before monitoring does | ✓ abgeleitet | diskutieren |
| Retries are unbounded, so a slow dependency becomes a flood | → | The staging environment does not resemble production | ✓ abgeleitet | diskutieren |
| Post-mortem actions are written up and then never scheduled | → | Every team has its own logging format | ✗ nein | diskutieren |
| Every team has its own logging format | → | Error budgets exist on a slide and nowhere else | ✗ nein | diskutieren |
| Feature work always outranks reliability work in planning | → | Customers report outages before monitoring does | ✗ nein | diskutieren |
| Error budgets exist on a slide and nowhere else | → | Tests that fail intermittently are retried until green | ✗ nein | diskutieren |
| Error budgets exist on a slide and nowhere else | → | One engineer knows how the payment path actually works | ✗ nein | diskutieren |
| Error budgets exist on a slide and nowhere else | → | Post-mortems assign actions to people who were not in the room | ✗ nein | diskutieren |
| Customers report outages before monitoring does | → | Post-mortems assign actions to people who were not in the room | ✗ nein | diskutieren |
| Post-mortem actions are written up and then never scheduled | → | Alerts fire so often that on-call mutes them | ✗ nein | diskutieren |
| Post-mortems assign actions to people who were not in the room | → | Alerts fire so often that on-call mutes them | ✗ nein | diskutieren |
| Error budgets exist on a slide and nowhere else | → | Customers report outages before monitoring does | ✗ nein | diskutieren |
| Customers report outages before monitoring does | → | The on-call rota has the same two people on it most weeks | ✗ nein | diskutieren |
| Post-mortem actions are written up and then never scheduled | → | Post-mortems assign actions to people who were not in the room | ✗ nein | diskutieren |
| Feature work always outranks reliability work in planning | → | Tests that fail intermittently are retried until green | ✗ nein | diskutieren |
| Tests that fail intermittently are retried until green | → | The on-call rota has the same two people on it most weeks | ✗ nein | diskutieren |
| Post-mortem actions are written up and then never scheduled | → | The on-call rota has the same two people on it most weeks | ✗ nein | diskutieren |
| Feature work always outranks reliability work in planning | → | Error budgets exist on a slide and nowhere else | ✗ nein | diskutieren |
| Tests that fail intermittently are retried until green | → | Every team has its own logging format | ✗ nein | diskutieren |
| The on-call rota has the same two people on it most weeks | → | Tests that fail intermittently are retried until green | ✗ nein | diskutieren |
| Post-mortems assign actions to people who were not in the room | → | Every team has its own logging format | ✗ nein | diskutieren |
| Feature work always outranks reliability work in planning | → | Post-mortems assign actions to people who were not in the room | ✗ nein | diskutieren |
| Tests that fail intermittently are retried until green | → | Alerts fire so often that on-call mutes them | ✗ nein | diskutieren |
| Post-mortems assign actions to people who were not in the room | → | Error budgets exist on a slide and nowhere else | ✗ nein | diskutieren |
| Alerts fire so often that on-call mutes them | → | One engineer knows how the payment path actually works | ✗ nein | diskutieren |
| Customers report outages before monitoring does | → | One engineer knows how the payment path actually works | ✗ nein | diskutieren |
| Alerts fire so often that on-call mutes them | → | Post-mortem actions are written up and then never scheduled | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |
| One engineer knows how the payment path actually works | → | Alerts fire so often that on-call mutes them | ✗ nein | diskutieren |
| Customers report outages before monitoring does | → | Alerts fire so often that on-call mutes them | ✗ nein | diskutieren |
| Error budgets exist on a slide and nowhere else | → | The on-call rota has the same two people on it most weeks | ✗ nein | diskutieren |
| Feature work always outranks reliability work in planning | → | Every team has its own logging format | ✗ nein | diskutieren |
| Customers report outages before monitoring does | → | Post-mortem actions are written up and then never scheduled | ✗ nein | diskutieren |
| Customers report outages before monitoring does | → | Every team has its own logging format | ✗ nein | diskutieren |
| Customers report outages before monitoring does | → | Error budgets exist on a slide and nowhere else | ✗ nein | diskutieren |
| Post-mortem actions are written up and then never scheduled | → | One engineer knows how the payment path actually works | ✗ nein | diskutieren |
| Customers report outages before monitoring does | → | Tests that fail intermittently are retried until green | ✗ nein | diskutieren |
| Every team has its own logging format | → | The on-call rota has the same two people on it most weeks | ✗ nein | diskutieren |
| Every team has its own logging format | → | Post-mortems assign actions to people who were not in the room | ✗ nein | diskutieren |
| Every team has its own logging format | → | Post-mortem actions are written up and then never scheduled | ✗ nein | diskutieren |
| Post-mortem actions are written up and then never scheduled | → | Tests that fail intermittently are retried until green | ✗ nein | diskutieren |
| The on-call rota has the same two people on it most weeks | → | Error budgets exist on a slide and nowhere else | ✗ nein | diskutieren |
| Alerts fire so often that on-call mutes them | → | The on-call rota has the same two people on it most weeks | ✗ nein | diskutieren |
| One engineer knows how the payment path actually works | → | Tests that fail intermittently are retried until green | ✗ nein | diskutieren |
| Tests that fail intermittently are retried until green | → | Post-mortems assign actions to people who were not in the room | ✗ nein | diskutieren |
| Feature work always outranks reliability work in planning | → | Alerts fire so often that on-call mutes them | ✗ nein | diskutieren |
| Customers report outages before monitoring does | → | Feature work always outranks reliability work in planning | ✗ nein | diskutieren |
| One engineer knows how the payment path actually works | → | Customers report outages before monitoring does | ✗ nein | diskutieren |
| Post-mortems assign actions to people who were not in the room | → | Customers report outages before monitoring does | ✗ nein | diskutieren |
| Error budgets exist on a slide and nowhere else | → | Feature work always outranks reliability work in planning | ✗ nein | diskutieren |
| Alerts fire so often that on-call mutes them | → | Post-mortems assign actions to people who were not in the room | ✗ nein | diskutieren |
| One engineer knows how the payment path actually works | → | Post-mortem actions are written up and then never scheduled | ✗ nein | diskutieren |
| The on-call rota has the same two people on it most weeks | → | One engineer knows how the payment path actually works | ✗ nein | diskutieren |
| Tests that fail intermittently are retried until green | → | One engineer knows how the payment path actually works | ✗ nein | diskutieren |
| The on-call rota has the same two people on it most weeks | → | Every team has its own logging format | ✗ nein | diskutieren |
| Alerts fire so often that on-call mutes them | → | Tests that fail intermittently are retried until green | ✗ nein | diskutieren |
| Every team has its own logging format | → | One engineer knows how the payment path actually works | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |
| Post-mortems assign actions to people who were not in the room | → | Tests that fail intermittently are retried until green | ✗ nein | diskutieren |
| Every team has its own logging format | → | Alerts fire so often that on-call mutes them | ✗ nein | diskutieren |
| The on-call rota has the same two people on it most weeks | → | Feature work always outranks reliability work in planning | ✗ nein | diskutieren |
| Tests that fail intermittently are retried until green | → | Feature work always outranks reliability work in planning | ✗ nein | diskutieren |
| Tests that fail intermittently are retried until green | → | Post-mortem actions are written up and then never scheduled | ✗ nein | diskutieren |
| Error budgets exist on a slide and nowhere else | → | Alerts fire so often that on-call mutes them | ✗ nein | diskutieren |
| Error budgets exist on a slide and nowhere else | → | Post-mortem actions are written up and then never scheduled | ✗ nein | diskutieren |
| Post-mortems assign actions to people who were not in the room | → | Feature work always outranks reliability work in planning | ✗ nein | diskutieren |
| One engineer knows how the payment path actually works | → | Feature work always outranks reliability work in planning | ✗ nein | diskutieren |
| Error budgets exist on a slide and nowhere else | → | Every team has its own logging format | ✗ nein | diskutieren |
| Tests that fail intermittently are retried until green | → | Error budgets exist on a slide and nowhere else | ✗ nein | diskutieren |
| Post-mortem actions are written up and then never scheduled | → | Error budgets exist on a slide and nowhere else | ✗ nein | diskutieren |
| Post-mortem actions are written up and then never scheduled | → | Customers report outages before monitoring does | ✗ nein | diskutieren |
| Every team has its own logging format | → | Tests that fail intermittently are retried until green | ✗ nein | diskutieren |
| One engineer knows how the payment path actually works | → | Post-mortems assign actions to people who were not in the room | ✗ nein | diskutieren |
| Feature work always outranks reliability work in planning | → | One engineer knows how the payment path actually works | ✗ nein | diskutieren |
| Every team has its own logging format | → | Feature work always outranks reliability work in planning | ✗ nein | diskutieren |
| One engineer knows how the payment path actually works | → | Error budgets exist on a slide and nowhere else | ✗ nein | diskutieren |
| Alerts fire so often that on-call mutes them | → | Error budgets exist on a slide and nowhere else | ✗ nein | diskutieren |
| Post-mortems assign actions to people who were not in the room | → | One engineer knows how the payment path actually works | ✗ nein | diskutieren |
| Alerts fire so often that on-call mutes them | → | Feature work always outranks reliability work in planning | ✗ nein | diskutieren |
| One engineer knows how the payment path actually works | → | Every team has its own logging format | ✗ nein | diskutieren |
| Feature work always outranks reliability work in planning | → | The on-call rota has the same two people on it most weeks | ✗ nein | diskutieren |
| Post-mortem actions are written up and then never scheduled | → | Feature work always outranks reliability work in planning | ✗ nein | diskutieren |
| The same three services cause most of the pages | → | The service map in the wiki is two years old | ✗ nein | diskutieren |
| Rollbacks take longer than the outage they are meant to end | → | The same three services cause most of the pages | ✗ nein | diskutieren |
| Config lives in five places and drifts between them | → | Rollbacks take longer than the outage they are meant to end | ✗ nein | diskutieren |
| … | → | The staging environment does not resemble production | ✗ nein | diskutieren |
| The incident channel fills with people asking for status instead of giving it | → | Config lives in five places and drifts between them | ✗ nein | diskutieren |
| Reliability has no budget line of its own | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ nein | diskutieren |
| The incident channel fills with people asking for status instead of giving it | → | Rollbacks take longer than the outage they are meant to end | ✗ nein | diskutieren |
| The same three services cause most of the pages | → | The incident channel fills with people asking for status instead of giving it | ✗ nein | diskutieren |
| The service map in the wiki is two years old | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ nein | diskutieren |
| Config lives in five places and drifts between them | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |
| Retries are unbounded, so a slow dependency becomes a flood | → | The service map in the wiki is two years old | ✗ nein | diskutieren |
| … | → | Reliability has no budget line of its own | ✗ nein | diskutieren |
| The service map in the wiki is two years old | → | Rollbacks take longer than the outage they are meant to end | ✗ nein | diskutieren |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | Reliability has no budget line of its own | ✗ nein | diskutieren |
| 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 | ✗ nein | diskutieren |
| Rollbacks take longer than the outage they are meant to end | → | … | ✗ nein | diskutieren |
| The incident channel fills with people asking for status instead of giving it | → | Reliability has no budget line of its own | ✗ nein | diskutieren |
| Config lives in five places and drifts between them | → | The staging environment does not resemble production | ✗ nein | diskutieren |
| … | → | Config lives in five places and drifts between them | ✗ nein | diskutieren |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | … | ✗ nein | diskutieren |
| Reliability has no budget line of its own | → | Config lives in five places and drifts between them | ✗ nein | diskutieren |
| The incident channel fills with people asking for status instead of giving it | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ nein | diskutieren |
| Rollbacks take longer than the outage they are meant to end | → | The incident channel fills with people asking for status instead of giving it | ✗ nein | diskutieren |
| The same three services cause most of the pages | → | Reliability has no budget line of its own | ✗ nein | diskutieren |
| … | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✗ nein | diskutieren |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | The service map in the wiki is two years old | ✗ nein | diskutieren |
| Config lives in five places and drifts between them | → | Reliability has no budget line of its own | ✗ nein | diskutieren |
| The staging environment does not resemble production | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✗ nein | diskutieren |
| Rollbacks take longer than the outage they are meant to end | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✗ nein | diskutieren |
| Retries are unbounded, so a slow dependency becomes a flood | → | Config lives in five places and drifts between them | ✗ nein | diskutieren |
| The service map in the wiki is two years old | → | Reliability has no budget line of its own | ✗ nein | diskutieren |
| The service map in the wiki is two years old | → | Config lives in five places and drifts between them | ✗ nein | diskutieren |
| The staging environment does not resemble production | → | Config lives in five places and drifts between them | ✗ nein | diskutieren |
| Rollbacks take longer than the outage they are meant to end | → | The service map in the wiki is two years old | ✗ nein | diskutieren |
| The staging environment does not resemble production | → | The service map in the wiki is two years old | ✗ nein | diskutieren |
| The staging environment does not resemble production | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ nein | diskutieren |
| … | → | The same three services cause most of the pages | ✗ nein | diskutieren |
| Retries are unbounded, so a slow dependency becomes a flood | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✗ nein | diskutieren |
| … | → | The service map in the wiki is two years old | ✗ nein | diskutieren |
| Config lives in five places and drifts between them | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ nein | diskutieren |
| The staging environment does not resemble production | → | … | ✗ nein | diskutieren |
| Reliability has no budget line of its own | → | … | ✗ nein | diskutieren |
| The same three services cause most of the pages | → | Config lives in five places and drifts between them | ✗ nein | diskutieren |
| … | → | The incident channel fills with people asking for status instead of giving it | ✗ nein | diskutieren |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | The staging environment does not resemble production | ✗ nein | diskutieren |
| Retries are unbounded, so a slow dependency becomes a flood | → | The incident channel fills with people asking for status instead of giving it | ✗ nein | diskutieren |
| Config lives in five places and drifts between them | → | … | ✗ nein | diskutieren |
| The staging environment does not resemble production | → | The same three services cause most of the pages | ✗ nein | diskutieren |
| Reliability has no budget line of its own | → | Rollbacks take longer than the outage they are meant to end | ✗ nein | diskutieren |
| Config lives in five places and drifts between them | → | The same three services cause most of the pages | ✗ nein | diskutieren |
| The staging environment does not resemble production | → | The incident channel fills with people asking for status instead of giving it | ✗ nein | diskutieren |
| Rollbacks take longer than the outage they are meant to end | → | The staging environment does not resemble production | ✗ nein | diskutieren |
| … | → | Rollbacks take longer than the outage they are meant to end | ✗ nein | diskutieren |
| Config lives in five places and drifts between them | → | The service map in the wiki is two years old | ✗ nein | diskutieren |
| The same three services cause most of the pages | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ nein | diskutieren |
| Rollbacks take longer than the outage they are meant to end | → | Config lives in five places and drifts between them | ✗ nein | diskutieren |
| Reliability has no budget line of its own | → | The service map in the wiki is two years old | ✗ nein | diskutieren |
| Retries are unbounded, so a slow dependency becomes a flood | → | … | ✗ nein | diskutieren |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | Config lives in five places and drifts between them | ✗ nein | diskutieren |
| Config lives in five places and drifts between them | → | The incident channel fills with people asking for status instead of giving it | ✗ nein | diskutieren |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ nein | diskutieren |
| The service map in the wiki is two years old | → | … | ✗ nein | diskutieren |
| The incident channel fills with people asking for status instead of giving it | → | The same three services cause most of the pages | ✗ nein | diskutieren |
| Rollbacks take longer than the outage they are meant to end | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ nein | diskutieren |
| Reliability has no budget line of its own | → | The same three services cause most of the pages | ✗ nein | diskutieren |
| Retries are unbounded, so a slow dependency becomes a flood | → | Rollbacks take longer than the outage they are meant to end | ✗ nein | diskutieren |
| The same three services cause most of the pages | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✗ nein | diskutieren |
| The service map in the wiki is two years old | → | The incident channel fills with people asking for status instead of giving it | ✗ nein | diskutieren |
| The service map in the wiki is two years old | → | The same three services cause most of the pages | ✗ nein | diskutieren |
| The incident channel fills with people asking for status instead of giving it | → | … | ✗ nein | diskutieren |
| The staging environment does not resemble production | → | Reliability has no budget line of its own | ✗ nein | diskutieren |
| The incident channel fills with people asking for status instead of giving it | → | The staging environment does not resemble production | ✗ nein | diskutieren |
| The same three services cause most of the pages | → | Rollbacks take longer than the outage they are meant to end | ✗ nein | diskutieren |
| … | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ nein | diskutieren |
| Retries are unbounded, so a slow dependency becomes a flood | → | Reliability has no budget line of its own | ✗ nein | diskutieren |