id stringlengths 21 21 | kind stringclasses 3
values | options listlengths 2 6 | target listlengths 2 6 | state stringlengths 146 231 | question stringclasses 8
values | domain stringclasses 1
value | family stringclasses 1
value | source stringclasses 1
value |
|---|---|---|---|---|---|---|---|---|
v3_74a4e0ab68d9626c_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.01,
0.62,
0.37
] | The checkout api shows certificate expiry in 40 minutes; additionally p99 latency jumped to 8.4s. Context: during a 3x traffic spike, during the holiday freeze. Reported by the automated check. | Rate customer impact for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_ce1a0e13123fd534_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.04,
0.83,
0.13
] | The search cluster lost its primary replica; additionally p99 latency jumped to 8.4s. Context: with no recent change, during an external partner integration. Reported by the operator. | Rate customer impact for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_cd4340f357be9574_c | choice | [
"deploy_regression",
"capacity",
"dependency_failure",
"infra_fault"
] | [
0.65,
0.02,
0.04,
0.29
] | The auth gateway is rejecting 30% of requests; additionally failed its health check in 3 of 5 regions. Context: in us-east-1 only, during the system migration. Reported by the monitoring system. | Root-cause hypothesis for this scenario. | incident_triage | technical | yuri_v3 |
v3_9895a1ba66ee4c6e_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.01,
0.72,
0.27
] | The auth gateway shows certificate expiry in 40 minutes; additionally error rate hit 14%. Context: with no recent change, with a new vendor onboarded. Reported by the automated check. | Rate operational urgency for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_01f585220f2a7512_n | noul | [
"false",
"true"
] | [
0.08,
0.92
] | The payments worker shows OOM kills every 90 seconds; additionally p99 latency jumped to 8.4s. Context: during a 3x traffic spike, under reduced staffing. Reported by the operator. | Is this scenario one where: this warrants waking the on-call? | incident_triage | technical | yuri_v3 |
v3_b14046f8f0cae6a9_c | choice | [
"deploy_regression",
"capacity",
"dependency_failure",
"infra_fault"
] | [
0.1,
0.85,
0.04,
0.01
] | The etl pipeline p99 latency jumped to 8.4s; additionally error rate hit 14%. Context: under normal load, under an active deadline. Reported by the review queue. | Root-cause hypothesis for this scenario. | incident_triage | technical | yuri_v3 |
v3_177e5d3b394c7e06_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.02,
0.88,
0.1
] | The checkout api returns 503s from one availability zone; additionally p99 latency jumped to 8.4s. Context: with no recent change, with staffing at reduced levels. Reported by the monitoring system. | Rate operational urgency for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_d64de024f3b83e3d_c | choice | [
"deploy_regression",
"capacity",
"dependency_failure",
"infra_fault"
] | [
0.55,
0.44,
0,
0.01
] | The search cluster shows OOM kills every 90 seconds; additionally p99 latency jumped to 8.4s. Context: following the schema migration, under an active deadline. Reported by the monitoring system. | Root-cause hypothesis for this scenario. | incident_triage | technical | yuri_v3 |
v3_c87d9647f1d41827_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.01,
0.65,
0.34
] | The checkout api error rate hit 14%; additionally lost its primary replica. Context: after the 14:00 deploy, immediately after go-live. Reported by the supervisor. | Rate customer impact for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_1117b6d34cb277cd_c | choice | [
"deploy_regression",
"capacity",
"dependency_failure",
"infra_fault"
] | [
0.01,
0.9,
0.01,
0.08
] | The etl pipeline shows OOM kills every 90 seconds; additionally returns 503s from one availability zone. Context: under normal load, while legacy systems are still active. Reported by the automated check. | Root-cause hypothesis for this scenario. | incident_triage | technical | yuri_v3 |
v3_48a45bc49918e8c9_c | choice | [
"rollback",
"scale_out",
"cordon_node",
"investigate_deeper"
] | [
0.87,
0.01,
0.04,
0.08
] | The search cluster p99 latency jumped to 8.4s; additionally returns 503s from one availability zone. Context: following the schema migration, during the system migration. Reported by the on-call engineer. | First action for this scenario. | incident_triage | technical | yuri_v3 |
v3_473f8fe14c4310c4_n | noul | [
"false",
"true"
] | [
0.66,
0.34
] | The etl pipeline has connections pooling at max; additionally succeeded its failover drill. Context: under normal load, during the quarterly review. Reported by the on-call engineer. | Is this scenario one where: this warrants waking the on-call? | incident_triage | technical | yuri_v3 |
v3_21d02c8daf395a91_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.02,
0.83,
0.15
] | The search cluster is rejecting 30% of requests; additionally lost its primary replica. Context: with no recent change, during the holiday freeze. Reported by the review queue. | Rate customer impact for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_e92f72ae3e889525_n | noul | [
"false",
"true"
] | [
0.15,
0.85
] | The checkout api returns 503s from one availability zone; additionally failed its health check in 3 of 5 regions. Context: following the schema migration, at the end of the fiscal period. Reported by the operator. | Is this scenario one where: this warrants waking the on-call? | incident_triage | technical | yuri_v3 |
v3_2280759e05fed9de_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.05,
0.91,
0.04
] | The auth gateway error rate hit 14%; additionally returns 503s from one availability zone. Context: under normal load, with a new vendor onboarded. Reported by the supervisor. | Rate operational urgency for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_d66ee72c37e246fe_n | noul | [
"false",
"true"
] | [
0.15,
0.85
] | The auth gateway shows certificate expiry in 40 minutes; additionally is serving stale data since 02:14. Context: with no recent change, mid-incident. Reported by the supervisor. | Is this scenario one where: this warrants waking the on-call? | incident_triage | technical | yuri_v3 |
v3_3f379c18396ccef7_n | noul | [
"false",
"true"
] | [
0.56,
0.44
] | The checkout api is serving stale data since 02:14; additionally shows certificate expiry in 40 minutes. Context: under normal load, under reduced staffing. Reported by the review queue. | Is this scenario one where: a rollback is safe here? | incident_triage | technical | yuri_v3 |
v3_cbedd710af052acf_n | noul | [
"false",
"true"
] | [
0.68,
0.32
] | The checkout api has a queue depth of 1.2M messages; additionally is serving stale data since 02:14. Context: with no recent change, during the holiday freeze. Reported by the supervisor. | Is this scenario one where: a rollback is safe here? | incident_triage | technical | yuri_v3 |
v3_f7064cceee68e061_c | choice | [
"deploy_regression",
"capacity",
"dependency_failure",
"infra_fault"
] | [
0.34,
0.59,
0.03,
0.04
] | The payments worker succeeded its failover drill; additionally is rejecting 30% of requests. Context: under normal load, during the morning shift. Reported by the supervisor. | Root-cause hypothesis for this scenario. | incident_triage | technical | yuri_v3 |
v3_9b578757e070cd94_n | noul | [
"false",
"true"
] | [
0.13,
0.87
] | The auth gateway has a queue depth of 1.2M messages; additionally returns 503s from one availability zone. Context: with no recent change, under reduced staffing. Reported by the on-call engineer. | Is this scenario one where: this warrants waking the on-call? | incident_triage | technical | yuri_v3 |
v3_e251f35e18549fc4_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.01,
0.79,
0.2
] | The checkout api error rate hit 14%; additionally p99 latency jumped to 8.4s. Context: after the 14:00 deploy, at the end of the fiscal period. Reported by the supervisor. | Rate customer impact for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_c701c921e0fdfe27_n | noul | [
"false",
"true"
] | [
0.37,
0.63
] | The payments worker error rate hit 14%; additionally has a queue depth of 1.2M messages. Context: following the schema migration, under an active deadline. Reported by the operator. | Is this scenario one where: this is customer-visible? | incident_triage | technical | yuri_v3 |
v3_93358990c55a8b61_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.18,
0.78,
0.04
] | The payments worker returns 503s from one availability zone; additionally is serving stale data since 02:14. Context: under normal load, mid-incident. Reported by the automated check. | Rate customer impact for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_24f5f1c0b5ca5c86_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.1,
0.87,
0.03
] | The etl pipeline error rate hit 14%; additionally has connections pooling at max. Context: following the schema migration, mid-incident. Reported by the review queue. | Rate customer impact for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_681960dd26be998f_c | choice | [
"rollback",
"scale_out",
"cordon_node",
"investigate_deeper"
] | [
0.23,
0.35,
0.18,
0.24
] | The etl pipeline returns 503s from one availability zone; additionally has a queue depth of 1.2M messages. Context: during a 3x traffic spike, during a scheduled maintenance window. Reported by the supervisor. | First action for this scenario. | incident_triage | technical | yuri_v3 |
v3_0811b07192068f3a_c | choice | [
"deploy_regression",
"capacity",
"dependency_failure",
"infra_fault"
] | [
0.43,
0.01,
0.53,
0.03
] | The payments worker failed its health check in 3 of 5 regions; additionally is rejecting 30% of requests. Context: in us-east-1 only, with a new vendor onboarded. Reported by the supervisor. | Root-cause hypothesis for this scenario. | incident_triage | technical | yuri_v3 |
v3_6a313cd2658a610a_c | choice | [
"SEV1",
"SEV2",
"SEV3",
"SEV4"
] | [
0.75,
0.25,
0,
0
] | The auth gateway shows certificate expiry in 40 minutes; additionally failed its health check in 3 of 5 regions. Context: following the schema migration, with staffing at reduced levels. Reported by the on-call engineer. | Severity for this scenario. | incident_triage | technical | yuri_v3 |
v3_77dd3ce1d9c59b39_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0,
0.53,
0.47
] | The etl pipeline has a queue depth of 1.2M messages; additionally shows certificate expiry in 40 minutes. Context: during a 3x traffic spike, mid-incident. Reported by the review queue. | Rate operational urgency for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_68b3be33284ca9ce_n | noul | [
"false",
"true"
] | [
0.16,
0.84
] | The etl pipeline has connections pooling at max; additionally is rejecting 30% of requests. Context: after the 14:00 deploy, during an external partner integration. Reported by the automated check. | Is this scenario one where: this warrants waking the on-call? | incident_triage | technical | yuri_v3 |
v3_b65bbc816b971bd2_c | choice | [
"rollback",
"scale_out",
"cordon_node",
"investigate_deeper"
] | [
0.36,
0.3,
0.05,
0.29
] | The checkout api shows certificate expiry in 40 minutes; additionally has a queue depth of 1.2M messages. Context: during a 3x traffic spike, with a new vendor onboarded. Reported by the review queue. | First action for this scenario. | incident_triage | technical | yuri_v3 |
v3_48dddc3cee12862d_n | noul | [
"false",
"true"
] | [
0.41,
0.59
] | The checkout api succeeded its failover drill; additionally failed its health check in 3 of 5 regions. Context: after the 14:00 deploy, with a new vendor onboarded. Reported by the on-call engineer. | Is this scenario one where: this is customer-visible? | incident_triage | technical | yuri_v3 |
v3_70311b80be3ff4d5_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.1,
0.87,
0.03
] | The search cluster error rate hit 14%; additionally returns 503s from one availability zone. Context: under normal load, mid-incident. Reported by the review queue. | Rate operational urgency for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_f2bdb3b52ef3c617_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0,
0.7,
0.3
] | The payments worker failed its health check in 3 of 5 regions; additionally is rejecting 30% of requests. Context: following the schema migration, immediately after go-live. Reported by the automated check. | Rate customer impact for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_e39bbaf1a29a8850_n | noul | [
"false",
"true"
] | [
0.32,
0.68
] | The auth gateway shows OOM kills every 90 seconds; additionally shows certificate expiry in 40 minutes. Context: in us-east-1 only, during the morning shift. Reported by the operator. | Is this scenario one where: this is customer-visible? | incident_triage | technical | yuri_v3 |
v3_06adb72c797baf8b_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.01,
0.62,
0.37
] | The search cluster shows certificate expiry in 40 minutes; additionally failed its health check in 3 of 5 regions. Context: after the 14:00 deploy, with staffing at reduced levels. Reported by the review queue. | Rate customer impact for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_2bc69020047a0174_c | choice | [
"deploy_regression",
"capacity",
"dependency_failure",
"infra_fault"
] | [
0.01,
0.03,
0.09,
0.87
] | The etl pipeline returns 503s from one availability zone; additionally failed its health check in 3 of 5 regions. Context: with no recent change, following a recent audit. Reported by the review queue. | Root-cause hypothesis for this scenario. | incident_triage | technical | yuri_v3 |
v3_d335bdc61b634908_c | choice | [
"SEV1",
"SEV2",
"SEV3",
"SEV4"
] | [
0.96,
0.04,
0,
0
] | The checkout api is serving stale data since 02:14; additionally shows OOM kills every 90 seconds. Context: during a 3x traffic spike, during peak load. Reported by the monitoring system. | Severity for this scenario. | incident_triage | technical | yuri_v3 |
v3_f5b83e479be94559_n | noul | [
"false",
"true"
] | [
0.36,
0.64
] | The search cluster failed its health check in 3 of 5 regions; additionally shows OOM kills every 90 seconds. Context: after the 14:00 deploy, with a new vendor onboarded. Reported by the supervisor. | Is this scenario one where: this is customer-visible? | incident_triage | technical | yuri_v3 |
v3_7faa14fdcf720edb_c | choice | [
"deploy_regression",
"capacity",
"dependency_failure",
"infra_fault"
] | [
0.42,
0.01,
0.5,
0.07
] | The payments worker returns 503s from one availability zone; additionally failed its health check in 3 of 5 regions. Context: following the schema migration, while legacy systems are still active. Reported by the operator. | Root-cause hypothesis for this scenario. | incident_triage | technical | yuri_v3 |
v3_c957e7272b0d1def_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.01,
0.63,
0.36
] | The auth gateway shows OOM kills every 90 seconds; additionally failed its health check in 3 of 5 regions. Context: in us-east-1 only, shortly after a software update. Reported by the operator. | Rate customer impact for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_d28b85bbdb0fd4fc_c | choice | [
"SEV1",
"SEV2",
"SEV3",
"SEV4"
] | [
0.79,
0.21,
0,
0
] | The payments worker is rejecting 30% of requests; additionally shows OOM kills every 90 seconds. Context: after the 14:00 deploy, during the morning shift. Reported by the monitoring system. | Severity for this scenario. | incident_triage | technical | yuri_v3 |
v3_1cc7c8e62d2d5614_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.04,
0.78,
0.18
] | The auth gateway has connections pooling at max; additionally p99 latency jumped to 8.4s. Context: in us-east-1 only, during the quarterly review. Reported by the monitoring system. | Rate customer impact for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_3843cddf071f8912_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.01,
0.81,
0.18
] | The auth gateway lost its primary replica; additionally is rejecting 30% of requests. Context: following the schema migration, during an external partner integration. Reported by the monitoring system. | Rate customer impact for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_60fdc42df06ab38b_n | noul | [
"false",
"true"
] | [
0.53,
0.47
] | The payments worker failed its health check in 3 of 5 regions; additionally shows certificate expiry in 40 minutes. Context: under normal load, during peak load. Reported by the automated check. | Is this scenario one where: a rollback is safe here? | incident_triage | technical | yuri_v3 |
v3_21c9e6968eec6fec_c | choice | [
"SEV1",
"SEV2",
"SEV3",
"SEV4"
] | [
0.88,
0.12,
0,
0
] | The etl pipeline has a queue depth of 1.2M messages; additionally shows OOM kills every 90 seconds. Context: with no recent change, during a scheduled maintenance window. Reported by the review queue. | Severity for this scenario. | incident_triage | technical | yuri_v3 |
v3_760ed69b29c9a3e3_n | noul | [
"false",
"true"
] | [
0.27,
0.73
] | The auth gateway succeeded its failover drill; additionally is serving stale data since 02:14. Context: with no recent change, during the morning shift. Reported by the on-call engineer. | Is this scenario one where: this is customer-visible? | incident_triage | technical | yuri_v3 |
v3_25cbe7a8fedcb82e_n | noul | [
"false",
"true"
] | [
0.65,
0.35
] | The etl pipeline shows certificate expiry in 40 minutes; additionally failed its health check in 3 of 5 regions. Context: in us-east-1 only, during normal operations. Reported by the on-call engineer. | Is this scenario one where: a rollback is safe here? | incident_triage | technical | yuri_v3 |
v3_2a80fc6068ef9781_n | noul | [
"false",
"true"
] | [
0.54,
0.46
] | The checkout api is rejecting 30% of requests; additionally shows certificate expiry in 40 minutes. Context: following the schema migration, with a new vendor onboarded. Reported by the automated check. | Is this scenario one where: a rollback is safe here? | incident_triage | technical | yuri_v3 |
v3_88ccdc528bd1de92_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.07,
0.74,
0.19
] | The checkout api returns 503s from one availability zone; additionally has a queue depth of 1.2M messages. Context: with no recent change, during a scheduled maintenance window. Reported by the operator. | Rate operational urgency for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_1f498ec49073b064_c | choice | [
"deploy_regression",
"capacity",
"dependency_failure",
"infra_fault"
] | [
0.57,
0.07,
0.12,
0.24
] | The search cluster shows certificate expiry in 40 minutes; additionally is serving stale data since 02:14. Context: after the 14:00 deploy, under reduced staffing. Reported by the supervisor. | Root-cause hypothesis for this scenario. | incident_triage | technical | yuri_v3 |
v3_8042f1741e06d40d_n | noul | [
"false",
"true"
] | [
0.56,
0.44
] | The auth gateway succeeded its failover drill; additionally is serving stale data since 02:14. Context: following the schema migration, as part of a compliance sweep. Reported by the monitoring system. | Is this scenario one where: a rollback is safe here? | incident_triage | technical | yuri_v3 |
v3_6bfbda46a8c76103_n | noul | [
"false",
"true"
] | [
0.68,
0.32
] | The auth gateway shows certificate expiry in 40 minutes; additionally has connections pooling at max. Context: following the schema migration, at the end of the fiscal period. Reported by the supervisor. | Is this scenario one where: a rollback is safe here? | incident_triage | technical | yuri_v3 |
v3_9d52dbff89e84a0d_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.09,
0.86,
0.05
] | The etl pipeline has connections pooling at max; additionally failed its health check in 3 of 5 regions. Context: in us-east-1 only, with a new vendor onboarded. Reported by the supervisor. | Rate customer impact for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_bfd9e2d24c1dbe61_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.04,
0.35,
0.54,
0.07,
0
] | The auth gateway succeeded its failover drill; additionally returns 503s from one availability zone. Context: in us-east-1 only, under reduced staffing. Reported by the operator. | Rate customer impact for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_7d15b6dfa1dde6d7_n | noul | [
"false",
"true"
] | [
0.32,
0.68
] | The auth gateway shows certificate expiry in 40 minutes; additionally lost its primary replica. Context: during a 3x traffic spike, following a recent audit. Reported by the supervisor. | Is this scenario one where: this is customer-visible? | incident_triage | technical | yuri_v3 |
v3_3570274584571387_n | noul | [
"false",
"true"
] | [
0.08,
0.92
] | The checkout api p99 latency jumped to 8.4s; additionally is rejecting 30% of requests. Context: after the 14:00 deploy, shortly after a software update. Reported by the review queue. | Is this scenario one where: this warrants waking the on-call? | incident_triage | technical | yuri_v3 |
v3_ce27819134205afc_n | noul | [
"false",
"true"
] | [
0.24,
0.76
] | The etl pipeline p99 latency jumped to 8.4s; additionally shows certificate expiry in 40 minutes. Context: under normal load, under reduced staffing. Reported by the operator. | Is this scenario one where: this warrants waking the on-call? | incident_triage | technical | yuri_v3 |
v3_31010d3201782650_c | choice | [
"SEV1",
"SEV2",
"SEV3",
"SEV4"
] | [
0.53,
0.46,
0.01,
0
] | The payments worker is serving stale data since 02:14; additionally has connections pooling at max. Context: in us-east-1 only, immediately after go-live. Reported by the monitoring system. | Severity for this scenario. | incident_triage | technical | yuri_v3 |
v3_a0f84a9cb5756c9e_n | noul | [
"false",
"true"
] | [
0.18,
0.82
] | The auth gateway error rate hit 14%; additionally lost its primary replica. Context: under normal load, during the holiday freeze. Reported by the on-call engineer. | Is this scenario one where: this is customer-visible? | incident_triage | technical | yuri_v3 |
v3_f946390018177350_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.05,
0.83,
0.12
] | The checkout api failed its health check in 3 of 5 regions; additionally has connections pooling at max. Context: during a 3x traffic spike, during a scheduled maintenance window. Reported by the automated check. | Rate customer impact for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_9a15ff0d4945bb96_c | choice | [
"rollback",
"scale_out",
"cordon_node",
"investigate_deeper"
] | [
0.84,
0,
0.01,
0.15
] | The search cluster failed its health check in 3 of 5 regions; additionally lost its primary replica. Context: after the 14:00 deploy, during the quarterly review. Reported by the automated check. | First action for this scenario. | incident_triage | technical | yuri_v3 |
v3_efef5ca6659ac925_c | choice | [
"deploy_regression",
"capacity",
"dependency_failure",
"infra_fault"
] | [
0.01,
0.02,
0.56,
0.41
] | The payments worker error rate hit 14%; additionally shows certificate expiry in 40 minutes. Context: with no recent change, following a recent audit. Reported by the monitoring system. | Root-cause hypothesis for this scenario. | incident_triage | technical | yuri_v3 |
v3_0b3612cff7c7dc15_c | choice | [
"deploy_regression",
"capacity",
"dependency_failure",
"infra_fault"
] | [
0,
0.02,
0.81,
0.17
] | The etl pipeline shows certificate expiry in 40 minutes; additionally p99 latency jumped to 8.4s. Context: with no recent change, during an external partner integration. Reported by the automated check. | Root-cause hypothesis for this scenario. | incident_triage | technical | yuri_v3 |
v3_be3c797e8e4df5e0_c | choice | [
"deploy_regression",
"capacity",
"dependency_failure",
"infra_fault"
] | [
0.33,
0.41,
0.08,
0.18
] | The checkout api has connections pooling at max; additionally returns 503s from one availability zone. Context: following the schema migration, under an active deadline. Reported by the review queue. | Root-cause hypothesis for this scenario. | incident_triage | technical | yuri_v3 |
v3_470b13469407bc0d_n | noul | [
"false",
"true"
] | [
0.22,
0.78
] | The etl pipeline error rate hit 14%; additionally has a queue depth of 1.2M messages. Context: after the 14:00 deploy, during peak load. Reported by the review queue. | Is this scenario one where: this warrants waking the on-call? | incident_triage | technical | yuri_v3 |
v3_5421a893f9241f69_n | noul | [
"false",
"true"
] | [
0.38,
0.62
] | The search cluster p99 latency jumped to 8.4s; additionally returns 503s from one availability zone. Context: following the schema migration, under an active deadline. Reported by the review queue. | Is this scenario one where: a rollback is safe here? | incident_triage | technical | yuri_v3 |
v3_4518f1e9214fdf14_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.09,
0.84,
0.07
] | The search cluster returns 503s from one availability zone; additionally p99 latency jumped to 8.4s. Context: in us-east-1 only, mid-incident. Reported by the operator. | Rate customer impact for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_f015baab7a721e6f_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.02,
0.2,
0.63,
0.15,
0
] | The etl pipeline succeeded its failover drill; additionally returns 503s from one availability zone. Context: during a 3x traffic spike, with a new vendor onboarded. Reported by the supervisor. | Rate customer impact for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_81b98cf0acbcde3a_n | noul | [
"false",
"true"
] | [
0.58,
0.42
] | The checkout api shows certificate expiry in 40 minutes; additionally succeeded its failover drill. Context: during a 3x traffic spike, following a recent audit. Reported by the supervisor. | Is this scenario one where: a rollback is safe here? | incident_triage | technical | yuri_v3 |
v3_4e43b11a090a0641_c | choice | [
"SEV1",
"SEV2",
"SEV3",
"SEV4"
] | [
0.09,
0.49,
0.32,
0.1
] | The search cluster has connections pooling at max; additionally succeeded its failover drill. Context: under normal load, during the morning shift. Reported by the supervisor. | Severity for this scenario. | incident_triage | technical | yuri_v3 |
v3_6b3fa3d3c48e922c_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.26,
0.72,
0.02
] | The payments worker error rate hit 14%; additionally returns 503s from one availability zone. Context: under normal load, during the morning shift. Reported by the supervisor. | Rate customer impact for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_c1df4fda9eccef49_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0,
0.75,
0.25
] | The search cluster has connections pooling at max; additionally p99 latency jumped to 8.4s. Context: during a 3x traffic spike, under reduced staffing. Reported by the review queue. | Rate operational urgency for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_df9fcff157b75202_n | noul | [
"false",
"true"
] | [
0.47,
0.53
] | The checkout api is serving stale data since 02:14; additionally is rejecting 30% of requests. Context: during a 3x traffic spike, during the morning shift. Reported by the review queue. | Is this scenario one where: a rollback is safe here? | incident_triage | technical | yuri_v3 |
v3_da5e104fb49d6f50_c | choice | [
"rollback",
"scale_out",
"cordon_node",
"investigate_deeper"
] | [
0.84,
0.04,
0.06,
0.06
] | The auth gateway p99 latency jumped to 8.4s; additionally shows OOM kills every 90 seconds. Context: in us-east-1 only, during the system migration. Reported by the operator. | First action for this scenario. | incident_triage | technical | yuri_v3 |
v3_363a4b5cf573d07b_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.01,
0.52,
0.47
] | The auth gateway has a queue depth of 1.2M messages; additionally is serving stale data since 02:14. Context: following the schema migration, mid-incident. Reported by the operator. | Rate customer impact for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_73ee1cd19f6ef9b1_c | choice | [
"deploy_regression",
"capacity",
"dependency_failure",
"infra_fault"
] | [
0.88,
0.05,
0.02,
0.05
] | The payments worker is serving stale data since 02:14; additionally error rate hit 14%. Context: in us-east-1 only, immediately after go-live. Reported by the monitoring system. | Root-cause hypothesis for this scenario. | incident_triage | technical | yuri_v3 |
v3_3173d4906cd6fc55_n | noul | [
"false",
"true"
] | [
0.19,
0.81
] | The search cluster shows certificate expiry in 40 minutes; additionally is serving stale data since 02:14. Context: after the 14:00 deploy, during peak load. Reported by the supervisor. | Is this scenario one where: this warrants waking the on-call? | incident_triage | technical | yuri_v3 |
v3_3bd2239040d92cd5_c | choice | [
"rollback",
"scale_out",
"cordon_node",
"investigate_deeper"
] | [
0.54,
0.2,
0.12,
0.14
] | The auth gateway succeeded its failover drill; additionally shows OOM kills every 90 seconds. Context: after the 14:00 deploy, with staffing at reduced levels. Reported by the on-call engineer. | First action for this scenario. | incident_triage | technical | yuri_v3 |
v3_1534b330eadceb80_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.2,
0.77,
0.03
] | The payments worker is serving stale data since 02:14; additionally returns 503s from one availability zone. Context: following the schema migration, during the system migration. Reported by the automated check. | Rate customer impact for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_fe16eeca3aaa9114_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0,
0.23,
0.77
] | The auth gateway p99 latency jumped to 8.4s; additionally shows OOM kills every 90 seconds. Context: during a 3x traffic spike, during normal operations. Reported by the on-call engineer. | Rate customer impact for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_62453faf2719489d_c | choice | [
"rollback",
"scale_out",
"cordon_node",
"investigate_deeper"
] | [
0.37,
0,
0.01,
0.62
] | The etl pipeline failed its health check in 3 of 5 regions; additionally succeeded its failover drill. Context: following the schema migration, mid-incident. Reported by the operator. | First action for this scenario. | incident_triage | technical | yuri_v3 |
v3_2628711dabaf7b6c_n | noul | [
"false",
"true"
] | [
0.2,
0.8
] | The etl pipeline succeeded its failover drill; additionally is rejecting 30% of requests. Context: during a 3x traffic spike, during the system migration. Reported by the operator. | Is this scenario one where: this is customer-visible? | incident_triage | technical | yuri_v3 |
v3_9f78419b8ccaa7ae_c | choice | [
"SEV1",
"SEV2",
"SEV3",
"SEV4"
] | [
0.15,
0.62,
0.2,
0.03
] | The payments worker error rate hit 14%; additionally p99 latency jumped to 8.4s. Context: in us-east-1 only, during a scheduled maintenance window. Reported by the monitoring system. | Severity for this scenario. | incident_triage | technical | yuri_v3 |
v3_c885f163173247be_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.01,
0.67,
0.32
] | The search cluster returns 503s from one availability zone; additionally shows certificate expiry in 40 minutes. Context: following the schema migration, mid-incident. Reported by the automated check. | Rate operational urgency for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_de7171307671f0a5_n | noul | [
"false",
"true"
] | [
0.29,
0.71
] | The search cluster error rate hit 14%; additionally succeeded its failover drill. Context: under normal load, during the holiday freeze. Reported by the review queue. | Is this scenario one where: this warrants waking the on-call? | incident_triage | technical | yuri_v3 |
v3_9fde95b646b378be_n | noul | [
"false",
"true"
] | [
0.25,
0.75
] | The payments worker failed its health check in 3 of 5 regions; additionally error rate hit 14%. Context: during a 3x traffic spike, during the system migration. Reported by the review queue. | Is this scenario one where: this is customer-visible? | incident_triage | technical | yuri_v3 |
v3_025d5ee8120bf9a5_n | noul | [
"false",
"true"
] | [
0.62,
0.38
] | The checkout api is rejecting 30% of requests; additionally shows certificate expiry in 40 minutes. Context: in us-east-1 only, during normal operations. Reported by the supervisor. | Is this scenario one where: a rollback is safe here? | incident_triage | technical | yuri_v3 |
v3_15c845701db0d127_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.01,
0.58,
0.41
] | The payments worker returns 503s from one availability zone; additionally shows OOM kills every 90 seconds. Context: with no recent change, while legacy systems are still active. Reported by the monitoring system. | Rate customer impact for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_2aa0f155117b429e_n | noul | [
"false",
"true"
] | [
0.74,
0.26
] | The payments worker has a queue depth of 1.2M messages; additionally lost its primary replica. Context: in us-east-1 only, under reduced staffing. Reported by the operator. | Is this scenario one where: a rollback is safe here? | incident_triage | technical | yuri_v3 |
v3_086198c58b932935_n | noul | [
"false",
"true"
] | [
0.1,
0.9
] | The payments worker has a queue depth of 1.2M messages; additionally failed its health check in 3 of 5 regions. Context: under normal load, during the holiday freeze. Reported by the operator. | Is this scenario one where: this warrants waking the on-call? | incident_triage | technical | yuri_v3 |
v3_f1648f255364d933_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.06,
0.17,
0.44,
0.28,
0.05,
0
] | The etl pipeline succeeded its failover drill; additionally has a queue depth of 1.2M messages. Context: following the schema migration, following a recent audit. Reported by the operator. | Rate customer impact for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_2ef118ea20e163de_c | choice | [
"deploy_regression",
"capacity",
"dependency_failure",
"infra_fault"
] | [
0.9,
0.08,
0,
0.02
] | The etl pipeline shows OOM kills every 90 seconds; additionally lost its primary replica. Context: after the 14:00 deploy, under reduced staffing. Reported by the operator. | Root-cause hypothesis for this scenario. | incident_triage | technical | yuri_v3 |
v3_bcb604b878f26eaa_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0,
0.31,
0.69
] | The auth gateway p99 latency jumped to 8.4s; additionally shows OOM kills every 90 seconds. Context: during a 3x traffic spike, as part of a compliance sweep. Reported by the automated check. | Rate operational urgency for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_ed3328f1878146cf_n | noul | [
"false",
"true"
] | [
0.47,
0.53
] | The search cluster has connections pooling at max; additionally succeeded its failover drill. Context: following the schema migration, during the holiday freeze. Reported by the monitoring system. | Is this scenario one where: this warrants waking the on-call? | incident_triage | technical | yuri_v3 |
v3_cb119035fcb4663c_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0,
0.43,
0.57
] | The search cluster shows OOM kills every 90 seconds; additionally is serving stale data since 02:14. Context: during a 3x traffic spike, during normal operations. Reported by the operator. | Rate customer impact for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
v3_f01f5b903d107af7_c | choice | [
"SEV1",
"SEV2",
"SEV3",
"SEV4"
] | [
0.79,
0.2,
0.01,
0
] | The checkout api error rate hit 14%; additionally has a queue depth of 1.2M messages. Context: after the 14:00 deploy, as part of a compliance sweep. Reported by the supervisor. | Severity for this scenario. | incident_triage | technical | yuri_v3 |
v3_839b9435b37bae45_c | choice | [
"deploy_regression",
"capacity",
"dependency_failure",
"infra_fault"
] | [
0.72,
0.27,
0.01,
0
] | The search cluster p99 latency jumped to 8.4s; additionally failed its health check in 3 of 5 regions. Context: following the schema migration, during peak load. Reported by the automated check. | Root-cause hypothesis for this scenario. | incident_triage | technical | yuri_v3 |
v3_fa805a2778e6a379_c | choice | [
"deploy_regression",
"capacity",
"dependency_failure",
"infra_fault"
] | [
0.83,
0.02,
0.03,
0.12
] | The etl pipeline error rate hit 14%; additionally returns 503s from one availability zone. Context: following the schema migration, following a recent audit. Reported by the review queue. | Root-cause hypothesis for this scenario. | incident_triage | technical | yuri_v3 |
v3_876fbb269a01f44e_c | choice | [
"deploy_regression",
"capacity",
"dependency_failure",
"infra_fault"
] | [
0.87,
0.02,
0.11,
0
] | The etl pipeline has a queue depth of 1.2M messages; additionally failed its health check in 3 of 5 regions. Context: after the 14:00 deploy, with a new vendor onboarded. Reported by the review queue. | Root-cause hypothesis for this scenario. | incident_triage | technical | yuri_v3 |
v3_a0ce5886351e6080_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0,
0.28,
0.72
] | The payments worker shows OOM kills every 90 seconds; additionally is serving stale data since 02:14. Context: during a 3x traffic spike, shortly after a software update. Reported by the on-call engineer. | Rate operational urgency for this scenario on a 0-5 scale. | incident_triage | technical | yuri_v3 |
End of preview. Expand in Data Studio
JEV corpus - incident_triage
9,572 typed calibrated decision rows from the jev-distill-corpus-v3 corpus (domain: incident_triage).
Each row is one typed decision: kind (noul / choice / score), a state, a question, options, and a target probability distribution over the options.
Part of the per-domain split of SargeDev/jev-distill-corpus-v3 - the full corpus in one repo.
Domains:
- Downloads last month
- 44