True Causes
RU
Bahasa IndonesiaDanskDeutschEnglishEspañolFrançaisItalianoNederlandsNorskPolskiPortuguêsSrpski (latinica)SvenskaTiếng ViệtTürkçeΕλληνικάРусскийСрпски (ћирилица)Українська中文日本語한국어
← в начало
7/7 · Действия · просмотр: Структурирование
людей: 30 · идей: 30
нажмите на завершенный этап, чтобы посмотреть его
✓
Сбор
✓
Пояснение
✓
Группировка
✓
Отбор
✓
Структурирование
✓
Карта
7
Действия
пробный прогон · не учитывается
препятствия · любой, у кого есть ссылка · в открытом списке · федерация включена
ведущий: ее ведущий (запечатана)
людей: 30 · идей: 30 · 2 группы
Паспорт → · Логика → · протокол
↗ поделиться этой картой
На другом сайте, как живая карта:
Как изображение: https://truecauses.org/d/6708d57/map.svg
Как данные: все оцененные пары в этой комнате (CSV). У каждого утверждения есть свой адрес, /c/6708d57/<card>, он указан под картой.
Укажите источник при публикации: Causal map: True Causes, https://truecauses.org/d/6708d57
ВОПРОС

Why does the same outage keep recurring?

Существенно ли одно влияет на другое? Решают три четверти поданных голосов.

закрыто · назад к этапу «Действия»
Вы смотрите как гость. Введите имя пользователя, чтобы присоединиться и участвовать.
Вопросы распределяются между группами, поэтому вы получаете те, что достались вашей группе, — а не все 180.
почему
Никто не смог бы ответить на несколько сотен пар. Каждая пара достается одной группе; пара, по которой мнения разделились, затем передается другим группам, поэтому она может позже появиться в вашем списке, хотя началась в другом месте. Число решенных включает работу всех групп, поэтому оно растет быстрее, чем сокращается ваш список.
решено: 176 / 180 ждут вашего ответа: 0
Последний подсчет: решено: 176 · передано панелям из нескольких групп: 1 · спорно: 0 · ниже кворума: 3 — панелям нужно не меньше max(2, 75% панели) поданных голосов; в вашей самой маленькой панели 15 участников.
закрыть ✕
The same three services cause most of the pages → влияет на? → The incident channel fills with people asking for status instead of giving it
Пока ничего не сказано.
Этап завершен — запись пар и голосов приведена выше.Проверить логику ↗
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✗ нетобсудить