ΤΟ ΕΡΩΤΗΜΑ
Why does the same outage keep recurring?
Επηρεάζει σημαντικά το ένα το άλλο; Αποφασίζουν τα τρία τέταρτα των ψήφων που δόθηκαν.
κλειστό · πίσω στο στάδιο Δράσεις
Προβολή ως επισκέπτης. Δώστε ένα όνομα χρήστη για να μπείτε και να συμμετάσχετε.
Τα ερωτήματα μοιράζονται ανάμεσα στις ομάδες, οπότε παίρνετε όσα δόθηκαν στην ομάδα σας — όχι και τα 180.
κρίθηκαν 176 / 180 για να απαντήσετε: 0 γιατί
Κανείς δεν θα μπορούσε να απαντήσει σε εκατοντάδες ζεύγη. Κάθε ζεύγος πηγαίνει σε μία ομάδα· ένα ζεύγος που διχάζει παραπέμπεται μετά σε άλλες ομάδες, οπότε μπορεί να εμφανιστεί αργότερα στη λίστα σας, παρόλο που ξεκίνησε αλλού. Ο αριθμός των κριμένων περιλαμβάνει τη δουλειά κάθε ομάδας, γι’ αυτό ανεβαίνει πιο γρήγορα απ’ ό,τι μικραίνει η δική σας λίστα.
Τελευταία καταμέτρηση: κρίθηκαν 176 · παραπέμφθηκαν σε διομαδικά πάνελ 1 · αμφισβητούμενα 0 · κάτω από την απαρτία 3 — τα πάνελ χρειάζονται τουλάχιστον max(2, 75% του πάνελ) ψήφους· το μικρότερο πάνελ σας έχει 15 μέλη.
Tests that fail intermittently are retried until green → επηρεάζει; → Customers report outages before monitoring does
Δεν ειπώθηκε τίποτα ακόμη.
Ολοκληρωμένη φάση — η καταγραφή ζευγών και ψήφων βρίσκεται παραπάνω.Ελέγξτε τη λογική ↗
| Reliability has no budget line of its own | → | Feature flags are never cleaned up, so nobody knows which paths are live | ανοιχτό | συζήτηση |
| The same three services cause most of the pages | → | … | ανοιχτό | συζήτηση |
| The incident channel fills with people asking for status instead of giving it | → | The service map in the wiki is two years old | ανοιχτό | συζήτηση |
| The staging environment does not resemble production | → | Rollbacks take longer than the outage they are meant to end | ανοιχτό σε παραπομπή | συζήτηση |
| Tests that fail intermittently are retried until green | → | Customers report outages before monitoring does | ✓ ναι | σε εστίαση ↑ · κλείσιμο ✕ |
| Alerts fire so often that on-call mutes them | → | Customers report outages before monitoring does | ✓ ναι | συζήτηση |
| Alerts fire so often that on-call mutes them | → | Every team has its own logging format | ✓ ναι | συζήτηση |
| Every team has its own logging format | → | Customers report outages before monitoring does | ✓ ναι | συζήτηση |
| The on-call rota has the same two people on it most weeks | → | Alerts fire so often that on-call mutes them | ✓ ναι | συζήτηση |
| Feature work always outranks reliability work in planning | → | Post-mortem actions are written up and then never scheduled | ✓ ναι | συζήτηση |
| One engineer knows how the payment path actually works | → | The on-call rota has the same two people on it most weeks | ✓ ναι | συζήτηση |
| The on-call rota has the same two people on it most weeks | → | Post-mortem actions are written up and then never scheduled | ✓ ναι | συζήτηση |
| Post-mortems assign actions to people who were not in the room | → | Post-mortem actions are written up and then never scheduled | ✓ ναι | συζήτηση |
| The service map in the wiki is two years old | → | The staging environment does not resemble production | ✓ ναι | συζήτηση |
| Rollbacks take longer than the outage they are meant to end | → | Reliability has no budget line of its own | ✓ ναι | συζήτηση |
| Reliability has no budget line of its own | → | The staging environment does not resemble production | ✓ ναι | συζήτηση |
| Retries are unbounded, so a slow dependency becomes a flood | → | The same three services cause most of the pages | ✓ ναι | συζήτηση |
| Reliability has no budget line of its own | → | The incident channel fills with people asking for status instead of giving it | ✓ ναι | συζήτηση |
| The same three services cause most of the pages | → | The staging environment does not resemble production | ✓ ναι | συζήτηση |
| The service map in the wiki is two years old | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✓ ναι | συζήτηση |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | Rollbacks take longer than the outage they are meant to end | ✓ ναι | συζήτηση |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | The same three services cause most of the pages | ✓ ναι | συζήτηση |
| The on-call rota has the same two people on it most weeks | → | Customers report outages before monitoring does | ✓ συναγόμενο | συζήτηση |
| Retries are unbounded, so a slow dependency becomes a flood | → | The staging environment does not resemble production | ✓ συναγόμενο | συζήτηση |
| Post-mortem actions are written up and then never scheduled | → | Every team has its own logging format | ✗ όχι | συζήτηση |
| Every team has its own logging format | → | Error budgets exist on a slide and nowhere else | ✗ όχι | συζήτηση |
| Feature work always outranks reliability work in planning | → | Customers report outages before monitoring does | ✗ όχι | συζήτηση |
| Error budgets exist on a slide and nowhere else | → | Tests that fail intermittently are retried until green | ✗ όχι | συζήτηση |
| Error budgets exist on a slide and nowhere else | → | One engineer knows how the payment path actually works | ✗ όχι | συζήτηση |
| Error budgets exist on a slide and nowhere else | → | Post-mortems assign actions to people who were not in the room | ✗ όχι | συζήτηση |
| Customers report outages before monitoring does | → | Post-mortems assign actions to people who were not in the room | ✗ όχι | συζήτηση |
| Post-mortem actions are written up and then never scheduled | → | Alerts fire so often that on-call mutes them | ✗ όχι | συζήτηση |
| Post-mortems assign actions to people who were not in the room | → | Alerts fire so often that on-call mutes them | ✗ όχι | συζήτηση |
| Error budgets exist on a slide and nowhere else | → | Customers report outages before monitoring does | ✗ όχι | συζήτηση |
| Customers report outages before monitoring does | → | The on-call rota has the same two people on it most weeks | ✗ όχι | συζήτηση |
| Post-mortem actions are written up and then never scheduled | → | Post-mortems assign actions to people who were not in the room | ✗ όχι | συζήτηση |
| Feature work always outranks reliability work in planning | → | Tests that fail intermittently are retried until green | ✗ όχι | συζήτηση |
| Tests that fail intermittently are retried until green | → | The on-call rota has the same two people on it most weeks | ✗ όχι | συζήτηση |
| Post-mortem actions are written up and then never scheduled | → | The on-call rota has the same two people on it most weeks | ✗ όχι | συζήτηση |
| Feature work always outranks reliability work in planning | → | Error budgets exist on a slide and nowhere else | ✗ όχι | συζήτηση |
| Tests that fail intermittently are retried until green | → | Every team has its own logging format | ✗ όχι | συζήτηση |
| The on-call rota has the same two people on it most weeks | → | Tests that fail intermittently are retried until green | ✗ όχι | συζήτηση |
| Post-mortems assign actions to people who were not in the room | → | Every team has its own logging format | ✗ όχι | συζήτηση |
| Feature work always outranks reliability work in planning | → | Post-mortems assign actions to people who were not in the room | ✗ όχι | συζήτηση |
| Tests that fail intermittently are retried until green | → | Alerts fire so often that on-call mutes them | ✗ όχι | συζήτηση |
| Post-mortems assign actions to people who were not in the room | → | Error budgets exist on a slide and nowhere else | ✗ όχι | συζήτηση |
| Alerts fire so often that on-call mutes them | → | One engineer knows how the payment path actually works | ✗ όχι | συζήτηση |
| Customers report outages before monitoring does | → | One engineer knows how the payment path actually works | ✗ όχι | συζήτηση |
| Alerts fire so often that on-call mutes them | → | Post-mortem actions are written up and then never scheduled | ✗ όχι | συζήτηση |
| Post-mortems assign actions to people who were not in the room | → | The on-call rota has the same two people on it most weeks | ✗ όχι | συζήτηση |
| One engineer knows how the payment path actually works | → | Alerts fire so often that on-call mutes them | ✗ όχι | συζήτηση |
| Customers report outages before monitoring does | → | Alerts fire so often that on-call mutes them | ✗ όχι | συζήτηση |
| Error budgets exist on a slide and nowhere else | → | The on-call rota has the same two people on it most weeks | ✗ όχι | συζήτηση |
| Feature work always outranks reliability work in planning | → | Every team has its own logging format | ✗ όχι | συζήτηση |
| Customers report outages before monitoring does | → | Post-mortem actions are written up and then never scheduled | ✗ όχι | συζήτηση |
| Customers report outages before monitoring does | → | Every team has its own logging format | ✗ όχι | συζήτηση |
| Customers report outages before monitoring does | → | Error budgets exist on a slide and nowhere else | ✗ όχι | συζήτηση |
| Post-mortem actions are written up and then never scheduled | → | One engineer knows how the payment path actually works | ✗ όχι | συζήτηση |
| Customers report outages before monitoring does | → | Tests that fail intermittently are retried until green | ✗ όχι | συζήτηση |
| Every team has its own logging format | → | The on-call rota has the same two people on it most weeks | ✗ όχι | συζήτηση |
| Every team has its own logging format | → | Post-mortems assign actions to people who were not in the room | ✗ όχι | συζήτηση |
| Every team has its own logging format | → | Post-mortem actions are written up and then never scheduled | ✗ όχι | συζήτηση |
| Post-mortem actions are written up and then never scheduled | → | Tests that fail intermittently are retried until green | ✗ όχι | συζήτηση |
| The on-call rota has the same two people on it most weeks | → | Error budgets exist on a slide and nowhere else | ✗ όχι | συζήτηση |
| Alerts fire so often that on-call mutes them | → | The on-call rota has the same two people on it most weeks | ✗ όχι | συζήτηση |
| One engineer knows how the payment path actually works | → | Tests that fail intermittently are retried until green | ✗ όχι | συζήτηση |
| Tests that fail intermittently are retried until green | → | Post-mortems assign actions to people who were not in the room | ✗ όχι | συζήτηση |
| Feature work always outranks reliability work in planning | → | Alerts fire so often that on-call mutes them | ✗ όχι | συζήτηση |
| Customers report outages before monitoring does | → | Feature work always outranks reliability work in planning | ✗ όχι | συζήτηση |
| One engineer knows how the payment path actually works | → | Customers report outages before monitoring does | ✗ όχι | συζήτηση |
| Post-mortems assign actions to people who were not in the room | → | Customers report outages before monitoring does | ✗ όχι | συζήτηση |
| Error budgets exist on a slide and nowhere else | → | Feature work always outranks reliability work in planning | ✗ όχι | συζήτηση |
| Alerts fire so often that on-call mutes them | → | Post-mortems assign actions to people who were not in the room | ✗ όχι | συζήτηση |
| One engineer knows how the payment path actually works | → | Post-mortem actions are written up and then never scheduled | ✗ όχι | συζήτηση |
| The on-call rota has the same two people on it most weeks | → | One engineer knows how the payment path actually works | ✗ όχι | συζήτηση |
| Tests that fail intermittently are retried until green | → | One engineer knows how the payment path actually works | ✗ όχι | συζήτηση |
| The on-call rota has the same two people on it most weeks | → | Every team has its own logging format | ✗ όχι | συζήτηση |
| Alerts fire so often that on-call mutes them | → | Tests that fail intermittently are retried until green | ✗ όχι | συζήτηση |
| Every team has its own logging format | → | One engineer knows how the payment path actually works | ✗ όχι | συζήτηση |
| The on-call rota has the same two people on it most weeks | → | Post-mortems assign actions to people who were not in the room | ✗ όχι | συζήτηση |
| Post-mortems assign actions to people who were not in the room | → | Tests that fail intermittently are retried until green | ✗ όχι | συζήτηση |
| Every team has its own logging format | → | Alerts fire so often that on-call mutes them | ✗ όχι | συζήτηση |
| The on-call rota has the same two people on it most weeks | → | Feature work always outranks reliability work in planning | ✗ όχι | συζήτηση |
| Tests that fail intermittently are retried until green | → | Feature work always outranks reliability work in planning | ✗ όχι | συζήτηση |
| Tests that fail intermittently are retried until green | → | Post-mortem actions are written up and then never scheduled | ✗ όχι | συζήτηση |
| Error budgets exist on a slide and nowhere else | → | Alerts fire so often that on-call mutes them | ✗ όχι | συζήτηση |
| Error budgets exist on a slide and nowhere else | → | Post-mortem actions are written up and then never scheduled | ✗ όχι | συζήτηση |
| Post-mortems assign actions to people who were not in the room | → | Feature work always outranks reliability work in planning | ✗ όχι | συζήτηση |
| One engineer knows how the payment path actually works | → | Feature work always outranks reliability work in planning | ✗ όχι | συζήτηση |
| Error budgets exist on a slide and nowhere else | → | Every team has its own logging format | ✗ όχι | συζήτηση |
| Tests that fail intermittently are retried until green | → | Error budgets exist on a slide and nowhere else | ✗ όχι | συζήτηση |
| Post-mortem actions are written up and then never scheduled | → | Error budgets exist on a slide and nowhere else | ✗ όχι | συζήτηση |
| Post-mortem actions are written up and then never scheduled | → | Customers report outages before monitoring does | ✗ όχι | συζήτηση |
| Every team has its own logging format | → | Tests that fail intermittently are retried until green | ✗ όχι | συζήτηση |
| One engineer knows how the payment path actually works | → | Post-mortems assign actions to people who were not in the room | ✗ όχι | συζήτηση |
| Feature work always outranks reliability work in planning | → | One engineer knows how the payment path actually works | ✗ όχι | συζήτηση |
| Every team has its own logging format | → | Feature work always outranks reliability work in planning | ✗ όχι | συζήτηση |
| One engineer knows how the payment path actually works | → | Error budgets exist on a slide and nowhere else | ✗ όχι | συζήτηση |
| Alerts fire so often that on-call mutes them | → | Error budgets exist on a slide and nowhere else | ✗ όχι | συζήτηση |
| Post-mortems assign actions to people who were not in the room | → | One engineer knows how the payment path actually works | ✗ όχι | συζήτηση |
| Alerts fire so often that on-call mutes them | → | Feature work always outranks reliability work in planning | ✗ όχι | συζήτηση |
| One engineer knows how the payment path actually works | → | Every team has its own logging format | ✗ όχι | συζήτηση |
| Feature work always outranks reliability work in planning | → | The on-call rota has the same two people on it most weeks | ✗ όχι | συζήτηση |
| Post-mortem actions are written up and then never scheduled | → | Feature work always outranks reliability work in planning | ✗ όχι | συζήτηση |
| The same three services cause most of the pages | → | The service map in the wiki is two years old | ✗ όχι | συζήτηση |
| Rollbacks take longer than the outage they are meant to end | → | The same three services cause most of the pages | ✗ όχι | συζήτηση |
| Config lives in five places and drifts between them | → | Rollbacks take longer than the outage they are meant to end | ✗ όχι | συζήτηση |
| … | → | The staging environment does not resemble production | ✗ όχι | συζήτηση |
| The incident channel fills with people asking for status instead of giving it | → | Config lives in five places and drifts between them | ✗ όχι | συζήτηση |
| Reliability has no budget line of its own | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ όχι | συζήτηση |
| The incident channel fills with people asking for status instead of giving it | → | Rollbacks take longer than the outage they are meant to end | ✗ όχι | συζήτηση |
| The same three services cause most of the pages | → | The incident channel fills with people asking for status instead of giving it | ✗ όχι | συζήτηση |
| The service map in the wiki is two years old | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ όχι | συζήτηση |
| Config lives in five places and drifts between them | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✗ όχι | συζήτηση |
| The incident channel fills with people asking for status instead of giving it | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✗ όχι | συζήτηση |
| Retries are unbounded, so a slow dependency becomes a flood | → | The service map in the wiki is two years old | ✗ όχι | συζήτηση |
| … | → | Reliability has no budget line of its own | ✗ όχι | συζήτηση |
| The service map in the wiki is two years old | → | Rollbacks take longer than the outage they are meant to end | ✗ όχι | συζήτηση |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | Reliability has no budget line of its own | ✗ όχι | συζήτηση |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | The incident channel fills with people asking for status instead of giving it | ✗ όχι | συζήτηση |
| Rollbacks take longer than the outage they are meant to end | → | … | ✗ όχι | συζήτηση |
| The incident channel fills with people asking for status instead of giving it | → | Reliability has no budget line of its own | ✗ όχι | συζήτηση |
| Config lives in five places and drifts between them | → | The staging environment does not resemble production | ✗ όχι | συζήτηση |
| … | → | Config lives in five places and drifts between them | ✗ όχι | συζήτηση |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | … | ✗ όχι | συζήτηση |
| Reliability has no budget line of its own | → | Config lives in five places and drifts between them | ✗ όχι | συζήτηση |
| The incident channel fills with people asking for status instead of giving it | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ όχι | συζήτηση |
| Rollbacks take longer than the outage they are meant to end | → | The incident channel fills with people asking for status instead of giving it | ✗ όχι | συζήτηση |
| The same three services cause most of the pages | → | Reliability has no budget line of its own | ✗ όχι | συζήτηση |
| … | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✗ όχι | συζήτηση |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | The service map in the wiki is two years old | ✗ όχι | συζήτηση |
| Config lives in five places and drifts between them | → | Reliability has no budget line of its own | ✗ όχι | συζήτηση |
| The staging environment does not resemble production | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✗ όχι | συζήτηση |
| Rollbacks take longer than the outage they are meant to end | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✗ όχι | συζήτηση |
| Retries are unbounded, so a slow dependency becomes a flood | → | Config lives in five places and drifts between them | ✗ όχι | συζήτηση |
| The service map in the wiki is two years old | → | Reliability has no budget line of its own | ✗ όχι | συζήτηση |
| The service map in the wiki is two years old | → | Config lives in five places and drifts between them | ✗ όχι | συζήτηση |
| The staging environment does not resemble production | → | Config lives in five places and drifts between them | ✗ όχι | συζήτηση |
| Rollbacks take longer than the outage they are meant to end | → | The service map in the wiki is two years old | ✗ όχι | συζήτηση |
| The staging environment does not resemble production | → | The service map in the wiki is two years old | ✗ όχι | συζήτηση |
| The staging environment does not resemble production | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ όχι | συζήτηση |
| … | → | The same three services cause most of the pages | ✗ όχι | συζήτηση |
| Retries are unbounded, so a slow dependency becomes a flood | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✗ όχι | συζήτηση |
| … | → | The service map in the wiki is two years old | ✗ όχι | συζήτηση |
| Config lives in five places and drifts between them | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ όχι | συζήτηση |
| The staging environment does not resemble production | → | … | ✗ όχι | συζήτηση |
| Reliability has no budget line of its own | → | … | ✗ όχι | συζήτηση |
| The same three services cause most of the pages | → | Config lives in five places and drifts between them | ✗ όχι | συζήτηση |
| … | → | The incident channel fills with people asking for status instead of giving it | ✗ όχι | συζήτηση |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | The staging environment does not resemble production | ✗ όχι | συζήτηση |
| Retries are unbounded, so a slow dependency becomes a flood | → | The incident channel fills with people asking for status instead of giving it | ✗ όχι | συζήτηση |
| Config lives in five places and drifts between them | → | … | ✗ όχι | συζήτηση |
| The staging environment does not resemble production | → | The same three services cause most of the pages | ✗ όχι | συζήτηση |
| Reliability has no budget line of its own | → | Rollbacks take longer than the outage they are meant to end | ✗ όχι | συζήτηση |
| Config lives in five places and drifts between them | → | The same three services cause most of the pages | ✗ όχι | συζήτηση |
| The staging environment does not resemble production | → | The incident channel fills with people asking for status instead of giving it | ✗ όχι | συζήτηση |
| Rollbacks take longer than the outage they are meant to end | → | The staging environment does not resemble production | ✗ όχι | συζήτηση |
| … | → | Rollbacks take longer than the outage they are meant to end | ✗ όχι | συζήτηση |
| Config lives in five places and drifts between them | → | The service map in the wiki is two years old | ✗ όχι | συζήτηση |
| The same three services cause most of the pages | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ όχι | συζήτηση |
| Rollbacks take longer than the outage they are meant to end | → | Config lives in five places and drifts between them | ✗ όχι | συζήτηση |
| Reliability has no budget line of its own | → | The service map in the wiki is two years old | ✗ όχι | συζήτηση |
| Retries are unbounded, so a slow dependency becomes a flood | → | … | ✗ όχι | συζήτηση |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | Config lives in five places and drifts between them | ✗ όχι | συζήτηση |
| Config lives in five places and drifts between them | → | The incident channel fills with people asking for status instead of giving it | ✗ όχι | συζήτηση |
| Feature flags are never cleaned up, so nobody knows which paths are live | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ όχι | συζήτηση |
| The service map in the wiki is two years old | → | … | ✗ όχι | συζήτηση |
| The incident channel fills with people asking for status instead of giving it | → | The same three services cause most of the pages | ✗ όχι | συζήτηση |
| Rollbacks take longer than the outage they are meant to end | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ όχι | συζήτηση |
| Reliability has no budget line of its own | → | The same three services cause most of the pages | ✗ όχι | συζήτηση |
| Retries are unbounded, so a slow dependency becomes a flood | → | Rollbacks take longer than the outage they are meant to end | ✗ όχι | συζήτηση |
| The same three services cause most of the pages | → | Feature flags are never cleaned up, so nobody knows which paths are live | ✗ όχι | συζήτηση |
| The service map in the wiki is two years old | → | The incident channel fills with people asking for status instead of giving it | ✗ όχι | συζήτηση |
| The service map in the wiki is two years old | → | The same three services cause most of the pages | ✗ όχι | συζήτηση |
| The incident channel fills with people asking for status instead of giving it | → | … | ✗ όχι | συζήτηση |
| The staging environment does not resemble production | → | Reliability has no budget line of its own | ✗ όχι | συζήτηση |
| The incident channel fills with people asking for status instead of giving it | → | The staging environment does not resemble production | ✗ όχι | συζήτηση |
| The same three services cause most of the pages | → | Rollbacks take longer than the outage they are meant to end | ✗ όχι | συζήτηση |
| … | → | Retries are unbounded, so a slow dependency becomes a flood | ✗ όχι | συζήτηση |
| Retries are unbounded, so a slow dependency becomes a flood | → | Reliability has no budget line of its own | ✗ όχι | συζήτηση |