id stringlengths 21 21 | kind stringclasses 3
values | options listlengths 2 6 | target listlengths 2 6 | state stringlengths 166 248 | question stringclasses 7
values | domain stringclasses 1
value | family stringclasses 1
value | source stringclasses 1
value |
|---|---|---|---|---|---|---|---|---|
v3_ff0a156c64e53236_n | noul | [
"false",
"true"
] | [
0.87,
0.13
] | The log shipper shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: during the batch window, mid-incident. Reported by the supervisor. | Is this scenario one where: this can wait until morning? | observability | technical | yuri_v3 |
v3_fce3179791601617_c | choice | [
"capacity",
"code_regression",
"dependency",
"telemetry_artifact"
] | [
0.01,
0.01,
0.63,
0.35
] | The metrics pipeline reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: across all regions, during an external partner integration. Reported by the supervisor. | Diagnosis for this scenario. | observability | technical | yuri_v3 |
v3_18e2129dba1ee58d_c | choice | [
"capacity",
"code_regression",
"dependency",
"telemetry_artifact"
] | [
0.02,
0.06,
0.65,
0.27
] | Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: in production only, during an external partner integration. Reported by the automated check. | Diagnosis for this scenario. | observability | technical | yuri_v3 |
v3_2e56f45b3ba05ac5_c | choice | [
"capacity",
"code_regression",
"dependency",
"telemetry_artifact"
] | [
0.92,
0.03,
0.01,
0.04
] | Service catalog-sync flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, following a recent audit. Reported by the automated check. | Diagnosis for this scenario. | observability | technical | yuri_v3 |
v3_31041d976e2fc465_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.01,
0.87,
0.12,
0
] | Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: over the last hour, during the quarterly review. Reported by the monitoring system. | Rate user-visible impact for this scenario on a 0-5 scale. | observability | technical | yuri_v3 |
v3_ef5a129d99ba731b_c | choice | [
"page_on_call",
"open_ticket",
"watch",
"auto_remediate"
] | [
0.94,
0.04,
0,
0.02
] | Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, with staffing at reduced levels. Reported by the on-call engineer. | Action for this scenario. | observability | technical | yuri_v3 |
v3_48ee605a64b55f7b_c | choice | [
"capacity",
"code_regression",
"dependency",
"telemetry_artifact"
] | [
0.29,
0.53,
0.15,
0.03
] | Dashboard checkout-funnel flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: during the batch window, during the system migration. Reported by the on-call engineer. | Diagnosis for this scenario. | observability | technical | yuri_v3 |
v3_49a28c17b6d89e43_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.03,
0.85,
0.12,
0
] | The log shipper shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: during the batch window, as part of a compliance sweep. Reported by the supervisor. | Rate anomaly confidence for this scenario on a 0-5 scale. | observability | technical | yuri_v3 |
v3_5bebd3d7f2d6c668_c | choice | [
"page_on_call",
"open_ticket",
"watch",
"auto_remediate"
] | [
0.62,
0.33,
0.03,
0.02
] | The metrics pipeline reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: in production only, while legacy systems are still active. Reported by the automated check. | Action for this scenario. | observability | technical | yuri_v3 |
v3_f25b1409884691c8_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.27,
0.71,
0.02
] | Node pgsql-14 flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: over the last hour, immediately after go-live. Reported by the on-call engineer. | Rate user-visible impact for this scenario on a 0-5 scale. | observability | technical | yuri_v3 |
v3_57b9030626dc3630_n | noul | [
"false",
"true"
] | [
0.36,
0.64
] | Service catalog-sync correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: over the last hour, during normal operations. Reported by the on-call engineer. | Is this scenario one where: this is a real incident, not an artifact? | observability | technical | yuri_v3 |
v3_647017d2485abd9c_n | noul | [
"false",
"true"
] | [
0.65,
0.35
] | The log shipper returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: during the batch window, during normal operations. Reported by the monitoring system. | Is this scenario one where: this can wait until morning? | observability | technical | yuri_v3 |
v3_5669f50f0831c0f7_n | noul | [
"false",
"true"
] | [
0.73,
0.27
] | The log shipper shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during an external partner integration. Reported by the supervisor. | Is this scenario one where: this can wait until morning? | observability | technical | yuri_v3 |
v3_069b055d1fda653b_n | noul | [
"false",
"true"
] | [
0.35,
0.65
] | The metrics pipeline matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: in production only, during the quarterly review. Reported by the review queue. | Is this scenario one where: this is a real incident, not an artifact? | observability | technical | yuri_v3 |
v3_03791fb3cdaef214_n | noul | [
"false",
"true"
] | [
0.34,
0.66
] | Service catalog-sync returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: during the batch window, during normal operations. Reported by the monitoring system. | Is this scenario one where: this can wait until morning? | observability | technical | yuri_v3 |
v3_c94ccb87b60a2083_n | noul | [
"false",
"true"
] | [
0.72,
0.28
] | Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: across all regions, as part of a compliance sweep. Reported by the on-call engineer. | Is this scenario one where: the dashboard itself is broken? | observability | technical | yuri_v3 |
v3_6b7688f70b233edf_c | choice | [
"page_on_call",
"open_ticket",
"watch",
"auto_remediate"
] | [
0.7,
0.28,
0.02,
0
] | The metrics pipeline shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: during the batch window, with staffing at reduced levels. Reported by the operator. | Action for this scenario. | observability | technical | yuri_v3 |
v3_e5c6eee36852ab2f_n | noul | [
"false",
"true"
] | [
0.46,
0.54
] | Node pgsql-14 returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: during the batch window, shortly after a software update. Reported by the operator. | Is this scenario one where: this can wait until morning? | observability | technical | yuri_v3 |
v3_61b08f43844e7291_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.02,
0.65,
0.33,
0
] | The metrics pipeline flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: in production only, during the morning shift. Reported by the on-call engineer. | Rate user-visible impact for this scenario on a 0-5 scale. | observability | technical | yuri_v3 |
v3_7d5ddbd44240fa6f_n | noul | [
"false",
"true"
] | [
0.84,
0.16
] | The metrics pipeline reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: during the batch window, during the morning shift. Reported by the automated check. | Is this scenario one where: the dashboard itself is broken? | observability | technical | yuri_v3 |
v3_c6375aebe32873e6_n | noul | [
"false",
"true"
] | [
0.87,
0.13
] | Node pgsql-14 matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during normal operations. Reported by the automated check. | Is this scenario one where: the dashboard itself is broken? | observability | technical | yuri_v3 |
v3_1e62dc24510c8cf2_c | choice | [
"capacity",
"code_regression",
"dependency",
"telemetry_artifact"
] | [
0,
0,
0.37,
0.63
] | The metrics pipeline lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during an external partner integration. Reported by the operator. | Diagnosis for this scenario. | observability | technical | yuri_v3 |
v3_21837cf7ba18fb90_n | noul | [
"false",
"true"
] | [
0.89,
0.11
] | The log shipper shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: over the last hour, with a new vendor onboarded. Reported by the review queue. | Is this scenario one where: the dashboard itself is broken? | observability | technical | yuri_v3 |
v3_2382d88f8fd7ecc3_c | choice | [
"capacity",
"code_regression",
"dependency",
"telemetry_artifact"
] | [
0.2,
0.22,
0.03,
0.55
] | The log shipper matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during the holiday freeze. Reported by the operator. | Diagnosis for this scenario. | observability | technical | yuri_v3 |
v3_53f914db37d4a5de_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.08,
0.86,
0.06
] | Dashboard checkout-funnel correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: over the last hour, shortly after a software update. Reported by the supervisor. | Rate user-visible impact for this scenario on a 0-5 scale. | observability | technical | yuri_v3 |
v3_894f65ab8abff315_n | noul | [
"false",
"true"
] | [
0.3,
0.7
] | The metrics pipeline shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: during the batch window, with staffing at reduced levels. Reported by the monitoring system. | Is this scenario one where: this is a real incident, not an artifact? | observability | technical | yuri_v3 |
v3_13a6d05023596613_n | noul | [
"false",
"true"
] | [
0.55,
0.45
] | The log shipper matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: during the batch window, during a scheduled maintenance window. Reported by the on-call engineer. | Is this scenario one where: this can wait until morning? | observability | technical | yuri_v3 |
v3_efc8fcb3cb26ca93_c | choice | [
"capacity",
"code_regression",
"dependency",
"telemetry_artifact"
] | [
0.06,
0.1,
0.06,
0.78
] | The metrics pipeline lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: during the batch window, during the holiday freeze. Reported by the operator. | Diagnosis for this scenario. | observability | technical | yuri_v3 |
v3_fe9df27e1c7fd446_c | choice | [
"page_on_call",
"open_ticket",
"watch",
"auto_remediate"
] | [
0.27,
0.44,
0.29,
0
] | Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, at the end of the fiscal period. Reported by the operator. | Action for this scenario. | observability | technical | yuri_v3 |
v3_aec98a3a9e3f1f1f_n | noul | [
"false",
"true"
] | [
0.29,
0.71
] | Service catalog-sync reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: across all regions, with a new vendor onboarded. Reported by the on-call engineer. | Is this scenario one where: this is a real incident, not an artifact? | observability | technical | yuri_v3 |
v3_96d04de87344f636_n | noul | [
"false",
"true"
] | [
0.78,
0.22
] | The log shipper reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: over the last hour, during normal operations. Reported by the supervisor. | Is this scenario one where: this can wait until morning? | observability | technical | yuri_v3 |
v3_adca8a0ea05bc659_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.01,
0.03,
0.76,
0.2,
0
] | Service catalog-sync shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: over the last hour, while legacy systems are still active. Reported by the review queue. | Rate user-visible impact for this scenario on a 0-5 scale. | observability | technical | yuri_v3 |
v3_2b1854e3c1526efc_n | noul | [
"false",
"true"
] | [
0.34,
0.66
] | Service catalog-sync flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: in production only, immediately after go-live. Reported by the supervisor. | Is this scenario one where: this is a real incident, not an artifact? | observability | technical | yuri_v3 |
v3_c4c78b0ad369674b_c | choice | [
"capacity",
"code_regression",
"dependency",
"telemetry_artifact"
] | [
0.91,
0.01,
0.02,
0.06
] | Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, under an active deadline. Reported by the review queue. | Diagnosis for this scenario. | observability | technical | yuri_v3 |
v3_efc353f7676bf1b2_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.07,
0.33,
0.59,
0.01,
0
] | The log shipper returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: over the last hour, while legacy systems are still active. Reported by the review queue. | Rate user-visible impact for this scenario on a 0-5 scale. | observability | technical | yuri_v3 |
v3_80094e3d5dddb5c0_n | noul | [
"false",
"true"
] | [
0.89,
0.11
] | The log shipper lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: during the batch window, during peak load. Reported by the on-call engineer. | Is this scenario one where: the dashboard itself is broken? | observability | technical | yuri_v3 |
v3_0ff5975111ff4320_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.01,
0.28,
0.69,
0.02
] | The metrics pipeline correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: in production only, during the holiday freeze. Reported by the monitoring system. | Rate user-visible impact for this scenario on a 0-5 scale. | observability | technical | yuri_v3 |
v3_6a5029580a679384_n | noul | [
"false",
"true"
] | [
0.35,
0.65
] | The metrics pipeline reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: across all regions, during a scheduled maintenance window. Reported by the operator. | Is this scenario one where: this is a real incident, not an artifact? | observability | technical | yuri_v3 |
v3_c5e4db7101cc3109_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.22,
0.76,
0.02
] | The log shipper matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: over the last hour, while legacy systems are still active. Reported by the monitoring system. | Rate anomaly confidence for this scenario on a 0-5 scale. | observability | technical | yuri_v3 |
v3_565edaa049f70cd9_n | noul | [
"false",
"true"
] | [
0.62,
0.38
] | Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during a scheduled maintenance window. Reported by the automated check. | Is this scenario one where: this is a real incident, not an artifact? | observability | technical | yuri_v3 |
v3_cc6595839cc38d9d_n | noul | [
"false",
"true"
] | [
0.31,
0.69
] | The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, mid-incident. Reported by the on-call engineer. | Is this scenario one where: this is a real incident, not an artifact? | observability | technical | yuri_v3 |
v3_8d66c145f5cfa212_c | choice | [
"capacity",
"code_regression",
"dependency",
"telemetry_artifact"
] | [
0.23,
0.3,
0.42,
0.05
] | Node pgsql-14 shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: across all regions, during peak load. Reported by the automated check. | Diagnosis for this scenario. | observability | technical | yuri_v3 |
v3_b9805bade1c8d8ce_n | noul | [
"false",
"true"
] | [
0.86,
0.14
] | The metrics pipeline shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: over the last hour, while on-call rotation changed. Reported by the monitoring system. | Is this scenario one where: this can wait until morning? | observability | technical | yuri_v3 |
v3_afcdc63909944fdd_n | noul | [
"false",
"true"
] | [
0.65,
0.35
] | The metrics pipeline reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: during the batch window, while on-call rotation changed. Reported by the operator. | Is this scenario one where: this can wait until morning? | observability | technical | yuri_v3 |
v3_95a7c8a1230d242c_c | choice | [
"capacity",
"code_regression",
"dependency",
"telemetry_artifact"
] | [
0.04,
0.34,
0.11,
0.51
] | Service catalog-sync flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: over the last hour, immediately after go-live. Reported by the operator. | Diagnosis for this scenario. | observability | technical | yuri_v3 |
v3_9d6fda594fc58b03_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.05,
0.58,
0.35,
0.02,
0
] | Service catalog-sync flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, under reduced staffing. Reported by the operator. | Rate anomaly confidence for this scenario on a 0-5 scale. | observability | technical | yuri_v3 |
v3_e433e948e8425db3_n | noul | [
"false",
"true"
] | [
0.75,
0.25
] | Node pgsql-14 shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: over the last hour, during peak load. Reported by the operator. | Is this scenario one where: this can wait until morning? | observability | technical | yuri_v3 |
v3_2ada9b258093da08_c | choice | [
"capacity",
"code_regression",
"dependency",
"telemetry_artifact"
] | [
0.4,
0.55,
0.01,
0.04
] | Node pgsql-14 shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: during the batch window, following a recent audit. Reported by the on-call engineer. | Diagnosis for this scenario. | observability | technical | yuri_v3 |
v3_a1309467849eac7b_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.39,
0.61,
0
] | Dashboard checkout-funnel shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: during the batch window, while legacy systems are still active. Reported by the supervisor. | Rate anomaly confidence for this scenario on a 0-5 scale. | observability | technical | yuri_v3 |
v3_fd6e5af4cf910782_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.01,
0.24,
0.73,
0.02
] | The log shipper reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: during the batch window, under an active deadline. Reported by the operator. | Rate user-visible impact for this scenario on a 0-5 scale. | observability | technical | yuri_v3 |
v3_58dadfd5861b2f57_n | noul | [
"false",
"true"
] | [
0.34,
0.66
] | The log shipper shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: over the last hour, during a scheduled maintenance window. Reported by the supervisor. | Is this scenario one where: this can wait until morning? | observability | technical | yuri_v3 |
v3_37ae90525cfdba8c_n | noul | [
"false",
"true"
] | [
0.34,
0.66
] | Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: across all regions, under reduced staffing. Reported by the supervisor. | Is this scenario one where: this is a real incident, not an artifact? | observability | technical | yuri_v3 |
v3_853d89db29a14380_c | choice | [
"page_on_call",
"open_ticket",
"watch",
"auto_remediate"
] | [
0.9,
0.08,
0,
0.02
] | Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: during the batch window, during the quarterly review. Reported by the monitoring system. | Action for this scenario. | observability | technical | yuri_v3 |
v3_aad0eb13de87d49a_n | noul | [
"false",
"true"
] | [
0.73,
0.27
] | Service catalog-sync lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during the system migration. Reported by the automated check. | Is this scenario one where: the dashboard itself is broken? | observability | technical | yuri_v3 |
v3_1b5ad631cf962775_n | noul | [
"false",
"true"
] | [
0.27,
0.73
] | Node pgsql-14 lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: during the batch window, during the holiday freeze. Reported by the on-call engineer. | Is this scenario one where: this is a real incident, not an artifact? | observability | technical | yuri_v3 |
v3_16e736628ba9a108_n | noul | [
"false",
"true"
] | [
0.88,
0.12
] | Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: across all regions, as part of a compliance sweep. Reported by the on-call engineer. | Is this scenario one where: the dashboard itself is broken? | observability | technical | yuri_v3 |
v3_984688f750256d98_n | noul | [
"false",
"true"
] | [
0.79,
0.21
] | Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during an external partner integration. Reported by the review queue. | Is this scenario one where: the dashboard itself is broken? | observability | technical | yuri_v3 |
v3_d5dfa6bb5816849b_c | choice | [
"capacity",
"code_regression",
"dependency",
"telemetry_artifact"
] | [
0.3,
0.08,
0.28,
0.34
] | The metrics pipeline shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: across all regions, during the quarterly review. Reported by the review queue. | Diagnosis for this scenario. | observability | technical | yuri_v3 |
v3_201c4196616c2a9b_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.01,
0.14,
0.73,
0.12,
0
] | Service catalog-sync returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during a scheduled maintenance window. Reported by the supervisor. | Rate anomaly confidence for this scenario on a 0-5 scale. | observability | technical | yuri_v3 |
v3_f9c6743791c50afc_n | noul | [
"false",
"true"
] | [
0.8,
0.2
] | The metrics pipeline shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: across all regions, with a new vendor onboarded. Reported by the operator. | Is this scenario one where: the dashboard itself is broken? | observability | technical | yuri_v3 |
v3_5e6c6f3e2379d60f_c | choice | [
"capacity",
"code_regression",
"dependency",
"telemetry_artifact"
] | [
0.08,
0.03,
0.39,
0.5
] | The log shipper reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: in production only, with a new vendor onboarded. Reported by the on-call engineer. | Diagnosis for this scenario. | observability | technical | yuri_v3 |
v3_fca572de5a213c93_c | choice | [
"page_on_call",
"open_ticket",
"watch",
"auto_remediate"
] | [
0.05,
0.71,
0.22,
0.02
] | Dashboard checkout-funnel returned to baseline after 11 minutes; additionally matches last Tuesday's incident signature. Context: over the last hour, during an external partner integration. Reported by the review queue. | Action for this scenario. | observability | technical | yuri_v3 |
v3_97a207dec9d37412_c | choice | [
"page_on_call",
"open_ticket",
"watch",
"auto_remediate"
] | [
0.21,
0.39,
0.36,
0.04
] | Node pgsql-14 correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: over the last hour, under an active deadline. Reported by the automated check. | Action for this scenario. | observability | technical | yuri_v3 |
v3_9233c1d4d2cbb9c9_n | noul | [
"false",
"true"
] | [
0.86,
0.14
] | Node pgsql-14 shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during the quarterly review. Reported by the automated check. | Is this scenario one where: the dashboard itself is broken? | observability | technical | yuri_v3 |
v3_0bb7bd9d8a3b5adb_c | choice | [
"page_on_call",
"open_ticket",
"watch",
"auto_remediate"
] | [
0.17,
0.66,
0.16,
0.01
] | The log shipper returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, with staffing at reduced levels. Reported by the automated check. | Action for this scenario. | observability | technical | yuri_v3 |
v3_eb5e389c3df44f62_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.01,
0.14,
0.83,
0.02,
0
] | Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: over the last hour, with staffing at reduced levels. Reported by the operator. | Rate anomaly confidence for this scenario on a 0-5 scale. | observability | technical | yuri_v3 |
v3_ac086d809344ab35_n | noul | [
"false",
"true"
] | [
0.62,
0.38
] | Dashboard checkout-funnel flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: across all regions, as part of a compliance sweep. Reported by the automated check. | Is this scenario one where: this can wait until morning? | observability | technical | yuri_v3 |
v3_bc8f3307498becf5_n | noul | [
"false",
"true"
] | [
0.74,
0.26
] | The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during an external partner integration. Reported by the operator. | Is this scenario one where: this can wait until morning? | observability | technical | yuri_v3 |
v3_b413ba0305cd020d_c | choice | [
"capacity",
"code_regression",
"dependency",
"telemetry_artifact"
] | [
0.2,
0.37,
0.02,
0.41
] | The metrics pipeline reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: across all regions, following a recent audit. Reported by the monitoring system. | Diagnosis for this scenario. | observability | technical | yuri_v3 |
v3_4711b30509e98063_n | noul | [
"false",
"true"
] | [
0.2,
0.8
] | Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, mid-incident. Reported by the operator. | Is this scenario one where: this is a real incident, not an artifact? | observability | technical | yuri_v3 |
v3_344346d1dca94942_n | noul | [
"false",
"true"
] | [
0.62,
0.38
] | Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: in production only, during an external partner integration. Reported by the operator. | Is this scenario one where: this can wait until morning? | observability | technical | yuri_v3 |
v3_01c856536e7ab858_c | choice | [
"page_on_call",
"open_ticket",
"watch",
"auto_remediate"
] | [
0.34,
0.21,
0.36,
0.09
] | Dashboard checkout-funnel reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: across all regions, under an active deadline. Reported by the automated check. | Action for this scenario. | observability | technical | yuri_v3 |
v3_9d9a3a664d376955_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.01,
0.04,
0.07,
0.66,
0.22,
0
] | The metrics pipeline reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: across all regions, during a scheduled maintenance window. Reported by the review queue. | Rate user-visible impact for this scenario on a 0-5 scale. | observability | technical | yuri_v3 |
v3_2ff29ff1fc9d0f16_n | noul | [
"false",
"true"
] | [
0.23,
0.77
] | The metrics pipeline returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: over the last hour, with staffing at reduced levels. Reported by the on-call engineer. | Is this scenario one where: this is a real incident, not an artifact? | observability | technical | yuri_v3 |
v3_0d07ac46d6dc45e9_c | choice | [
"capacity",
"code_regression",
"dependency",
"telemetry_artifact"
] | [
0.1,
0.01,
0.75,
0.14
] | Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: in production only, under reduced staffing. Reported by the automated check. | Diagnosis for this scenario. | observability | technical | yuri_v3 |
v3_3afaf2a4d79d6160_c | choice | [
"capacity",
"code_regression",
"dependency",
"telemetry_artifact"
] | [
0.19,
0.35,
0.02,
0.44
] | Dashboard checkout-funnel flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: in production only, under an active deadline. Reported by the on-call engineer. | Diagnosis for this scenario. | observability | technical | yuri_v3 |
v3_9e01b76ac1d2fe41_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.0101,
0.8182,
0.1717,
0
] | The log shipper reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: during the batch window, with a new vendor onboarded. Reported by the supervisor. | Rate user-visible impact for this scenario on a 0-5 scale. | observability | technical | yuri_v3 |
v3_a53ae687e89e5ae9_n | noul | [
"false",
"true"
] | [
0.44,
0.56
] | Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: during the batch window, with staffing at reduced levels. Reported by the review queue. | Is this scenario one where: this can wait until morning? | observability | technical | yuri_v3 |
v3_ca8dba4dcd1ba083_c | choice | [
"page_on_call",
"open_ticket",
"watch",
"auto_remediate"
] | [
0.3,
0.59,
0.11,
0
] | The metrics pipeline shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: in production only, under reduced staffing. Reported by the operator. | Action for this scenario. | observability | technical | yuri_v3 |
v3_0be0dd120daa6d13_c | choice | [
"capacity",
"code_regression",
"dependency",
"telemetry_artifact"
] | [
0.06,
0.14,
0.18,
0.62
] | Node pgsql-14 matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during the morning shift. Reported by the operator. | Diagnosis for this scenario. | observability | technical | yuri_v3 |
v3_e162c1c272515eb3_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.01,
0.07,
0.85,
0.07,
0
] | Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: during the batch window, while legacy systems are still active. Reported by the supervisor. | Rate user-visible impact for this scenario on a 0-5 scale. | observability | technical | yuri_v3 |
v3_b42d3a1d02e12882_c | choice | [
"page_on_call",
"open_ticket",
"watch",
"auto_remediate"
] | [
0.13,
0.48,
0.38,
0.01
] | Service catalog-sync returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: in production only, under reduced staffing. Reported by the review queue. | Action for this scenario. | observability | technical | yuri_v3 |
v3_2a8eb2da414f463e_n | noul | [
"false",
"true"
] | [
0.86,
0.14
] | Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: during the batch window, during the morning shift. Reported by the supervisor. | Is this scenario one where: the dashboard itself is broken? | observability | technical | yuri_v3 |
v3_ba906ede36fc534a_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.01,
0.11,
0.64,
0.24,
0
] | Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during peak load. Reported by the review queue. | Rate user-visible impact for this scenario on a 0-5 scale. | observability | technical | yuri_v3 |
v3_5d56181bcae176a6_c | choice | [
"page_on_call",
"open_ticket",
"watch",
"auto_remediate"
] | [
0.01,
0.66,
0.32,
0.01
] | The metrics pipeline shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: across all regions, at the end of the fiscal period. Reported by the supervisor. | Action for this scenario. | observability | technical | yuri_v3 |
v3_9a1574be24cd87f7_c | choice | [
"capacity",
"code_regression",
"dependency",
"telemetry_artifact"
] | [
0.34,
0.05,
0.04,
0.57
] | The log shipper shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, at the end of the fiscal period. Reported by the operator. | Diagnosis for this scenario. | observability | technical | yuri_v3 |
v3_2087f0d847954f04_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.12,
0.63,
0.24,
0.01,
0
] | Node pgsql-14 shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: in production only, under reduced staffing. Reported by the on-call engineer. | Rate anomaly confidence for this scenario on a 0-5 scale. | observability | technical | yuri_v3 |
v3_212bbe79f6c1935b_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0.01,
0,
0.01,
0.35,
0.61,
0.02
] | Dashboard checkout-funnel reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: in production only, immediately after go-live. Reported by the review queue. | Rate user-visible impact for this scenario on a 0-5 scale. | observability | technical | yuri_v3 |
v3_35b85705a61db93d_c | choice | [
"page_on_call",
"open_ticket",
"watch",
"auto_remediate"
] | [
0.42,
0.54,
0.03,
0.01
] | The log shipper shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: during the batch window, with staffing at reduced levels. Reported by the review queue. | Action for this scenario. | observability | technical | yuri_v3 |
v3_960173adc879629f_n | noul | [
"false",
"true"
] | [
0.6,
0.4
] | Dashboard checkout-funnel correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: during the batch window, under reduced staffing. Reported by the review queue. | Is this scenario one where: this can wait until morning? | observability | technical | yuri_v3 |
v3_bdf27e54313a0029_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.01,
0.48,
0.51,
0
] | Node pgsql-14 matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, at the end of the fiscal period. Reported by the operator. | Rate anomaly confidence for this scenario on a 0-5 scale. | observability | technical | yuri_v3 |
v3_51093287d6f340b9_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.05,
0.66,
0.28,
0.01,
0
] | Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: across all regions, during peak load. Reported by the on-call engineer. | Rate user-visible impact for this scenario on a 0-5 scale. | observability | technical | yuri_v3 |
v3_60d9e915b1e89d80_c | choice | [
"page_on_call",
"open_ticket",
"watch",
"auto_remediate"
] | [
0.04,
0.62,
0.28,
0.06
] | Node pgsql-14 matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: in production only, during the system migration. Reported by the review queue. | Action for this scenario. | observability | technical | yuri_v3 |
v3_07868d5791c82d2d_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0.16,
0.66,
0.18,
0,
0
] | Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: in production only, with staffing at reduced levels. Reported by the automated check. | Rate user-visible impact for this scenario on a 0-5 scale. | observability | technical | yuri_v3 |
v3_8d7074f1ceb7e28a_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0,
0.16,
0.8,
0.04
] | Service catalog-sync correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: across all regions, immediately after go-live. Reported by the review queue. | Rate user-visible impact for this scenario on a 0-5 scale. | observability | technical | yuri_v3 |
v3_d7970b88840122a1_n | noul | [
"false",
"true"
] | [
0.42,
0.58
] | Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: in production only, immediately after go-live. Reported by the automated check. | Is this scenario one where: this is a real incident, not an artifact? | observability | technical | yuri_v3 |
v3_26f0f108f603a02c_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.01,
0.36,
0.61,
0.02
] | Node pgsql-14 flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: across all regions, during normal operations. Reported by the supervisor. | Rate anomaly confidence for this scenario on a 0-5 scale. | observability | technical | yuri_v3 |
v3_9b356b5f4371089a_n | noul | [
"false",
"true"
] | [
0.83,
0.17
] | The log shipper matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, following a recent audit. Reported by the supervisor. | Is this scenario one where: the dashboard itself is broken? | observability | technical | yuri_v3 |
v3_8fe04c1c6d6ea837_s | score | [
"0",
"1",
"2",
"3",
"4",
"5"
] | [
0,
0,
0.01,
0.47,
0.51,
0.01
] | Dashboard checkout-funnel correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: during the batch window, as part of a compliance sweep. Reported by the review queue. | Rate user-visible impact for this scenario on a 0-5 scale. | observability | technical | yuri_v3 |
v3_083572132303d418_c | choice | [
"page_on_call",
"open_ticket",
"watch",
"auto_remediate"
] | [
0.67,
0.28,
0.04,
0.01
] | Service catalog-sync flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: during the batch window, during the morning shift. Reported by the on-call engineer. | Action for this scenario. | observability | technical | yuri_v3 |
End of preview. Expand in Data Studio
JEV corpus - observability
9,711 typed calibrated decision rows from the jev-distill-corpus-v3 corpus (domain: observability).
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
- 35