LA PREGUNTA
Why does the same outage keep recurring?
¿Influye una significativamente en la otra? Deciden tres cuartas partes de los votos emitidos.
cerrada · volver a Acciones
Viendo como invitado. Escribe un nombre de usuario para unirte y participar.
Las preguntas se reparten entre los grupos, así que recibes las que le tocaron al tuyo — no las 180.
resueltas: 176 / 180 por responder: 0 por qué
Nadie podría responder varios cientos de pares. Cada par va a un grupo; un par que se divide se deriva después a otros grupos, así que puede aparecer más tarde en tu lista aunque empezara en otro sitio. La cifra de resueltas incluye el trabajo de todos los grupos, y por eso sube más rápido de lo que se acorta tu propia lista.
Último recuento: decididas: 176 · derivadas a paneles entre grupos: 1 · disputadas: 0 · sin quórum: 3 — los paneles necesitan al menos max(2, 75 % del panel) votos emitidos; tu panel más pequeño tiene 15 miembros.
One engineer knows how the payment path actually works → ¿influye en? → Tests that fail intermittently are retried until green
Nadie ha dicho nada aún.
Fase terminada — el registro de pares y votos queda arriba.Comprobar la lógica ↗
| Reliability has no budget line of its own | → | Feature flags are never cleaned up, so nobody knows which paths are live | abierto | discutir |
| The same three services cause most of the pages | → | … | abierto | discutir |
| The incident channel fills with people asking for status instead of giving it | → | The service map in the wiki is two years old | abierto | discutir |
| The staging environment does not resemble production | → | Rollbacks take longer than the outage they are meant to end | abierto derivado | discutir |
| Tests that fail intermittently are retried until green | → | Customers report outages before monitoring does | ✓ sí | discutir |
| Alerts fire so often that on-call mutes them | → | Customers report outages before monitoring does | ✓ sí | discutir |
| Alerts fire so often that on-call mutes them | → | Every team has its own logging format | ✓ sí | discutir |
| Every team has its own logging format | → | Customers report outages before monitoring does | ✓ sí | discutir |
| The on-call rota has the same two people on it most weeks | → | Alerts fire so often that on-call mutes them | ✓ sí | discutir |
| Feature work always outranks reliability work in planning | → | Post-mortem actions are written up and then never scheduled | ✓ sí | discutir |
| One engineer knows how the payment path actually works | → | The on-call rota has the same two people on it most weeks | ✓ sí | discutir |
| The on-call rota has the same two people on it most weeks | → | Post-mortem actions are written up and then never scheduled | ✓ sí | discutir |
| Post-mortems assign actions to people who were not in the room | → | Post-mortem actions are written up and then never scheduled | ✓ sí | discutir |
| The service map in the wiki is two years old | → | The staging environment does not resemble production | ✓ sí | discutir |
| Rollbacks take longer than the outage they are meant to end | → | Reliability has no budget line of its own | ✓ sí | discutir |
| Reliability has no budget line of its own | → | The staging environment does not resemble production | ✓ sí | discutir |
| Retries are unbounded, so a slow dependency becomes a flood | → | The same three services cause most of the pages | ✓ sí | discutir |
| Reliability has no budget line of its own | → | The incident channel fills with people asking for status instead of giving it | ✓ sí | discutir |
| The same three services cause most of the pages | → | The staging environment does not resemble production | ✓ sí | discutir |
| The service map in the wiki is two years old | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✓ sí | discutir |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | Rollbacks take longer than the outage they are meant to end | ✓ sí | discutir |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | The same three services cause most of the pages | ✓ sí | discutir |
| The on-call rota has the same two people on it most weeks | → | Customers report outages before monitoring does | ✓ inferido | discutir |
| Retries are unbounded, so a slow dependency becomes a flood | → | The staging environment does not resemble production | ✓ inferido | discutir |
| Post-mortem actions are written up and then never scheduled | → | Every team has its own logging format | ✗ no | discutir |
| Every team has its own logging format | → | Error budgets exist on a slide and nowhere else | ✗ no | discutir |
| Feature work always outranks reliability work in planning | → | Customers report outages before monitoring does | ✗ no | discutir |
| Error budgets exist on a slide and nowhere else | → | Tests that fail intermittently are retried until green | ✗ no | discutir |
| Error budgets exist on a slide and nowhere else | → | One engineer knows how the payment path actually works | ✗ no | discutir |
| Error budgets exist on a slide and nowhere else | → | Post-mortems assign actions to people who were not in the room | ✗ no | discutir |
| Customers report outages before monitoring does | → | Post-mortems assign actions to people who were not in the room | ✗ no | discutir |
| Post-mortem actions are written up and then never scheduled | → | Alerts fire so often that on-call mutes them | ✗ no | discutir |
| Post-mortems assign actions to people who were not in the room | → | Alerts fire so often that on-call mutes them | ✗ no | discutir |
| Error budgets exist on a slide and nowhere else | → | Customers report outages before monitoring does | ✗ no | discutir |
| Customers report outages before monitoring does | → | The on-call rota has the same two people on it most weeks | ✗ no | discutir |
| Post-mortem actions are written up and then never scheduled | → | Post-mortems assign actions to people who were not in the room | ✗ no | discutir |
| Feature work always outranks reliability work in planning | → | Tests that fail intermittently are retried until green | ✗ no | discutir |
| Tests that fail intermittently are retried until green | → | The on-call rota has the same two people on it most weeks | ✗ no | discutir |
| Post-mortem actions are written up and then never scheduled | → | The on-call rota has the same two people on it most weeks | ✗ no | discutir |
| Feature work always outranks reliability work in planning | → | Error budgets exist on a slide and nowhere else | ✗ no | discutir |
| Tests that fail intermittently are retried until green | → | Every team has its own logging format | ✗ no | discutir |
| The on-call rota has the same two people on it most weeks | → | Tests that fail intermittently are retried until green | ✗ no | discutir |
| Post-mortems assign actions to people who were not in the room | → | Every team has its own logging format | ✗ no | discutir |
| Feature work always outranks reliability work in planning | → | Post-mortems assign actions to people who were not in the room | ✗ no | discutir |
| Tests that fail intermittently are retried until green | → | Alerts fire so often that on-call mutes them | ✗ no | discutir |
| Post-mortems assign actions to people who were not in the room | → | Error budgets exist on a slide and nowhere else | ✗ no | discutir |
| Alerts fire so often that on-call mutes them | → | One engineer knows how the payment path actually works | ✗ no | discutir |
| Customers report outages before monitoring does | → | One engineer knows how the payment path actually works | ✗ no | discutir |
| Alerts fire so often that on-call mutes them | → | Post-mortem actions are written up and then never scheduled | ✗ no | discutir |
| 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 | ✗ no | discutir |
| One engineer knows how the payment path actually works | → | Alerts fire so often that on-call mutes them | ✗ no | discutir |
| Customers report outages before monitoring does | → | Alerts fire so often that on-call mutes them | ✗ no | discutir |
| Error budgets exist on a slide and nowhere else | → | The on-call rota has the same two people on it most weeks | ✗ no | discutir |
| Feature work always outranks reliability work in planning | → | Every team has its own logging format | ✗ no | discutir |
| Customers report outages before monitoring does | → | Post-mortem actions are written up and then never scheduled | ✗ no | discutir |
| Customers report outages before monitoring does | → | Every team has its own logging format | ✗ no | discutir |
| Customers report outages before monitoring does | → | Error budgets exist on a slide and nowhere else | ✗ no | discutir |
| Post-mortem actions are written up and then never scheduled | → | One engineer knows how the payment path actually works | ✗ no | discutir |
| Customers report outages before monitoring does | → | Tests that fail intermittently are retried until green | ✗ no | discutir |
| Every team has its own logging format | → | The on-call rota has the same two people on it most weeks | ✗ no | discutir |
| Every team has its own logging format | → | Post-mortems assign actions to people who were not in the room | ✗ no | discutir |
| Every team has its own logging format | → | Post-mortem actions are written up and then never scheduled | ✗ no | discutir |
| Post-mortem actions are written up and then never scheduled | → | Tests that fail intermittently are retried until green | ✗ no | discutir |
| The on-call rota has the same two people on it most weeks | → | Error budgets exist on a slide and nowhere else | ✗ no | discutir |
| Alerts fire so often that on-call mutes them | → | The on-call rota has the same two people on it most weeks | ✗ no | discutir |
| One engineer knows how the payment path actually works | → | Tests that fail intermittently are retried until green | ✗ no | en foco ↑ · cerrar ✕ |
| Tests that fail intermittently are retried until green | → | Post-mortems assign actions to people who were not in the room | ✗ no | discutir |
| Feature work always outranks reliability work in planning | → | Alerts fire so often that on-call mutes them | ✗ no | discutir |
| Customers report outages before monitoring does | → | Feature work always outranks reliability work in planning | ✗ no | discutir |
| One engineer knows how the payment path actually works | → | Customers report outages before monitoring does | ✗ no | discutir |
| Post-mortems assign actions to people who were not in the room | → | Customers report outages before monitoring does | ✗ no | discutir |
| Error budgets exist on a slide and nowhere else | → | Feature work always outranks reliability work in planning | ✗ no | discutir |
| Alerts fire so often that on-call mutes them | → | Post-mortems assign actions to people who were not in the room | ✗ no | discutir |
| One engineer knows how the payment path actually works | → | Post-mortem actions are written up and then never scheduled | ✗ no | discutir |
| The on-call rota has the same two people on it most weeks | → | One engineer knows how the payment path actually works | ✗ no | discutir |
| Tests that fail intermittently are retried until green | → | One engineer knows how the payment path actually works | ✗ no | discutir |
| The on-call rota has the same two people on it most weeks | → | Every team has its own logging format | ✗ no | discutir |
| Alerts fire so often that on-call mutes them | → | Tests that fail intermittently are retried until green | ✗ no | discutir |
| Every team has its own logging format | → | One engineer knows how the payment path actually works | ✗ no | discutir |
| 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 | ✗ no | discutir |
| Post-mortems assign actions to people who were not in the room | → | Tests that fail intermittently are retried until green | ✗ no | discutir |
| Every team has its own logging format | → | Alerts fire so often that on-call mutes them | ✗ no | discutir |
| The on-call rota has the same two people on it most weeks | → | Feature work always outranks reliability work in planning | ✗ no | discutir |
| Tests that fail intermittently are retried until green | → | Feature work always outranks reliability work in planning | ✗ no | discutir |
| Tests that fail intermittently are retried until green | → | Post-mortem actions are written up and then never scheduled | ✗ no | discutir |
| Error budgets exist on a slide and nowhere else | → | Alerts fire so often that on-call mutes them | ✗ no | discutir |
| Error budgets exist on a slide and nowhere else | → | Post-mortem actions are written up and then never scheduled | ✗ no | discutir |
| Post-mortems assign actions to people who were not in the room | → | Feature work always outranks reliability work in planning | ✗ no | discutir |
| One engineer knows how the payment path actually works | → | Feature work always outranks reliability work in planning | ✗ no | discutir |
| Error budgets exist on a slide and nowhere else | → | Every team has its own logging format | ✗ no | discutir |
| Tests that fail intermittently are retried until green | → | Error budgets exist on a slide and nowhere else | ✗ no | discutir |
| Post-mortem actions are written up and then never scheduled | → | Error budgets exist on a slide and nowhere else | ✗ no | discutir |
| Post-mortem actions are written up and then never scheduled | → | Customers report outages before monitoring does | ✗ no | discutir |
| Every team has its own logging format | → | Tests that fail intermittently are retried until green | ✗ no | discutir |
| One engineer knows how the payment path actually works | → | Post-mortems assign actions to people who were not in the room | ✗ no | discutir |
| Feature work always outranks reliability work in planning | → | One engineer knows how the payment path actually works | ✗ no | discutir |
| Every team has its own logging format | → | Feature work always outranks reliability work in planning | ✗ no | discutir |
| One engineer knows how the payment path actually works | → | Error budgets exist on a slide and nowhere else | ✗ no | discutir |
| Alerts fire so often that on-call mutes them | → | Error budgets exist on a slide and nowhere else | ✗ no | discutir |
| Post-mortems assign actions to people who were not in the room | → | One engineer knows how the payment path actually works | ✗ no | discutir |
| Alerts fire so often that on-call mutes them | → | Feature work always outranks reliability work in planning | ✗ no | discutir |
| One engineer knows how the payment path actually works | → | Every team has its own logging format | ✗ no | discutir |
| Feature work always outranks reliability work in planning | → | The on-call rota has the same two people on it most weeks | ✗ no | discutir |
| Post-mortem actions are written up and then never scheduled | → | Feature work always outranks reliability work in planning | ✗ no | discutir |
| The same three services cause most of the pages | → | The service map in the wiki is two years old | ✗ no | discutir |
| Rollbacks take longer than the outage they are meant to end | → | The same three services cause most of the pages | ✗ no | discutir |
| Config lives in five places and drifts between them | → | Rollbacks take longer than the outage they are meant to end | ✗ no | discutir |
| … | → | The staging environment does not resemble production | ✗ no | discutir |
| The incident channel fills with people asking for status instead of giving it | → | Config lives in five places and drifts between them | ✗ no | discutir |
| Reliability has no budget line of its own | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ no | discutir |
| The incident channel fills with people asking for status instead of giving it | → | Rollbacks take longer than the outage they are meant to end | ✗ no | discutir |
| The same three services cause most of the pages | → | The incident channel fills with people asking for status instead of giving it | ✗ no | discutir |
| The service map in the wiki is two years old | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ no | discutir |
| Config lives in five places and drifts between them | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✗ no | discutir |
| 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 | ✗ no | discutir |
| Retries are unbounded, so a slow dependency becomes a flood | → | The service map in the wiki is two years old | ✗ no | discutir |
| … | → | Reliability has no budget line of its own | ✗ no | discutir |
| The service map in the wiki is two years old | → | Rollbacks take longer than the outage they are meant to end | ✗ no | discutir |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | Reliability has no budget line of its own | ✗ no | discutir |
| 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 | ✗ no | discutir |
| Rollbacks take longer than the outage they are meant to end | → | … | ✗ no | discutir |
| The incident channel fills with people asking for status instead of giving it | → | Reliability has no budget line of its own | ✗ no | discutir |
| Config lives in five places and drifts between them | → | The staging environment does not resemble production | ✗ no | discutir |
| … | → | Config lives in five places and drifts between them | ✗ no | discutir |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | … | ✗ no | discutir |
| Reliability has no budget line of its own | → | Config lives in five places and drifts between them | ✗ no | discutir |
| The incident channel fills with people asking for status instead of giving it | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ no | discutir |
| Rollbacks take longer than the outage they are meant to end | → | The incident channel fills with people asking for status instead of giving it | ✗ no | discutir |
| The same three services cause most of the pages | → | Reliability has no budget line of its own | ✗ no | discutir |
| … | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✗ no | discutir |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | The service map in the wiki is two years old | ✗ no | discutir |
| Config lives in five places and drifts between them | → | Reliability has no budget line of its own | ✗ no | discutir |
| The staging environment does not resemble production | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✗ no | discutir |
| Rollbacks take longer than the outage they are meant to end | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✗ no | discutir |
| Retries are unbounded, so a slow dependency becomes a flood | → | Config lives in five places and drifts between them | ✗ no | discutir |
| The service map in the wiki is two years old | → | Reliability has no budget line of its own | ✗ no | discutir |
| The service map in the wiki is two years old | → | Config lives in five places and drifts between them | ✗ no | discutir |
| The staging environment does not resemble production | → | Config lives in five places and drifts between them | ✗ no | discutir |
| Rollbacks take longer than the outage they are meant to end | → | The service map in the wiki is two years old | ✗ no | discutir |
| The staging environment does not resemble production | → | The service map in the wiki is two years old | ✗ no | discutir |
| The staging environment does not resemble production | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ no | discutir |
| … | → | The same three services cause most of the pages | ✗ no | discutir |
| Retries are unbounded, so a slow dependency becomes a flood | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✗ no | discutir |
| … | → | The service map in the wiki is two years old | ✗ no | discutir |
| Config lives in five places and drifts between them | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ no | discutir |
| The staging environment does not resemble production | → | … | ✗ no | discutir |
| Reliability has no budget line of its own | → | … | ✗ no | discutir |
| The same three services cause most of the pages | → | Config lives in five places and drifts between them | ✗ no | discutir |
| … | → | The incident channel fills with people asking for status instead of giving it | ✗ no | discutir |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | The staging environment does not resemble production | ✗ no | discutir |
| Retries are unbounded, so a slow dependency becomes a flood | → | The incident channel fills with people asking for status instead of giving it | ✗ no | discutir |
| Config lives in five places and drifts between them | → | … | ✗ no | discutir |
| The staging environment does not resemble production | → | The same three services cause most of the pages | ✗ no | discutir |
| Reliability has no budget line of its own | → | Rollbacks take longer than the outage they are meant to end | ✗ no | discutir |
| Config lives in five places and drifts between them | → | The same three services cause most of the pages | ✗ no | discutir |
| The staging environment does not resemble production | → | The incident channel fills with people asking for status instead of giving it | ✗ no | discutir |
| Rollbacks take longer than the outage they are meant to end | → | The staging environment does not resemble production | ✗ no | discutir |
| … | → | Rollbacks take longer than the outage they are meant to end | ✗ no | discutir |
| Config lives in five places and drifts between them | → | The service map in the wiki is two years old | ✗ no | discutir |
| The same three services cause most of the pages | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ no | discutir |
| Rollbacks take longer than the outage they are meant to end | → | Config lives in five places and drifts between them | ✗ no | discutir |
| Reliability has no budget line of its own | → | The service map in the wiki is two years old | ✗ no | discutir |
| Retries are unbounded, so a slow dependency becomes a flood | → | … | ✗ no | discutir |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | Config lives in five places and drifts between them | ✗ no | discutir |
| Config lives in five places and drifts between them | → | The incident channel fills with people asking for status instead of giving it | ✗ no | discutir |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ no | discutir |
| The service map in the wiki is two years old | → | … | ✗ no | discutir |
| The incident channel fills with people asking for status instead of giving it | → | The same three services cause most of the pages | ✗ no | discutir |
| Rollbacks take longer than the outage they are meant to end | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ no | discutir |
| Reliability has no budget line of its own | → | The same three services cause most of the pages | ✗ no | discutir |
| Retries are unbounded, so a slow dependency becomes a flood | → | Rollbacks take longer than the outage they are meant to end | ✗ no | discutir |
| The same three services cause most of the pages | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✗ no | discutir |
| The service map in the wiki is two years old | → | The incident channel fills with people asking for status instead of giving it | ✗ no | discutir |
| The service map in the wiki is two years old | → | The same three services cause most of the pages | ✗ no | discutir |
| The incident channel fills with people asking for status instead of giving it | → | … | ✗ no | discutir |
| The staging environment does not resemble production | → | Reliability has no budget line of its own | ✗ no | discutir |
| The incident channel fills with people asking for status instead of giving it | → | The staging environment does not resemble production | ✗ no | discutir |
| The same three services cause most of the pages | → | Rollbacks take longer than the outage they are meant to end | ✗ no | discutir |
| … | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ no | discutir |
| Retries are unbounded, so a slow dependency becomes a flood | → | Reliability has no budget line of its own | ✗ no | discutir |