A PERGUNTA
Why does the same outage keep recurring?
Um influencia significativamente o outro? Decidem três quartos dos votos expressos.
fechada · voltar a Ações
A ver como convidado. Introduza um nome de utilizador para entrar e participar.
As perguntas são repartidas entre os grupos, por isso recebe as que foram dadas ao seu grupo — não todas as 180.
decididos: 176 / 180 para responder: 0 porquê
Ninguém conseguiria responder a várias centenas de pares. Cada par vai para um grupo; um par que se divide é depois enviado a outros grupos, por isso pode aparecer mais tarde na sua lista, mesmo tendo começado noutro lado. A contagem de decididos inclui o trabalho de todos os grupos, e é por isso que sobe mais depressa do que a sua própria lista encolhe.
Última contagem: decididos 176 · enviados a painéis entre grupos 1 · disputados 0 · abaixo do quórum 3 — os painéis precisam de pelo menos max(2, 75% do painel) votos expressos; o seu painel mais pequeno tem 15 membros.
Rollbacks take longer than the outage they are meant to end → influencia? → The incident channel fills with people asking for status instead of giving it
Ainda nada foi dito.
Fase concluída — o registo de pares e votos mantém-se acima.Verificar a lógica ↗
| Reliability has no budget line of its own | → | Feature flags are never cleaned up, so nobody knows which paths are live | em aberto | discutir |
| The same three services cause most of the pages | → | … | em aberto | discutir |
| The incident channel fills with people asking for status instead of giving it | → | The service map in the wiki is two years old | em aberto | discutir |
| The staging environment does not resemble production | → | Rollbacks take longer than the outage they are meant to end | em aberto reencaminhado | discutir |
| Tests that fail intermittently are retried until green | → | Customers report outages before monitoring does | ✓ sim | discutir |
| Alerts fire so often that on-call mutes them | → | Customers report outages before monitoring does | ✓ sim | discutir |
| Alerts fire so often that on-call mutes them | → | Every team has its own logging format | ✓ sim | discutir |
| Every team has its own logging format | → | Customers report outages before monitoring does | ✓ sim | discutir |
| The on-call rota has the same two people on it most weeks | → | Alerts fire so often that on-call mutes them | ✓ sim | discutir |
| Feature work always outranks reliability work in planning | → | Post-mortem actions are written up and then never scheduled | ✓ sim | discutir |
| One engineer knows how the payment path actually works | → | The on-call rota has the same two people on it most weeks | ✓ sim | discutir |
| The on-call rota has the same two people on it most weeks | → | Post-mortem actions are written up and then never scheduled | ✓ sim | discutir |
| Post-mortems assign actions to people who were not in the room | → | Post-mortem actions are written up and then never scheduled | ✓ sim | discutir |
| The service map in the wiki is two years old | → | The staging environment does not resemble production | ✓ sim | discutir |
| Rollbacks take longer than the outage they are meant to end | → | Reliability has no budget line of its own | ✓ sim | discutir |
| Reliability has no budget line of its own | → | The staging environment does not resemble production | ✓ sim | discutir |
| Retries are unbounded, so a slow dependency becomes a flood | → | The same three services cause most of the pages | ✓ sim | discutir |
| Reliability has no budget line of its own | → | The incident channel fills with people asking for status instead of giving it | ✓ sim | discutir |
| The same three services cause most of the pages | → | The staging environment does not resemble production | ✓ sim | discutir |
| The service map in the wiki is two years old | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✓ sim | 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 | ✓ sim | discutir |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | The same three services cause most of the pages | ✓ sim | 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 | ✗ não | discutir |
| Every team has its own logging format | → | Error budgets exist on a slide and nowhere else | ✗ não | discutir |
| Feature work always outranks reliability work in planning | → | Customers report outages before monitoring does | ✗ não | discutir |
| Error budgets exist on a slide and nowhere else | → | Tests that fail intermittently are retried until green | ✗ não | discutir |
| Error budgets exist on a slide and nowhere else | → | One engineer knows how the payment path actually works | ✗ não | discutir |
| Error budgets exist on a slide and nowhere else | → | Post-mortems assign actions to people who were not in the room | ✗ não | discutir |
| Customers report outages before monitoring does | → | Post-mortems assign actions to people who were not in the room | ✗ não | discutir |
| Post-mortem actions are written up and then never scheduled | → | Alerts fire so often that on-call mutes them | ✗ não | discutir |
| Post-mortems assign actions to people who were not in the room | → | Alerts fire so often that on-call mutes them | ✗ não | discutir |
| Error budgets exist on a slide and nowhere else | → | Customers report outages before monitoring does | ✗ não | discutir |
| Customers report outages before monitoring does | → | The on-call rota has the same two people on it most weeks | ✗ não | discutir |
| Post-mortem actions are written up and then never scheduled | → | Post-mortems assign actions to people who were not in the room | ✗ não | discutir |
| Feature work always outranks reliability work in planning | → | Tests that fail intermittently are retried until green | ✗ não | discutir |
| Tests that fail intermittently are retried until green | → | The on-call rota has the same two people on it most weeks | ✗ não | discutir |
| Post-mortem actions are written up and then never scheduled | → | The on-call rota has the same two people on it most weeks | ✗ não | discutir |
| Feature work always outranks reliability work in planning | → | Error budgets exist on a slide and nowhere else | ✗ não | discutir |
| Tests that fail intermittently are retried until green | → | Every team has its own logging format | ✗ não | discutir |
| The on-call rota has the same two people on it most weeks | → | Tests that fail intermittently are retried until green | ✗ não | discutir |
| Post-mortems assign actions to people who were not in the room | → | Every team has its own logging format | ✗ não | discutir |
| Feature work always outranks reliability work in planning | → | Post-mortems assign actions to people who were not in the room | ✗ não | discutir |
| Tests that fail intermittently are retried until green | → | Alerts fire so often that on-call mutes them | ✗ não | discutir |
| Post-mortems assign actions to people who were not in the room | → | Error budgets exist on a slide and nowhere else | ✗ não | discutir |
| Alerts fire so often that on-call mutes them | → | One engineer knows how the payment path actually works | ✗ não | discutir |
| Customers report outages before monitoring does | → | One engineer knows how the payment path actually works | ✗ não | discutir |
| Alerts fire so often that on-call mutes them | → | Post-mortem actions are written up and then never scheduled | ✗ não | 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 | ✗ não | discutir |
| One engineer knows how the payment path actually works | → | Alerts fire so often that on-call mutes them | ✗ não | discutir |
| Customers report outages before monitoring does | → | Alerts fire so often that on-call mutes them | ✗ não | discutir |
| Error budgets exist on a slide and nowhere else | → | The on-call rota has the same two people on it most weeks | ✗ não | discutir |
| Feature work always outranks reliability work in planning | → | Every team has its own logging format | ✗ não | discutir |
| Customers report outages before monitoring does | → | Post-mortem actions are written up and then never scheduled | ✗ não | discutir |
| Customers report outages before monitoring does | → | Every team has its own logging format | ✗ não | discutir |
| Customers report outages before monitoring does | → | Error budgets exist on a slide and nowhere else | ✗ não | discutir |
| Post-mortem actions are written up and then never scheduled | → | One engineer knows how the payment path actually works | ✗ não | discutir |
| Customers report outages before monitoring does | → | Tests that fail intermittently are retried until green | ✗ não | discutir |
| Every team has its own logging format | → | The on-call rota has the same two people on it most weeks | ✗ não | discutir |
| Every team has its own logging format | → | Post-mortems assign actions to people who were not in the room | ✗ não | discutir |
| Every team has its own logging format | → | Post-mortem actions are written up and then never scheduled | ✗ não | discutir |
| Post-mortem actions are written up and then never scheduled | → | Tests that fail intermittently are retried until green | ✗ não | discutir |
| The on-call rota has the same two people on it most weeks | → | Error budgets exist on a slide and nowhere else | ✗ não | discutir |
| Alerts fire so often that on-call mutes them | → | The on-call rota has the same two people on it most weeks | ✗ não | discutir |
| One engineer knows how the payment path actually works | → | Tests that fail intermittently are retried until green | ✗ não | discutir |
| Tests that fail intermittently are retried until green | → | Post-mortems assign actions to people who were not in the room | ✗ não | discutir |
| Feature work always outranks reliability work in planning | → | Alerts fire so often that on-call mutes them | ✗ não | discutir |
| Customers report outages before monitoring does | → | Feature work always outranks reliability work in planning | ✗ não | discutir |
| One engineer knows how the payment path actually works | → | Customers report outages before monitoring does | ✗ não | discutir |
| Post-mortems assign actions to people who were not in the room | → | Customers report outages before monitoring does | ✗ não | discutir |
| Error budgets exist on a slide and nowhere else | → | Feature work always outranks reliability work in planning | ✗ não | discutir |
| Alerts fire so often that on-call mutes them | → | Post-mortems assign actions to people who were not in the room | ✗ não | discutir |
| One engineer knows how the payment path actually works | → | Post-mortem actions are written up and then never scheduled | ✗ não | discutir |
| The on-call rota has the same two people on it most weeks | → | One engineer knows how the payment path actually works | ✗ não | discutir |
| Tests that fail intermittently are retried until green | → | One engineer knows how the payment path actually works | ✗ não | discutir |
| The on-call rota has the same two people on it most weeks | → | Every team has its own logging format | ✗ não | discutir |
| Alerts fire so often that on-call mutes them | → | Tests that fail intermittently are retried until green | ✗ não | discutir |
| Every team has its own logging format | → | One engineer knows how the payment path actually works | ✗ não | 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 | ✗ não | discutir |
| Post-mortems assign actions to people who were not in the room | → | Tests that fail intermittently are retried until green | ✗ não | discutir |
| Every team has its own logging format | → | Alerts fire so often that on-call mutes them | ✗ não | discutir |
| The on-call rota has the same two people on it most weeks | → | Feature work always outranks reliability work in planning | ✗ não | discutir |
| Tests that fail intermittently are retried until green | → | Feature work always outranks reliability work in planning | ✗ não | discutir |
| Tests that fail intermittently are retried until green | → | Post-mortem actions are written up and then never scheduled | ✗ não | discutir |
| Error budgets exist on a slide and nowhere else | → | Alerts fire so often that on-call mutes them | ✗ não | discutir |
| Error budgets exist on a slide and nowhere else | → | Post-mortem actions are written up and then never scheduled | ✗ não | discutir |
| Post-mortems assign actions to people who were not in the room | → | Feature work always outranks reliability work in planning | ✗ não | discutir |
| One engineer knows how the payment path actually works | → | Feature work always outranks reliability work in planning | ✗ não | discutir |
| Error budgets exist on a slide and nowhere else | → | Every team has its own logging format | ✗ não | discutir |
| Tests that fail intermittently are retried until green | → | Error budgets exist on a slide and nowhere else | ✗ não | discutir |
| Post-mortem actions are written up and then never scheduled | → | Error budgets exist on a slide and nowhere else | ✗ não | discutir |
| Post-mortem actions are written up and then never scheduled | → | Customers report outages before monitoring does | ✗ não | discutir |
| Every team has its own logging format | → | Tests that fail intermittently are retried until green | ✗ não | discutir |
| One engineer knows how the payment path actually works | → | Post-mortems assign actions to people who were not in the room | ✗ não | discutir |
| Feature work always outranks reliability work in planning | → | One engineer knows how the payment path actually works | ✗ não | discutir |
| Every team has its own logging format | → | Feature work always outranks reliability work in planning | ✗ não | discutir |
| One engineer knows how the payment path actually works | → | Error budgets exist on a slide and nowhere else | ✗ não | discutir |
| Alerts fire so often that on-call mutes them | → | Error budgets exist on a slide and nowhere else | ✗ não | discutir |
| Post-mortems assign actions to people who were not in the room | → | One engineer knows how the payment path actually works | ✗ não | discutir |
| Alerts fire so often that on-call mutes them | → | Feature work always outranks reliability work in planning | ✗ não | discutir |
| One engineer knows how the payment path actually works | → | Every team has its own logging format | ✗ não | discutir |
| Feature work always outranks reliability work in planning | → | The on-call rota has the same two people on it most weeks | ✗ não | discutir |
| Post-mortem actions are written up and then never scheduled | → | Feature work always outranks reliability work in planning | ✗ não | discutir |
| The same three services cause most of the pages | → | The service map in the wiki is two years old | ✗ não | discutir |
| Rollbacks take longer than the outage they are meant to end | → | The same three services cause most of the pages | ✗ não | discutir |
| Config lives in five places and drifts between them | → | Rollbacks take longer than the outage they are meant to end | ✗ não | discutir |
| … | → | The staging environment does not resemble production | ✗ não | discutir |
| The incident channel fills with people asking for status instead of giving it | → | Config lives in five places and drifts between them | ✗ não | discutir |
| Reliability has no budget line of its own | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ não | 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 | ✗ não | discutir |
| The same three services cause most of the pages | → | The incident channel fills with people asking for status instead of giving it | ✗ não | discutir |
| The service map in the wiki is two years old | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ não | discutir |
| Config lives in five places and drifts between them | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✗ não | 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 | ✗ não | discutir |
| Retries are unbounded, so a slow dependency becomes a flood | → | The service map in the wiki is two years old | ✗ não | discutir |
| … | → | Reliability has no budget line of its own | ✗ não | discutir |
| The service map in the wiki is two years old | → | Rollbacks take longer than the outage they are meant to end | ✗ não | discutir |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | Reliability has no budget line of its own | ✗ não | 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 | ✗ não | discutir |
| Rollbacks take longer than the outage they are meant to end | → | … | ✗ não | discutir |
| The incident channel fills with people asking for status instead of giving it | → | Reliability has no budget line of its own | ✗ não | discutir |
| Config lives in five places and drifts between them | → | The staging environment does not resemble production | ✗ não | discutir |
| … | → | Config lives in five places and drifts between them | ✗ não | discutir |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | … | ✗ não | discutir |
| Reliability has no budget line of its own | → | Config lives in five places and drifts between them | ✗ não | discutir |
| The incident channel fills with people asking for status instead of giving it | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ não | 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 | ✗ não | em foco ↑ · fechar ✕ |
| The same three services cause most of the pages | → | Reliability has no budget line of its own | ✗ não | discutir |
| … | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✗ não | discutir |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | The service map in the wiki is two years old | ✗ não | discutir |
| Config lives in five places and drifts between them | → | Reliability has no budget line of its own | ✗ não | discutir |
| The staging environment does not resemble production | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✗ não | 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 | ✗ não | discutir |
| Retries are unbounded, so a slow dependency becomes a flood | → | Config lives in five places and drifts between them | ✗ não | discutir |
| The service map in the wiki is two years old | → | Reliability has no budget line of its own | ✗ não | discutir |
| The service map in the wiki is two years old | → | Config lives in five places and drifts between them | ✗ não | discutir |
| The staging environment does not resemble production | → | Config lives in five places and drifts between them | ✗ não | discutir |
| Rollbacks take longer than the outage they are meant to end | → | The service map in the wiki is two years old | ✗ não | discutir |
| The staging environment does not resemble production | → | The service map in the wiki is two years old | ✗ não | discutir |
| The staging environment does not resemble production | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ não | discutir |
| … | → | The same three services cause most of the pages | ✗ não | discutir |
| Retries are unbounded, so a slow dependency becomes a flood | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✗ não | discutir |
| … | → | The service map in the wiki is two years old | ✗ não | discutir |
| Config lives in five places and drifts between them | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ não | discutir |
| The staging environment does not resemble production | → | … | ✗ não | discutir |
| Reliability has no budget line of its own | → | … | ✗ não | discutir |
| The same three services cause most of the pages | → | Config lives in five places and drifts between them | ✗ não | discutir |
| … | → | The incident channel fills with people asking for status instead of giving it | ✗ não | discutir |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | The staging environment does not resemble production | ✗ não | discutir |
| Retries are unbounded, so a slow dependency becomes a flood | → | The incident channel fills with people asking for status instead of giving it | ✗ não | discutir |
| Config lives in five places and drifts between them | → | … | ✗ não | discutir |
| The staging environment does not resemble production | → | The same three services cause most of the pages | ✗ não | discutir |
| Reliability has no budget line of its own | → | Rollbacks take longer than the outage they are meant to end | ✗ não | discutir |
| Config lives in five places and drifts between them | → | The same three services cause most of the pages | ✗ não | discutir |
| The staging environment does not resemble production | → | The incident channel fills with people asking for status instead of giving it | ✗ não | discutir |
| Rollbacks take longer than the outage they are meant to end | → | The staging environment does not resemble production | ✗ não | discutir |
| … | → | Rollbacks take longer than the outage they are meant to end | ✗ não | discutir |
| Config lives in five places and drifts between them | → | The service map in the wiki is two years old | ✗ não | discutir |
| The same three services cause most of the pages | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ não | discutir |
| Rollbacks take longer than the outage they are meant to end | → | Config lives in five places and drifts between them | ✗ não | discutir |
| Reliability has no budget line of its own | → | The service map in the wiki is two years old | ✗ não | discutir |
| Retries are unbounded, so a slow dependency becomes a flood | → | … | ✗ não | discutir |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | Config lives in five places and drifts between them | ✗ não | discutir |
| Config lives in five places and drifts between them | → | The incident channel fills with people asking for status instead of giving it | ✗ não | discutir |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ não | discutir |
| The service map in the wiki is two years old | → | … | ✗ não | discutir |
| The incident channel fills with people asking for status instead of giving it | → | The same three services cause most of the pages | ✗ não | discutir |
| Rollbacks take longer than the outage they are meant to end | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ não | discutir |
| Reliability has no budget line of its own | → | The same three services cause most of the pages | ✗ não | discutir |
| Retries are unbounded, so a slow dependency becomes a flood | → | Rollbacks take longer than the outage they are meant to end | ✗ não | discutir |
| The same three services cause most of the pages | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✗ não | discutir |
| The service map in the wiki is two years old | → | The incident channel fills with people asking for status instead of giving it | ✗ não | discutir |
| The service map in the wiki is two years old | → | The same three services cause most of the pages | ✗ não | discutir |
| The incident channel fills with people asking for status instead of giving it | → | … | ✗ não | discutir |
| The staging environment does not resemble production | → | Reliability has no budget line of its own | ✗ não | discutir |
| The incident channel fills with people asking for status instead of giving it | → | The staging environment does not resemble production | ✗ não | discutir |
| The same three services cause most of the pages | → | Rollbacks take longer than the outage they are meant to end | ✗ não | discutir |
| … | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ não | discutir |
| Retries are unbounded, so a slow dependency becomes a flood | → | Reliability has no budget line of its own | ✗ não | discutir |