{"id": "v3_ff0a156c64e53236_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "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.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fce3179791601617_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.63, 0.35], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_18e2129dba1ee58d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.06, 0.65, 0.27], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2e56f45b3ba05ac5_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.92, 0.03, 0.01, 0.04], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_31041d976e2fc465_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.87, 0.12, 0.0], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ef5a129d99ba731b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.94, 0.04, 0.0, 0.02], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_48ee605a64b55f7b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.29, 0.53, 0.15, 0.03], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_49a28c17b6d89e43_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.85, 0.12, 0.0], "state": "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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5bebd3d7f2d6c668_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.62, 0.33, 0.03, 0.02], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f25b1409884691c8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.27, 0.71, 0.02], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_57b9030626dc3630_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "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.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_647017d2485abd9c_n", "kind": "noul", "options": ["false", "true"], "target": [0.65, 0.35], "state": "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.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5669f50f0831c0f7_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "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.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_069b055d1fda653b_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "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.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_03791fb3cdaef214_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "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.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c94ccb87b60a2083_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "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.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6b7688f70b233edf_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.7, 0.28, 0.02, 0.0], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e5c6eee36852ab2f_n", "kind": "noul", "options": ["false", "true"], "target": [0.46, 0.54], "state": "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.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_61b08f43844e7291_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.65, 0.33, 0.0], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7d5ddbd44240fa6f_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "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.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c6375aebe32873e6_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "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.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1e62dc24510c8cf2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.0, 0.37, 0.63], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_21837cf7ba18fb90_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "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.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2382d88f8fd7ecc3_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.2, 0.22, 0.03, 0.55], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_53f914db37d4a5de_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.08, 0.86, 0.06], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_894f65ab8abff315_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "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.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_13a6d05023596613_n", "kind": "noul", "options": ["false", "true"], "target": [0.55, 0.45], "state": "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.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_efc8fcb3cb26ca93_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.06, 0.1, 0.06, 0.78], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fe9df27e1c7fd446_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.27, 0.44, 0.29, 0.0], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aec98a3a9e3f1f1f_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "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.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_96d04de87344f636_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "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.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_adca8a0ea05bc659_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.03, 0.76, 0.2, 0.0], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2b1854e3c1526efc_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "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.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c4c78b0ad369674b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.91, 0.01, 0.02, 0.06], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_efc353f7676bf1b2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.07, 0.33, 0.59, 0.01, 0.0], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_80094e3d5dddb5c0_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "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.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ff5975111ff4320_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.28, 0.69, 0.02], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6a5029580a679384_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "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.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c5e4db7101cc3109_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.22, 0.76, 0.02], "state": "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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_565edaa049f70cd9_n", "kind": "noul", "options": ["false", "true"], "target": [0.62, 0.38], "state": "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.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cc6595839cc38d9d_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "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.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8d66c145f5cfa212_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.23, 0.3, 0.42, 0.05], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b9805bade1c8d8ce_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "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.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_afcdc63909944fdd_n", "kind": "noul", "options": ["false", "true"], "target": [0.65, 0.35], "state": "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.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_95a7c8a1230d242c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.34, 0.11, 0.51], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9d6fda594fc58b03_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.58, 0.35, 0.02, 0.0], "state": "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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e433e948e8425db3_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "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.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2ada9b258093da08_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.4, 0.55, 0.01, 0.04], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a1309467849eac7b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.39, 0.61, 0.0], "state": "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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fd6e5af4cf910782_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.24, 0.73, 0.02], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_58dadfd5861b2f57_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "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.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_37ae90525cfdba8c_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "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.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_853d89db29a14380_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.9, 0.08, 0.0, 0.02], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aad0eb13de87d49a_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "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.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1b5ad631cf962775_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "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.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_16e736628ba9a108_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "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.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_984688f750256d98_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "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.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d5dfa6bb5816849b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.3, 0.08, 0.28, 0.34], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_201c4196616c2a9b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.14, 0.73, 0.12, 0.0], "state": "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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f9c6743791c50afc_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "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.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5e6c6f3e2379d60f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.08, 0.03, 0.39, 0.5], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fca572de5a213c93_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.05, 0.71, 0.22, 0.02], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_97a207dec9d37412_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.21, 0.39, 0.36, 0.04], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9233c1d4d2cbb9c9_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "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.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0bb7bd9d8a3b5adb_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.17, 0.66, 0.16, 0.01], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eb5e389c3df44f62_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.14, 0.83, 0.02, 0.0], "state": "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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ac086d809344ab35_n", "kind": "noul", "options": ["false", "true"], "target": [0.62, 0.38], "state": "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.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bc8f3307498becf5_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "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.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b413ba0305cd020d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.2, 0.37, 0.02, 0.41], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4711b30509e98063_n", "kind": "noul", "options": ["false", "true"], "target": [0.2, 0.8], "state": "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.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_344346d1dca94942_n", "kind": "noul", "options": ["false", "true"], "target": [0.62, 0.38], "state": "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.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_01c856536e7ab858_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.34, 0.21, 0.36, 0.09], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9d9a3a664d376955_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.04, 0.07, 0.66, 0.22, 0.0], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2ff29ff1fc9d0f16_n", "kind": "noul", "options": ["false", "true"], "target": [0.23, 0.77], "state": "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.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0d07ac46d6dc45e9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.1, 0.01, 0.75, 0.14], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3afaf2a4d79d6160_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.19, 0.35, 0.02, 0.44], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9e01b76ac1d2fe41_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0101, 0.8182, 0.1717, 0.0], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a53ae687e89e5ae9_n", "kind": "noul", "options": ["false", "true"], "target": [0.44, 0.56], "state": "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.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca8dba4dcd1ba083_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.3, 0.59, 0.11, 0.0], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0be0dd120daa6d13_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.06, 0.14, 0.18, 0.62], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e162c1c272515eb3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.07, 0.85, 0.07, 0.0], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b42d3a1d02e12882_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.13, 0.48, 0.38, 0.01], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2a8eb2da414f463e_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "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.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ba906ede36fc534a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.11, 0.64, 0.24, 0.0], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5d56181bcae176a6_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.66, 0.32, 0.01], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9a1574be24cd87f7_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.34, 0.05, 0.04, 0.57], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2087f0d847954f04_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.12, 0.63, 0.24, 0.01, 0.0], "state": "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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_212bbe79f6c1935b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.0, 0.01, 0.35, 0.61, 0.02], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_35b85705a61db93d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.42, 0.54, 0.03, 0.01], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_960173adc879629f_n", "kind": "noul", "options": ["false", "true"], "target": [0.6, 0.4], "state": "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.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bdf27e54313a0029_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.48, 0.51, 0.0], "state": "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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_51093287d6f340b9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.66, 0.28, 0.01, 0.0], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_60d9e915b1e89d80_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.04, 0.62, 0.28, 0.06], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_07868d5791c82d2d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.16, 0.66, 0.18, 0.0, 0.0], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8d7074f1ceb7e28a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.16, 0.8, 0.04], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d7970b88840122a1_n", "kind": "noul", "options": ["false", "true"], "target": [0.42, 0.58], "state": "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.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_26f0f108f603a02c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.36, 0.61, 0.02], "state": "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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9b356b5f4371089a_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "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.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8fe04c1c6d6ea837_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.47, 0.51, 0.01], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_083572132303d418_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.67, 0.28, 0.04, 0.01], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b823c5d2c4c506a_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: in production only, immediately after go-live. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4e7bc91902129acb_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.49, 0.4, 0.1, 0.01], "state": "The log shipper correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: across all regions, during an external partner integration. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6360776fb1e276c2_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: over the last hour, following a recent audit. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7bde691cefeedcf1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.68, 0.31, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: across all regions, with staffing at reduced levels. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_841c3cd4ebb9bdc0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.15, 0.83, 0.02], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: over the last hour, during the morning shift. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_36923e671b026ebe_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.73, 0.04, 0.11, 0.12], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: over the last hour, during peak load. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c70871659c3c8ff5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.28, 0.68, 0.03], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: during the batch window, shortly after a software update. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_07e74f2692ddc9f0_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "The log shipper shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: across all regions, shortly after a software update. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5643c936177f0ea7_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.04, 0.74, 0.18], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: across all regions, during a scheduled maintenance window. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5f467367354d8ee2_n", "kind": "noul", "options": ["false", "true"], "target": [0.69, 0.31], "state": "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, during a scheduled maintenance window. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fb791193185fb3f3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.28, 0.61, 0.09, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, with a new vendor onboarded. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1e662f3ffa543bd3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.56, 0.42, 0.0], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: over the last hour, during an external partner integration. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ce62d55fd3ddfcff_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.14, 0.83, 0.03], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: over the last hour, shortly after a software update. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_85b33f2c32a7b687_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.02, 0.86, 0.12], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, shortly after a software update. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4823de6a955f1d2b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.38, 0.38, 0.23, 0.01], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: during the batch window, during the quarterly review. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_468ca58642b7f647_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, with staffing at reduced levels. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a9072bff2b56fa32_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.53, 0.47, 0.0], "state": "The log shipper flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during normal operations. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2251e74fea8f70c1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.06, 0.83, 0.11], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, under an active deadline. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fc96fde01460ee2d_n", "kind": "noul", "options": ["false", "true"], "target": [0.71, 0.29], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: in production only, under reduced staffing. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a945668295e4f718_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: during the batch window, while on-call rotation changed. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e3500517b879aeda_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during the morning shift. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_65ca17f9372e1113_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: during the batch window, with staffing at reduced levels. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_87140ad0960ddcf1_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, at the end of the fiscal period. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ee7816cd9003d341_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.53, 0.46, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: in production only, while legacy systems are still active. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f3fbfe3f13be8618_n", "kind": "noul", "options": ["false", "true"], "target": [0.48, 0.52], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, shortly after a software update. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2053e3f435637359_n", "kind": "noul", "options": ["false", "true"], "target": [0.38, 0.62], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: over the last hour, as part of a compliance sweep. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6758e4fb9ad82d86_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.71, 0.26, 0.0], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: during the batch window, during the quarterly review. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_455f09eefb92e1fa_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.77, 0.22, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: over the last hour, during normal operations. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_96f05717227a6ec2_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: across all regions, at the end of the fiscal period. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4cdad156cf9c9766_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: in production only, while legacy systems are still active. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6ecd546ed440f92d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.09, 0.0, 0.31, 0.6], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, mid-incident. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5c9857624b6b7335_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.09, 0.81, 0.1], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: across all regions, during the system migration. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7ee79485d64c1165_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.95, 0.04, 0.01], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: over the last hour, shortly after a software update. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f28d8c77725efe8b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.69, 0.3, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: over the last hour, under an active deadline. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4588982227a81cf6_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.87, 0.12, 0.01, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, following a recent audit. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d43487580c637577_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.02, 0.52, 0.45, 0.01], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: across all regions, as part of a compliance sweep. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_60979879de07aeae_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.14, 0.83, 0.03], "state": "Dashboard checkout-funnel 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 operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4a05de57be0e607f_n", "kind": "noul", "options": ["false", "true"], "target": [0.58, 0.42], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: over the last hour, following a recent audit. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_29ee6e62a09b9992_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.41, 0.59, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during an external partner integration. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6e508750f8b38761_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.31, 0.19, 0.16, 0.34], "state": "The log shipper reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: in production only, during peak load. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c9995ce3b68dba4c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.74, 0.24, 0.01, 0.01], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, shortly after a software update. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1ac955cbb2df91fd_n", "kind": "noul", "options": ["false", "true"], "target": [0.42, 0.58], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: over the last hour, during the system migration. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a3dc59b5d6b06448_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.24, 0.61, 0.1, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: across all regions, as part of a compliance sweep. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_905c2d544341369c_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: in production only, during the system migration. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_66392cfefcaa9ea4_n", "kind": "noul", "options": ["false", "true"], "target": [0.17, 0.83], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8a7810bd7055a8b1_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, at the end of the fiscal period. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e7cfb2b39213a511_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: across all regions, following a recent audit. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cf899c2c42d90245_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.24, 0.05, 0.18, 0.53], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during the morning shift. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0d486d0b7385002c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.09, 0.86, 0.05], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, under reduced staffing. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0e6ab303437251b8_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.02, 0.18, 0.79], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: across all regions, following a recent audit. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_11e74406f2c69529_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.04, 0.81, 0.15], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: across all regions, during peak load. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_60141a44e3b59106_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.17, 0.78, 0.04], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: across all regions, during normal operations. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8a471ef95a0ece3c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.99, 0.01, 0.0, 0.0], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: in production only, mid-incident. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_88f7ed5f46ac527a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.11, 0.79, 0.1], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during peak load. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5c901e4b4cdbbf66_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.06, 0.86, 0.08], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: during the batch window, with staffing at reduced levels. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b7518a39270d96e_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: during the batch window, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d4d0a1a65fd39dec_n", "kind": "noul", "options": ["false", "true"], "target": [0.6, 0.4], "state": "The log shipper shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: over the last hour, following a recent audit. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9a70db0dd23672d5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.43, 0.57, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, shortly after a software update. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c24672b83c43d101_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "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 a scheduled maintenance window. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e10bb6384fe1548f_n", "kind": "noul", "options": ["false", "true"], "target": [0.48, 0.52], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: over the last hour, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bc8f3307498becf5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.24, 0.53, 0.22, 0.0], "state": "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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e41472fb4e217242_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.16, 0.58, 0.02, 0.24], "state": "The log shipper lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: in production only, immediately after go-live. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8bbcafc2d335d18c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.93, 0.06, 0.01, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: over the last hour, during peak load. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9ad9fee1a68a23cd_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "The log shipper lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: in production only, at the end of the fiscal period. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_efc8fcb3cb26ca93_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "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.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_77e60a417a4a2d0a_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: in production only, during normal operations. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_827bf7e6e90a2b23_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.34, 0.27, 0.34, 0.04], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: across all regions, immediately after go-live. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d12e6c036d8cb1b0_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.23, 0.25, 0.14, 0.38], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally matches last Tuesday's incident signature. Context: across all regions, during normal operations. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c3389c61e89d727a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.57, 0.32, 0.09, 0.02], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during the holiday freeze. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8aacede6799cccd2_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.54, 0.36, 0.07, 0.03], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: over the last hour, as part of a compliance sweep. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cb4f7665497fea7f_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, as part of a compliance sweep. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_74b1284e36c182d3_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.32, 0.04, 0.35, 0.29], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, immediately after go-live. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d4abfded1cdfc7aa_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.4, 0.44, 0.14, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, at the end of the fiscal period. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c4b0beaae4f8368e_n", "kind": "noul", "options": ["false", "true"], "target": [0.41, 0.59], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: during the batch window, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a7c6dc939f337830_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.29, 0.04, 0.44, 0.23], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: during the batch window, while legacy systems are still active. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9ce93d49d2f29bc8_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "The metrics pipeline lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: in production only, during peak load. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b6ec7181a44acfe3_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.94, 0.06, 0.0, 0.0], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: over the last hour, immediately after go-live. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_71e45e9d99f4ac48_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.13, 0.85, 0.01], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: during the batch window, during the system migration. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_556c80c853a5e281_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.81, 0.13, 0.05, 0.01], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: over the last hour, under reduced staffing. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_76588361c48cd90d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.29, 0.7, 0.01], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: in production only, under reduced staffing. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_62750f00a5a3d36e_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: over the last hour, immediately after go-live. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ba7378867f32f758_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.01, 0.01, 0.95], "state": "The log shipper lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the quarterly review. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f1a9b30315d91a07_n", "kind": "noul", "options": ["false", "true"], "target": [0.7, 0.3], "state": "The log shipper flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: during the batch window, while legacy systems are still active. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9ffb5b5d6c4ace52_n", "kind": "noul", "options": ["false", "true"], "target": [0.41, 0.59], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: in production only, during the holiday freeze. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fe95596ba68177bc_n", "kind": "noul", "options": ["false", "true"], "target": [0.49, 0.51], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during the system migration. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_772a46962736a64d_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: in production only, under reduced staffing. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_17c7e4a4a80c79d3_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.61, 0.37, 0.02, 0.0], "state": "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 review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1b5ad631cf962775_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.21, 0.78, 0.01], "state": "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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8a471ef95a0ece3c_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: in production only, mid-incident. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_851bd2badb5f5560_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.01, 0.21, 0.72, 0.05], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_85f813f277b23c44_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.28, 0.71, 0.01], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, following a recent audit. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2f9b56e7ef8f3e7c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.8, 0.17, 0.0], "state": "The metrics pipeline shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: in production only, shortly after a software update. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4bcf900df94ce124_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.2, 0.78, 0.02], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: across all regions, shortly after a software update. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e774b490445dda10_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: over the last hour, at the end of the fiscal period. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_38781e2e071af25f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.22, 0.75, 0.02], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: in production only, following a recent audit. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7087b7c9b084b4b0_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: in production only, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c0e9313553ca6a7b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.22, 0.76, 0.02], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: over the last hour, with staffing at reduced levels. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_654c01db7c4c4b8d_n", "kind": "noul", "options": ["false", "true"], "target": [0.19, 0.81], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: during the batch window, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0c134def800aa1c9_n", "kind": "noul", "options": ["false", "true"], "target": [0.38, 0.62], "state": "The log shipper matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: during the batch window, shortly after a software update. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_36e2ce5740948990_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_79e2542a894980f9_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.64, 0.34, 0.01, 0.01], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: across all regions, during the morning shift. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1f024b689f270178_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.85, 0.07, 0.08], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: across all regions, shortly after a software update. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3071548093364da5_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "The log shipper matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: across all regions, during peak load. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8f46112e7084c475_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.19, 0.67, 0.11, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: across all regions, following a recent audit. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8951268fd6299411_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.69, 0.26, 0.03, 0.02], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: during the batch window, following a recent audit. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_99013ca6d731cb82_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.17, 0.25, 0.56, 0.01, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during a scheduled maintenance window. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a91ff7f327926f23_n", "kind": "noul", "options": ["false", "true"], "target": [0.45, 0.55], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: over the last hour, as part of a compliance sweep. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b18d2feb847fa4ff_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.41, 0.03, 0.26, 0.3], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the quarterly review. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7885f1677fba5cb2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.42, 0.58, 0.0], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: across all regions, during the quarterly review. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_466b6e9a7228ff54_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.31, 0.68, 0.01], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, while on-call rotation changed. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fa187083df92d77e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.05, 0.81, 0.13, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: during the batch window, as part of a compliance sweep. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dc615a99273670b9_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.2, 0.47, 0.25, 0.08], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: over the last hour, as part of a compliance sweep. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7f80f01c5cdd444b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.09, 0.82, 0.02, 0.07], "state": "Service catalog-sync shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: in production only, immediately after go-live. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bcbc38fa26d067f8_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: in production only, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bc84ff902854fa73_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.0, 0.99, 0.01], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_35e102fa1fc1cc2d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.54, 0.45, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: across all regions, shortly after a software update. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_681e0bca6ec34e87_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.0, 0.49, 0.5], "state": "Service catalog-sync lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: during the batch window, as part of a compliance sweep. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8ed9de562d3a6bbc_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.56, 0.41, 0.02, 0.01], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the quarterly review. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f489dc894211209f_n", "kind": "noul", "options": ["false", "true"], "target": [0.45, 0.55], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: during the batch window, under reduced staffing. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9bf81910b00d1383_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during an external partner integration. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_27fc771fbfe70a3f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.27, 0.69, 0.03], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; 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 supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d8e8cc48cc1147cf_n", "kind": "noul", "options": ["false", "true"], "target": [0.62, 0.38], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: during the batch window, with a new vendor onboarded. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_456350603fa2e7af_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_53ff01805160aa1f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.83, 0.16, 0.01, 0.0], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: over the last hour, during normal operations. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ceda2a9239c50953_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.01, 0.03, 0.39, 0.54, 0.02], "state": "The log shipper correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: in production only, during an external partner integration. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_12d6b12542b29960_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.32, 0.58, 0.05], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during a scheduled maintenance window. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1e4150f7cac3fb69_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.09, 0.84, 0.07], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, under an active deadline. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b0b77bf66bda844_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.41, 0.57, 0.01], "state": "The log shipper matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: during the batch window, immediately after go-live. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f2e825d080e92416_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.3, 0.48, 0.22, 0.0, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: during the batch window, with a new vendor onboarded. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1da04e52cc450f8f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.33, 0.56, 0.09, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: over the last hour, following a recent audit. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_53f92526701613b6_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "The log shipper reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: in production only, with staffing at reduced levels. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a99ccb61670d717b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.5, 0.33, 0.16, 0.01], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during peak load. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e8c3a0081e4b3c96_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.06, 0.88, 0.06], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: across all regions, following a recent audit. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3481db3cdf7f5b86_n", "kind": "noul", "options": ["false", "true"], "target": [0.21, 0.79], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: over the last hour, shortly after a software update. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0c036f2017501725_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: in production only, during normal operations. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d12e6c036d8cb1b0_n", "kind": "noul", "options": ["false", "true"], "target": [0.37, 0.63], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally matches last Tuesday's incident signature. Context: across all regions, during normal operations. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e451d3fef511fe19_n", "kind": "noul", "options": ["false", "true"], "target": [0.51, 0.49], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: during the batch window, while on-call rotation changed. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aa368f98bb0e3dd7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.37, 0.57, 0.01, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: over the last hour, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_31fc0aa79f95762a_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: across all regions, during peak load. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_10a82816ac73e3b2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.06, 0.64, 0.29, 0.0], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: in production only, during an external partner integration. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_971982240c76a7a1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.21, 0.76, 0.03], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: across all regions, following a recent audit. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cee24fa5ca3ef226_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.24, 0.71, 0.04], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: in production only, during the system migration. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c4dbccb422e5bcea_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.93, 0.05, 0.0, 0.02], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally flags a step-function change in error slope. Context: during the batch window, during the holiday freeze. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e455ff57eb833cdb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.3, 0.69, 0.01], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: during the batch window, under an active deadline. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b030858a4608ba2_n", "kind": "noul", "options": ["false", "true"], "target": [0.53, 0.47], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: during the batch window, mid-incident. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8182e66bd543e93d_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally flags a step-function change in error slope. Context: over the last hour, during the morning shift. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8d6150966e165d09_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.49, 0.19, 0.16, 0.16], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, under an active deadline. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_901674df022a7e68_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.14, 0.67, 0.18, 0.0], "state": "Service catalog-sync correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: across all regions, during peak load. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3def9c518bb7fdc1_n", "kind": "noul", "options": ["false", "true"], "target": [0.5, 0.5], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: across all regions, during the holiday freeze. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e3e7347614a55680_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: in production only, mid-incident. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_112bccad2b878170_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during the morning shift. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1c6cdbe10b67e762_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.0, 0.27, 0.72], "state": "The log shipper lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: across all regions, during normal operations. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_99676f46df41db7d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.64, 0.29, 0.06, 0.01], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during an external partner integration. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d342bd2d1e301a7a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.15, 0.44, 0.34, 0.06, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: across all regions, mid-incident. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_82af816a7946017e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.25, 0.09, 0.42, 0.24], "state": "The metrics pipeline correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: during the batch window, following a recent audit. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_456a1d1c0045078a_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: across all regions, under reduced staffing. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fe5d1a897a972bd3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.11, 0.46, 0.4, 0.03, 0.0], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: in production only, under reduced staffing. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bb0fbbfbdb697cb8_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.63, 0.32, 0.03, 0.02], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: across all regions, while on-call rotation changed. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9d75fd8975599d47_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.16, 0.83, 0.01], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, shortly after a software update. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4711b30509e98063_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.6, 0.01, 0.0, 0.39], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0010a37e03a70c3f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.42, 0.0, 0.02, 0.56], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: across all regions, during peak load. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0c978cd45b6cb01e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.82, 0.15, 0.01, 0.02], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: during the batch window, shortly after a software update. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f43efce8babe58d6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.76, 0.19, 0.01, 0.0], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the morning shift. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_76a8b4df68809f82_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.03, 0.18, 0.62, 0.16, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: in production only, while legacy systems are still active. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4052f5d37f117db3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.1, 0.85, 0.05], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: during the batch window, during peak load. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_48f606f4c92bc39f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.02, 0.54, 0.31, 0.13], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: during the batch window, during an external partner integration. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_06ddfbdc2832b1a6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.6, 0.39, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; 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 supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca4d74b0fce0bbe4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.14, 0.78, 0.06, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: during the batch window, while on-call rotation changed. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b4e2c416f547c80e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.9, 0.06, 0.01, 0.03], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: across all regions, mid-incident. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b7592a9bb394666a_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: in production only, as part of a compliance sweep. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d793baadbb4826d3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.05, 0.73, 0.21, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: across all regions, under reduced staffing. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8d7ca293241c40aa_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: over the last hour, immediately after go-live. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1873fee42c08954c_n", "kind": "noul", "options": ["false", "true"], "target": [0.57, 0.43], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: over the last hour, during normal operations. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c264d463301bf161_n", "kind": "noul", "options": ["false", "true"], "target": [0.67, 0.33], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: during the batch window, while on-call rotation changed. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0e033fed180f3a11_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.07, 0.63, 0.28, 0.0], "state": "Service catalog-sync flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: in production only, during a scheduled maintenance window. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_de90092fcc6136a3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.05, 0.82, 0.13], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: in production only, during peak load. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8bdfeca16a246683_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.04, 0.7, 0.26, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: over the last hour, during the morning shift. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_37cf5fda142ee2d9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.54, 0.01, 0.04, 0.41], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during the holiday freeze. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ef79b4f0829010d1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.12, 0.1, 0.55, 0.23], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: in production only, with a new vendor onboarded. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7d75b0710d84c256_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.3434, 0.5455, 0.101, 0.0101], "state": "The log shipper reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: during the batch window, with a new vendor onboarded. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_67dabcbe7f0b42bf_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: over the last hour, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c408e7af0ba3b01f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.09, 0.47, 0.35, 0.09], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: during the batch window, shortly after a software update. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_840b04b0ffcb1a93_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.75, 0.18, 0.01, 0.0], "state": "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, following a recent audit. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3dcfc9c612e22cea_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.22, 0.29, 0.46], "state": "The log shipper correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: across all regions, during normal operations. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bcbc38fa26d067f8_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.0, 0.42, 0.55], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: in production only, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e406804a28d03521_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.5, 0.47, 0.01], "state": "The metrics pipeline lost 4 minutes of trace data; 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 automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2359a7003883c3ea_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.02, 0.63, 0.33, 0.02], "state": "The log shipper matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: across all regions, following a recent audit. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d9c469bca95a91f8_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.13, 0.19, 0.65], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: in production only, while legacy systems are still active. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1b76625ca98d7956_n", "kind": "noul", "options": ["false", "true"], "target": [0.43, 0.57], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during the holiday freeze. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7989573b8beb385a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.09, 0.34, 0.55, 0.02, 0.0], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: over the last hour, with staffing at reduced levels. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_442baca2c631d496_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "The log shipper correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: across all regions, during peak load. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_47332bf69763991b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.27, 0.54, 0.15, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: in production only, mid-incident. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ec0d5e1348186e49_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.27, 0.53, 0.2, 0.0, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: over the last hour, during a scheduled maintenance window. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2a63604f303b271f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.54, 0.22, 0.2, 0.04], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: in production only, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d73c6d72a77ca8f6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.56, 0.43, 0.0], "state": "The log shipper matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: across all regions, while on-call rotation changed. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_64ee4969bf48651c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.52, 0.46, 0.01], "state": "Service catalog-sync shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: across all regions, with a new vendor onboarded. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e7c9f9ceda672ec5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.01, 0.79, 0.2], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: over the last hour, immediately after go-live. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8d078dbfd2394745_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.59, 0.34, 0.06, 0.0, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: across all regions, with a new vendor onboarded. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_83c1a04a4d35d43b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.01, 0.52, 0.43], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: over the last hour, under reduced staffing. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_66d80698bd02fe75_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: in production only, with a new vendor onboarded. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e58f1e8b5e5bbfad_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The log shipper shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: over the last hour, during the quarterly review. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e930831482b59e58_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.17, 0.76, 0.06], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: in production only, under an active deadline. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1773e44d7f04a9f7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.2, 0.76, 0.03, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: across all regions, during the system migration. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a4969c7289a63af4_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "The log shipper shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: across all regions, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8a5c4babefb361ca_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.16, 0.81, 0.03], "state": "The metrics pipeline flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during the holiday freeze. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e69b00e4c5dec16a_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: during the batch window, as part of a compliance sweep. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7e9a8d9a8eb1316c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.55, 0.44, 0.0], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: during the batch window, while on-call rotation changed. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5546744a16703882_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.09, 0.08, 0.47, 0.36], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: in production only, with a new vendor onboarded. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_57684952aeeb3e85_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.45, 0.1, 0.03, 0.42], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: during the batch window, mid-incident. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ef82a64766ff1b8b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.26, 0.72, 0.02], "state": "The log shipper flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: across all regions, during the holiday freeze. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9532084c9ed62bdf_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.69, 0.29, 0.02, 0.0], "state": "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 monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_92b1f9b106fc6c8b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.75, 0.0, 0.02, 0.23], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, under reduced staffing. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_01a35b27674392a1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.25, 0.05, 0.2, 0.5], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, with a new vendor onboarded. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ed936eb5fe70a25b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.58, 0.0, 0.21, 0.21], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during the quarterly review. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ea760551b7d00e36_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.66, 0.01, 0.27, 0.06], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: across all regions, during normal operations. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c7786d696b458edc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.75, 0.22, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: in production only, during the morning shift. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e58f1e8b5e5bbfad_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.28, 0.19, 0.34, 0.19], "state": "The log shipper shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: over the last hour, during the quarterly review. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a7c7f2b922c368fe_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: in production only, during the morning shift. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e1e1bcfd7eca4832_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.05, 0.49, 0.45, 0.01], "state": "The log shipper flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: during the batch window, during the quarterly review. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6d99814a6e888011_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Service catalog-sync shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: in production only, during peak load. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b28e2d0ccd3aa9b0_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: across all regions, under an active deadline. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_53407943d6fc4d96_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.14, 0.45, 0.4, 0.01, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: during the batch window, during the holiday freeze. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_246b4b115e9dc514_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.17, 0.72, 0.08, 0.03, 0.0, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: over the last hour, at the end of the fiscal period. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4f6f81272d9c789c_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: in production only, during a scheduled maintenance window. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_87ab9afb3a19bbd5_n", "kind": "noul", "options": ["false", "true"], "target": [0.69, 0.31], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: in production only, immediately after go-live. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4e147ada80a8dcdb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.61, 0.31, 0.03, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: during the batch window, following a recent audit. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b682a359127d9ec4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.29, 0.54, 0.17, 0.0, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: during the batch window, while on-call rotation changed. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eb24bc1e23923820_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.11, 0.58, 0.3, 0.01], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during the morning shift. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e3a420e8604f6bfb_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.53, 0.39, 0.06, 0.02], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during the holiday freeze. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c96e41496d30b863_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.46, 0.52, 0.01], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: in production only, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6a3a545ccc4e6807_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.36, 0.29, 0.32, 0.02, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: during the batch window, during a scheduled maintenance window. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e888ad684ee71b35_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.11, 0.23, 0.11, 0.55], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: in production only, during normal operations. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e5e471ada76e6ef2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.1, 0.83, 0.07], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: in production only, with staffing at reduced levels. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1528d2a2f47bd904_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.59, 0.3, 0.09, 0.02], "state": "The log shipper reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: over the last hour, during the holiday freeze. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_596463621ef4ec46_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.7, 0.2, 0.09, 0.01], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: over the last hour, during the system migration. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_76c8886f02ccf218_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.11, 0.01, 0.03, 0.85], "state": "The log shipper lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: during the batch window, as part of a compliance sweep. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6cf8107ef036082b_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: over the last hour, with staffing at reduced levels. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4d291bb2bb8bde41_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.28, 0.58, 0.14, 0.0], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: over the last hour, while legacy systems are still active. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3b3f8f2a3a82fb3a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.38, 0.04, 0.03, 0.55], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: across all regions, under an active deadline. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bfdd70984d0564b2_n", "kind": "noul", "options": ["false", "true"], "target": [0.42, 0.58], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during the quarterly review. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_840c9f402a8099bd_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.1, 0.66, 0.24, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: over the last hour, during an external partner integration. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_06db838a044838b2_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.85, 0.13, 0.02, 0.0], "state": "Service catalog-sync correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: during the batch window, during peak load. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_062e6ffb1e13c0cf_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.48, 0.52, 0.0], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during the system migration. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a1a5e9d86e2c463f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.45, 0.54, 0.0], "state": "The metrics pipeline shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: across all regions, immediately after go-live. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7d090c18c10f1c54_n", "kind": "noul", "options": ["false", "true"], "target": [0.23, 0.77], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: in production only, following a recent audit. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b29a0c843627ccb2_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "The log shipper returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: across all regions, during normal operations. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2ff29ff1fc9d0f16_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.12, 0.77, 0.1, 0.0], "state": "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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_137bc5b4eaa7f808_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.23, 0.75, 0.02], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: over the last hour, under reduced staffing. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c3562ebd5b0d7dca_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.19, 0.52, 0.28, 0.01, 0.0], "state": "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, as part of a compliance sweep. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6b5f524f399edc48_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.54, 0.04, 0.03, 0.39], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during a scheduled maintenance window. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ac9bbe311a4a14ee_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.38, 0.01, 0.44, 0.17], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, while legacy systems are still active. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dc615a99273670b9_n", "kind": "noul", "options": ["false", "true"], "target": [0.64, 0.36], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: over the last hour, as part of a compliance sweep. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eba233a568cd214d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.24, 0.69, 0.01, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: during the batch window, with staffing at reduced levels. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_478e92f3536ea767_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The log shipper reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: during the batch window, mid-incident. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5a00a871f09e89bb_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: in production only, during peak load. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eef5fb97e67f8ba4_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, at the end of the fiscal period. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9d2cc02020d814ff_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, as part of a compliance sweep. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_22109dc3b16c5d1e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.13, 0.67, 0.19, 0.01], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: over the last hour, while legacy systems are still active. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_335498e1b7cc01fc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.12, 0.61, 0.26, 0.01, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: across all regions, shortly after a software update. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f35184d970045cfe_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.22, 0.24, 0.08, 0.46], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: over the last hour, immediately after go-live. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1fb4b566884b701a_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "The metrics pipeline 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 operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_71d8e406f440ac30_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.33, 0.59, 0.08, 0.0], "state": "The metrics pipeline shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: during the batch window, during the morning shift. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_56088222b0d835e9_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.61, 0.38, 0.01, 0.0], "state": "The log shipper matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: during the batch window, during the holiday freeze. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_751ea2ffabf34b6b_n", "kind": "noul", "options": ["false", "true"], "target": [0.68, 0.32], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: during the batch window, with a new vendor onboarded. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8cd4f0e7d6a49602_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.05, 0.82, 0.13], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: during the batch window, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8df7816c5c79884c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.43, 0.34, 0.2, 0.03], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: over the last hour, shortly after a software update. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ce17ae92b76ef1f_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: over the last hour, during an external partner integration. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e01504564441af8b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.96, 0.01, 0.01, 0.02], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: during the batch window, during peak load. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d467ac77213602b6_n", "kind": "noul", "options": ["false", "true"], "target": [0.42, 0.58], "state": "The metrics pipeline flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: across all regions, as part of a compliance sweep. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5fb88450f8bbbf1e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.5, 0.47, 0.01], "state": "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, following a recent audit. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_23754b46a24529a9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.34, 0.64], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: across all regions, during the quarterly review. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6fa5fda86d36b09f_n", "kind": "noul", "options": ["false", "true"], "target": [0.54, 0.46], "state": "The log shipper lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: across all regions, during normal operations. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a66f0bc423fce0ec_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.26, 0.53, 0.21, 0.0, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: across all regions, during the system migration. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fc8c8f644eab98cb_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: over the last hour, during an external partner integration. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c39afb7c8182f63c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.43, 0.55, 0.01], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: across all regions, during peak load. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2bf45a3e160d846e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.14, 0.55, 0.3, 0.01, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: over the last hour, during the holiday freeze. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_64d30da221b9c18b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.06, 0.27, 0.11, 0.56], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: in production only, following a recent audit. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9aeb8e1ea28c05b8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.67, 0.32, 0.0], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: during the batch window, immediately after go-live. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_60bfb4d08b612946_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "Service catalog-sync lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: during the batch window, with staffing at reduced levels. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c0333d784473ef7d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.1, 0.71, 0.19, 0.0, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, with a new vendor onboarded. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e01504564441af8b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.34, 0.66, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: during the batch window, during peak load. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e08c6b84f129c0ef_n", "kind": "noul", "options": ["false", "true"], "target": [0.63, 0.37], "state": "The log shipper shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: in production only, while legacy systems are still active. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ed91a614e1108c87_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.09, 0.71, 0.14, 0.06, 0.0, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: over the last hour, with staffing at reduced levels. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_218b498fcde24643_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.68, 0.31, 0.01, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: in production only, during the quarterly review. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bb2d55b3a9f5ed0b_n", "kind": "noul", "options": ["false", "true"], "target": [0.66, 0.34], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: across all regions, while on-call rotation changed. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8ecfc8dce5a2c073_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.46, 0.51, 0.01], "state": "The metrics pipeline correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: in production only, during normal operations. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_942325462431fba5_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.99, 0.01, 0.0, 0.0], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: over the last hour, with staffing at reduced levels. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_56528b34b1cf8ef8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.61, 0.37, 0.0], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: during the batch window, during normal operations. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f600703ac21f8796_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.19, 0.06, 0.71, 0.04], "state": "The log shipper shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during an external partner integration. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c58194d84ea71f80_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.74, 0.1, 0.16, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: in production only, mid-incident. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d1f023c009d65819_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.29, 0.58, 0.12, 0.01], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: during the batch window, at the end of the fiscal period. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b346462eb9530065_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during normal operations. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8705e53da2e25089_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.52, 0.38, 0.1, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: over the last hour, following a recent audit. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_70fcab06027d3899_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.17, 0.05, 0.1, 0.68], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: over the last hour, during the holiday freeze. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2f14d116ce3faf91_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.15, 0.83, 0.02], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: in production only, during the system migration. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cb6fd6bb89e5b8ca_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.32, 0.67, 0.01], "state": "The log shipper shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0a6133bc92d2db48_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.21, 0.57, 0.21], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: in production only, during an external partner integration. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_998a6f7e1468bd11_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: during the batch window, during the system migration. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_498c5de0fcaefcc9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.26, 0.7, 0.03], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: in production only, during the quarterly review. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f2f342a03b1c7fc8_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "The log shipper returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: across all regions, immediately after go-live. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7cab7342b53cded8_n", "kind": "noul", "options": ["false", "true"], "target": [0.69, 0.31], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, mid-incident. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2a208ac07afc7b0f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.15, 0.11, 0.06, 0.68], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: in production only, as part of a compliance sweep. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6ad6a5a621285968_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.17, 0.7, 0.11, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during a scheduled maintenance window. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2b36062772979607_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.34, 0.65, 0.01], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, following a recent audit. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2a84b92a71f7d080_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: in production only, as part of a compliance sweep. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bf69ee53b0d543e8_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.04, 0.85, 0.1], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: during the batch window, during an external partner integration. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_575e5ca6751b20b8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.06, 0.67, 0.27, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: in production only, during the morning shift. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f378f16b1dbac2bc_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: during the batch window, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bc92d0c302846595_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.42, 0.22, 0.34], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: in production only, while legacy systems are still active. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5aa873a353ec7ebd_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.01, 0.87, 0.12], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: in production only, with staffing at reduced levels. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_545525135e4bbee4_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.12, 0.08, 0.03, 0.77], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: over the last hour, while on-call rotation changed. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_98763e2d62de8ffb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.44, 0.53, 0.01], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: over the last hour, under reduced staffing. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bf559bafb5ad8462_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: across all regions, under reduced staffing. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_072f8c770e3b902e_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "Service catalog-sync flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: in production only, mid-incident. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_20f9e4f9fbd9818c_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: in production only, while legacy systems are still active. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e232cdcc94d54785_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0303, 0.3838, 0.5657, 0.0202, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: across all regions, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6a129659707217e9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.11, 0.14, 0.49, 0.24, 0.02], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_db4bb4b7ff883eb8_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.27, 0.35, 0.04, 0.34], "state": "The log shipper flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: in production only, during the morning shift. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2359d166bc00cc05_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.98, 0.02, 0.0, 0.0], "state": "Dashboard checkout-funnel 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 automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_556c80c853a5e281_n", "kind": "noul", "options": ["false", "true"], "target": [0.38, 0.62], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: over the last hour, under reduced staffing. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_61c55b61f014a9a4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.25, 0.74, 0.01], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: in production only, during the morning shift. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1c6cdbe10b67e762_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "The log shipper lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: across all regions, during normal operations. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ac9bbe311a4a14ee_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.3, 0.61, 0.05, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, while legacy systems are still active. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f5a51e4b5b1a51ae_n", "kind": "noul", "options": ["false", "true"], "target": [0.66, 0.34], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: in production only, while on-call rotation changed. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a0eb51a20dfc3ba7_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: over the last hour, during the quarterly review. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d334d1d6b4e3fd1e_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: over the last hour, immediately after go-live. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8fe04c1c6d6ea837_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.35, 0.58, 0.07, 0.0], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_91ab44ea52730b7e_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "The log shipper lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: across all regions, with a new vendor onboarded. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8de6bb003c3d2b1b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.87, 0.06, 0.01, 0.06], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, mid-incident. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4588982227a81cf6_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, following a recent audit. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_65164c533f2393ba_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.68, 0.31, 0.01, 0.0], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: in production only, while legacy systems are still active. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3dc5bdb51f48200a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.29, 0.68, 0.02], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: in production only, while on-call rotation changed. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aa69aab3b8d0a7fd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.2, 0.76, 0.04], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: during the batch window, mid-incident. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3db124ff31bab8ad_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.61, 0.37, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during a scheduled maintenance window. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2598e1a8666ae0f4_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.87, 0.08, 0.03, 0.02], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: over the last hour, immediately after go-live. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_574342a250015f84_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: across all regions, while legacy systems are still active. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b6646de0624ade50_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.27, 0.71, 0.02], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: during the batch window, under an active deadline. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ec61f330e1a97f3_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.01, 0.96, 0.03], "state": "The metrics pipeline correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: in production only, with a new vendor onboarded. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3a5e19408b2892dd_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.02, 0.16, 0.79], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: in production only, during the holiday freeze. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9aa69dcc2f37800a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.17, 0.7, 0.13, 0.0, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, following a recent audit. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3f7adeb864a7e1f2_n", "kind": "noul", "options": ["false", "true"], "target": [0.58, 0.42], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: in production only, shortly after a software update. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3a175b815d50ffa3_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.0, 0.21, 0.79], "state": "The log shipper lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: in production only, at the end of the fiscal period. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_363ab3914ab76edc_n", "kind": "noul", "options": ["false", "true"], "target": [0.22, 0.78], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: in production only, during the morning shift. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_09534f74484f4af8_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.0, 0.43, 0.57], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: across all regions, mid-incident. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5d7ce2b7d51b3a4d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.11, 0.85, 0.04], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, while legacy systems are still active. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_09e03f67b8d6e374_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: during the batch window, immediately after go-live. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_14fda788ea4a1301_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "The log shipper correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, immediately after go-live. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c6b805d255ae34b3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.16, 0.53, 0.29, 0.0], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: in production only, under an active deadline. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bd80b5eee25864f1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.73, 0.27, 0.0], "state": "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, while on-call rotation changed. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7241262bc15b1a69_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.63, 0.36, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during an external partner integration. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_224fa9977b916206_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.08, 0.57, 0.3, 0.05, 0.0], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during a scheduled maintenance window. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4e27d9c356ed44bc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.24, 0.76, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: over the last hour, during peak load. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6f26a11ee442fa08_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.14, 0.81, 0.05], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during the holiday freeze. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5c0b8d813b1524e8_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: during the batch window, with staffing at reduced levels. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b43bb01678d11fb9_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: during the batch window, following a recent audit. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f058d2ac0152c1dd_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.43, 0.26, 0.03, 0.28], "state": "The metrics pipeline 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 monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d95a591b3f79cbb1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.31, 0.53, 0.15, 0.01], "state": "The log shipper matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, under reduced staffing. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_81bd92ca93f66a16_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.0, 0.32, 0.67], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: across all regions, during normal operations. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_10f6ba45bc3f7a9a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.64, 0.31, 0.05, 0.0], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during the holiday freeze. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_64ce0de3a1e55b5b_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9b5204cab2d65615_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.24, 0.43, 0.31, 0.02], "state": "Node pgsql-14 flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: during the batch window, during a scheduled maintenance window. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b9fe556e15174b6_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: during the batch window, during peak load. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_49cd06ac56cd17ea_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.03, 0.19, 0.77], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: in production only, as part of a compliance sweep. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c809391ee7fd89fa_n", "kind": "noul", "options": ["false", "true"], "target": [0.57, 0.43], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: during the batch window, during normal operations. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6ab93b5ad7c4d156_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.89, 0.08, 0.0, 0.03], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: in production only, mid-incident. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cc16eebfc031642b_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: over the last hour, during the quarterly review. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cb49ecccbaebd557_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: during the batch window, during peak load. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fcbfde8cc9d3ed1e_n", "kind": "noul", "options": ["false", "true"], "target": [0.19, 0.81], "state": "The log shipper correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, while on-call rotation changed. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_495296d44a858770_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.07, 0.88, 0.02, 0.03], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: across all regions, immediately after go-live. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_149a05711fd8dd9b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.75, 0.23, 0.01, 0.01], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: during the batch window, during normal operations. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2ac2b5ab057cac08_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: across all regions, during peak load. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9cbbd1680620315d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.57, 0.43, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, with a new vendor onboarded. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bcbc38fa26d067f8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.23, 0.73, 0.03], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: in production only, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4e56f946c3cc47ae_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "The log shipper matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: over the last hour, during the system migration. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0817c4b41659386a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.22, 0.77, 0.01], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: during the batch window, during the morning shift. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_38b4d16ac56fec8f_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Node pgsql-14 flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: across all regions, shortly after a software update. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_58e5f31dd0809b9e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.03, 0.76, 0.21], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: in production only, under an active deadline. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e0ae7820f9a081bf_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.7, 0.25, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during a scheduled maintenance window. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5db51a5cbb5c60fb_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.13, 0.6, 0.26], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: during the batch window, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_75cf109945554dd7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.04, 0.79, 0.17], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, mid-incident. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1e632400d4131ecf_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.27, 0.51, 0.12, 0.1], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: over the last hour, during the system migration. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d12cea274bfd49a9_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.18, 0.66, 0.15, 0.01], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the morning shift. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5e60a338cf4d34af_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: across all regions, shortly after a software update. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_94e09ad0b5782a30_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.26, 0.72], "state": "The metrics pipeline flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: in production only, while on-call rotation changed. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_036e389c7e256b6b_n", "kind": "noul", "options": ["false", "true"], "target": [0.63, 0.37], "state": "The log shipper matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: during the batch window, as part of a compliance sweep. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a7a560de3d09e969_n", "kind": "noul", "options": ["false", "true"], "target": [0.91, 0.09], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: during the batch window, mid-incident. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ce09c5375d1e59f8_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.13, 0.6, 0.05, 0.22], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: over the last hour, during the morning shift. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a10e77c283ac762f_n", "kind": "noul", "options": ["false", "true"], "target": [0.91, 0.09], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: during the batch window, during the system migration. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_79522b9794cc46fa_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.26, 0.73, 0.01], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: during the batch window, while on-call rotation changed. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f0ce468748a2527f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.35, 0.61, 0.03], "state": "The metrics pipeline correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: during the batch window, mid-incident. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0e77bc02de5b7405_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.35, 0.63, 0.01], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: over the last hour, during the holiday freeze. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f489dc894211209f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.04, 0.38, 0.54, 0.04], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: during the batch window, under reduced staffing. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d24481041f98bbfb_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.38, 0.6, 0.01, 0.01], "state": "The log shipper lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the system migration. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_92abc61435214c2d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.01, 0.05, 0.91], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: in production only, following a recent audit. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e2b7a60a9f4f4bd5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.48, 0.52, 0.0], "state": "The log shipper reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, with staffing at reduced levels. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0946abd1ce2cba91_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.11, 0.4, 0.43, 0.06], "state": "Service catalog-sync shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2aebe535c0d5bae6_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: over the last hour, during peak load. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d769e299e40de70a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.42, 0.44, 0.13, 0.01], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: in production only, shortly after a software update. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_26967d4f336328e0_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.1, 0.0, 0.35, 0.55], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during normal operations. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fbdffc654aa70f03_n", "kind": "noul", "options": ["false", "true"], "target": [0.39, 0.61], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: over the last hour, following a recent audit. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c4f2d21e5c9a9086_n", "kind": "noul", "options": ["false", "true"], "target": [0.67, 0.33], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: in production only, shortly after a software update. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0a1d17d256c6fd47_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.05, 0.83, 0.11, 0.0], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during a scheduled maintenance window. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cece94212703d62c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.05, 0.78, 0.16, 0.0], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: across all regions, as part of a compliance sweep. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_20ea0a82af75b82e_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: over the last hour, with staffing at reduced levels. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_427718e03b89aa72_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.8081, 0.1717, 0.0101, 0.0101], "state": "The log shipper reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: over the last hour, while legacy systems are still active. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_210bbb60ba10d1a8_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: in production only, during the morning shift. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6d191dd289c4ca26_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.85, 0.12, 0.02, 0.01], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: across all regions, under reduced staffing. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_960f2ef33f6ac65f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.2, 0.73, 0.01, 0.06], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: during the batch window, mid-incident. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_160cdd3dd043a27d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.21, 0.73, 0.05], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: over the last hour, during the system migration. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_20969bf86f8537fc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.65, 0.35, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: during the batch window, during an external partner integration. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b33828d12e995afa_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: in production only, immediately after go-live. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9bfac4de582550ed_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: across all regions, following a recent audit. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7efce999ad7f183a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.62, 0.37, 0.0], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: over the last hour, during a scheduled maintenance window. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_625fa8f565c2a248_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.64, 0.35, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: during the batch window, during normal operations. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_745f9e31eea67a99_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.67, 0.28, 0.02, 0.03], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: during the batch window, while legacy systems are still active. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5693c7d309454c00_n", "kind": "noul", "options": ["false", "true"], "target": [0.48, 0.52], "state": "The log shipper returned to baseline after 11 minutes; additionally matches last Tuesday's incident signature. Context: across all regions, during the morning shift. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0f8f8be3858de579_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during peak load. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_153715564c81edb5_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "The log shipper correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: over the last hour, at the end of the fiscal period. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_36e2ce5740948990_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.66, 0.21, 0.11, 0.02], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_92b531736a70ec94_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.12, 0.73, 0.14, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: over the last hour, as part of a compliance sweep. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_70b0c11c7c3d0a6a_n", "kind": "noul", "options": ["false", "true"], "target": [0.41, 0.59], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: across all regions, with a new vendor onboarded. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e3e3679d054cba97_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.07, 0.89, 0.03, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: across all regions, with a new vendor onboarded. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9bf81910b00d1383_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.07, 0.0, 0.76, 0.17], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during an external partner integration. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6fba0c5727731a7d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.95, 0.02, 0.0, 0.03], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, shortly after a software update. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_503689448e21ac83_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.16, 0.81, 0.03], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: in production only, under reduced staffing. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ac87df9fb6324d6d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.12, 0.83, 0.05], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, while legacy systems are still active. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9c0c0f781124a8fa_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: across all regions, during a scheduled maintenance window. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b4c7fe91e9f34870_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.03, 0.13, 0.27, 0.48, 0.08, 0.01], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: during the batch window, during normal operations. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7cc84cecf82b5ec6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.24, 0.34, 0.38, 0.04, 0.0], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: across all regions, during a scheduled maintenance window. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4f396ccf243b9cf9_n", "kind": "noul", "options": ["false", "true"], "target": [0.61, 0.39], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: over the last hour, during the holiday freeze. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b7ab1229ac0e1c4_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.69, 0.01, 0.0, 0.3], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: during the batch window, during peak load. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4a63846f26f48b2f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.11, 0.8, 0.07, 0.02], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: during the batch window, following a recent audit. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c121cb4bd7c416f0_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.68, 0.3, 0.0, 0.02], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: across all regions, immediately after go-live. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_751ea2ffabf34b6b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.46, 0.54, 0.0], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: during the batch window, with a new vendor onboarded. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5dda34188ae3e327_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.22, 0.52, 0.24, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, immediately after go-live. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_97001f04aa21e0f7_n", "kind": "noul", "options": ["false", "true"], "target": [0.9, 0.1], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, immediately after go-live. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9e25a2f2d14d8fe5_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: during the batch window, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_58bc0c178f0a9b47_n", "kind": "noul", "options": ["false", "true"], "target": [0.5, 0.5], "state": "Node pgsql-14 flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: across all regions, during a scheduled maintenance window. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_521674ef10f726af_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.27, 0.71, 0.02], "state": "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 system migration. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_96f05717227a6ec2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.38, 0.15, 0.01, 0.46], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: across all regions, at the end of the fiscal period. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2f9b1b3ed919ff21_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.19, 0.79, 0.02], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during the system migration. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2b5e426e13e4097f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.23, 0.55, 0.2, 0.02], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during peak load. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_33ba0018b4ef327e_n", "kind": "noul", "options": ["false", "true"], "target": [0.37, 0.63], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: in production only, following a recent audit. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fe43d435020c821f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.09, 0.74, 0.15, 0.02], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: across all regions, during normal operations. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ec0f74236b5241f_n", "kind": "noul", "options": ["false", "true"], "target": [0.41, 0.59], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: over the last hour, following a recent audit. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_41f1416b8b74b8e4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.2, 0.78, 0.02], "state": "The log shipper correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: across all regions, during the morning shift. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3022b2cba57e00f9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.24, 0.01, 0.42, 0.33], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the system migration. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6995010547d0c99f_n", "kind": "noul", "options": ["false", "true"], "target": [0.5, 0.5], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: over the last hour, shortly after a software update. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2b9544613cc677d7_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.72, 0.14, 0.13, 0.01], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, as part of a compliance sweep. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fa23cf9ae529de09_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.2, 0.79, 0.01], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: in production only, shortly after a software update. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d370006c9d89eb00_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.56, 0.42, 0.0], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: over the last hour, shortly after a software update. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_27ff8cfde95ffcc9_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the system migration. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a048eae1fe84eb0b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.87, 0.1, 0.02, 0.01], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, following a recent audit. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1b98c22b19ae758b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.18, 0.8, 0.02], "state": "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, with a new vendor onboarded. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_baa7474bfe001b61_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: in production only, during the holiday freeze. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ff9cb7cda865e323_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.06, 0.55, 0.38, 0.01], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during normal operations. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ee6e702f9629d850_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: in production only, during the system migration. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a5a31f49d9e9f9e3_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during normal operations. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3f5db9c342ca4315_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.31, 0.69, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: in production only, shortly after a software update. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_942325462431fba5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.07, 0.89, 0.04], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: over the last hour, with staffing at reduced levels. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e677b2e9f6a4e03c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.8, 0.16, 0.03, 0.01], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: across all regions, during peak load. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4bba3cc77a32e022_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: during the batch window, during the quarterly review. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_679eea852bb4c45c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.66, 0.33, 0.0], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: during the batch window, during the morning shift. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3ed77c902cb513e4_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: in production only, while on-call rotation changed. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b9fe556e15174b6_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.4, 0.01, 0.35, 0.24], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: during the batch window, during peak load. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_632090753f0a2f31_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: over the last hour, during the holiday freeze. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1f63d2502608b95b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.23, 0.73, 0.03], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: across all regions, following a recent audit. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b8c1e1782716be55_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.96, 0.04, 0.0, 0.0], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during an external partner integration. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3692e15ea4220a74_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "The metrics pipeline correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: across all regions, with staffing at reduced levels. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1a15c6baf15cb8f1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.52, 0.48, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: across all regions, during the morning shift. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d9c469bca95a91f8_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: in production only, while legacy systems are still active. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_53d9e41d178b5151_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.09, 0.82, 0.02, 0.07], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: over the last hour, following a recent audit. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c2e8529d0771b780_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.04, 0.56, 0.39, 0.01], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: during the batch window, under reduced staffing. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fc714cc230b209b8_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.0, 0.01, 0.99], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f371525de860d663_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.53, 0.43, 0.03, 0.01], "state": "Service catalog-sync shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: during the batch window, with staffing at reduced levels. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4e75e7300d0dc4bd_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: in production only, while on-call rotation changed. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3134e8a1d0c0385d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.89, 0.07, 0.04, 0.0], "state": "The metrics pipeline 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 monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f3ead914998e1fee_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: over the last hour, with staffing at reduced levels. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d7fafbba230995aa_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: across all regions, during the holiday freeze. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ae40cf170ae906d3_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "The metrics pipeline lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: over the last hour, while legacy systems are still active. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d95a23a39934bd33_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.29, 0.61, 0.07, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: during the batch window, during the quarterly review. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8bbcafc2d335d18c_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: over the last hour, during peak load. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_61f22e5ef6632689_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.34, 0.65, 0.01], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, while legacy systems are still active. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_98204fad5a3a3e7a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.08, 0.76, 0.15, 0.0], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: over the last hour, as part of a compliance sweep. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2c4f7fb030eff125_n", "kind": "noul", "options": ["false", "true"], "target": [0.44, 0.56], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: in production only, while on-call rotation changed. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b331cc75576b83ca_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.06, 0.49, 0.43, 0.02], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: during the batch window, with staffing at reduced levels. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7e7c81c30e21ace5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.08, 0.16, 0.67, 0.09, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during a scheduled maintenance window. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a7a8aab3da95bb6e_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: in production only, during normal operations. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cbae5c2d06540a15_n", "kind": "noul", "options": ["false", "true"], "target": [0.65, 0.35], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: across all regions, during the quarterly review. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_992c93647f6ea09c_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: over the last hour, while legacy systems are still active. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f343b871297b5240_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: during the batch window, during peak load. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_73e8f2c7f6e13828_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.0, 0.99, 0.01], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: across all regions, mid-incident. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_812c5d6a46b04e31_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.06, 0.06, 0.45, 0.43], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: during the batch window, under an active deadline. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dd97a7644ebbc681_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.5, 0.47, 0.01, 0.02], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: in production only, during peak load. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b9993a106179523c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.29, 0.62, 0.08, 0.01], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: across all regions, during normal operations. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4e88f6b96494f179_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: during the batch window, during the morning shift. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b9805bade1c8d8ce_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.14, 0.83, 0.03], "state": "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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cd8f12694c9c6955_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.33, 0.66, 0.01], "state": "Service catalog-sync shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: across all regions, immediately after go-live. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dfd85ae7205acc7b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.35, 0.63], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: across all regions, during the system migration. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f19fd1eae93d2162_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.19, 0.75, 0.05], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: across all regions, during peak load. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4bd38927d42d4903_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.31, 0.68, 0.01], "state": "The metrics pipeline shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: over the last hour, during the holiday freeze. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b43bb01678d11fb9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.01, 0.44, 0.53, 0.01], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: during the batch window, following a recent audit. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ac67f1040237794f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.46, 0.54, 0.0], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: in production only, during the quarterly review. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_12992fb1e8cb5abd_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, following a recent audit. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3b78cd6bf32fd906_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.35, 0.62, 0.02], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: over the last hour, during peak load. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_59579f45781f574d_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: in production only, with a new vendor onboarded. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b1507c9b316351c8_n", "kind": "noul", "options": ["false", "true"], "target": [0.41, 0.59], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally matches last Tuesday's incident signature. Context: during the batch window, with staffing at reduced levels. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b7a892b2f526cadf_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.13, 0.14, 0.39, 0.34], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: during the batch window, during a scheduled maintenance window. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f9cbf7da1cc37d74_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.16, 0.79, 0.04], "state": "The log shipper matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: across all regions, during peak load. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_80bafac4c6d50132_n", "kind": "noul", "options": ["false", "true"], "target": [0.57, 0.43], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: across all regions, while on-call rotation changed. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fb8f4c761e0bb2e8_n", "kind": "noul", "options": ["false", "true"], "target": [0.63, 0.37], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: over the last hour, during peak load. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_16e92ac674d39d0b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.09, 0.62, 0.01, 0.28], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: across all regions, following a recent audit. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0d486d0b7385002c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.93, 0.05, 0.0, 0.02], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, under reduced staffing. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0410c076b8450bc0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.26, 0.73, 0.01], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, with a new vendor onboarded. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b1304c1ae11f1899_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: in production only, during peak load. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e151901d0a38d868_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: in production only, while legacy systems are still active. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5037335403753775_n", "kind": "noul", "options": ["false", "true"], "target": [0.4, 0.6], "state": "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, with a new vendor onboarded. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_276fc9aeb1983cc1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.69, 0.28, 0.02, 0.01], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, shortly after a software update. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e451d3fef511fe19_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.73, 0.24, 0.02, 0.01], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: during the batch window, while on-call rotation changed. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b82820cab21b5aee_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.11, 0.29, 0.15, 0.45], "state": "The log shipper returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: across all regions, during the system migration. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2f8a296cfcd34492_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during the holiday freeze. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_15301f5d5b06612e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.96, 0.03, 0.01, 0.0], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: in production only, shortly after a software update. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_716ee0bd230f6f27_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.09, 0.09, 0.79], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: in production only, during the quarterly review. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_149c47203de6a4a4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.3, 0.65, 0.03], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: over the last hour, immediately after go-live. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_60c0abbb70fed2e9_n", "kind": "noul", "options": ["false", "true"], "target": [0.37, 0.63], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: in production only, during the quarterly review. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bacfa983d36c7daf_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.15, 0.79, 0.04, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: across all regions, while legacy systems are still active. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b160c7b04d538eb5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.75, 0.23, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: over the last hour, during the holiday freeze. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d39019ef922da8d3_n", "kind": "noul", "options": ["false", "true"], "target": [0.71, 0.29], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: across all regions, during the system migration. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_851bd2badb5f5560_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7d37fbf63f0dee75_n", "kind": "noul", "options": ["false", "true"], "target": [0.23, 0.77], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: during the batch window, while legacy systems are still active. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1cf9f0d3cfca3e8a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.77, 0.21, 0.01, 0.01], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during the quarterly review. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a9072bff2b56fa32_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.95, 0.02, 0.0, 0.03], "state": "The log shipper flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during normal operations. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_798d797a313b07f2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.06, 0.01, 0.92], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: during the batch window, as part of a compliance sweep. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1a95450d51ad667c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.39, 0.6, 0.01], "state": "The log shipper shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: during the batch window, mid-incident. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f519a0039b1664cb_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.02, 0.82, 0.13], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: in production only, with a new vendor onboarded. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9b43c7032ec1dc83_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.08, 0.74, 0.18, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, with staffing at reduced levels. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_34863c051a2d4ba6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.04, 0.85, 0.11], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, mid-incident. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_efa38ebe01de4c3e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.0, 0.01, 0.98], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_43523ac4550235f9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.01, 0.29, 0.68], "state": "The log shipper flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: in production only, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_85688f9763147841_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.4, 0.53, 0.01, 0.06], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: over the last hour, shortly after a software update. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2733feaf80593d29_n", "kind": "noul", "options": ["false", "true"], "target": [0.39, 0.61], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: across all regions, during the quarterly review. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_069762646f419472_n", "kind": "noul", "options": ["false", "true"], "target": [0.23, 0.77], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: over the last hour, during the morning shift. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_84f7679c565901d5_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.42, 0.46, 0.11, 0.01], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: over the last hour, while legacy systems are still active. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ade11d20613f9f34_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, while legacy systems are still active. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6f6c1e78524580ff_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.06, 0.87, 0.07], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during an external partner integration. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_db6d5eb40c692ee6_n", "kind": "noul", "options": ["false", "true"], "target": [0.56, 0.44], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: in production only, while legacy systems are still active. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_25e9aa649a52bac8_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.17, 0.74, 0.08, 0.01], "state": "The log shipper correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: across all regions, during the morning shift. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_517fa3126e74beeb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.1717, 0.8081, 0.0202], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, shortly after a software update. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_db9aa15d151d6cac_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: over the last hour, immediately after go-live. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_14b2d53ae1c71c7b_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: in production only, immediately after go-live. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6861f37adea39929_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: in production only, while on-call rotation changed. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ce09c5375d1e59f8_n", "kind": "noul", "options": ["false", "true"], "target": [0.62, 0.38], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: over the last hour, during the morning shift. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_33ff6bc9795e087c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.01, 0.05, 0.44, 0.48, 0.01], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: in production only, while legacy systems are still active. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_83c1a04a4d35d43b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.08, 0.29, 0.61, 0.02, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: over the last hour, under reduced staffing. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0d0751f20335acfb_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, immediately after go-live. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cc62ecec6e2d026e_n", "kind": "noul", "options": ["false", "true"], "target": [0.55, 0.45], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: in production only, with staffing at reduced levels. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8caecf8f5f0117cc_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.36, 0.62], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: across all regions, under an active deadline. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3632e8c50902eb91_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: over the last hour, following a recent audit. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8aee2ec7c43a35af_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.08, 0.72, 0.18, 0.0], "state": "The metrics pipeline shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: in production only, as part of a compliance sweep. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2320f5aecd351132_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.44, 0.56, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: in production only, with a new vendor onboarded. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_91da20bdfaadc1ea_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.69, 0.31, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: during the batch window, during the quarterly review. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c91c50225ad9611d_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: in production only, shortly after a software update. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c0a45cdb89379103_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.05, 0.35, 0.58], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: across all regions, while on-call rotation changed. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_88118af93c4bb4af_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.27, 0.02, 0.09, 0.62], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the system migration. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3095aa37879e8a08_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.97, 0.03, 0.0, 0.0], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: across all regions, during the quarterly review. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f5ef7d7c90540f2e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.47, 0.52, 0.01, 0.0], "state": "The log shipper flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: during the batch window, following a recent audit. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1a4814e94cce0b1d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.1, 0.28, 0.61], "state": "The log shipper reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: across all regions, immediately after go-live. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f058d2ac0152c1dd_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "The metrics pipeline 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 monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8df7d1ab3fcf6704_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.22, 0.05, 0.27, 0.46], "state": "The log shipper correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during the holiday freeze. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_961b0853111a061d_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, mid-incident. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_33f650286cf00f43_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: during the batch window, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_54fa6598301360c7_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.46, 0.21, 0.32, 0.01], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: over the last hour, during a scheduled maintenance window. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_57634c0496e4f3b5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.19, 0.59, 0.22, 0.0, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: over the last hour, under an active deadline. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d3b5c90e93d85e69_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.67, 0.29, 0.02, 0.02], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: over the last hour, while legacy systems are still active. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_63045fc69664036c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.64, 0.35, 0.0], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: over the last hour, while legacy systems are still active. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bc268bff73441d3a_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "The log shipper matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: in production only, during the holiday freeze. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8b813f3c190927ad_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.0505, 0.8182, 0.1313], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: across all regions, under an active deadline. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2670c947e9e3c315_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.02, 0.01, 0.93], "state": "The log shipper matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: during the batch window, mid-incident. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_91549f3bc93c3dc1_n", "kind": "noul", "options": ["false", "true"], "target": [0.37, 0.63], "state": "The metrics pipeline flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: during the batch window, shortly after a software update. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2014496a9dce3ec4_n", "kind": "noul", "options": ["false", "true"], "target": [0.53, 0.47], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: across all regions, shortly after a software update. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8727bbe0322250d7_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: across all regions, under an active deadline. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6ef967fe36a54c57_n", "kind": "noul", "options": ["false", "true"], "target": [0.61, 0.39], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: during the batch window, with a new vendor onboarded. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a556272ae0245ef6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.79, 0.19, 0.0], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: in production only, at the end of the fiscal period. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_26361aac64b070b9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.08, 0.67, 0.24, 0.01, 0.0], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: in production only, with a new vendor onboarded. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b409eee2b9716b2d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.11, 0.66, 0.21, 0.0], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: in production only, following a recent audit. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5b52bd3614aea0ae_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during peak load. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ebe8321726c860a_n", "kind": "noul", "options": ["false", "true"], "target": [0.39, 0.61], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: in production only, at the end of the fiscal period. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_93ef5a84e6de6317_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: across all regions, mid-incident. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_91ed4f963370609b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.18, 0.64, 0.16, 0.0], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: across all regions, shortly after a software update. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d080312d52c4565a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.0, 0.76, 0.22], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during an external partner integration. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_08c4879e270f947b_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: over the last hour, during an external partner integration. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_62750f00a5a3d36e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.24, 0.74, 0.02], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: over the last hour, immediately after go-live. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f058d2ac0152c1dd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.12, 0.82, 0.06], "state": "The metrics pipeline 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 monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8f72d51ca19c9dd3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.17, 0.77, 0.05], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: in production only, while on-call rotation changed. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_af8d46ec951ebf38_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.34, 0.62, 0.02], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: in production only, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f0ce468748a2527f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.06, 0.31, 0.56, 0.06, 0.0], "state": "The metrics pipeline correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: during the batch window, mid-incident. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e0f1a655de4eee0c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.25, 0.7, 0.0, 0.05], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: over the last hour, during peak load. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_37b77ed14c3ac6cc_n", "kind": "noul", "options": ["false", "true"], "target": [0.67, 0.33], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: across all regions, while on-call rotation changed. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c6a353e612fb4672_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: across all regions, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ede2d168903bcca5_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "The log shipper shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during normal operations. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ddadfca7416d7644_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.57, 0.41, 0.01, 0.01], "state": "The log shipper reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: during the batch window, following a recent audit. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_be2032e6fb885b88_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.92, 0.0, 0.0, 0.08], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during normal operations. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0e397acb484ee7ff_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.04, 0.27, 0.68], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: in production only, as part of a compliance sweep. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_06db838a044838b2_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "Service catalog-sync correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: during the batch window, during peak load. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f34761ceb82b0ab0_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: over the last hour, during normal operations. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f8c815a17fd22454_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.07, 0.76, 0.16, 0.01], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: across all regions, following a recent audit. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_51595f59048edd37_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.24, 0.75, 0.01], "state": "Service catalog-sync flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: across all regions, under reduced staffing. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a57a88343e4459c6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.03, 0.8, 0.17], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: over the last hour, immediately after go-live. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1912f80da9967b97_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.1, 0.06, 0.14, 0.7], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: in production only, during the system migration. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e0ae7820f9a081bf_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.34, 0.01, 0.26, 0.39], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during a scheduled maintenance window. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b1c916cf4691d848_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.05, 0.35, 0.59, 0.01], "state": "The log shipper shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: across all regions, under reduced staffing. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0050c0907da73be7_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.72, 0.25, 0.01, 0.02], "state": "The log shipper reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: during the batch window, shortly after a software update. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8ef898e8a0867e12_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The log shipper returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: across all regions, shortly after a software update. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_156ce471cf9938c3_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, mid-incident. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_534519c6a9e9a124_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.17, 0.8, 0.03], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, while on-call rotation changed. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ceb084f2230cd528_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: during the batch window, as part of a compliance sweep. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fcf51493fa10bfbb_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: during the batch window, while legacy systems are still active. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a89b7747919e89e5_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.48, 0.46, 0.06, 0.0], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: over the last hour, following a recent audit. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b62c7d585a3696fc_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, under reduced staffing. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aba3520249b2f616_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.33, 0.66, 0.01], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: in production only, immediately after go-live. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8b9ef5e3c46df5aa_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "The metrics pipeline flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: in production only, under an active deadline. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6421fa2479e9fe3a_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "The log shipper shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: across all regions, during an external partner integration. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e60673a904e76c15_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.24, 0.57, 0.13, 0.06, 0.0, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: in production only, under an active deadline. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a3fd12b97610374f_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: across all regions, mid-incident. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b346462eb9530065_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.53, 0.29, 0.16, 0.01], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during normal operations. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_489f26b7fb5967a0_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: across all regions, as part of a compliance sweep. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_11e442e37771ac24_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.58, 0.37, 0.02, 0.0], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, while on-call rotation changed. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_db17b3504e14379a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.02, 0.1, 0.22, 0.53, 0.12, 0.01], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: during the batch window, following a recent audit. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e3a420e8604f6bfb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.15, 0.82, 0.03], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during the holiday freeze. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2e726eb914bac300_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.15, 0.03, 0.13, 0.69], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: during the batch window, mid-incident. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2e726eb914bac300_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.17, 0.49, 0.21, 0.12, 0.01, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: during the batch window, mid-incident. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6b243ccf8d56a9ed_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: in production only, as part of a compliance sweep. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bf64f3f1964fba67_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.19, 0.79, 0.02], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: in production only, during the quarterly review. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4158b18bfcd543f4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.08, 0.23, 0.6, 0.08, 0.0], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: across all regions, during normal operations. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e55bc18fb598a779_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during the quarterly review. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_44153cd37285ec04_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.02, 0.49, 0.31, 0.17, 0.01, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during a scheduled maintenance window. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e8aafe32aa2fbbc0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.17, 0.14, 0.51, 0.16, 0.01], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: over the last hour, during a scheduled maintenance window. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a42ae064a33d5d0e_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "The metrics pipeline flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: in production only, shortly after a software update. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5cdb1fae2f20fdb9_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, at the end of the fiscal period. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d3680106218d9f24_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.76, 0.2, 0.0, 0.04], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: during the batch window, under an active deadline. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8c492d4adb43361a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.04, 0.26, 0.68], "state": "The log shipper correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: during the batch window, mid-incident. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_59579f45781f574d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.5, 0.48, 0.02, 0.0], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: in production only, with a new vendor onboarded. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_960f2ef33f6ac65f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.29, 0.6, 0.1, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: during the batch window, mid-incident. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5cbedb575cb6174b_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during peak load. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_238ce2e06ddb6af4_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: in production only, during normal operations. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_036c6e90a816311e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.36, 0.52, 0.11, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: over the last hour, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3188e8874bce1a97_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.53, 0.09, 0.01, 0.37], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: across all regions, under an active deadline. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a58cd5c438d924c0_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.67, 0.24, 0.05, 0.04], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the morning shift. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a2498889afa24083_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.17, 0.59, 0.19, 0.01], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: in production only, immediately after go-live. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1528d2a2f47bd904_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "The log shipper reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: over the last hour, during the holiday freeze. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7f80f01c5cdd444b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.34, 0.65, 0.01], "state": "Service catalog-sync shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: in production only, immediately after go-live. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7fcbabbdf44a2632_n", "kind": "noul", "options": ["false", "true"], "target": [0.43, 0.57], "state": "The log shipper reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: during the batch window, while legacy systems are still active. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5882da9e497469a1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.5, 0.44, 0.01], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: in production only, as part of a compliance sweep. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f0d4bc694780a65d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.27, 0.71, 0.02], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during an external partner integration. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_997648e0ee6b8ec5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.24, 0.71, 0.04], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: across all regions, during an external partner integration. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b24f3846df5d5918_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.25, 0.56, 0.19, 0.0, 0.0], "state": "The log shipper reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: over the last hour, during the system migration. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c1a96edb63a5a8de_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.88, 0.02, 0.01, 0.09], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during the holiday freeze. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ac086d809344ab35_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.74, 0.25, 0.0], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3dbcbe75b3cbf9dc_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.61, 0.29, 0.06, 0.04], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: over the last hour, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7a4cdedf5403fe94_n", "kind": "noul", "options": ["false", "true"], "target": [0.63, 0.37], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: during the batch window, during peak load. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_af946a1127ccc143_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.41, 0.0, 0.01, 0.58], "state": "The log shipper lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during peak load. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8e70add2b7ab95a2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.29, 0.7, 0.01], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during the quarterly review. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_16ffffbd9705bf8b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.5657, 0.3939, 0.0303, 0.0101], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: over the last hour, while legacy systems are still active. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_71816d5a66a5e2c9_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: in production only, as part of a compliance sweep. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eb95d37d2b64d356_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: across all regions, as part of a compliance sweep. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fa187083df92d77e_n", "kind": "noul", "options": ["false", "true"], "target": [0.42, 0.58], "state": "The metrics pipeline lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: during the batch window, as part of a compliance sweep. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_228e78771b4734ae_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.17, 0.73, 0.08, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: during the batch window, immediately after go-live. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_10fffb62f8792019_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.95, 0.05, 0.0, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: across all regions, under an active deadline. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9a4445224650c1fe_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.19, 0.33, 0.01, 0.47], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: in production only, at the end of the fiscal period. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_28b87ce873ad21ba_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.43, 0.02, 0.26, 0.29], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: during the batch window, during peak load. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_739b3abc81682118_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.16, 0.38, 0.43, 0.03], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, mid-incident. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f378f16b1dbac2bc_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.24, 0.58, 0.16, 0.02], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: during the batch window, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_de73388b593aaeef_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.46, 0.33, 0.18, 0.01], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: across all regions, under an active deadline. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_262558387e04415f_n", "kind": "noul", "options": ["false", "true"], "target": [0.38, 0.62], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9e25a2f2d14d8fe5_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.87, 0.1, 0.0, 0.03], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: during the batch window, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8e770a834f9d8039_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.02, 0.12, 0.18, 0.5, 0.17, 0.01], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: in production only, immediately after go-live. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3f1331550dd99f51_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.0, 0.05, 0.93, 0.02], "state": "The log shipper returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the system migration. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_21c9926a6455b119_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.19, 0.49, 0.3, 0.02], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: over the last hour, while on-call rotation changed. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c182ce7efb082c0e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.7, 0.27, 0.02, 0.01], "state": "Service catalog-sync 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 on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c480412abf78579a_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "The log shipper flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: across all regions, under reduced staffing. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ac3e76047bdb94a8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.46, 0.53, 0.0], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, as part of a compliance sweep. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c8482fa532daa8e0_n", "kind": "noul", "options": ["false", "true"], "target": [0.6, 0.4], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, following a recent audit. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6febbf9e643d1b73_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.57, 0.42, 0.0], "state": "The log shipper reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, while on-call rotation changed. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fdcff6beec7cfcfe_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: in production only, during the system migration. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_67a3ef9b5c3333f2_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.5657, 0.3939, 0.0404, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during the quarterly review. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7e974876a8103eda_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.11, 0.0, 0.28, 0.61], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: over the last hour, during peak load. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8849fd2195514c3e_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: over the last hour, during the system migration. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6692ec315001119e_n", "kind": "noul", "options": ["false", "true"], "target": [0.44, 0.56], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during the quarterly review. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_47c916f501463dd4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.3, 0.69, 0.01], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: over the last hour, while legacy systems are still active. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_38a900fb92b93a92_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: in production only, following a recent audit. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_16bc14f2836ed622_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.61, 0.07, 0.01, 0.31], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: in production only, during peak load. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_67646f50f7d6a63c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.9, 0.09, 0.01, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: during the batch window, under an active deadline. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_60ebf4e98066460e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.22, 0.54, 0.17, 0.07], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: during the batch window, under an active deadline. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_21d9312f011dad51_n", "kind": "noul", "options": ["false", "true"], "target": [0.43, 0.57], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: in production only, shortly after a software update. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1bf61105ff21c8f7_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during a scheduled maintenance window. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_674a06c2ce038dac_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.85, 0.0, 0.01, 0.14], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during a scheduled maintenance window. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a649a716eddcc566_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.63, 0.36, 0.0], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: across all regions, under reduced staffing. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_da0f99f458880cd2_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, under an active deadline. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2942076c054edae5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.19, 0.54, 0.27, 0.0, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: during the batch window, under reduced staffing. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1bb7ccdcf2837ac0_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.14, 0.55, 0.28], "state": "The log shipper correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: during the batch window, while legacy systems are still active. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_44ac967da236b9b4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.22, 0.76, 0.02], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: across all regions, immediately after go-live. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_606798a0f69dfd68_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, as part of a compliance sweep. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_43517daf835f7502_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, as part of a compliance sweep. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_924b0bcead71b0e7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.72, 0.28, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during normal operations. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0e8d9c60ae634ed8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.23, 0.71, 0.02, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: during the batch window, shortly after a software update. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b55301be242f245c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.61, 0.38, 0.0], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: during the batch window, during an external partner integration. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bc68020d58b91c74_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.92, 0.05, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during the holiday freeze. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_204af7bbcf2b5e94_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.39, 0.59, 0.01], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: during the batch window, as part of a compliance sweep. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3c48d3a073d3a744_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: during the batch window, during the morning shift. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9618e6991497442b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.13, 0.84, 0.03], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during an external partner integration. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_039f2146f7a14c26_n", "kind": "noul", "options": ["false", "true"], "target": [0.37, 0.63], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the system migration. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_62e0a52251e8256c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.38, 0.13, 0.01, 0.48], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during peak load. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b38845dbdb9bb370_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.5455, 0.0202, 0.2323, 0.202], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during normal operations. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f142b65e793e590b_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: across all regions, during the quarterly review. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_21d9312f011dad51_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0101, 0.0505, 0.6566, 0.2828, 0.0], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: in production only, shortly after a software update. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8fc8d29a6ad476ea_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.92, 0.07, 0.01, 0.0], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: across all regions, immediately after go-live. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_581eb6e36d7f091f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.35, 0.06, 0.04, 0.55], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: during the batch window, following a recent audit. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ad266a43f2d8dfac_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.02, 0.15, 0.26, 0.5, 0.07, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: over the last hour, as part of a compliance sweep. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f93a5062e3ab5f9b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.0, 0.48, 0.51], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: during the batch window, immediately after go-live. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3e0329d8027e223b_n", "kind": "noul", "options": ["false", "true"], "target": [0.7, 0.3], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, shortly after a software update. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a4969c7289a63af4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.02, 0.68, 0.29, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: across all regions, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9917f62ce2c7095a_n", "kind": "noul", "options": ["false", "true"], "target": [0.44, 0.56], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: across all regions, at the end of the fiscal period. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_476ae933bbb6825b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.9, 0.08, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: across all regions, during normal operations. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d6823ad76f582175_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: across all regions, under an active deadline. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c0e9313553ca6a7b_n", "kind": "noul", "options": ["false", "true"], "target": [0.18, 0.82], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: over the last hour, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_448a13b1040cc306_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.06, 0.26, 0.33, 0.32, 0.03, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: in production only, during peak load. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_84b64af02524bf49_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.21, 0.78, 0.01], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: over the last hour, at the end of the fiscal period. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7cde686750879b14_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.24, 0.57, 0.17, 0.02], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during peak load. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5d56181bcae176a6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.44, 0.5, 0.06, 0.0, 0.0], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_262558387e04415f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.02, 0.47, 0.34, 0.16, 0.01, 0.0], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_01b253b5b4a26597_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: during the batch window, during the holiday freeze. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_22595ea42966dc81_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.5, 0.49, 0.0], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: in production only, while on-call rotation changed. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6e654852fa039ae2_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.48, 0.39, 0.12, 0.01], "state": "The log shipper correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: across all regions, during normal operations. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8cde76217ac60a7b_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: in production only, shortly after a software update. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a0748c3ca4594d4d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.54, 0.2, 0.22, 0.04], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: across all regions, under reduced staffing. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e07935bdabd6ece5_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.03, 0.07, 0.84, 0.06], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: over the last hour, mid-incident. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0987f0ea596d295c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.54, 0.37, 0.06, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: across all regions, at the end of the fiscal period. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b593e43e14c7af84_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.01, 0.02, 0.24, 0.67, 0.05], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: across all regions, during the system migration. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8fea6aec19972988_n", "kind": "noul", "options": ["false", "true"], "target": [0.45, 0.55], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, while on-call rotation changed. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_af1a1e5d663d8e93_n", "kind": "noul", "options": ["false", "true"], "target": [0.56, 0.44], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: across all regions, during normal operations. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8cde76217ac60a7b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.86, 0.08, 0.06], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: in production only, shortly after a software update. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_349eb495867da9be_n", "kind": "noul", "options": ["false", "true"], "target": [0.7, 0.3], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, following a recent audit. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_42e149363a519e75_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during the holiday freeze. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0393f26486638091_n", "kind": "noul", "options": ["false", "true"], "target": [0.68, 0.32], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during an external partner integration. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_52886e4edc0cb23d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.33, 0.64, 0.02], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: across all regions, during normal operations. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_74360a146f22d76c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.0, 0.02, 0.95, 0.03], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: over the last hour, during the morning shift. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_18b7126b266b8b88_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.93, 0.06, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: in production only, during normal operations. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4fbd4f19a33531ca_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.2, 0.7, 0.1, 0.0, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, at the end of the fiscal period. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_03791fb3cdaef214_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.0, 0.96, 0.03], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_daabd32aac924cfc_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.85, 0.13, 0.01, 0.01], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: in production only, during peak load. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d9b1b40b971901ab_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.77, 0.22, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: in production only, mid-incident. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_46fc6b5934e4b648_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: across all regions, during the quarterly review. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_204af7bbcf2b5e94_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.62, 0.3, 0.05, 0.03], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: during the batch window, as part of a compliance sweep. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_99faf32861a9e7ae_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.02, 0.28, 0.67, 0.02], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: in production only, during a scheduled maintenance window. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3273873af4e5532e_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: in production only, while on-call rotation changed. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9f576097d3c2da5e_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: across all regions, at the end of the fiscal period. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a6b0b1cdc95d7c62_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.12, 0.69, 0.18, 0.01], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during the holiday freeze. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_569cecf3eb6d7fd1_n", "kind": "noul", "options": ["false", "true"], "target": [0.65, 0.35], "state": "The log shipper correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during the quarterly review. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cd8ea6a5eb6c1279_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally flags a step-function change in error slope. Context: during the batch window, during normal operations. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_91dda2b071d780ab_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.02, 0.86, 0.12], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: in production only, shortly after a software update. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8a5c4babefb361ca_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "The metrics pipeline flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during the holiday freeze. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6dcfaba90c16d99d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.19, 0.72, 0.07, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: over the last hour, during an external partner integration. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9580b5c3a6e00a21_n", "kind": "noul", "options": ["false", "true"], "target": [0.64, 0.36], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: over the last hour, with staffing at reduced levels. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4a84bcf25bcb06cb_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The log shipper matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: over the last hour, immediately after go-live. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_43368c76580c1474_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.55, 0.03, 0.09, 0.33], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, with a new vendor onboarded. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fa169560f9c54f95_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: during the batch window, during an external partner integration. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b51203e090bb5e3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.45, 0.48, 0.02, 0.0], "state": "The metrics pipeline shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d3c87cd61b7833da_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: over the last hour, following a recent audit. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_442baca2c631d496_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.39, 0.0, 0.21, 0.4], "state": "The log shipper correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: across all regions, during peak load. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fa169560f9c54f95_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.63, 0.35, 0.02, 0.0], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: during the batch window, during an external partner integration. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_66bb7c13ab3eebe2_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.17, 0.74, 0.08, 0.01], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: across all regions, while legacy systems are still active. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7e45a3f0b745f909_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.2, 0.77, 0.03], "state": "The log shipper correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: across all regions, with staffing at reduced levels. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3796f609358d6057_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: during the batch window, at the end of the fiscal period. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_949ffb792b47aacd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.09, 0.61, 0.25, 0.05, 0.0], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: across all regions, as part of a compliance sweep. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_062e6ffb1e13c0cf_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.46, 0.01, 0.28, 0.25], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during the system migration. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d958ef3f41f3e2bb_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.58, 0.39, 0.02, 0.01], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: across all regions, during an external partner integration. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_75d74d57db0a99c5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.15, 0.83, 0.02], "state": "The metrics pipeline lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: during the batch window, following a recent audit. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_40a63bb8846bf86a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.26, 0.72, 0.02], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, immediately after go-live. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b099293a4333e1b1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.63, 0.36, 0.0], "state": "The log shipper correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: over the last hour, under reduced staffing. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_12d5cd5faff2bb64_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.84, 0.15, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: over the last hour, while legacy systems are still active. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ceb084f2230cd528_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.0, 0.1717, 0.8081, 0.0202], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: during the batch window, as part of a compliance sweep. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ada90d9e2c31d601_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.08, 0.36, 0.52, 0.04, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, shortly after a software update. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3f2a5c0bdb9bd726_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during a scheduled maintenance window. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0dbb5c90e33dd3d5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.19, 0.63, 0.16, 0.02, 0.0], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during the holiday freeze. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bbe480e6e4fb9f6f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.38, 0.54, 0.06, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: over the last hour, during peak load. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b6bae954cee8b3d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.32, 0.68, 0.0], "state": "The log shipper flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: during the batch window, while on-call rotation changed. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_efeed6b3e524f2dd_n", "kind": "noul", "options": ["false", "true"], "target": [0.48, 0.52], "state": "The log shipper shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: in production only, during the quarterly review. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cc6595839cc38d9d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.45, 0.17, 0.37, 0.01], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0cebf13cfcf4e49d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.06, 0.67, 0.26, 0.0], "state": "Service catalog-sync correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: across all regions, during the morning shift. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_01962ea974c463f1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.34, 0.64, 0.01], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: during the batch window, with a new vendor onboarded. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_110eef25c8924319_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: over the last hour, during the morning shift. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9578e242693a8cce_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.64, 0.34, 0.0], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: in production only, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3641702b2d37aa09_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.58, 0.4, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: over the last hour, during peak load. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b6bae954cee8b3d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.8, 0.2, 0.0, 0.0], "state": "The log shipper flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: during the batch window, while on-call rotation changed. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_57e52c160f30209f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.23, 0.03, 0.47, 0.27], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: across all regions, during the morning shift. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3b002d0b93ad4f84_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.26, 0.03, 0.21, 0.5], "state": "The log shipper shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: during the batch window, during the quarterly review. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c61f01fb26fee313_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during normal operations. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a91ff7f327926f23_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.24, 0.09, 0.03, 0.64], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: over the last hour, as part of a compliance sweep. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4c4aecf64f40f659_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.26, 0.16, 0.04, 0.54], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: across all regions, immediately after go-live. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_26276d48f610b8d0_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.89, 0.05, 0.01, 0.05], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: over the last hour, mid-incident. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b087eafd33e8f843_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.47, 0.29, 0.22, 0.02], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, mid-incident. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b548a71aafaf06fe_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.38, 0.6, 0.01], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, following a recent audit. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_61e49f518d313d51_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.29, 0.67, 0.03], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: in production only, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9f171ab6c27b5d16_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.13, 0.77, 0.08, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: over the last hour, during the system migration. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dff7c6f6e7e4c812_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.37, 0.59, 0.03, 0.01], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: during the batch window, with a new vendor onboarded. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b3cc7f981c5e0a32_n", "kind": "noul", "options": ["false", "true"], "target": [0.46, 0.54], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: over the last hour, while legacy systems are still active. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2c9823436b1dea76_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.32, 0.67, 0.01], "state": "The metrics pipeline flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: across all regions, during the holiday freeze. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0112ab333ed0d80f_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during the system migration. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8ef898e8a0867e12_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.17, 0.67, 0.12, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: across all regions, shortly after a software update. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_71d8e406f440ac30_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.04, 0.75, 0.21, 0.0], "state": "The metrics pipeline shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: during the batch window, during the morning shift. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3db124ff31bab8ad_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during a scheduled maintenance window. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c44bf3123b7c5a41_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.95, 0.02, 0.02, 0.01], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: in production only, mid-incident. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e7c9f9ceda672ec5_n", "kind": "noul", "options": ["false", "true"], "target": [0.92, 0.08], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: over the last hour, immediately after go-live. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7dc7ead57a2f6174_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: in production only, during normal operations. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ed6d02519f6e5bb7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.19, 0.77, 0.04], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: across all regions, during peak load. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7bec2da789ef6e87_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: over the last hour, during the holiday freeze. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9fd26bc8a4b18ae8_n", "kind": "noul", "options": ["false", "true"], "target": [0.56, 0.44], "state": "The log shipper correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: over the last hour, during the morning shift. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dde53effbf8fe07b_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, while on-call rotation changed. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f00cab47410d53e3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.01, 0.02, 0.47, 0.48, 0.01], "state": "The log shipper correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: during the batch window, during the quarterly review. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_30292a804880b775_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.21, 0.52, 0.27, 0.0, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: over the last hour, with a new vendor onboarded. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c78f7fa6311228bb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.37, 0.39, 0.23, 0.01], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: in production only, with staffing at reduced levels. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ed06191f323926de_n", "kind": "noul", "options": ["false", "true"], "target": [0.69, 0.31], "state": "The log shipper correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: over the last hour, during a scheduled maintenance window. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c7bd7ca1bc56f2a0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.01, 0.01, 0.15, 0.75, 0.07], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: in production only, during an external partner integration. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8ca21b3ed75eccfe_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.08, 0.28, 0.03, 0.61], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: over the last hour, immediately after go-live. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6b3e5b1c8b2742ff_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, as part of a compliance sweep. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_25bcac4ec77a1283_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.08, 0.47, 0.44], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: in production only, with a new vendor onboarded. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_585afcaa3f6fd825_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Service catalog-sync flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: in production only, following a recent audit. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a6fb2e1c6ce2dcb8_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.61, 0.01, 0.01, 0.37], "state": "The log shipper lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: during the batch window, during peak load. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0f5a1fab444e6257_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.46, 0.52, 0.01], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: across all regions, while on-call rotation changed. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d664c425658d2667_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.0, 0.78, 0.2], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: across all regions, during the morning shift. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6abdd07f3694153e_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: across all regions, under an active deadline. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a62ab8910c8d9272_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "Service catalog-sync shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: in production only, at the end of the fiscal period. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_facda66362759f45_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.15, 0.8, 0.05], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the holiday freeze. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1e7dc03ca6a50b91_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, as part of a compliance sweep. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8e8ae622f0a63d9c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.28, 0.59, 0.08, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during a scheduled maintenance window. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_90f1bbe49bb23f91_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: in production only, during the system migration. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_66d80698bd02fe75_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.89, 0.11, 0.0, 0.0], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: in production only, with a new vendor onboarded. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cba6a0d1b0ab4c06_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.48, 0.5, 0.01], "state": "Dashboard checkout-funnel 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 automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9ee4337e34322b9b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.52, 0.37, 0.08, 0.0], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, with a new vendor onboarded. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1ac955cbb2df91fd_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.07, 0.24, 0.32, 0.37], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: over the last hour, during the system migration. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_151f039ab5db2c82_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.36, 0.64, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: in production only, under reduced staffing. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_967b0b75cee0e199_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.2, 0.05, 0.52, 0.23], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: over the last hour, during the holiday freeze. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_99f247f513528d3a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.72, 0.28, 0.0, 0.0], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: during the batch window, following a recent audit. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_35e102fa1fc1cc2d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.73, 0.1, 0.17], "state": "The log shipper shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: across all regions, shortly after a software update. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_74360a146f22d76c_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: over the last hour, during the morning shift. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_399c65059fa89b66_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.07, 0.65, 0.01, 0.27], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: over the last hour, shortly after a software update. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_24317890bc911412_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.2, 0.73, 0.02, 0.05], "state": "Service catalog-sync shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: during the batch window, following a recent audit. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4d43d3bf973f0738_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.05, 0.9, 0.05], "state": "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, immediately after go-live. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7d1add9a463ea921_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.14, 0.83, 0.03], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, under reduced staffing. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_37e710e3d7077bfa_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.04, 0.79, 0.17, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: in production only, during peak load. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d5077479eefccca7_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "The log shipper shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: over the last hour, during an external partner integration. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7c6361f77d49fde9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.17, 0.81, 0.02], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: across all regions, during an external partner integration. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1f9e4a2792794a54_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: in production only, at the end of the fiscal period. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2f335d0fc964897d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.05, 0.85, 0.1], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, following a recent audit. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6b579976843d1062_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.18, 0.74, 0.07], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: during the batch window, during normal operations. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_74f9f38627addd2c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.38, 0.6, 0.01], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: in production only, while on-call rotation changed. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_42c2d907b8a801ec_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.15, 0.83, 0.02], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: across all regions, shortly after a software update. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9374e027075bf9a1_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The log shipper matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, under reduced staffing. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_93a6705828bd18e0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.16, 0.38, 0.46, 0.0, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: in production only, during a scheduled maintenance window. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d359e2525c4a5b38_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.75, 0.06, 0.0, 0.19], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: over the last hour, while on-call rotation changed. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3e0b261085d79448_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.68, 0.0, 0.26, 0.06], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: during the batch window, under reduced staffing. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e422908a07b68972_n", "kind": "noul", "options": ["false", "true"], "target": [0.66, 0.34], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: across all regions, during the holiday freeze. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7153fd5fcc5c1049_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.83, 0.14, 0.03, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during the morning shift. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6f26a11ee442fa08_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during the holiday freeze. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ad266a43f2d8dfac_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.11, 0.64, 0.24, 0.01], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: over the last hour, as part of a compliance sweep. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bcec6f69a8081c83_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: across all regions, during the holiday freeze. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_af946a1127ccc143_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "The log shipper lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during peak load. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_41bc23ba4909fb60_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.73, 0.23, 0.02, 0.02], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: across all regions, during normal operations. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_91e8ebd752ab9302_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.1, 0.78, 0.1, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: in production only, following a recent audit. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1e62dc24510c8cf2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.1, 0.76, 0.14, 0.0, 0.0], "state": "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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8f72d51ca19c9dd3_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.88, 0.12, 0.0, 0.0], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: in production only, while on-call rotation changed. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fe09c177a65ed5d6_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.0, 0.77, 0.22], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: over the last hour, during the quarterly review. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8427d38227d31588_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.05, 0.91, 0.04], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: in production only, with staffing at reduced levels. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0d0751f20335acfb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.33, 0.66, 0.01], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, immediately after go-live. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_56a9c3acbff7a655_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.13, 0.05, 0.49, 0.33], "state": "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 operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_67e0e30fbee38639_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.33, 0.05, 0.45, 0.17], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: over the last hour, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_53c4e587a82efb74_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.12, 0.84, 0.04], "state": "The log shipper reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: in production only, during peak load. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6f04216405832758_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: over the last hour, immediately after go-live. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_55c606641a6da7e9_n", "kind": "noul", "options": ["false", "true"], "target": [0.41, 0.59], "state": "The log shipper reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during an external partner integration. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d5ccbe15f3edec00_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0202, 0.5657, 0.2626, 0.1515, 0.0, 0.0], "state": "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, during a scheduled maintenance window. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_03284d438b2c61b9_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.55, 0.4, 0.04, 0.01], "state": "Service catalog-sync flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: in production only, at the end of the fiscal period. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_65356be287049889_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: during the batch window, under an active deadline. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_65f8f8d04abdd31e_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: over the last hour, during the quarterly review. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f695fd40f46117d0_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.56, 0.19, 0.25, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: across all regions, mid-incident. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_93961702b07ef9c1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.88, 0.08, 0.03, 0.01], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, under reduced staffing. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9c23c2dc47f95729_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.16, 0.71, 0.09, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, following a recent audit. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1ebba6cfc3480f5c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.48, 0.5, 0.01], "state": "Service catalog-sync flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: over the last hour, during the quarterly review. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_039fa142e996e655_n", "kind": "noul", "options": ["false", "true"], "target": [0.23, 0.77], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, with staffing at reduced levels. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b8671d192b8b5dec_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.04, 0.27, 0.68], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: across all regions, while legacy systems are still active. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_72c3b840fc8d7de9_n", "kind": "noul", "options": ["false", "true"], "target": [0.55, 0.45], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: during the batch window, during the holiday freeze. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4ce5feea1e28e872_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.01, 0.25, 0.72], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, while legacy systems are still active. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dbf66c332f74855c_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: in production only, at the end of the fiscal period. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6ae34dee4512a1fb_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.9, 0.07, 0.02, 0.01], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: over the last hour, during the system migration. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c0994cd7f6b4611a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.38, 0.6, 0.01], "state": "The log shipper correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: in production only, with staffing at reduced levels. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b1750ddf94a17685_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.62, 0.37, 0.0], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: in production only, during normal operations. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2acdfd4e4a77c6c9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.87, 0.01, 0.01, 0.11], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: during the batch window, under reduced staffing. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2f1d3cafc152e493_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.24, 0.4, 0.04, 0.32], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: in production only, while legacy systems are still active. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2c9823436b1dea76_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "The metrics pipeline flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: across all regions, during the holiday freeze. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f60c955a34ab25dc_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.95, 0.04, 0.0, 0.01], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: during the batch window, mid-incident. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7250bb536a5bbaa7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.29, 0.7, 0.01], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during normal operations. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_222f73525a210641_n", "kind": "noul", "options": ["false", "true"], "target": [0.23, 0.77], "state": "The log shipper lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: over the last hour, mid-incident. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4604d758f9ad4c28_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: in production only, while on-call rotation changed. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c43c84a42210daa8_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.53, 0.29, 0.13, 0.05], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: across all regions, during the holiday freeze. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_80bafac4c6d50132_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.18, 0.38, 0.43, 0.01], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: across all regions, while on-call rotation changed. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dc2f0c6dddb325ca_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: in production only, during normal operations. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c91a0c6c3b5f61f2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.15, 0.81, 0.04], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: over the last hour, shortly after a software update. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7176ab8fda0c5be8_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The metrics pipeline shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: over the last hour, during normal operations. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6c38529665fae474_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.17, 0.47, 0.03, 0.33], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: in production only, under an active deadline. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_657782ff04a1376c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.35, 0.61, 0.03, 0.01], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: in production only, shortly after a software update. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e8897e368b85ec9d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.14, 0.79, 0.07], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: during the batch window, during the morning shift. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_164c228273e57223_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.75, 0.22, 0.03, 0.0], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: during the batch window, during normal operations. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_57634c0496e4f3b5_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.23, 0.58, 0.03, 0.16], "state": "Service catalog-sync shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: over the last hour, under an active deadline. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4789c62be23dc7ce_n", "kind": "noul", "options": ["false", "true"], "target": [0.51, 0.49], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: during the batch window, during the quarterly review. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_623fef2612bba743_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally flags a step-function change in error slope. Context: across all regions, with a new vendor onboarded. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b8903fa1b9b72984_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.93, 0.06, 0.01, 0.0], "state": "The log shipper correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: over the last hour, during peak load. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e162c1c272515eb3_n", "kind": "noul", "options": ["false", "true"], "target": [0.51, 0.49], "state": "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.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_53a869627becc0c8_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.0, 0.49, 0.47], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, with a new vendor onboarded. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9e51802b54417469_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: during the batch window, during an external partner integration. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b9a8ffee826f927e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.13, 0.82, 0.05], "state": "The log shipper reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: across all regions, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1583f50fa2d0bdd3_n", "kind": "noul", "options": ["false", "true"], "target": [0.43, 0.57], "state": "The log shipper lost 4 minutes of trace data; 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.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_988b1a8138cf2d11_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.21, 0.76, 0.03], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: across all regions, while on-call rotation changed. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_508c80b4f8c4e90e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.88, 0.01, 0.0, 0.11], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, immediately after go-live. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ccb06f9acae4aa61_n", "kind": "noul", "options": ["false", "true"], "target": [0.2, 0.8], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: across all regions, during the system migration. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_88e535ac3e1db8b4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.02, 0.11, 0.15, 0.59, 0.13, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: in production only, during the morning shift. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_013945f2e84c1fae_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.84, 0.12, 0.02, 0.02], "state": "The log shipper correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: across all regions, immediately after go-live. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6cf8107ef036082b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.12, 0.0, 0.01, 0.87], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: over the last hour, with staffing at reduced levels. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a0ea99df027a094b_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: over the last hour, mid-incident. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ce87114a2568a43a_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "The log shipper lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: in production only, immediately after go-live. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4fd0409603d0714d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.39, 0.59], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: across all regions, during the system migration. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ef782d9abc028e10_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.88, 0.0, 0.1], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: across all regions, shortly after a software update. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f8119d431f51d5a4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.35, 0.63, 0.02], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during normal operations. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_961c4e5381856f9e_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The log shipper matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: in production only, while on-call rotation changed. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aac7e59190d56ec7_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: over the last hour, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3134e8a1d0c0385d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.49, 0.23, 0.26, 0.02], "state": "The metrics pipeline 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 monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b88a8c95ac44dff3_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.07, 0.01, 0.89], "state": "The log shipper matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, mid-incident. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ac3e76047bdb94a8_n", "kind": "noul", "options": ["false", "true"], "target": [0.65, 0.35], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, as part of a compliance sweep. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2bfc7efc31d78a61_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "The log shipper lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: in production only, as part of a compliance sweep. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b7d09fae8fc48d6e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.66, 0.32, 0.01, 0.01], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: over the last hour, with a new vendor onboarded. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c9cb7279de74fac6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.19, 0.75, 0.05], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: during the batch window, immediately after go-live. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_10503ecb519f6583_n", "kind": "noul", "options": ["false", "true"], "target": [0.9, 0.1], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during peak load. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5a3646aa4cab7454_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: in production only, under an active deadline. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9bfac4de582550ed_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.35, 0.63, 0.01], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: across all regions, following a recent audit. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_afcdc63909944fdd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.49, 0.51, 0.0], "state": "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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1ab979a6a834fbe1_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "The metrics pipeline lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_07155236268c03f8_n", "kind": "noul", "options": ["false", "true"], "target": [0.9, 0.1], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during the system migration. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_88118af93c4bb4af_n", "kind": "noul", "options": ["false", "true"], "target": [0.65, 0.35], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the system migration. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c8d6550a00e3dd9a_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The log shipper returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: across all regions, while legacy systems are still active. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7250bb536a5bbaa7_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during normal operations. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4e1a247e52a78373_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.14, 0.67, 0.19, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, under reduced staffing. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_de7a0cbacbca0cea_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: across all regions, mid-incident. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_68870693804515e6_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during the holiday freeze. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_663c06d39654009c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.39, 0.57, 0.01, 0.03], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: over the last hour, during peak load. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c31bb85dc7450e2d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.02, 0.33, 0.64, 0.01], "state": "Service catalog-sync shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: across all regions, while on-call rotation changed. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_15d41388f85a1729_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.55, 0.35, 0.07, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: over the last hour, under an active deadline. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6768b86a2cdb4545_n", "kind": "noul", "options": ["false", "true"], "target": [0.37, 0.63], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: across all regions, mid-incident. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ed6266a6519926a5_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.95, 0.0, 0.0, 0.05], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: across all regions, during normal operations. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4049b2027d639a83_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.26, 0.67, 0.06, 0.01], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: across all regions, during the quarterly review. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_639ff2a14f558dcf_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.35, 0.61, 0.03], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: over the last hour, mid-incident. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_75cf109945554dd7_n", "kind": "noul", "options": ["false", "true"], "target": [0.93, 0.07], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, mid-incident. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3acf5baf3e23037b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.8, 0.14, 0.05, 0.01], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: in production only, while on-call rotation changed. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_149a05711fd8dd9b_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: during the batch window, during normal operations. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4f207dc26fda8cd1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.22, 0.55, 0.21, 0.01, 0.0], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during normal operations. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cda127205fd949cf_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.17, 0.07, 0.37, 0.39], "state": "The metrics pipeline 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 supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_150a8aba43875b5a_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: over the last hour, at the end of the fiscal period. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c58194d84ea71f80_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.39, 0.49, 0.1, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: in production only, mid-incident. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c94ccb87b60a2083_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.15, 0.8, 0.04], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1b251321bbaa4228_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.3, 0.69, 0.01], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during the morning shift. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_27fc771fbfe70a3f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.6, 0.02, 0.06, 0.32], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; 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 supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_534519c6a9e9a124_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, while on-call rotation changed. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_49cd06ac56cd17ea_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: in production only, as part of a compliance sweep. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_344346d1dca94942_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.03, 0.43, 0.52, 0.01], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_242e000715e8eb89_n", "kind": "noul", "options": ["false", "true"], "target": [0.65, 0.35], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during the quarterly review. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b827af4f5d711d9d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.0, 0.25, 0.75], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: across all regions, during an external partner integration. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_798d797a313b07f2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.02, 0.33, 0.61, 0.03], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: during the batch window, as part of a compliance sweep. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1aebe92b3bf1cbda_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.25, 0.57, 0.18, 0.0], "state": "The metrics pipeline shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: in production only, during a scheduled maintenance window. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_12e4781122b634e7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.42, 0.54, 0.02], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: across all regions, mid-incident. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f5a84925684d56a1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.37, 0.62, 0.01], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during the morning shift. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1ebba6cfc3480f5c_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "Service catalog-sync flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: over the last hour, during the quarterly review. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_26967d4f336328e0_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during normal operations. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f2790d0c8cc45d38_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.57, 0.42, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: over the last hour, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_091896d507eec22b_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: across all regions, during the holiday freeze. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fb802cf7dc288858_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.34, 0.58, 0.04, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: across all regions, during the system migration. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e1b0750dd323948a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.98, 0.0, 0.01, 0.01], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: during the batch window, while legacy systems are still active. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0eb8dc03a6d9403e_n", "kind": "noul", "options": ["false", "true"], "target": [0.21, 0.79], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, while on-call rotation changed. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a35ae03469d0f602_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: during the batch window, while on-call rotation changed. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8a32fe9806674f79_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.4, 0.58, 0.01], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, following a recent audit. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_de565b1e99ef021a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.01, 0.45, 0.52], "state": "The log shipper reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: during the batch window, under an active deadline. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f93549a551cfb627_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the holiday freeze. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ab7a336100c02c62_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.28, 0.02, 0.43, 0.27], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: over the last hour, under an active deadline. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_12b1ca0108f9d3dc_n", "kind": "noul", "options": ["false", "true"], "target": [0.57, 0.43], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: across all regions, as part of a compliance sweep. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ba23a0abeef89bac_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, under reduced staffing. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_218b498fcde24643_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.03, 0.43, 0.52, 0.01], "state": "The metrics pipeline lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: in production only, during the quarterly review. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_85c813a84cc6697f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.11, 0.28, 0.01, 0.6], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: across all regions, during the quarterly review. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_54fa6598301360c7_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: over the last hour, during a scheduled maintenance window. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_51af7aa51dae33a3_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.07, 0.51, 0.41, 0.01], "state": "The metrics pipeline flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: over the last hour, under reduced staffing. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b548a71aafaf06fe_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.88, 0.0, 0.02, 0.1], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, following a recent audit. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7d85d6a60969d515_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.08, 0.5, 0.4, 0.02, 0.0], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: over the last hour, under reduced staffing. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8b3ac1455ee1eaf2_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: during the batch window, following a recent audit. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cc149a3eb4870e24_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.38, 0.42, 0.2, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: over the last hour, during normal operations. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5fe6eeeb3ee53d02_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.33, 0.66, 0.01], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: over the last hour, during the quarterly review. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_87140ad0960ddcf1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.0, 0.01, 0.94], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, at the end of the fiscal period. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f06452859da3ed37_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.14, 0.8, 0.06, 0.0], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: across all regions, during the quarterly review. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b28e2d0ccd3aa9b0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.07, 0.49, 0.36, 0.08, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: across all regions, under an active deadline. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5598765d8af5f7f5_n", "kind": "noul", "options": ["false", "true"], "target": [0.37, 0.63], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the morning shift. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8b9ef5e3c46df5aa_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0202, 0.1717, 0.6667, 0.1414, 0.0], "state": "The metrics pipeline flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: in production only, under an active deadline. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5882da9e497469a1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.02, 0.4, 0.58], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: in production only, as part of a compliance sweep. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b3f19600df86d460_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.49, 0.48, 0.02, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, following a recent audit. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6a3a545ccc4e6807_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: during the batch window, during a scheduled maintenance window. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3b78cd6bf32fd906_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.22, 0.53, 0.21, 0.04], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: over the last hour, during peak load. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bc9401edbbc3d49c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.17, 0.72, 0.11, 0.0, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: in production only, during peak load. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_964ba3537197a273_n", "kind": "noul", "options": ["false", "true"], "target": [0.69, 0.31], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, with a new vendor onboarded. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4591add51f7fdc1c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.22, 0.72, 0.01, 0.05], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: in production only, during the morning shift. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2053e3f435637359_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.03, 0.53, 0.42], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: over the last hour, as part of a compliance sweep. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_622ae85dc4e3b148_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.54, 0.39, 0.06], "state": "The metrics pipeline lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: during the batch window, as part of a compliance sweep. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4b726c3ecf66c27d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.28, 0.64, 0.08, 0.0, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during peak load. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cff0debea5b0a5e3_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: in production only, during the system migration. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f11379ae644a65bb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.61, 0.37, 0.01], "state": "The log shipper shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: over the last hour, following a recent audit. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ef812cca97747fde_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.1, 0.01, 0.13, 0.76], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: in production only, during the system migration. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_47cbadcb91c14c54_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.92, 0.08, 0.0, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: in production only, under reduced staffing. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c08d0b0439f2bba3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.19, 0.8, 0.01], "state": "Service catalog-sync flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: during the batch window, during the holiday freeze. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_84a89e92a2b1200a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.5, 0.43, 0.07, 0.0], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: in production only, during normal operations. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_93ec4830fbf491e1_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, under an active deadline. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_672aef205a121ddc_n", "kind": "noul", "options": ["false", "true"], "target": [0.52, 0.48], "state": "Service catalog-sync lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: in production only, during the system migration. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e4bf362afb6c1a52_n", "kind": "noul", "options": ["false", "true"], "target": [0.47, 0.53], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, as part of a compliance sweep. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_446e1db3767a6605_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.24, 0.73, 0.02], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: across all regions, during peak load. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_905c2d544341369c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.23, 0.75, 0.02], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: in production only, during the system migration. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a755e8a7eee0a84b_n", "kind": "noul", "options": ["false", "true"], "target": [0.49, 0.51], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during normal operations. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_08bcbe44d03d599e_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: across all regions, under reduced staffing. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_75ea0aabd79305be_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during peak load. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b24a498fc67ae71d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.39, 0.61, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: over the last hour, during the system migration. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_84a89e92a2b1200a_n", "kind": "noul", "options": ["false", "true"], "target": [0.37, 0.63], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: in production only, during normal operations. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fb591d0b8976cb74_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.66, 0.3, 0.02, 0.02], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: over the last hour, with a new vendor onboarded. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_85b33f2c32a7b687_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, shortly after a software update. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_043f4d0be564ac57_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.82, 0.16, 0.02, 0.0], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: in production only, during the quarterly review. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_73c6a7add3479ecd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.22, 0.54, 0.21, 0.03, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cf8ba037ff802f40_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.19, 0.13, 0.21, 0.47], "state": "Service catalog-sync shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: during the batch window, as part of a compliance sweep. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_15b7ae0a35f3c290_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.06, 0.01, 0.61, 0.32], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: during the batch window, under an active deadline. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cb7b14485d6ed187_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.57, 0.41, 0.01], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: over the last hour, at the end of the fiscal period. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_26e332c0615f3a4a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.43, 0.57, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: over the last hour, shortly after a software update. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a6698dc29da472d1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.25, 0.66, 0.03, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: over the last hour, at the end of the fiscal period. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a6d4811b61d9839e_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: across all regions, with staffing at reduced levels. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5df8e2890c108205_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.35, 0.09, 0.05, 0.51], "state": "The log shipper flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: in production only, during a scheduled maintenance window. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2bcb2c106496e532_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.12, 0.48, 0.32, 0.07, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: in production only, mid-incident. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_41ba49f42d60bbdd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.26, 0.63, 0.07, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during a scheduled maintenance window. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5840917e4f6e4358_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.32, 0.41, 0.23, 0.04], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: in production only, mid-incident. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_74694fd8b8f973ce_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.38, 0.0, 0.59, 0.03], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, under reduced staffing. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_67ac392549e72423_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.15, 0.29, 0.52], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: across all regions, during the holiday freeze. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b1534353421146be_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.1, 0.6, 0.29, 0.01], "state": "The log shipper returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: in production only, under reduced staffing. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ed91a614e1108c87_n", "kind": "noul", "options": ["false", "true"], "target": [0.9, 0.1], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: over the last hour, with staffing at reduced levels. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_69429f4259b7c1c8_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "The metrics pipeline correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: during the batch window, while on-call rotation changed. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3597cd06d52cbaf3_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.78, 0.19, 0.02, 0.01], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally flags a step-function change in error slope. Context: during the batch window, following a recent audit. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5954213ea658489c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.62, 0.35, 0.0], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: across all regions, at the end of the fiscal period. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7796777046413d21_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.02, 0.42, 0.27, 0.27, 0.02, 0.0], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: in production only, during a scheduled maintenance window. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_03d92c4362a0bfd0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.12, 0.83, 0.05], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the holiday freeze. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_da6384c63ed0e1db_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: in production only, during a scheduled maintenance window. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_98a33d5a00a81ead_n", "kind": "noul", "options": ["false", "true"], "target": [0.46, 0.54], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the holiday freeze. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5cf8f96dcbc30307_n", "kind": "noul", "options": ["false", "true"], "target": [0.23, 0.77], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: in production only, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0383cc86b4f6dda9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.36, 0.62, 0.01], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: during the batch window, while legacy systems are still active. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_78fb08c3d4f4706e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.35, 0.64, 0.01], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the morning shift. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_786fd6c9b705d052_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.63, 0.28, 0.04, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: during the batch window, as part of a compliance sweep. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ba3abcf5132b506_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.31, 0.65, 0.02], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: over the last hour, as part of a compliance sweep. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3d6e20396755e444_n", "kind": "noul", "options": ["false", "true"], "target": [0.4, 0.6], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: during the batch window, while on-call rotation changed. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_91da20bdfaadc1ea_n", "kind": "noul", "options": ["false", "true"], "target": [0.58, 0.42], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: during the batch window, during the quarterly review. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_70614cc21ef4a4ed_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.32, 0.66, 0.01], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: during the batch window, with staffing at reduced levels. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9da1b28dbf4c61ab_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.39, 0.58, 0.01], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the holiday freeze. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_53d83ba39ce2df30_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.92, 0.01, 0.05], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, shortly after a software update. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8df4554cf94edd62_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.74, 0.25, 0.01, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: in production only, under reduced staffing. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2a428105b2080529_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.57, 0.43, 0.0], "state": "The log shipper reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: across all regions, shortly after a software update. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_48881da220e866d7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.27, 0.62, 0.06, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during the quarterly review. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_18a7d3189732ac20_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.14, 0.44, 0.4, 0.01, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: across all regions, during normal operations. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a3c2c989350e98be_n", "kind": "noul", "options": ["false", "true"], "target": [0.2, 0.8], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, under reduced staffing. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a8e2192939c31c07_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: over the last hour, as part of a compliance sweep. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c90a0a59b7619521_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.16, 0.71, 0.12, 0.01], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during the quarterly review. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d121442ff2aac3fc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.09, 0.24, 0.61, 0.06, 0.0], "state": "Service catalog-sync correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: across all regions, during the system migration. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_137f7e268343db03_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.06, 0.68, 0.25, 0.0], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during normal operations. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_656bb57d498888ff_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.29, 0.7, 0.01], "state": "The log shipper correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: in production only, while legacy systems are still active. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ce87114a2568a43a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0303, 0.6869, 0.2828, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: in production only, immediately after go-live. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b8e8427e555dae8e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.15, 0.08, 0.09, 0.68], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, following a recent audit. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aa76e1b08be64164_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.39, 0.61, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: during the batch window, under reduced staffing. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_62e0a52251e8256c_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during peak load. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dec7fc902d1dcf13_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.7, 0.01, 0.19, 0.1], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: over the last hour, with staffing at reduced levels. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e45e4e003d661c54_n", "kind": "noul", "options": ["false", "true"], "target": [0.21, 0.79], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: across all regions, under reduced staffing. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f8f438425cb40297_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during peak load. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_672aef205a121ddc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.13, 0.52, 0.33, 0.02, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: in production only, during the system migration. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4d327cc1eb0401de_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.5, 0.48, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: over the last hour, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2b137f3aa877f9ff_n", "kind": "noul", "options": ["false", "true"], "target": [0.22, 0.78], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: in production only, during an external partner integration. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ba6246cfc8df2c60_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.47, 0.5, 0.01], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: over the last hour, while on-call rotation changed. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_828b4494a8f3b38f_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "Service catalog-sync shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: during the batch window, following a recent audit. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a74a5846c0d519b2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.64, 0.35, 0.0], "state": "The metrics pipeline flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: during the batch window, during the quarterly review. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9d4df05514fd9267_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.9, 0.05, 0.01, 0.04], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5cfefea696488038_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.23, 0.73, 0.01, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: during the batch window, as part of a compliance sweep. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1435a99ea7828863_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.06, 0.76, 0.18, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: over the last hour, with staffing at reduced levels. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_22f8e532376a35cb_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.63, 0.3, 0.06, 0.01], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: over the last hour, while legacy systems are still active. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_17016241ae04a323_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: in production only, during the holiday freeze. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4dc26a73df75a210_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.47, 0.51, 0.01], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: over the last hour, during the quarterly review. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_774e8481d67f4166_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: in production only, immediately after go-live. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_269ed858d810daff_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: in production only, during normal operations. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_382ea4987732ecb7_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.0, 0.98, 0.02], "state": "The metrics pipeline correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: across all regions, during an external partner integration. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d61e8130995f9914_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.43, 0.57, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: during the batch window, with staffing at reduced levels. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c28ba3093f1ef556_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: during the batch window, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7b8e4d292498c347_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: in production only, while on-call rotation changed. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c91a0c6c3b5f61f2_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.89, 0.09, 0.01, 0.01], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: over the last hour, shortly after a software update. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b37c42f380f7793a_n", "kind": "noul", "options": ["false", "true"], "target": [0.38, 0.62], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: during the batch window, during the system migration. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0045a4bca93cf802_n", "kind": "noul", "options": ["false", "true"], "target": [0.93, 0.07], "state": "The metrics pipeline flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: in production only, mid-incident. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_38ed57fe11ba1918_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.78, 0.09, 0.1, 0.03], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, mid-incident. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7e3e859e419da64f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.03, 0.42, 0.53, 0.01], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the holiday freeze. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7c6361f77d49fde9_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.7, 0.25, 0.03, 0.02], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: across all regions, during an external partner integration. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_28392deab2b429a4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.15, 0.81, 0.04], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: in production only, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_08bf1943832b0ed2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.01, 0.19, 0.8], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: over the last hour, while on-call rotation changed. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_abd8539d50bf5dac_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: during the batch window, during the system migration. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_48ed8e6a3c640e11_n", "kind": "noul", "options": ["false", "true"], "target": [0.67, 0.33], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during an external partner integration. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_210bbb60ba10d1a8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.09, 0.73, 0.17, 0.01, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: in production only, during the morning shift. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a7c7f2b922c368fe_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.06, 0.89, 0.05], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: in production only, during the morning shift. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7d44ae9c8406eaa6_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.97, 0.02, 0.0, 0.01], "state": "The metrics pipeline flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: across all regions, immediately after go-live. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_86d8cf82e5e3f28b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.55, 0.44, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, with staffing at reduced levels. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_47a22788d012fdad_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: across all regions, while on-call rotation changed. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f19f77177f7bd9a7_n", "kind": "noul", "options": ["false", "true"], "target": [0.22, 0.78], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: during the batch window, mid-incident. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ef7da40d716fc88e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.15, 0.8, 0.05], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: during the batch window, mid-incident. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b548a71aafaf06fe_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, following a recent audit. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_64bdcffa6827d158_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.28, 0.33, 0.02, 0.37], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: across all regions, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c74a3d4e65c9743f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.09, 0.25, 0.64, 0.02, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during a scheduled maintenance window. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9abb9af0195b8608_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during the quarterly review. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3f377361ce9ed677_n", "kind": "noul", "options": ["false", "true"], "target": [0.46, 0.54], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: during the batch window, during a scheduled maintenance window. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3e141ec8bff8cbe0_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: over the last hour, during the system migration. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d4e6234994855e22_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.07, 0.13, 0.66, 0.14, 0.0], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: across all regions, during a scheduled maintenance window. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1ab979a6a834fbe1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.36, 0.59, 0.02], "state": "The metrics pipeline lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0c997215de6741f8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.24, 0.74, 0.02], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during the holiday freeze. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_05266732ea7c0c47_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during normal operations. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7d84ac1cd5cc9acd_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.56, 0.3, 0.12, 0.02], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during a scheduled maintenance window. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_15403d7b1d1f70cd_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.04, 0.92, 0.04], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: in production only, during the system migration. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f7d57590bd644635_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.98, 0.02, 0.0, 0.0], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: across all regions, under an active deadline. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cbae5c2d06540a15_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.0, 0.63, 0.37], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: across all regions, during the quarterly review. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0c619429577bda08_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: over the last hour, at the end of the fiscal period. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_08ef69d24f5ac611_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: over the last hour, mid-incident. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_06ffe40dc1ecfdde_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.03, 0.64, 0.32, 0.0], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during a scheduled maintenance window. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_77daea2b4f824801_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: over the last hour, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a62ab8910c8d9272_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.6, 0.39, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: in production only, at the end of the fiscal period. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_99faf32861a9e7ae_n", "kind": "noul", "options": ["false", "true"], "target": [0.66, 0.34], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: in production only, during a scheduled maintenance window. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c809391ee7fd89fa_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.54, 0.45, 0.0], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: during the batch window, during normal operations. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_43523ac4550235f9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.46, 0.53, 0.0], "state": "The log shipper flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: in production only, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e48a5c99ac87a31b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.22, 0.69, 0.09, 0.0], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: across all regions, during normal operations. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_12a453bfcf0b453a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.65, 0.34, 0.01, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: across all regions, at the end of the fiscal period. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_68595eefb765b625_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.56, 0.42, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: during the batch window, during the quarterly review. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9d87bb3b5405569f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.24, 0.25, 0.02, 0.49], "state": "The log shipper matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: across all regions, under an active deadline. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_df16f73c93476cf2_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: in production only, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3f71b728b03afc43_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: in production only, shortly after a software update. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8aee2ec7c43a35af_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "The metrics pipeline shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: in production only, as part of a compliance sweep. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9f0becfd17c7b108_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during a scheduled maintenance window. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4c06da280a9854e8_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.94, 0.05, 0.01, 0.0], "state": "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, while on-call rotation changed. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aba3520249b2f616_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.37, 0.18, 0.14, 0.31], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: in production only, immediately after go-live. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cb49ecccbaebd557_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.8, 0.15, 0.02, 0.03], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: during the batch window, during peak load. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eacad67578dcca81_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: in production only, following a recent audit. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a246203937346e78_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.44, 0.54], "state": "The log shipper correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: during the batch window, mid-incident. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca506297b3ad9fb6_n", "kind": "noul", "options": ["false", "true"], "target": [0.64, 0.36], "state": "Service catalog-sync flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: during the batch window, shortly after a software update. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_85982566fbdd6976_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: across all regions, immediately after go-live. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_812a1f9f8adef74b_n", "kind": "noul", "options": ["false", "true"], "target": [0.37, 0.63], "state": "The log shipper returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: over the last hour, during an external partner integration. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5de635d89ae898b3_n", "kind": "noul", "options": ["false", "true"], "target": [0.45, 0.55], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: in production only, at the end of the fiscal period. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4586cd9210939cd7_n", "kind": "noul", "options": ["false", "true"], "target": [0.37, 0.63], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: across all regions, immediately after go-live. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_654c01db7c4c4b8d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.59, 0.05, 0.07, 0.29], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: during the batch window, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c8a4136b63829911_n", "kind": "noul", "options": ["false", "true"], "target": [0.63, 0.37], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: over the last hour, following a recent audit. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d958ef3f41f3e2bb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.4, 0.57, 0.01], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: across all regions, during an external partner integration. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3200b294ae89a7ba_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "The log shipper shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: during the batch window, during normal operations. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e41c06d8279b9423_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.08, 0.6, 0.31, 0.0], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: over the last hour, following a recent audit. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c628e485afbd8145_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.4, 0.58, 0.01], "state": "The log shipper matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: in production only, shortly after a software update. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_74fb6a159a931ff2_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The log shipper shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: over the last hour, with staffing at reduced levels. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b1be6df2ebc315ab_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.14, 0.71, 0.14, 0.0], "state": "The log shipper reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: over the last hour, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7b7d956d04e1d809_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.78, 0.2, 0.01, 0.01], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, with staffing at reduced levels. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9f41cd9ffb0db4b3_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: in production only, as part of a compliance sweep. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_047055b1f2df0124_n", "kind": "noul", "options": ["false", "true"], "target": [0.18, 0.82], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: during the batch window, mid-incident. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_504d32baf68334f2_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: over the last hour, shortly after a software update. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fe827752ddaf5a89_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "The log shipper reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: over the last hour, immediately after go-live. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a75162cd3e9a33f0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0101, 0.0404, 0.8081, 0.1414, 0.0], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: during the batch window, shortly after a software update. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bb469e4d9692e553_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.53, 0.46, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: during the batch window, during the holiday freeze. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e626b6f2c18bb8e9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.75, 0.25, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: over the last hour, under reduced staffing. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_06e97b9a5af907c6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.53, 0.46, 0.0], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: during the batch window, immediately after go-live. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f06452859da3ed37_n", "kind": "noul", "options": ["false", "true"], "target": [0.43, 0.57], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: across all regions, during the quarterly review. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_898a558af9a0d38a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.0, 0.97, 0.02], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during the holiday freeze. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c9f4f3cfde85f2b5_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.49, 0.13, 0.02, 0.36], "state": "Node pgsql-14 flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: during the batch window, following a recent audit. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4b93bcb1a0d92877_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.39, 0.6, 0.01], "state": "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 monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a068a3e8abd279b5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.55, 0.43, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: over the last hour, under reduced staffing. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f7d9a996dabbf780_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.34, 0.65, 0.01], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, with staffing at reduced levels. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_04c24b382d8c57df_n", "kind": "noul", "options": ["false", "true"], "target": [0.48, 0.52], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: across all regions, under reduced staffing. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_323a55f575902780_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.05, 0.62, 0.31, 0.01], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: across all regions, during the holiday freeze. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f343b871297b5240_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.01, 0.75, 0.24], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: during the batch window, during peak load. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6c1f7a7112b072ba_n", "kind": "noul", "options": ["false", "true"], "target": [0.47, 0.53], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: during the batch window, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aa72a0886afb4d0c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.91, 0.08, 0.0, 0.01], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: across all regions, with staffing at reduced levels. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_43083e3d91c8c547_n", "kind": "noul", "options": ["false", "true"], "target": [0.45, 0.55], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, with a new vendor onboarded. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7bf34953bd349b2b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.61, 0.37], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: across all regions, as part of a compliance sweep. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2b36062772979607_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.09, 0.01, 0.06, 0.84], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, following a recent audit. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9d2cc02020d814ff_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.02, 0.32, 0.62, 0.03], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, as part of a compliance sweep. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_440d56252ff6d322_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The log shipper reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: across all regions, under reduced staffing. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_296a5aaaa21f5cf1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.72, 0.26, 0.0], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: during the batch window, under reduced staffing. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_81950e3214baac62_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.15, 0.82, 0.03], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, under an active deadline. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_29a091039fd3a398_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.05, 0.87, 0.08], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during peak load. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7f7ef4f001d86676_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.84, 0.13, 0.01, 0.02], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during the quarterly review. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_26e332c0615f3a4a_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: over the last hour, shortly after a software update. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ade0fbc0c3a1a2c5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.15, 0.53, 0.27, 0.05, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: in production only, as part of a compliance sweep. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d66ab3dc157eacbb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.19, 0.55, 0.2, 0.06, 0.0, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during the holiday freeze. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3796f609358d6057_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.42, 0.56, 0.01], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: during the batch window, at the end of the fiscal period. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5d7aa24ab5384821_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "The log shipper correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: across all regions, with a new vendor onboarded. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a93ffc9a7eb94c9c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.53, 0.46, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: across all regions, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0953579938936ca9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.86, 0.11, 0.0, 0.03], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: in production only, following a recent audit. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3e0329d8027e223b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.81, 0.17, 0.01, 0.01], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, shortly after a software update. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c2227aeade41dedc_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: during the batch window, during an external partner integration. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ea20420b7e883739_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.02, 0.31, 0.64, 0.02], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: over the last hour, during a scheduled maintenance window. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_15d1d04c17f926ec_n", "kind": "noul", "options": ["false", "true"], "target": [0.66, 0.34], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: over the last hour, as part of a compliance sweep. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f00cab47410d53e3_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "The log shipper correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: during the batch window, during the quarterly review. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7cb4e7a980f6d8e0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.12, 0.58, 0.3, 0.0, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: across all regions, at the end of the fiscal period. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c7bd7ca1bc56f2a0_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.61, 0.38, 0.01, 0.0], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: in production only, during an external partner integration. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_238ce2e06ddb6af4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.13, 0.73, 0.12, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: in production only, during normal operations. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5dfccb36cbc1710f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.22, 0.76, 0.02], "state": "The log shipper correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: across all regions, during the morning shift. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ae5e4931ec1281f_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during normal operations. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a49f409c5b768314_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Service catalog-sync flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: in production only, with a new vendor onboarded. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7a46391bdb0054ac_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.48, 0.52, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: in production only, with a new vendor onboarded. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3c01e06ec51286ab_n", "kind": "noul", "options": ["false", "true"], "target": [0.48, 0.52], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the quarterly review. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7744676a7b52bd13_n", "kind": "noul", "options": ["false", "true"], "target": [0.6, 0.4], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: over the last hour, under an active deadline. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f2c15a53a287c548_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.24, 0.23, 0.06, 0.47], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: during the batch window, during the system migration. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4089d938fba218e2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.48, 0.51, 0.0], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: across all regions, during the quarterly review. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bc956fa83e9fd6d5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.26, 0.56, 0.13, 0.0], "state": "The log shipper reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: in production only, as part of a compliance sweep. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f90304720e25103d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.08, 0.65, 0.19, 0.08, 0.0, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: over the last hour, during peak load. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e32d41b698f78d64_n", "kind": "noul", "options": ["false", "true"], "target": [0.93, 0.07], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: in production only, under an active deadline. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2dc8704e2a26c3de_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.72, 0.0, 0.28], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: across all regions, shortly after a software update. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5dfc58659e326391_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.37, 0.63, 0.0], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: in production only, while on-call rotation changed. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6b6c375dbbd121a1_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during the system migration. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1ac955cbb2df91fd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.21, 0.65, 0.08, 0.0], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: over the last hour, during the system migration. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_242e000715e8eb89_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.26, 0.67, 0.07, 0.0, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during the quarterly review. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9e9308d8a2dc38e8_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during normal operations. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4c06da280a9854e8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.2, 0.76, 0.04], "state": "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, while on-call rotation changed. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_59579f45781f574d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.24, 0.6, 0.16, 0.0], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: in production only, with a new vendor onboarded. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ae7fc9aa95d5ab94_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, immediately after go-live. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_246b4b115e9dc514_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.0, 0.01, 0.93, 0.06], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: over the last hour, at the end of the fiscal period. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6b243ccf8d56a9ed_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.21, 0.76, 0.03], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: in production only, as part of a compliance sweep. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1bb7ccdcf2837ac0_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "The log shipper correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: during the batch window, while legacy systems are still active. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_30a9f599e64f3200_n", "kind": "noul", "options": ["false", "true"], "target": [0.49, 0.51], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: in production only, during a scheduled maintenance window. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7a4631603fa4a7d7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.09, 0.75, 0.15, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: across all regions, under reduced staffing. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_071a266928eeba09_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.54, 0.45, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: in production only, while legacy systems are still active. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6d75fe6a611dab9b_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, shortly after a software update. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b51203e090bb5e3_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.15, 0.35, 0.04, 0.46], "state": "The metrics pipeline shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_569cecf3eb6d7fd1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.48, 0.43, 0.04, 0.0], "state": "The log shipper correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during the quarterly review. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_11e442e37771ac24_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.63, 0.26, 0.11, 0.0], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, while on-call rotation changed. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2466a8342d40299f_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The metrics pipeline lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: during the batch window, at the end of the fiscal period. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1596da3f8c3755b7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.08, 0.32, 0.59, 0.01, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the morning shift. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b46629538f55c1e8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.03, 0.75, 0.21, 0.0], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: over the last hour, as part of a compliance sweep. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_40cc3fe25478bc2e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.44, 0.55, 0.0], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: during the batch window, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5a57bc5668966986_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.03, 0.06, 0.83, 0.08], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: in production only, mid-incident. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_43083e3d91c8c547_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.08, 0.66, 0.25, 0.01, 0.0], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, with a new vendor onboarded. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_79522b9794cc46fa_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.77, 0.2, 0.02, 0.01], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: during the batch window, while on-call rotation changed. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_10e8a1b1d307d5f8_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: across all regions, during the morning shift. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8b710a9ef2d60041_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.76, 0.22, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: in production only, during the holiday freeze. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_02ea75e1250dbc31_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.56, 0.32, 0.06, 0.0], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during the system migration. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_56b98ac626c74c7e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.18, 0.43, 0.38, 0.01, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: across all regions, immediately after go-live. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4d28dd10f802b020_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.11, 0.0, 0.41, 0.48], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5546744a16703882_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: in production only, with a new vendor onboarded. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_13e9b2a5dc8ab04e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.45, 0.49, 0.06, 0.0], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: in production only, following a recent audit. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_660bb640fe1e5921_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.14, 0.48, 0.33, 0.04, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: in production only, as part of a compliance sweep. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_637cd14b331077a7_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, immediately after go-live. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fa9c53349b78f486_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: over the last hour, under an active deadline. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b099293a4333e1b1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.77, 0.18, 0.05, 0.0], "state": "The log shipper correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: over the last hour, under reduced staffing. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_38b4d16ac56fec8f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.99, 0.0, 0.01], "state": "Node pgsql-14 flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: across all regions, shortly after a software update. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_90ce4d95cbab93cf_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.51, 0.43, 0.01], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: during the batch window, mid-incident. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3afd33334f10c617_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.15, 0.02, 0.12, 0.71], "state": "The log shipper shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: over the last hour, mid-incident. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f519a0039b1664cb_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: in production only, with a new vendor onboarded. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_833dc0d74faeac74_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.06, 0.63, 0.28, 0.01], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: across all regions, during a scheduled maintenance window. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_01bc2814a90e6c0d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.07, 0.25, 0.63, 0.05, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: over the last hour, during the holiday freeze. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d8fe699ad5d2466e_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during normal operations. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_37e710e3d7077bfa_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The log shipper lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: in production only, during peak load. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e032e061bd2cd86b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.23, 0.03, 0.1, 0.64], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: over the last hour, under an active deadline. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_37a17dba460329ee_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.56, 0.01, 0.02, 0.41], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during the holiday freeze. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_521674ef10f726af_n", "kind": "noul", "options": ["false", "true"], "target": [0.22, 0.78], "state": "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 system migration. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c5dc4663b70cf323_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.34, 0.57, 0.06, 0.03], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: during the batch window, shortly after a software update. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_37024efe4bc0be10_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.09, 0.41, 0.47, 0.03], "state": "The metrics pipeline correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: in production only, immediately after go-live. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f11379ae644a65bb_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.45, 0.49, 0.05, 0.01], "state": "The log shipper shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: over the last hour, following a recent audit. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ee496d54df12764a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.31, 0.59, 0.04, 0.0], "state": "The metrics pipeline correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: in production only, during the system migration. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b315feb1b9118c47_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.0, 0.9, 0.06], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, mid-incident. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fe95596ba68177bc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.44, 0.45, 0.05, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during the system migration. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0e397acb484ee7ff_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.06, 0.6, 0.31, 0.01], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: in production only, as part of a compliance sweep. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_abc699cd8c2bd7c5_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.03, 0.63, 0.33, 0.01], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: across all regions, following a recent audit. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_abd8539d50bf5dac_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.38, 0.1, 0.35, 0.17], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: during the batch window, during the system migration. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_91ab44ea52730b7e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.58, 0.41, 0.01, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: across all regions, with a new vendor onboarded. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_adadb78e16f3a478_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.52, 0.46], "state": "The log shipper lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: during the batch window, during an external partner integration. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5e60a338cf4d34af_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.58, 0.35, 0.06, 0.01], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: across all regions, shortly after a software update. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_214cf9eb8da30da8_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.0, 0.68, 0.3], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: during the batch window, during the morning shift. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e6c5564f5604e6b4_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.9, 0.1, 0.0, 0.0], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: in production only, under an active deadline. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1e783e44639ee69f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.06, 0.03, 0.79, 0.12], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, following a recent audit. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7b5966e621aeef56_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: over the last hour, during the holiday freeze. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_153715564c81edb5_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.11, 0.83, 0.06, 0.0], "state": "The log shipper correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: over the last hour, at the end of the fiscal period. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cb5f8301b187a435_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.11, 0.14, 0.55, 0.19, 0.01], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: in production only, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8d0ab85e9cbcb251_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: across all regions, immediately after go-live. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_693dcb1497790085_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.15, 0.07, 0.11, 0.67], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: in production only, during the morning shift. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3b78cd6bf32fd906_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: over the last hour, during peak load. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d54909cdd49e31c0_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.87, 0.0, 0.11, 0.02], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during the quarterly review. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_850ab3eafa006973_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.26, 0.03, 0.14, 0.57], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during the holiday freeze. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5f581f00af3017d1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.7, 0.22, 0.03, 0.05], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: over the last hour, shortly after a software update. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ed402eb293d8430c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.94, 0.04, 0.01, 0.01], "state": "The log shipper shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: during the batch window, under an active deadline. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_22e3d324c0e7f69c_n", "kind": "noul", "options": ["false", "true"], "target": [0.44, 0.56], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f9ac22395ae0610b_n", "kind": "noul", "options": ["false", "true"], "target": [0.5, 0.5], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during a scheduled maintenance window. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e7a139f815283fb8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.05, 0.46, 0.39, 0.1, 0.0, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, immediately after go-live. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5fe6eeeb3ee53d02_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: over the last hour, during the quarterly review. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2f52988d4facffdb_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.97, 0.0, 0.0, 0.03], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: during the batch window, under reduced staffing. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e8735976824db8bc_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.24, 0.08, 0.02, 0.66], "state": "The log shipper shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: across all regions, as part of a compliance sweep. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca80377af16a4b61_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.15, 0.8, 0.05], "state": "The metrics pipeline lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: over the last hour, mid-incident. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_66392cfefcaa9ea4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.02, 0.69, 0.29], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f601f758371c811b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.49, 0.07, 0.4], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: across all regions, mid-incident. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_647017d2485abd9c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0505, 0.0101, 0.5354, 0.404], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_04b9059eddd942ca_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.21, 0.08, 0.4, 0.31], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, under an active deadline. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6efbe7753cc413fc_n", "kind": "noul", "options": ["false", "true"], "target": [0.67, 0.33], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, while legacy systems are still active. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_409b8061e2bd0a7b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.65, 0.33, 0.0], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: during the batch window, following a recent audit. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1875f02a27d6242b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.09, 0.36, 0.51, 0.03, 0.0], "state": "The log shipper matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: over the last hour, as part of a compliance sweep. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7e592ecde7250f28_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.07, 0.82, 0.11], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, mid-incident. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d342bd2d1e301a7a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.0, 0.17, 0.83], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: across all regions, mid-incident. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6cf4229cc0ad81df_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.12, 0.06, 0.42, 0.4], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: across all regions, during the system migration. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_20757a8833b86768_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.07, 0.32, 0.61], "state": "The log shipper matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: across all regions, immediately after go-live. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ff85ab7601af8108_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.78, 0.18, 0.02, 0.02], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, at the end of the fiscal period. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ade8caae7b6af3b6_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.27, 0.27, 0.02, 0.44], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: across all regions, mid-incident. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cd2837ca730e63eb_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: over the last hour, following a recent audit. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_16da5341d8244d31_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.08, 0.78, 0.13, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: during the batch window, under an active deadline. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b4b6f5d7fed02caa_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.42, 0.49, 0.02, 0.07], "state": "The metrics pipeline 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 monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3ea5399fbd4ad000_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: across all regions, under an active deadline. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8b076748302085c8_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: in production only, while legacy systems are still active. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3e99da57536937ff_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.24, 0.51, 0.21, 0.04, 0.0], "state": "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, during a scheduled maintenance window. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1110ef5f9271cdd1_n", "kind": "noul", "options": ["false", "true"], "target": [0.57, 0.43], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_83527f519ef88177_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.0, 0.07, 0.93], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: during the batch window, as part of a compliance sweep. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a99ccb61670d717b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.42, 0.36, 0.17, 0.01], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during peak load. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d0fe9e5e8c6fd465_n", "kind": "noul", "options": ["false", "true"], "target": [0.43, 0.57], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: during the batch window, while on-call rotation changed. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_921101e5a60627a9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.03, 0.73, 0.2], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: in production only, while on-call rotation changed. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_998a6f7e1468bd11_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.31, 0.57, 0.09, 0.03, 0.0, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: during the batch window, during the system migration. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f75ded48dc776781_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: across all regions, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_db34284446ab4d26_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.13, 0.58, 0.28, 0.01], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during an external partner integration. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8ec79f61de5e4b47_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.81, 0.01, 0.15], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: during the batch window, shortly after a software update. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3c38daa65961c11c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.23, 0.75, 0.02], "state": "The log shipper matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during an external partner integration. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cce6e77b0ca1ddc9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.11, 0.3, 0.18, 0.41], "state": "The log shipper reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: across all regions, immediately after go-live. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5df18bda476b8971_n", "kind": "noul", "options": ["false", "true"], "target": [0.47, 0.53], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: across all regions, during an external partner integration. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e45e4e003d661c54_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.02, 0.75, 0.23], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: across all regions, under reduced staffing. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a57a88343e4459c6_n", "kind": "noul", "options": ["false", "true"], "target": [0.92, 0.08], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: over the last hour, immediately after go-live. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aeff9321fa6647f9_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: over the last hour, under an active deadline. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_51e5daf9cf251ae9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.51, 0.46, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: in production only, following a recent audit. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1b92df4264a99dcf_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.11, 0.81, 0.08], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, as part of a compliance sweep. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_268d94dd53f57fe3_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.13, 0.32, 0.02, 0.53], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: across all regions, following a recent audit. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_76320323facabee7_n", "kind": "noul", "options": ["false", "true"], "target": [0.56, 0.44], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: across all regions, during the system migration. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2359a7003883c3ea_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.1, 0.77, 0.12, 0.0], "state": "The log shipper matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: across all regions, following a recent audit. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8d7074f1ceb7e28a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.3, 0.64, 0.05], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_231bc63070bccc8b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.41, 0.58, 0.0], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: in production only, shortly after a software update. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fe827752ddaf5a89_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.34, 0.64, 0.01], "state": "The log shipper reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: over the last hour, immediately after go-live. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5510412336f7641d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.47, 0.46, 0.02], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, as part of a compliance sweep. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_639ff2a14f558dcf_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.95, 0.03, 0.02, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: over the last hour, mid-incident. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bb469e4d9692e553_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.71, 0.25, 0.04, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: during the batch window, during the holiday freeze. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_23d0d911e1afcbc5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.18, 0.78, 0.04], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: during the batch window, under an active deadline. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_349b2dd10020ca1c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.48, 0.5, 0.01, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: in production only, with a new vendor onboarded. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ff502dd9e03f8734_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.09, 0.71, 0.2, 0.0, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: over the last hour, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c97be4dbb893c35a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.67, 0.29, 0.04, 0.0], "state": "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 an external partner integration. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_704b27b53243450b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.92, 0.0, 0.0, 0.08], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during a scheduled maintenance window. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a13ebcb97ef90039_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.24, 0.65, 0.07, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: in production only, during the morning shift. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_41824fec2c70eead_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.54, 0.4, 0.06, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: during the batch window, during normal operations. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_89f30119524ce2dd_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.55, 0.42, 0.0, 0.03], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: in production only, shortly after a software update. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_56f6fe7f6e74332a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.18, 0.31, 0.05, 0.46], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: in production only, during the quarterly review. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ade8caae7b6af3b6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.4, 0.58, 0.01], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: across all regions, mid-incident. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_efc678416d230d59_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.08, 0.52, 0.01, 0.39], "state": "The metrics pipeline shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: in production only, immediately after go-live. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_400a08a44495bcf1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.88, 0.0, 0.09, 0.03], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, mid-incident. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_011a3de7240e2672_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.99, 0.0, 0.0, 0.01], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, as part of a compliance sweep. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_42f0c521fe1af430_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.03, 0.48, 0.47, 0.02], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: over the last hour, during the holiday freeze. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ceb084f2230cd528_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.26, 0.41, 0.32, 0.01, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: during the batch window, as part of a compliance sweep. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_075ac3175d7d18bb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.07, 0.53, 0.33, 0.02], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, as part of a compliance sweep. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_47e144991d782291_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.33, 0.67, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, while legacy systems are still active. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b34c139b172551c0_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.0, 0.01, 0.96, 0.03], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: during the batch window, during the quarterly review. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0a638fbb87921849_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.71, 0.23, 0.05, 0.01], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: over the last hour, during the holiday freeze. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_17776cc8ed98e594_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.04, 0.66, 0.3, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: across all regions, while on-call rotation changed. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6f0eb02cbf85fb98_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.58, 0.28, 0.13, 0.01], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: in production only, under an active deadline. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6749a06461a7b369_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.05, 0.66, 0.29, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: across all regions, while on-call rotation changed. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0f169180279b0e05_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.64, 0.35, 0.01, 0.0], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: in production only, during an external partner integration. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c3a2ada5d16a2084_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0404, 0.404, 0.5354, 0.0202, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: over the last hour, during the morning shift. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1bde45a30bbfa4db_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: in production only, shortly after a software update. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dbf66c332f74855c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.17, 0.72, 0.1, 0.01, 0.0], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: in production only, at the end of the fiscal period. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1eec0c816a283727_n", "kind": "noul", "options": ["false", "true"], "target": [0.4, 0.6], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: in production only, as part of a compliance sweep. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_04e8f5cd7285c3f5_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.12, 0.05, 0.19, 0.64], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: over the last hour, as part of a compliance sweep. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4a05de57be0e607f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.06, 0.61, 0.32, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: over the last hour, following a recent audit. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6121fed1bd4f7b28_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: over the last hour, during normal operations. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dc6a2ddbfcdfd694_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: over the last hour, under an active deadline. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7445d6c551f5ebd5_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.66, 0.12, 0.02, 0.2], "state": "The log shipper shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: during the batch window, during peak load. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_da464cff8aa41c4a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.61, 0.38, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: across all regions, with a new vendor onboarded. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b24a498fc67ae71d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.89, 0.09, 0.02, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: over the last hour, during the system migration. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_01cb87f57400e18e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.94, 0.05, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: over the last hour, while legacy systems are still active. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5e2d1d3c5adeb520_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c7beaa610ae1942c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.74, 0.21, 0.0], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: in production only, during a scheduled maintenance window. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_35f4912499cd4b94_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.15, 0.8, 0.05], "state": "The log shipper reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: in production only, at the end of the fiscal period. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3095aa37879e8a08_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.3, 0.68, 0.02], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: across all regions, during the quarterly review. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d21329268b5c61fe_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.9, 0.0, 0.06, 0.04], "state": "The log shipper correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during the quarterly review. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a0b95efe4d304143_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.02, 0.89, 0.08], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: over the last hour, under an active deadline. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e48a5c99ac87a31b_n", "kind": "noul", "options": ["false", "true"], "target": [0.6, 0.4], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: across all regions, during normal operations. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d99970ae3f1a446d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.8, 0.17, 0.02, 0.01], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during peak load. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_308c4b2d2048ba61_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.7, 0.29, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: over the last hour, at the end of the fiscal period. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ec3b535540087519_n", "kind": "noul", "options": ["false", "true"], "target": [0.17, 0.83], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: in production only, mid-incident. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_35ae5057b3ed2f56_n", "kind": "noul", "options": ["false", "true"], "target": [0.38, 0.62], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: in production only, with a new vendor onboarded. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_431a66b17ed96ca5_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The log shipper reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: during the batch window, during the system migration. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_155a9a01e72a50b9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.86, 0.01, 0.0, 0.13], "state": "The log shipper matches last Tuesday's incident signature; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during a scheduled maintenance window. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2f335d0fc964897d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.74, 0.06, 0.0, 0.2], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, following a recent audit. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aab0393fe585104a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.23, 0.76, 0.01], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, under reduced staffing. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8b67093c7f6d8e83_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.12, 0.82, 0.06], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, following a recent audit. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_473d1ec7670fe3a5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.2, 0.78, 0.02], "state": "The metrics pipeline lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: in production only, under reduced staffing. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6604a3f32186c6ea_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: in production only, while on-call rotation changed. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4964069808d6059f_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: over the last hour, during the holiday freeze. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9dd6b6cb29b08253_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.75, 0.24, 0.0], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: across all regions, under reduced staffing. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eb24bc1e23923820_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.18, 0.72, 0.06, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during the morning shift. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6662573648e8c782_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, with a new vendor onboarded. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_434119ea1bca8f26_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: during the batch window, at the end of the fiscal period. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a8e0822392107bec_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.1, 0.51, 0.37, 0.02, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: in production only, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c6273579a445e029_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.33, 0.66, 0.01], "state": "The log shipper flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: over the last hour, during an external partner integration. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2af8710379a6f6bb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.08, 0.4, 0.49, 0.03, 0.0], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: across all regions, while legacy systems are still active. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6d6ab3436bdebeef_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.37, 0.59, 0.03, 0.01], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: in production only, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e4614c35d8ee9572_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally flags a step-function change in error slope. Context: during the batch window, immediately after go-live. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_88c3e6db5bc225ed_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.01, 0.05, 0.45, 0.47, 0.01], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: in production only, as part of a compliance sweep. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_51d4266f49a57570_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "The metrics pipeline flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: over the last hour, during peak load. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5a3646aa4cab7454_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.11, 0.43, 0.01, 0.45], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: in production only, under an active deadline. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_28c32a9a0fe43d99_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.19, 0.69, 0.12, 0.0, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: in production only, while on-call rotation changed. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9ea9f6459fd775af_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.28, 0.31, 0.03, 0.38], "state": "Service catalog-sync shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during a scheduled maintenance window. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d9e74ceba11e7d0c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.0, 0.3, 0.69], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: across all regions, during the quarterly review. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cfea0e44ac3dbae2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.04, 0.81, 0.15], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: in production only, under an active deadline. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_74161e49d0e4cf6c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.22, 0.13, 0.03, 0.62], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during the quarterly review. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_479bc5901d292b5f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.58, 0.34, 0.07, 0.01], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: in production only, during a scheduled maintenance window. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7c0f1199481a3cb2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.15, 0.56, 0.29, 0.0, 0.0], "state": "Service catalog-sync flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: during the batch window, with staffing at reduced levels. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e0157b39cf4a9495_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.6, 0.37, 0.01], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: across all regions, under reduced staffing. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_32ffea3054fc1fd2_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: during the batch window, under an active deadline. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a5a294bc959609ab_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, at the end of the fiscal period. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9e51802b54417469_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.12, 0.04, 0.64, 0.2], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: during the batch window, during an external partner integration. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e6617da963f1d26f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.65, 0.3, 0.04, 0.01], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during normal operations. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c0094f1664e73fe5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.77, 0.22, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: during the batch window, at the end of the fiscal period. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b02f6c792641cd74_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "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, during an external partner integration. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_607bc689a68c3686_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.12, 0.03, 0.31, 0.54], "state": "The log shipper returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: across all regions, with a new vendor onboarded. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c8482fa532daa8e0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.19, 0.62, 0.18, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, following a recent audit. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_30a9f599e64f3200_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.03, 0.17, 0.23, 0.48, 0.09, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: in production only, during a scheduled maintenance window. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6c01fb2f938e811a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.34, 0.38, 0.26, 0.01], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: across all regions, while legacy systems are still active. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_98ffdff94b2f3ace_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.07, 0.01, 0.71, 0.21], "state": "The metrics pipeline correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: across all regions, under reduced staffing. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c671edaa285d4eeb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.4, 0.35, 0.23, 0.01], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, while on-call rotation changed. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c42f2a3b387b7f49_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.11, 0.03, 0.35, 0.51], "state": "The log shipper reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: in production only, while legacy systems are still active. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d37ec17544ee6504_n", "kind": "noul", "options": ["false", "true"], "target": [0.71, 0.29], "state": "The log shipper shows a slow leak in heap growth; 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 automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_45e77208345803b0_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.54, 0.39, 0.06, 0.01], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during the morning shift. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_61f22e5ef6632689_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, while legacy systems are still active. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7838ddb82d0abc63_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.18, 0.69, 0.13, 0.0, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: in production only, during an external partner integration. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1d23983c7359b5f1_n", "kind": "noul", "options": ["false", "true"], "target": [0.4, 0.6], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c4dbccb422e5bcea_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.09, 0.86, 0.05], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally flags a step-function change in error slope. Context: during the batch window, during the holiday freeze. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8026e20213a82627_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: over the last hour, while on-call rotation changed. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0cc1c97c951a8113_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.42, 0.55, 0.01], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: across all regions, as part of a compliance sweep. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8151614ed408e0bc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.27, 0.54, 0.19, 0.0, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: over the last hour, during the system migration. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_536b0012375d1ea1_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, immediately after go-live. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5a074d11ac3e5840_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.65, 0.28, 0.06, 0.01], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: across all regions, during the system migration. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca0f5d777372d7aa_n", "kind": "noul", "options": ["false", "true"], "target": [0.56, 0.44], "state": "The log shipper returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: across all regions, mid-incident. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_46c37dc041e128d7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.14, 0.75, 0.11, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, following a recent audit. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b1032c0bf9c49f39_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.25, 0.74, 0.01], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: across all regions, during the system migration. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6a5029580a679384_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.33, 0.25, 0.03, 0.39], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fde66e0fe94ff3bd_n", "kind": "noul", "options": ["false", "true"], "target": [0.58, 0.42], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: during the batch window, shortly after a software update. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c380b0d2befb5070_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.76, 0.22, 0.01, 0.01], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: across all regions, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e6a70f212b29c37f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.02, 0.06, 0.71, 0.2, 0.0], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: during the batch window, as part of a compliance sweep. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_842eb6c144fc5785_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.17, 0.59, 0.24, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: during the batch window, during the system migration. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b8a122aa42e09f1c_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "The metrics pipeline shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: over the last hour, under an active deadline. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3acf5baf3e23037b_n", "kind": "noul", "options": ["false", "true"], "target": [0.65, 0.35], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: in production only, while on-call rotation changed. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b62d224e1129a318_n", "kind": "noul", "options": ["false", "true"], "target": [0.22, 0.78], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, while legacy systems are still active. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_632090753f0a2f31_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.21, 0.41, 0.04, 0.34], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: over the last hour, during the holiday freeze. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b9fa97166bf14d04_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: in production only, with staffing at reduced levels. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cbba21f642bcedaa_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.5, 0.47, 0.02], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: in production only, during a scheduled maintenance window. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_03f55cf13100fdd0_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: in production only, following a recent audit. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c4188a78fa997c1f_n", "kind": "noul", "options": ["false", "true"], "target": [0.44, 0.56], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: across all regions, under an active deadline. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_24317890bc911412_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.65, 0.32, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: during the batch window, following a recent audit. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_72d23f145204e5de_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.38, 0.24, 0.31, 0.07], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: over the last hour, under an active deadline. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5a00a871f09e89bb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.67, 0.31, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: in production only, during peak load. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_37eef3a144d584cf_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.96, 0.03, 0.0, 0.01], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during the quarterly review. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4f94f80db7a69a70_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during an external partner integration. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7cdeca455a794b68_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.24, 0.7, 0.01, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: over the last hour, with a new vendor onboarded. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b1621a960a29320e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.21, 0.58, 0.17, 0.0], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: in production only, under an active deadline. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7ee79485d64c1165_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: over the last hour, shortly after a software update. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_47fc9d3c64c7766a_n", "kind": "noul", "options": ["false", "true"], "target": [0.9, 0.1], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: in production only, during a scheduled maintenance window. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4f52de9c02c184ee_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.71, 0.24, 0.04, 0.01], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: in production only, under reduced staffing. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9d52780aed8ad930_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.23, 0.75, 0.02], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: in production only, during the system migration. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cb186b02bc6c26c6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.33, 0.5, 0.11, 0.01], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, immediately after go-live. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_60979879de07aeae_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.3, 0.02, 0.06, 0.62], "state": "Dashboard checkout-funnel 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 operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7132abf43f1ec5eb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.56, 0.44, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: over the last hour, during an external partner integration. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c60c33f721de1244_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.07, 0.56, 0.3, 0.07, 0.0, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, with a new vendor onboarded. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_04812f79194213ba_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.61, 0.0, 0.36, 0.03], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: across all regions, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_35cd9c5560429633_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: over the last hour, shortly after a software update. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_82981a27e1eae86c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.07, 0.64, 0.23, 0.06, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: during the batch window, under an active deadline. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7ec32feaa2ad91d2_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: across all regions, with a new vendor onboarded. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a2498889afa24083_n", "kind": "noul", "options": ["false", "true"], "target": [0.48, 0.52], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: in production only, immediately after go-live. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cce14a3df4f4873c_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: during the batch window, with staffing at reduced levels. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bd8faeadb33166f2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.14, 0.69, 0.14, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: across all regions, with staffing at reduced levels. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9f171ab6c27b5d16_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.05, 0.75, 0.19, 0.01], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: over the last hour, during the system migration. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_656bb57d498888ff_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "The log shipper correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: in production only, while legacy systems are still active. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_861f6fe81bd81dce_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.16, 0.55, 0.29, 0.0], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: across all regions, during a scheduled maintenance window. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_823ace2b5495f647_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.59, 0.4, 0.01, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: during the batch window, while on-call rotation changed. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d61e8130995f9914_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.94, 0.01, 0.02, 0.03], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: during the batch window, with staffing at reduced levels. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4d291bb2bb8bde41_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.74, 0.25, 0.0], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: over the last hour, while legacy systems are still active. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9da1b28dbf4c61ab_n", "kind": "noul", "options": ["false", "true"], "target": [0.67, 0.33], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the holiday freeze. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8644b952d3ebaac0_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: during the batch window, while on-call rotation changed. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_74f9f38627addd2c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.03, 0.57, 0.39], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: in production only, while on-call rotation changed. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9ca9b9c8c0e518ac_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: across all regions, shortly after a software update. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6e3eafa4f18dae14_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.23, 0.36, 0.05, 0.36], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: in production only, during the morning shift. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_53532c3c65dabec7_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.9, 0.1, 0.0, 0.0], "state": "The log shipper reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: across all regions, at the end of the fiscal period. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ec8f59d40bbe9c49_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.09, 0.12, 0.03, 0.76], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: in production only, immediately after go-live. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7edf279828e4417e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.06, 0.73, 0.2, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: in production only, with a new vendor onboarded. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e455ff57eb833cdb_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: during the batch window, under an active deadline. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_88ea141de90fa34b_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, immediately after go-live. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_979cb84cc6f5d341_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.19, 0.0, 0.43, 0.38], "state": "The log shipper correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: across all regions, during peak load. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_43431f65a39921a4_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.02, 0.19, 0.79, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, while on-call rotation changed. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cd5d347ba0050b66_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.28, 0.04, 0.05, 0.63], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the morning shift. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_85c813a84cc6697f_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: across all regions, during the quarterly review. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a8dba6d576872de7_n", "kind": "noul", "options": ["false", "true"], "target": [0.37, 0.63], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during the holiday freeze. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b0a7ab85acf14d98_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.05, 0.66, 0.29, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, while on-call rotation changed. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6dff0b779ba4a8cd_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.18, 0.02, 0.09, 0.71], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: across all regions, under reduced staffing. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_81950e3214baac62_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.66, 0.01, 0.14, 0.19], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, under an active deadline. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ad61efb97e1f4ef9_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.66, 0.33, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: across all regions, following a recent audit. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_01962ea974c463f1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.7, 0.28, 0.01, 0.01], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: during the batch window, with a new vendor onboarded. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_708e7182c7027705_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.0202, 0.8182, 0.1616], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: during the batch window, mid-incident. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7bec2da789ef6e87_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.32, 0.53, 0.15, 0.0, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: over the last hour, during the holiday freeze. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_08ef69d24f5ac611_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.49, 0.51, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: over the last hour, mid-incident. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e78804c7e8aa71c1_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The log shipper shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: during the batch window, while legacy systems are still active. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_657782ff04a1376c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0101, 0.0808, 0.8081, 0.101, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: in production only, shortly after a software update. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8495245eb1c1e365_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.29, 0.69, 0.02], "state": "The metrics pipeline correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during the holiday freeze. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d467ac77213602b6_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.17, 0.2, 0.58], "state": "The metrics pipeline flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: across all regions, as part of a compliance sweep. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8cd4f0e7d6a49602_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.89, 0.07, 0.0, 0.04], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: during the batch window, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cc5ed267b9aaa650_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.0, 0.41, 0.57], "state": "The log shipper correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: in production only, under reduced staffing. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cce14a3df4f4873c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.42, 0.3, 0.01, 0.27], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: during the batch window, with staffing at reduced levels. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_85f813f277b23c44_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.78, 0.0, 0.01, 0.21], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, following a recent audit. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_07868d5791c82d2d_n", "kind": "noul", "options": ["false", "true"], "target": [0.46, 0.54], "state": "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.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2f6747ae1b83b3ed_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.38, 0.55, 0.05, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: during the batch window, mid-incident. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5eb498820be4cc14_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.75, 0.2, 0.05, 0.0], "state": "The log shipper flags a step-function change in error slope; 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 on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1cd6e2261f731d88_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.03, 0.55, 0.35, 0.07, 0.0, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, with a new vendor onboarded. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eefbb4f87f80a9d4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.14, 0.63, 0.17, 0.0], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: in production only, during a scheduled maintenance window. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e406804a28d03521_n", "kind": "noul", "options": ["false", "true"], "target": [0.43, 0.57], "state": "The metrics pipeline lost 4 minutes of trace data; 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 automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f2d8ef78e21ccef8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.63, 0.37, 0.0], "state": "The metrics pipeline shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: across all regions, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_01360f5c6c52459a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.09, 0.64, 0.26, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: across all regions, during the holiday freeze. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_18b7126b266b8b88_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The log shipper shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: in production only, during normal operations. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c186c37c55649496_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, following a recent audit. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f1d87591c1b90962_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.47, 0.49, 0.04, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: across all regions, during the system migration. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7176ab8fda0c5be8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.89, 0.1, 0.0], "state": "The metrics pipeline shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: over the last hour, during normal operations. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0076d0b941179d9f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.06, 0.01, 0.07, 0.86], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: over the last hour, during the system migration. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9a70db0dd23672d5_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.93, 0.03, 0.01, 0.03], "state": "The log shipper shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, shortly after a software update. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c423434da9e809a6_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.77, 0.15, 0.08, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: over the last hour, during an external partner integration. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cd27e84a6dec0bde_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.75, 0.2, 0.0, 0.05], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, following a recent audit. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c5e4db7101cc3109_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.89, 0.09, 0.01, 0.01], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca298c74eb4f719a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.93, 0.06, 0.01, 0.0], "state": "The log shipper reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: over the last hour, during the morning shift. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fbe55c81d3079ca8_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: over the last hour, at the end of the fiscal period. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9cf9e625a0af11a4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.9, 0.08, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: during the batch window, during the morning shift. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_28f6438fe60d04f9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.11, 0.8, 0.08, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: across all regions, under reduced staffing. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1fee3cd78cf64772_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.73, 0.25, 0.01, 0.01], "state": "The metrics pipeline 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 on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9f4ef17bace861c4_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: over the last hour, with a new vendor onboarded. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_16e92ac674d39d0b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.09, 0.76, 0.15, 0.0, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: across all regions, following a recent audit. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_54c4ffe2c06b221f_n", "kind": "noul", "options": ["false", "true"], "target": [0.65, 0.35], "state": "The log shipper matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: in production only, during normal operations. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_70d49e49e5f42c45_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.2, 0.51, 0.29, 0.0, 0.0], "state": "The metrics pipeline shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: over the last hour, with staffing at reduced levels. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f2aad7b1c419bfe4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.46, 0.52, 0.01], "state": "The log shipper flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during the holiday freeze. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_adfc05087ba60020_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.57, 0.36, 0.06, 0.01], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: across all regions, as part of a compliance sweep. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0c5b0e5fa71ece38_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.35, 0.58, 0.05, 0.02], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: in production only, during normal operations. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cb19060120bffb30_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.1414, 0.8182, 0.0404], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: in production only, with staffing at reduced levels. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7f42867b99d812f1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.87, 0.01, 0.0, 0.12], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: across all regions, under an active deadline. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a8e2192939c31c07_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.03, 0.5, 0.45, 0.01], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: over the last hour, as part of a compliance sweep. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_74b1284e36c182d3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.21, 0.76, 0.03], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, immediately after go-live. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_59d4af37f278b8ba_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "The log shipper lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: over the last hour, at the end of the fiscal period. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5b2deedde26fa3f5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.18, 0.76, 0.04, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: in production only, with a new vendor onboarded. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f566513f84940757_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: over the last hour, following a recent audit. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f9ac22395ae0610b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.3, 0.67, 0.02], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during a scheduled maintenance window. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2d1ad33be094d480_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.87, 0.01, 0.01, 0.11], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_74898790f362a8e2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.52, 0.46], "state": "The log shipper reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: across all regions, during an external partner integration. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fde2bcf5f2bf3e7d_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: in production only, at the end of the fiscal period. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_570c66f20c5b16c3_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.85, 0.07, 0.02, 0.06], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7bc7b101dcdbe3af_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.88, 0.1, 0.02, 0.0], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during peak load. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7f682765c191dd2e_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "The log shipper matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: over the last hour, during the system migration. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c4a9a26108493ba7_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.33, 0.25, 0.02, 0.4], "state": "The metrics pipeline flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during normal operations. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_12d6b12542b29960_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during a scheduled maintenance window. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e29c8667c4bd6feb_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.64, 0.02, 0.03, 0.31], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: across all regions, at the end of the fiscal period. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_704f4a5275720b2f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.04, 0.88, 0.08], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: in production only, while legacy systems are still active. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a755e8a7eee0a84b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.24, 0.57, 0.17, 0.02], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during normal operations. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0d07ac46d6dc45e9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.1, 0.59, 0.29, 0.01], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4352b20a148e8169_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Service catalog-sync shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: during the batch window, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c87654c53254548b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.1, 0.51, 0.39, 0.0, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: during the batch window, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aec08ef1761f1453_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.18, 0.8, 0.02], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: in production only, under reduced staffing. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_49a4eafbc88ad433_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.09, 0.62, 0.25, 0.0], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b990aeaf95318e5c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.58, 0.4, 0.0], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: in production only, during the morning shift. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aa69aab3b8d0a7fd_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: during the batch window, mid-incident. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e23afe5fa28a8ed8_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.03, 0.43, 0.53], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: over the last hour, during the quarterly review. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f907d8363d30bfd7_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.54, 0.07, 0.18, 0.21], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: during the batch window, while on-call rotation changed. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e5deae37445dc8b7_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the holiday freeze. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_92394c7634ed84b7_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: during the batch window, under reduced staffing. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2b1ca094d49a6fda_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.79, 0.16, 0.04, 0.01], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during peak load. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2785e65a9c0c0f37_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: in production only, during a scheduled maintenance window. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5264c43db0d2c701_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: in production only, as part of a compliance sweep. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f52cf80f03b2f473_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.22, 0.77, 0.01], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: over the last hour, while on-call rotation changed. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3c2c67e4ba2eed32_n", "kind": "noul", "options": ["false", "true"], "target": [0.46, 0.54], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: over the last hour, as part of a compliance sweep. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bf38b3e21bbd4c13_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.73, 0.26, 0.0, 0.01], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, shortly after a software update. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_daf4a129c3d845c3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.05, 0.89, 0.06], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: across all regions, during an external partner integration. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca5e4a3ca7da9bf7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.07, 0.38, 0.42, 0.12, 0.01], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during the morning shift. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca8a4a5d872e469d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.59, 0.4, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the morning shift. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ec8f59d40bbe9c49_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: in production only, immediately after go-live. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3692e15ea4220a74_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.17, 0.8, 0.03], "state": "The metrics pipeline correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: across all regions, with staffing at reduced levels. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b52866d0c098e6d9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.2, 0.12, 0.01, 0.67], "state": "The log shipper flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: over the last hour, under an active deadline. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0d691a6b849ceb78_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.92, 0.0, 0.0, 0.08], "state": "The log shipper lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during the morning shift. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e1fb4e0d7b6d7b40_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.75, 0.19, 0.04, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, at the end of the fiscal period. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f217d4867c010acc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.56, 0.42, 0.0], "state": "The metrics pipeline correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: across all regions, while legacy systems are still active. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca5e4a3ca7da9bf7_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during the morning shift. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9eb56c666e84894c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.55, 0.44, 0.0], "state": "Service catalog-sync flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: during the batch window, under reduced staffing. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b9993a106179523c_n", "kind": "noul", "options": ["false", "true"], "target": [0.44, 0.56], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: across all regions, during normal operations. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f196ae510768623a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.78, 0.21, 0.0], "state": "The metrics pipeline shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: in production only, following a recent audit. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_808ee7ea36c93ce1_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: across all regions, following a recent audit. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8026e20213a82627_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.07, 0.76, 0.04, 0.13], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: over the last hour, while on-call rotation changed. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c723ab66964f0420_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: in production only, mid-incident. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c85324fa69061251_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.11, 0.84, 0.05], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: across all regions, while on-call rotation changed. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_988e171846ddba47_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "The log shipper shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: across all regions, during peak load. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_36232c7517c2d7a7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.38, 0.6, 0.01], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: over the last hour, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8a05b3d630b050ac_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.76, 0.23, 0.0], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: across all regions, while on-call rotation changed. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_01bc2814a90e6c0d_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: over the last hour, during the holiday freeze. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_059431d566345957_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.15, 0.32, 0.43, 0.08, 0.01], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9aa69dcc2f37800a_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, following a recent audit. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_627fc1d0bb79ef39_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.42, 0.51, 0.03, 0.0], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: in production only, with staffing at reduced levels. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f0510f5114fb2d5e_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: across all regions, with a new vendor onboarded. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f230eda2e67546ff_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.66, 0.27, 0.06, 0.01], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during the holiday freeze. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_922f4426e125350c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.37, 0.61, 0.01], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: across all regions, at the end of the fiscal period. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a4bb529c22bf8a2e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.86, 0.12, 0.01, 0.01], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: across all regions, during the morning shift. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2190c61ba35fcca9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.76, 0.0, 0.09, 0.15], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: during the batch window, during peak load. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_44a353ca23a860f5_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.53, 0.14, 0.03, 0.3], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: during the batch window, during the quarterly review. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_14bb8657208eea7e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.23, 0.47, 0.28, 0.02], "state": "The log shipper correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: in production only, during a scheduled maintenance window. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f595ca5db9d813c1_n", "kind": "noul", "options": ["false", "true"], "target": [0.23, 0.77], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during the holiday freeze. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cba6a0d1b0ab4c06_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "Dashboard checkout-funnel 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 automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fec0994ead8e5df1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.27, 0.0, 0.66, 0.07], "state": "Node pgsql-14 correlates with the vendor status page incident; 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 review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e2a3a1a75445e8b9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.03, 0.46, 0.49, 0.01], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: over the last hour, as part of a compliance sweep. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_61e5f4fbc82a7f1f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.73, 0.26, 0.0], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: over the last hour, with staffing at reduced levels. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9e85c3b0ccf82813_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, under reduced staffing. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5598765d8af5f7f5_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.37, 0.01, 0.02, 0.6], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the morning shift. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6ece76fb8913b976_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: across all regions, during the quarterly review. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4819207d764ba509_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during normal operations. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e6f0be0ee26cd291_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.66, 0.32, 0.02, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: during the batch window, at the end of the fiscal period. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4542a142423301c6_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.58, 0.29, 0.13, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: over the last hour, following a recent audit. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dbef714b7c0ecc06_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.04, 0.52, 0.41, 0.01], "state": "Service catalog-sync correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: during the batch window, as part of a compliance sweep. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9a4c6c8f98b76f55_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.06, 0.5, 0.41, 0.03], "state": "Node pgsql-14 flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: across all regions, during an external partner integration. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a10e77c283ac762f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.21, 0.55, 0.17, 0.07], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: during the batch window, during the system migration. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_996cbf04f5330895_n", "kind": "noul", "options": ["false", "true"], "target": [0.21, 0.79], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: during the batch window, while on-call rotation changed. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4d382faaa3ba5900_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.18, 0.79, 0.03], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during normal operations. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_37eef3a144d584cf_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.32, 0.67, 0.01], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during the quarterly review. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9dc9baa71baebcb3_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: over the last hour, while on-call rotation changed. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bb0fbbfbdb697cb8_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: across all regions, while on-call rotation changed. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cbba21f642bcedaa_n", "kind": "noul", "options": ["false", "true"], "target": [0.48, 0.52], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: in production only, during a scheduled maintenance window. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_47c916f501463dd4_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: over the last hour, while legacy systems are still active. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_008849a1db9ef8be_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: in production only, with a new vendor onboarded. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_52479c30f023af04_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.54, 0.45, 0.0], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: over the last hour, at the end of the fiscal period. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_77a43e0b963196a8_n", "kind": "noul", "options": ["false", "true"], "target": [0.62, 0.38], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: in production only, during normal operations. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0707d6980385b9ab_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.54, 0.32, 0.14, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: during the batch window, while legacy systems are still active. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1bf61105ff21c8f7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.54, 0.42, 0.01], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during a scheduled maintenance window. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ce62293b097c6114_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.46, 0.53, 0.01], "state": "Service catalog-sync flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: over the last hour, during normal operations. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0707d6980385b9ab_n", "kind": "noul", "options": ["false", "true"], "target": [0.67, 0.33], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: during the batch window, while legacy systems are still active. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_00dfb172536b037c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.31, 0.01, 0.05, 0.63], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: during the batch window, at the end of the fiscal period. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_82aad936141ec329_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "The log shipper returned to baseline after 11 minutes; additionally matches last Tuesday's incident signature. Context: during the batch window, during the holiday freeze. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_216953f6972b360a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.76, 0.23, 0.0], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: over the last hour, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_926277f27352de01_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.03, 0.55, 0.41, 0.01], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: in production only, during normal operations. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_88a74779fae07bf6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.27, 0.7, 0.02], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: during the batch window, following a recent audit. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca22e8ede04e9aa4_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.18, 0.75, 0.06, 0.01], "state": "The log shipper correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: during the batch window, at the end of the fiscal period. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_97a558b660ebe2c9_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: across all regions, during an external partner integration. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a0b04ca34efa6bd0_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.69, 0.29, 0.01], "state": "The log shipper returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: over the last hour, during the morning shift. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_06b26597ccd037f7_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.04, 0.16, 0.74, 0.06], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: over the last hour, mid-incident. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cb5f8301b187a435_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.15, 0.11, 0.55, 0.19], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: in production only, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_205e052ad6391b62_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.79, 0.21, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: across all regions, while on-call rotation changed. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_308c4b2d2048ba61_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.34, 0.31, 0.01, 0.34], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: over the last hour, at the end of the fiscal period. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7229b2df6cfa304a_n", "kind": "noul", "options": ["false", "true"], "target": [0.7, 0.3], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during the system migration. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_35ae5057b3ed2f56_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.13, 0.57, 0.29, 0.01, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: in production only, with a new vendor onboarded. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e7c89786e3fe5f4d_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: in production only, immediately after go-live. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_add1200b69a1f53f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.44, 0.49, 0.04, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: across all regions, mid-incident. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_61c0a617ebc96d83_n", "kind": "noul", "options": ["false", "true"], "target": [0.58, 0.42], "state": "The metrics pipeline flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: across all regions, during a scheduled maintenance window. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a5813840f23e3054_n", "kind": "noul", "options": ["false", "true"], "target": [0.62, 0.38], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: in production only, shortly after a software update. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fbedb222726e3c66_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.26, 0.63, 0.02, 0.09], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: in production only, during the morning shift. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9da1b28dbf4c61ab_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.62, 0.31, 0.06, 0.01], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the holiday freeze. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_62b43fe04867b058_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: in production only, during an external partner integration. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3d2cc8f4a2d083b8_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.17, 0.77, 0.01, 0.05], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: across all regions, under an active deadline. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d7be60fd2231db9a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.15, 0.84, 0.01], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: across all regions, with a new vendor onboarded. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aad0eb13de87d49a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.52, 0.31, 0.16, 0.01], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2b36062772979607_n", "kind": "noul", "options": ["false", "true"], "target": [0.71, 0.29], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, following a recent audit. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dbbac309ee66ee9a_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, as part of a compliance sweep. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_67e0e30fbee38639_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.3, 0.69, 0.01], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: over the last hour, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f28d8c77725efe8b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.79, 0.16, 0.04, 0.01], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: over the last hour, under an active deadline. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_20f9e4f9fbd9818c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.18, 0.8, 0.02], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: in production only, while legacy systems are still active. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3ed77c902cb513e4_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.63, 0.32, 0.05, 0.0], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: in production only, while on-call rotation changed. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_456fb1d34f094150_n", "kind": "noul", "options": ["false", "true"], "target": [0.9, 0.1], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during normal operations. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a77c072b668561ff_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: across all regions, during a scheduled maintenance window. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c7e1db94774d2b39_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: during the batch window, at the end of the fiscal period. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0c036f2017501725_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.77, 0.18, 0.01, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: in production only, during normal operations. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_84b64af02524bf49_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: over the last hour, at the end of the fiscal period. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d28825504e2c6ded_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.11, 0.5, 0.31, 0.08, 0.0], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, mid-incident. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_583a9d9300dbcfca_n", "kind": "noul", "options": ["false", "true"], "target": [0.53, 0.47], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: across all regions, during the quarterly review. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_85f813f277b23c44_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, following a recent audit. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4ba14d8db16d29ae_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.27, 0.72, 0.01], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: across all regions, shortly after a software update. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4a47156b24bdf414_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.24, 0.03, 0.02, 0.71], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: in production only, under an active deadline. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e709f3d55bcce818_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: over the last hour, as part of a compliance sweep. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ee70faaa7c266a11_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.63, 0.28, 0.05, 0.0], "state": "The log shipper reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during peak load. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c94222e015712dde_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: during the batch window, during normal operations. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d80df85652d31fc7_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.62, 0.24, 0.06, 0.08], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: over the last hour, as part of a compliance sweep. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d5f5748cc374dc99_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.32, 0.49, 0.12, 0.07, 0.0, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: during the batch window, following a recent audit. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_302d2da1911ae2df_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.21, 0.7, 0.09, 0.0], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: in production only, during the quarterly review. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_89673f54ca543ba6_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "Service catalog-sync lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: across all regions, during peak load. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_290699e716823253_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.1717, 0.8081, 0.0202], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: in production only, shortly after a software update. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_407f524abe95fe94_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.81, 0.01, 0.17], "state": "The log shipper shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: across all regions, shortly after a software update. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2936ceb17d733c3c_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: in production only, with staffing at reduced levels. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8f169565ba6b09a5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.18, 0.8, 0.02], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, at the end of the fiscal period. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ad575291779696e4_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during the morning shift. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0f5a1fab444e6257_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: across all regions, while on-call rotation changed. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b1d2d3b4c9c30330_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.45, 0.0, 0.22, 0.33], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during the morning shift. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_609dc6d4704804d2_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9618e6991497442b_n", "kind": "noul", "options": ["false", "true"], "target": [0.23, 0.77], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during an external partner integration. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_98df6761f6cafb95_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.28, 0.7], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: in production only, during the holiday freeze. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1d28f4f0f7c7f819_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: across all regions, while on-call rotation changed. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_672217b2dac8da3f_n", "kind": "noul", "options": ["false", "true"], "target": [0.22, 0.78], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, while legacy systems are still active. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ab601c1ac485840d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.45, 0.4, 0.14, 0.01], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the holiday freeze. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2ac2b5ab057cac08_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.04, 0.8, 0.16], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: across all regions, during peak load. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_242c8bdf74d35e85_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: over the last hour, under an active deadline. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_92c19f9a4b528733_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.07, 0.62, 0.3, 0.0], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: in production only, during the morning shift. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_52886e4edc0cb23d_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: across all regions, during normal operations. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_890bb9cb8a63379f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.23, 0.76, 0.01], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during the system migration. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0410c076b8450bc0_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.81, 0.18, 0.01, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, with a new vendor onboarded. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eb6ea5606f235807_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.31, 0.65, 0.03], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: over the last hour, mid-incident. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6cc342b089e81b8f_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "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, during the holiday freeze. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4727001c7d64a364_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.29, 0.71, 0.0], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, with a new vendor onboarded. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4117b7e7a759d4a8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.11, 0.59, 0.28, 0.02, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: across all regions, under reduced staffing. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ef7da40d716fc88e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.24, 0.01, 0.07, 0.68], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: during the batch window, mid-incident. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c74a3d4e65c9743f_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during a scheduled maintenance window. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b4d779a1c56ae22c_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during a scheduled maintenance window. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_104854ae7a68ea0b_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: during the batch window, while legacy systems are still active. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ea760551b7d00e36_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: across all regions, during normal operations. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3bac710ac65352a9_n", "kind": "noul", "options": ["false", "true"], "target": [0.7, 0.3], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: in production only, under reduced staffing. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c4c78b0ad369674b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.28, 0.53, 0.18, 0.0], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cde254bd49761764_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.72, 0.27, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: over the last hour, following a recent audit. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e30155814afc346d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.73, 0.23, 0.03, 0.01], "state": "The log shipper shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, under reduced staffing. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7dab1716961e82a1_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: across all regions, following a recent audit. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3d831cd6f7b6b5d4_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.02, 0.45, 0.51], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: during the batch window, at the end of the fiscal period. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8528a9e45dccf30e_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: during the batch window, during peak load. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b8457396d6c277df_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: in production only, shortly after a software update. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8eb27cc5bd011ff9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.79, 0.07, 0.14], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: in production only, shortly after a software update. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_79206a5fcf142ed7_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.13, 0.0, 0.56, 0.31], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: across all regions, with staffing at reduced levels. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1d9d7ec7d9b7f95e_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "Service catalog-sync shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: during the batch window, at the end of the fiscal period. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_beb05f659f3c2cd6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.56, 0.43, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: across all regions, following a recent audit. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fd9177b268c37a08_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.77, 0.13, 0.09, 0.01], "state": "The log shipper shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during an external partner integration. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7ecac66d833b6fed_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.5, 0.44, 0.01], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_db6d5eb40c692ee6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.63, 0.34, 0.0], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: in production only, while legacy systems are still active. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_45e86a12b377851d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.39, 0.55, 0.06, 0.0, 0.0], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during normal operations. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b55301be242f245c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.54, 0.4, 0.05, 0.01], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: during the batch window, during an external partner integration. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c480c95278615ad0_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: over the last hour, mid-incident. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca4d74b0fce0bbe4_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: during the batch window, while on-call rotation changed. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0054e34ce95304aa_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.75, 0.19, 0.05, 0.01], "state": "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, during the morning shift. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b8a122aa42e09f1c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.78, 0.2, 0.02, 0.0], "state": "The metrics pipeline shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: over the last hour, under an active deadline. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6b9eb51da91f5a45_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: in production only, during the holiday freeze. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e40ea791579aa67e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.47, 0.51, 0.01], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: over the last hour, shortly after a software update. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_033149b8bcd98fc1_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "The log shipper returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during an external partner integration. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_59df05b7ff77a1e8_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.48, 0.36, 0.15, 0.01], "state": "The log shipper reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: in production only, during a scheduled maintenance window. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f38e1f0c0a985f55_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.17, 0.55, 0.27, 0.01], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: over the last hour, at the end of the fiscal period. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_29b325db92776c1b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.0, 0.94, 0.05], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, while on-call rotation changed. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e61ce4baa570a6ae_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.27, 0.7, 0.02], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: in production only, following a recent audit. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_41bc23ba4909fb60_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: across all regions, during normal operations. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_61942adc56474cdf_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.63, 0.35, 0.01, 0.01], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: across all regions, following a recent audit. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5da7a731d5765fd9_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.43, 0.52, 0.03, 0.02], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during peak load. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6e95efe5053620b1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.98, 0.02, 0.0, 0.0], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: over the last hour, under an active deadline. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7f6e48708ae5e353_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.41, 0.57, 0.01], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the morning shift. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e4b2b625eb33c08f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.08, 0.89, 0.02], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: in production only, while legacy systems are still active. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_76a826f3f2704ba8_n", "kind": "noul", "options": ["false", "true"], "target": [0.44, 0.56], "state": "The log shipper lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: during the batch window, under reduced staffing. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_427718e03b89aa72_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.29, 0.7, 0.01], "state": "The log shipper reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: over the last hour, while legacy systems are still active. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5eb6585f11572cda_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: across all regions, during the morning shift. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2e1d1517a60fb1ef_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.07, 0.8, 0.13, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: over the last hour, under an active deadline. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_679eea852bb4c45c_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: during the batch window, during the morning shift. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fde2bcf5f2bf3e7d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.16, 0.72, 0.1, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: in production only, at the end of the fiscal period. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ad728eb195d5ba7d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.36, 0.64, 0.0], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: in production only, with a new vendor onboarded. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_33f650286cf00f43_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.21, 0.75, 0.03, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: during the batch window, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1cb8e128731420f4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.62, 0.37, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, with staffing at reduced levels. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a13ebcb97ef90039_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.19, 0.73, 0.08, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: in production only, during the morning shift. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4d8e06e7e260f8c0_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.05, 0.28, 0.62, 0.05], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: over the last hour, during peak load. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_52e912d5342d4c2d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.03, 0.23, 0.72, 0.02], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: over the last hour, during a scheduled maintenance window. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d85562652e7126d1_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: in production only, at the end of the fiscal period. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5529705762f31a4d_n", "kind": "noul", "options": ["false", "true"], "target": [0.9, 0.1], "state": "The metrics pipeline 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 operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3e6afe433b454e31_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.41, 0.02, 0.05, 0.52], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: during the batch window, with staffing at reduced levels. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_774e8481d67f4166_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.01, 0.03, 0.96], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: in production only, immediately after go-live. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c61f01fb26fee313_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.42, 0.56, 0.01], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during normal operations. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1d28f4f0f7c7f819_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.83, 0.16, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: across all regions, while on-call rotation changed. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_40cc3fe25478bc2e_n", "kind": "noul", "options": ["false", "true"], "target": [0.66, 0.34], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: during the batch window, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9580b5c3a6e00a21_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.5, 0.01, 0.01, 0.48], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: over the last hour, with staffing at reduced levels. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1fef59a7e048d966_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.12, 0.22, 0.02, 0.64], "state": "The metrics pipeline shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: in production only, during the holiday freeze. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_49a4eafbc88ad433_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.46, 0.01, 0.31, 0.22], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_456fb1d34f094150_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.23, 0.68, 0.0, 0.09], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during normal operations. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e5f0b2e1373ee2b2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.62, 0.07, 0.08, 0.23], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, with a new vendor onboarded. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5123410baa410380_n", "kind": "noul", "options": ["false", "true"], "target": [0.23, 0.77], "state": "The log shipper reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: over the last hour, during the morning shift. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_66f8e652dbf689b9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.02, 0.82, 0.16], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, under an active deadline. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0cebf13cfcf4e49d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.0, 0.77, 0.23], "state": "Service catalog-sync correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: across all regions, during the morning shift. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_91a6cbeabcbdbf56_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.0, 0.08, 0.91], "state": "The log shipper shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: across all regions, while legacy systems are still active. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b6119e2a56046946_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.08, 0.81, 0.11, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: during the batch window, during an external partner integration. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca195f786ef7e800_n", "kind": "noul", "options": ["false", "true"], "target": [0.61, 0.39], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: during the batch window, while legacy systems are still active. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c8362ddb444df4ab_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "The log shipper lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, with staffing at reduced levels. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_60c0abbb70fed2e9_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.22, 0.72, 0.06, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: in production only, during the quarterly review. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bffecabe386dadc7_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.64, 0.33, 0.02, 0.01], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: in production only, at the end of the fiscal period. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9bf3d029423f50a4_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.37, 0.52, 0.1, 0.01], "state": "The log shipper matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: over the last hour, during the system migration. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6583018f16aa9359_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.92, 0.06, 0.01, 0.01], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: over the last hour, with staffing at reduced levels. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_74f8f8d935a47cd0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.02, 0.63, 0.33, 0.01], "state": "The metrics pipeline flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: across all regions, during normal operations. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7d44ae9c8406eaa6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.21, 0.75, 0.04], "state": "The metrics pipeline flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: across all regions, immediately after go-live. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3afaf2a4d79d6160_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "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.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2b1854e3c1526efc_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.1, 0.6, 0.08, 0.22], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_11e74406f2c69529_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.84, 0.13, 0.01, 0.02], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: across all regions, during peak load. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_65ae3fcde11f63fc_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: in production only, immediately after go-live. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_00bdfdf29e75ccae_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.23, 0.2, 0.5, 0.07], "state": "The log shipper shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: during the batch window, with a new vendor onboarded. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a3ff9c1026560def_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.46, 0.38, 0.16, 0.0, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: across all regions, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f6298bd5448856d8_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: in production only, following a recent audit. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ce17ae92b76ef1f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.49, 0.42, 0.06, 0.03], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: over the last hour, during an external partner integration. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0e8d9c60ae634ed8_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: during the batch window, shortly after a software update. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2f8a296cfcd34492_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.3, 0.59, 0.11, 0.0, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during the holiday freeze. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_93ef5a84e6de6317_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.03, 0.15, 0.39, 0.31, 0.11, 0.01], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: across all regions, mid-incident. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9c072b71562fa923_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.73, 0.05, 0.01, 0.21], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during the system migration. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_39d4be40d71b66b3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.11, 0.69, 0.17, 0.0], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: over the last hour, shortly after a software update. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_28f6438fe60d04f9_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.17, 0.61, 0.21, 0.01], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: across all regions, under reduced staffing. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b7a892b2f526cadf_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: during the batch window, during a scheduled maintenance window. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f14800d0a9e642c0_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.34, 0.25, 0.06, 0.35], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: during the batch window, with a new vendor onboarded. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7110795baa64fd8a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.64, 0.33, 0.01], "state": "The metrics pipeline flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: in production only, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2aee5cd9ba8a0aa7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.8, 0.18, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: over the last hour, during the quarterly review. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e1d3c56502e47eb2_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: in production only, while legacy systems are still active. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_150a8aba43875b5a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.22, 0.76, 0.02], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: over the last hour, at the end of the fiscal period. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b343641b0be50a3_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.56, 0.39, 0.03, 0.02], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: across all regions, during an external partner integration. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9a775181659353d2_n", "kind": "noul", "options": ["false", "true"], "target": [0.53, 0.47], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: over the last hour, while on-call rotation changed. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8d07db9868f04269_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.39, 0.59, 0.01], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: over the last hour, during an external partner integration. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e0f1a655de4eee0c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.72, 0.24, 0.01, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: over the last hour, during peak load. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0a6133bc92d2db48_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.32, 0.43, 0.21, 0.01], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: in production only, during an external partner integration. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aceabe8eaecd69ed_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.28, 0.29, 0.03, 0.4], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: in production only, under reduced staffing. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_786793717d5bfc6a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.42, 0.56, 0.01], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; 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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b0b1324bb5485df7_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: across all regions, during a scheduled maintenance window. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_898bc52872afa92e_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "The log shipper flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during the quarterly review. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_afe0382cc9655d87_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.5, 0.5, 0.0, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: across all regions, with a new vendor onboarded. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d73c6d72a77ca8f6_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.52, 0.03, 0.41], "state": "The log shipper matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: across all regions, while on-call rotation changed. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7467c6f62e8a76e8_n", "kind": "noul", "options": ["false", "true"], "target": [0.92, 0.08], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: across all regions, under an active deadline. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_597f43800d3b3d80_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.88, 0.1, 0.01, 0.01], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: in production only, shortly after a software update. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2af8710379a6f6bb_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.1, 0.01, 0.22, 0.67], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: across all regions, while legacy systems are still active. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dc0f96a446849eb1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.65, 0.3, 0.0], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: over the last hour, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_116e5b31ccbf4cb1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.73, 0.24, 0.0], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: across all regions, during normal operations. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_503689448e21ac83_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: in production only, under reduced staffing. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b315feb1b9118c47_n", "kind": "noul", "options": ["false", "true"], "target": [0.14, 0.86], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, mid-incident. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_65ae3fcde11f63fc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.47, 0.51, 0.01], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: in production only, immediately after go-live. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3abcf796d0ebfba8_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: over the last hour, during an external partner integration. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3afeab695af83995_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.02, 0.07, 0.7, 0.2, 0.0], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: across all regions, during normal operations. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f9384266eddbe211_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.05, 0.04, 0.9], "state": "The log shipper matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: across all regions, at the end of the fiscal period. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d57446422899d7d8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.55, 0.39, 0.01], "state": "The log shipper correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: across all regions, during the holiday freeze. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e75832a0890e034f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.02, 0.26, 0.7, 0.02], "state": "The metrics pipeline flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: over the last hour, during the system migration. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0341c9777930bf4e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.8, 0.14, 0.03, 0.03], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during the holiday freeze. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aebf9812fc5d1d09_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The log shipper lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: in production only, during peak load. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8d6150966e165d09_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.12, 0.84, 0.04], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, under an active deadline. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7a0356cd898b698d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.1616, 0.8182, 0.0202], "state": "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, with staffing at reduced levels. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_953db24316107fda_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.56, 0.38, 0.01], "state": "Node pgsql-14 flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: across all regions, as part of a compliance sweep. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9c57d1b9e77a1d06_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "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, under reduced staffing. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_55416dd8c1b0adb5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.15, 0.47, 0.35, 0.02, 0.0], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the morning shift. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a5a31f49d9e9f9e3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.16, 0.8, 0.04], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during normal operations. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a96867d88435ebe3_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.04, 0.42, 0.52], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: in production only, under an active deadline. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_93a6705828bd18e0_n", "kind": "noul", "options": ["false", "true"], "target": [0.43, 0.57], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: in production only, during a scheduled maintenance window. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0112ab333ed0d80f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.27, 0.45, 0.23, 0.05], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during the system migration. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2382d88f8fd7ecc3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.22, 0.75, 0.03], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ee30c52a1ded9efc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.25, 0.73, 0.01, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: over the last hour, at the end of the fiscal period. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a6698dc29da472d1_n", "kind": "noul", "options": ["false", "true"], "target": [0.45, 0.55], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: over the last hour, at the end of the fiscal period. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6d1f28fdb02a4ab3_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.91, 0.07, 0.01, 0.01], "state": "Service catalog-sync flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: during the batch window, under an active deadline. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6632272cee29b1c5_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.78, 0.14, 0.08, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the holiday freeze. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fe5d1a897a972bd3_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.01, 0.44, 0.51], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: in production only, under reduced staffing. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1a95450d51ad667c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.48, 0.04, 0.04, 0.44], "state": "The log shipper shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: during the batch window, mid-incident. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_05960ad92306a4af_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.16, 0.79, 0.04], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: across all regions, with staffing at reduced levels. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9c549c42833a7d2d_n", "kind": "noul", "options": ["false", "true"], "target": [0.67, 0.33], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: in production only, during normal operations. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_66bb7c13ab3eebe2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.65, 0.25, 0.06, 0.0], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: across all regions, while legacy systems are still active. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_921101e5a60627a9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.17, 0.62, 0.18, 0.01], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: in production only, while on-call rotation changed. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_657ddbe0fe7a038b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.83, 0.15, 0.01, 0.01], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during the morning shift. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7b83ff3ff41a6095_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.98, 0.01, 0.0, 0.01], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: during the batch window, under an active deadline. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d61e8130995f9914_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: during the batch window, with staffing at reduced levels. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ac0c9e827cfa0342_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: in production only, while legacy systems are still active. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_50b80b47106921e4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.63, 0.36, 0.0], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: over the last hour, while on-call rotation changed. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_198189809cde8bd4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.1, 0.66, 0.23, 0.0], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: across all regions, during the quarterly review. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2b68debf5a99a940_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.22, 0.76, 0.02], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3ea5399fbd4ad000_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.37, 0.02, 0.24, 0.37], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: across all regions, under an active deadline. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cbae5c2d06540a15_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.45, 0.52, 0.01], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: across all regions, during the quarterly review. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5b5f7f02e116823c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.07, 0.28, 0.61, 0.04, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: across all regions, following a recent audit. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9bfee9027cafea34_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.01, 0.94, 0.05], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: across all regions, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_79c85077e9a3722a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.54, 0.32, 0.11, 0.0], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during peak load. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_30ccf5005028298a_n", "kind": "noul", "options": ["false", "true"], "target": [0.46, 0.54], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: across all regions, during a scheduled maintenance window. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a89b7747919e89e5_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: over the last hour, following a recent audit. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5f18df083fac50c9_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.09, 0.34, 0.55, 0.02], "state": "Service catalog-sync flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: in production only, during an external partner integration. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6671c30b7e2b8817_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.42, 0.56, 0.01], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: over the last hour, at the end of the fiscal period. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_623fef2612bba743_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.23, 0.75, 0.02], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally flags a step-function change in error slope. Context: across all regions, with a new vendor onboarded. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_20edde1efbee14ce_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.87, 0.01, 0.04, 0.08], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: during the batch window, under an active deadline. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_76bdd9f766d045c3_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.12, 0.07, 0.47, 0.34], "state": "The log shipper reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: during the batch window, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2b68debf5a99a940_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.76, 0.22, 0.01, 0.01], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d7124e66f116bcfa_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during an external partner integration. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dcf345bc0fc88370_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.65, 0.27, 0.05, 0.03], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, shortly after a software update. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4cce35ce6e2fcbf5_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "The log shipper correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, following a recent audit. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_01cc837a77c9a5e4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.26, 0.64, 0.05, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: during the batch window, as part of a compliance sweep. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4e1a247e52a78373_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.16, 0.76, 0.07, 0.01], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, under reduced staffing. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fdb77e1552a4c52e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.03, 0.59, 0.36, 0.01], "state": "Service catalog-sync lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: across all regions, as part of a compliance sweep. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_237a191771e57089_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.51, 0.41, 0.06, 0.0], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, under reduced staffing. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_18fda9a7e70ed3b2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.12, 0.84, 0.04], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: in production only, while on-call rotation changed. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cc180ce1eff32f15_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: over the last hour, mid-incident. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f0d4bc694780a65d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.03, 0.67, 0.26], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during an external partner integration. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9b8adf337dc171bb_n", "kind": "noul", "options": ["false", "true"], "target": [0.48, 0.52], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: across all regions, during the morning shift. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_93a6705828bd18e0_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.38, 0.6, 0.01], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: in production only, during a scheduled maintenance window. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_078416288844daee_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.31, 0.03, 0.03, 0.63], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, while on-call rotation changed. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_64d30da221b9c18b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.17, 0.7, 0.12, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: in production only, following a recent audit. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_19e4768dee9b2567_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "The log shipper reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: during the batch window, during the quarterly review. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2aeea829b43dd105_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.35, 0.55, 0.09, 0.01], "state": "The log shipper returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: across all regions, with staffing at reduced levels. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ae9c956bfd8b20c8_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: across all regions, as part of a compliance sweep. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_41f1416b8b74b8e4_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The log shipper correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: across all regions, during the morning shift. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0e397acb484ee7ff_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: in production only, as part of a compliance sweep. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e40ea791579aa67e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.71, 0.26, 0.02, 0.01], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: over the last hour, shortly after a software update. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_96a63b219bc5c215_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: in production only, while on-call rotation changed. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_82dc141b100e1979_n", "kind": "noul", "options": ["false", "true"], "target": [0.47, 0.53], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: during the batch window, with staffing at reduced levels. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_04071ec7e18e13fb_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: across all regions, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f217d4867c010acc_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "The metrics pipeline correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: across all regions, while legacy systems are still active. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_57e52c160f30209f_n", "kind": "noul", "options": ["false", "true"], "target": [0.68, 0.32], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: across all regions, during the morning shift. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9578e242693a8cce_n", "kind": "noul", "options": ["false", "true"], "target": [0.62, 0.38], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: in production only, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bc268bff73441d3a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.07, 0.56, 0.33, 0.04], "state": "The log shipper matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: in production only, during the holiday freeze. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ada669e16345170d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.6, 0.29, 0.09, 0.02], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: in production only, during the holiday freeze. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_31041d976e2fc465_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "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.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_53f92526701613b6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.5, 0.41, 0.07, 0.0], "state": "The log shipper reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: in production only, with staffing at reduced levels. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7e3a9f077ade4737_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.02, 0.32, 0.4, 0.25, 0.01, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the holiday freeze. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_89145242e68e8fb6_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.06, 0.03, 0.05, 0.86], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, while on-call rotation changed. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b4c7fe91e9f34870_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: during the batch window, during normal operations. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d9b1b40b971901ab_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.93, 0.03, 0.03, 0.01], "state": "The log shipper shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: in production only, mid-incident. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e6c5564f5604e6b4_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: in production only, under an active deadline. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cd8f12694c9c6955_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.83, 0.15, 0.01, 0.01], "state": "Service catalog-sync shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: across all regions, immediately after go-live. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dec713caa4567308_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.14, 0.79, 0.06], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: in production only, under an active deadline. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_03f55cf13100fdd0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.17, 0.8, 0.03], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: in production only, following a recent audit. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5d7aa24ab5384821_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.61, 0.37, 0.0], "state": "The log shipper correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: across all regions, with a new vendor onboarded. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_baa7474bfe001b61_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.65, 0.32, 0.02, 0.01], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: in production only, during the holiday freeze. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3ea1f47f29d357cf_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "The log shipper 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.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5840917e4f6e4358_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.1, 0.67, 0.22, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: in production only, mid-incident. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9ff804b41f5d7fa7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.43, 0.55, 0.01], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during an external partner integration. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_522576dc9328401c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.63, 0.36, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: over the last hour, while on-call rotation changed. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_539feeb361eb70c1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.07, 0.36, 0.52, 0.05, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during normal operations. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aa76e1b08be64164_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "Service catalog-sync shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: during the batch window, under reduced staffing. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_236179a567f39fc9_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "The log shipper flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: across all regions, during a scheduled maintenance window. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_43523ac4550235f9_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "The log shipper flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: in production only, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_574342a250015f84_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.49, 0.48, 0.02, 0.01], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: across all regions, while legacy systems are still active. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4dfe869f8715374f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.54, 0.31, 0.1, 0.01], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during normal operations. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f5df45a6c61efc82_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.48, 0.52, 0.0], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: across all regions, at the end of the fiscal period. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4f94f80db7a69a70_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.46, 0.54, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during an external partner integration. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f371525de860d663_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "Service catalog-sync shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: during the batch window, with staffing at reduced levels. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3d8d0b2a52741e1d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.35, 0.4, 0.23, 0.02], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: across all regions, immediately after go-live. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c8482fa532daa8e0_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.1414, 0.6869, 0.1515, 0.0202], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, following a recent audit. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_79e208fcf5e75713_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.34, 0.03, 0.3, 0.33], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: across all regions, at the end of the fiscal period. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7a443e158d554e34_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.08, 0.01, 0.04, 0.87], "state": "The log shipper lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the morning shift. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7f7ef4f001d86676_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during the quarterly review. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9592d32f8fccfaa8_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Service catalog-sync 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 automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9720fe8d8545cc27_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.1, 0.16, 0.01, 0.73], "state": "The log shipper lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: across all regions, at the end of the fiscal period. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_920f01907e47b37f_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, while on-call rotation changed. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a6ce3ebdc670834f_n", "kind": "noul", "options": ["false", "true"], "target": [0.2, 0.8], "state": "The log shipper shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, immediately after go-live. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e201dbb56cb51406_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.67, 0.23, 0.09, 0.01], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during normal operations. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fada334b3b0dc509_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.79, 0.19, 0.02, 0.0], "state": "The log shipper matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: over the last hour, under reduced staffing. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_11e74406f2c69529_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: across all regions, during peak load. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_466b6e9a7228ff54_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, while on-call rotation changed. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_72f32cc98b1f4832_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.33, 0.57, 0.1, 0.0, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: across all regions, during an external partner integration. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_85c813a84cc6697f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.04, 0.9, 0.06, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: across all regions, during the quarterly review. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9618e6991497442b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.65, 0.28, 0.05, 0.02], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during an external partner integration. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_038ae8f8c83a3da7_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.39, 0.04, 0.03, 0.54], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: in production only, while legacy systems are still active. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2e569a7241a0d41a_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: across all regions, during normal operations. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_242c8bdf74d35e85_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.37, 0.61, 0.01], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: over the last hour, under an active deadline. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6de561fa5caf14c8_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: over the last hour, while on-call rotation changed. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_386aac66aa5e21d7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.35, 0.61, 0.01, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: over the last hour, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_670f4fdeadf62e9b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.2, 0.69, 0.1, 0.01], "state": "The metrics pipeline lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: over the last hour, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_adc6bba1f78247aa_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.0, 0.88, 0.08], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during peak load. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_110eef25c8924319_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.07, 0.11, 0.01, 0.81], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: over the last hour, during the morning shift. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5a205d87791964fd_n", "kind": "noul", "options": ["false", "true"], "target": [0.2, 0.8], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, as part of a compliance sweep. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_324d5e3696d6ee1c_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: across all regions, under an active deadline. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6148f5c63aeb1104_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during peak load. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_980f9f9f1ccd2df3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.54, 0.45, 0.0], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: during the batch window, during peak load. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eac204ed8d795d76_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.04, 0.31, 0.64], "state": "The log shipper reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: across all regions, during normal operations. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9bbf7a56da71d304_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.06, 0.47, 0.46, 0.01], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: in production only, during the morning shift. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_22227024cda67999_n", "kind": "noul", "options": ["false", "true"], "target": [0.21, 0.79], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: in production only, mid-incident. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9a775181659353d2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.15, 0.29, 0.02, 0.54], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: over the last hour, while on-call rotation changed. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_730e3426a2252ae4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.58, 0.36, 0.01], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: during the batch window, as part of a compliance sweep. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_13e9b2a5dc8ab04e_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: in production only, following a recent audit. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6f6c1e78524580ff_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.64, 0.0, 0.35, 0.01], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during an external partner integration. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_121e836575d8c3d4_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.08, 0.59, 0.32, 0.01], "state": "The log shipper correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: across all regions, at the end of the fiscal period. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f1a9b30315d91a07_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.02, 0.35, 0.61], "state": "The log shipper flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: during the batch window, while legacy systems are still active. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ae2a070a1caa4457_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.31, 0.25, 0.33, 0.11], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: during the batch window, while legacy systems are still active. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c96e41496d30b863_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: in production only, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e39a6feee2dfa616_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.78, 0.2, 0.01, 0.01], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: during the batch window, shortly after a software update. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bdd01ab419590571_n", "kind": "noul", "options": ["false", "true"], "target": [0.23, 0.77], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: over the last hour, with staffing at reduced levels. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d95a23a39934bd33_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: during the batch window, during the quarterly review. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_25000f5928f5bef2_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.75, 0.18, 0.07, 0.0], "state": "The log shipper correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during the morning shift. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1b57621f08128cb1_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "The log shipper reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: over the last hour, under reduced staffing. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2e56f45b3ba05ac5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.36, 0.63, 0.01], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_840c9f402a8099bd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.6, 0.36, 0.01, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: over the last hour, during an external partner integration. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5eb498820be4cc14_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "The log shipper flags a step-function change in error slope; 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 on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3ef81b5d239fce3c_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, mid-incident. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5e4cb06dbd8a7956_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, while on-call rotation changed. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_523114ae4c36d008_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.04, 0.8, 0.16, 0.0], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: in production only, as part of a compliance sweep. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_72d23f145204e5de_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: over the last hour, under an active deadline. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bc8f3307498becf5_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.55, 0.31, 0.11, 0.03], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e10bb6384fe1548f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.09, 0.05, 0.02, 0.84], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: over the last hour, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_95e3d80e01e422c9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.18, 0.79, 0.03], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: during the batch window, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_11e964bfae4d2d86_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0101, 0.0202, 0.3838, 0.5556, 0.0303], "state": "The metrics pipeline correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: in production only, at the end of the fiscal period. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_22555bf02c5aeb9a_n", "kind": "noul", "options": ["false", "true"], "target": [0.9, 0.1], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: during the batch window, during the holiday freeze. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6a63d3469ffb55aa_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.05, 0.58, 0.36, 0.01], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: in production only, during a scheduled maintenance window. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f99f5730e059bc97_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.38, 0.6, 0.01], "state": "Service catalog-sync flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: across all regions, during the system migration. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fe43d435020c821f_n", "kind": "noul", "options": ["false", "true"], "target": [0.48, 0.52], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: across all regions, during normal operations. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6a3a545ccc4e6807_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.0, 0.28, 0.71], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: during the batch window, during a scheduled maintenance window. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d8557dec28ea9ed2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.19, 0.8, 0.01], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, under reduced staffing. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ff1d5a64a457a3aa_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.47, 0.47, 0.05, 0.01], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: in production only, at the end of the fiscal period. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6749a06461a7b369_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.07, 0.78, 0.15, 0.0, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: across all regions, while on-call rotation changed. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_929cdb50e988d398_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.9, 0.09, 0.01, 0.0], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: during the batch window, shortly after a software update. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_68e841043ccc5fe5_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.02, 0.08, 0.86], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: in production only, as part of a compliance sweep. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_af08ddb14f69a289_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.64, 0.23, 0.11, 0.02], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, immediately after go-live. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9018d507e426d4df_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: across all regions, mid-incident. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5510412336f7641d_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, as part of a compliance sweep. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1280069eac0fbae6_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.05, 0.51, 0.43, 0.01], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, with a new vendor onboarded. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1596da3f8c3755b7_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.36, 0.02, 0.11, 0.51], "state": "The log shipper returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the morning shift. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_025f00cdf95d94c1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.06, 0.78, 0.15, 0.01], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during the system migration. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_22e3d324c0e7f69c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.53, 0.36, 0.08, 0.0], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_db769b16385b31ad_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.15, 0.56, 0.25, 0.04, 0.0, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, at the end of the fiscal period. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c28ba3093f1ef556_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.01, 0.46, 0.51], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: during the batch window, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_caa940303ee6411b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.08, 0.06, 0.03, 0.83], "state": "The log shipper lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: in production only, while on-call rotation changed. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cd44d6d05ff598c1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.34, 0.66, 0.0], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: across all regions, with staffing at reduced levels. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_751ea2ffabf34b6b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.18, 0.35, 0.44, 0.03], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: during the batch window, with a new vendor onboarded. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3d4dd6d3b06567ec_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.94, 0.04, 0.01, 0.01], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: across all regions, mid-incident. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_913b4247c0a78821_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.07, 0.2, 0.61, 0.12], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: during the batch window, with a new vendor onboarded. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_57b179edc1fdbf9a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.16, 0.48, 0.31, 0.04, 0.0], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: in production only, following a recent audit. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_35bba68ddcf9bf15_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.02, 0.31, 0.39, 0.27, 0.01, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_979cb84cc6f5d341_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.26, 0.72, 0.02], "state": "The log shipper correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: across all regions, during peak load. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_535dc7fd36cac5fa_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.28, 0.72, 0.0], "state": "The metrics pipeline shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during peak load. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_881292248a6bb1b4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.12, 0.59, 0.28, 0.01, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: in production only, with staffing at reduced levels. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_615204ccced27a63_n", "kind": "noul", "options": ["false", "true"], "target": [0.64, 0.36], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: over the last hour, while on-call rotation changed. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2384e81482b7f811_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: during the batch window, under reduced staffing. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ecf4bac04640e56_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.0, 0.46, 0.49], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: in production only, with a new vendor onboarded. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e010bce7a3a7b68a_n", "kind": "noul", "options": ["false", "true"], "target": [0.18, 0.82], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the holiday freeze. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_04bc125e78dcf00e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.12, 0.15, 0.2, 0.53], "state": "Service catalog-sync flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: over the last hour, mid-incident. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3ce4acf51d346757_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "The log shipper reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: during the batch window, during the system migration. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_68b798b2fcbb5d51_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.9, 0.07, 0.01, 0.02], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, immediately after go-live. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7b83ff3ff41a6095_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: during the batch window, under an active deadline. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_407f524abe95fe94_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "The log shipper shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: across all regions, shortly after a software update. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a8ac7e4a18959862_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: in production only, during the system migration. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2aab6e54b27b1a57_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.46, 0.36, 0.17, 0.01], "state": "The log shipper correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, under reduced staffing. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f60c955a34ab25dc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.13, 0.82, 0.05], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: during the batch window, mid-incident. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fdb06f8787c48d91_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "Node pgsql-14 flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: across all regions, during the morning shift. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bf559bafb5ad8462_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.6, 0.38, 0.01, 0.01], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: across all regions, under reduced staffing. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e98758c47a7b50a3_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.62, 0.25, 0.11, 0.02], "state": "The log shipper reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: over the last hour, during the holiday freeze. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_67ac392549e72423_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.19, 0.73, 0.07], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: across all regions, during the holiday freeze. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e83e904acaa6460c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.03, 0.45, 0.51, 0.01], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: over the last hour, under reduced staffing. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6ea9db45eda855e1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.11, 0.02, 0.02, 0.85], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e888ad684ee71b35_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.07, 0.84, 0.08, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: in production only, during normal operations. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b1750ddf94a17685_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: in production only, during normal operations. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1216e41e760ddc18_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.43, 0.01, 0.2, 0.36], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, while legacy systems are still active. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5e60a338cf4d34af_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.16, 0.71, 0.13, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: across all regions, shortly after a software update. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_848048a71f969129_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.47, 0.53, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: over the last hour, immediately after go-live. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_11e67c763449ec23_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.66, 0.33, 0.0], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: during the batch window, with staffing at reduced levels. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_237a191771e57089_n", "kind": "noul", "options": ["false", "true"], "target": [0.38, 0.62], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, under reduced staffing. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ba86727b0ec7d77_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.31, 0.64, 0.04], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: across all regions, during the system migration. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4de3bf7802faa79a_n", "kind": "noul", "options": ["false", "true"], "target": [0.51, 0.49], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: across all regions, at the end of the fiscal period. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_497e2a8e51291455_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: in production only, during peak load. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9a2dd2384612bc89_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: across all regions, during the holiday freeze. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_df1a1ada49983578_n", "kind": "noul", "options": ["false", "true"], "target": [0.56, 0.44], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during the quarterly review. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ea95c5e5f83eb24c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.94, 0.01, 0.01, 0.04], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, while on-call rotation changed. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aec8610f6543fe11_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: during the batch window, under an active deadline. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b1750ddf94a17685_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.26, 0.02, 0.03, 0.69], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: in production only, during normal operations. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2a02ff15271547cf_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.04, 0.51, 0.44, 0.01], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1bbc907370dde24d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.14, 0.49, 0.36, 0.01], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, following a recent audit. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6d479b6637d93b78_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.78, 0.17, 0.04, 0.01], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, while on-call rotation changed. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e4a7b3fa2b0418cf_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "The log shipper returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: in production only, with a new vendor onboarded. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aceabe8eaecd69ed_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.66, 0.34, 0.0], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: in production only, under reduced staffing. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fdb3f0a51f488cfa_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.35, 0.03, 0.38, 0.24], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: across all regions, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c31f7ce2fa687714_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.04, 0.68, 0.22, 0.06, 0.0, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: across all regions, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3f377361ce9ed677_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.04, 0.8, 0.16, 0.0], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: during the batch window, during a scheduled maintenance window. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ee70faaa7c266a11_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.01, 0.34, 0.61], "state": "The log shipper reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during peak load. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dec713caa4567308_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.99, 0.01, 0.0, 0.0], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: in production only, under an active deadline. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3df20839b079da87_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.41, 0.57, 0.01], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: across all regions, during the quarterly review. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_abdfc795f51f9d49_n", "kind": "noul", "options": ["false", "true"], "target": [0.67, 0.33], "state": "Service catalog-sync lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: over the last hour, while on-call rotation changed. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8bf5e929e40df477_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.63, 0.01, 0.15, 0.21], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the morning shift. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9f6a3e70d748fd2c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.18, 0.81, 0.01], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during the holiday freeze. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8495245eb1c1e365_n", "kind": "noul", "options": ["false", "true"], "target": [0.71, 0.29], "state": "The metrics pipeline correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during the holiday freeze. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a4bb529c22bf8a2e_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: across all regions, during the morning shift. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_808ee7ea36c93ce1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.66, 0.33, 0.01, 0.0], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: across all regions, following a recent audit. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f9448e26ddb2fe9b_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "The log shipper reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: in production only, shortly after a software update. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6f04216405832758_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.44, 0.56, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: over the last hour, immediately after go-live. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4e88f6b96494f179_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.05, 0.83, 0.12, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: during the batch window, during the morning shift. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_27e7547f7e9b05fb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.19, 0.58, 0.23, 0.0, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: during the batch window, while legacy systems are still active. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f5a84925684d56a1_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during the morning shift. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_47740b1e2abd1e22_n", "kind": "noul", "options": ["false", "true"], "target": [0.53, 0.47], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: in production only, under reduced staffing. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_98df6761f6cafb95_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: in production only, during the holiday freeze. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e784c803e5cb8bb7_n", "kind": "noul", "options": ["false", "true"], "target": [0.9, 0.1], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: during the batch window, under an active deadline. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_08adbaf45c80c98f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.15, 0.83, 0.02], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during peak load. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e30155814afc346d_n", "kind": "noul", "options": ["false", "true"], "target": [0.21, 0.79], "state": "The log shipper shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, under reduced staffing. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fca00df26f3262e6_n", "kind": "noul", "options": ["false", "true"], "target": [0.7, 0.3], "state": "Node pgsql-14 flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: over the last hour, under an active deadline. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b731e1d576c176a3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.11, 0.75, 0.13, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: during the batch window, during normal operations. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ed3b510e1cf44a1f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.19, 0.56, 0.25, 0.0, 0.0], "state": "The metrics pipeline shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: across all regions, while on-call rotation changed. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8bdfeca16a246683_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: over the last hour, during the morning shift. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7b0b3acd5cd2fcd8_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.05, 0.76, 0.18, 0.01], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, at the end of the fiscal period. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6ef967fe36a54c57_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.71, 0.28, 0.0], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: during the batch window, with a new vendor onboarded. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_71fea8d702466c2f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.49, 0.5, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: across all regions, with staffing at reduced levels. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_520da00a44ac5fe6_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.06, 0.61, 0.32, 0.01], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: across all regions, with a new vendor onboarded. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ba4ac7a5ef0c9344_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.23, 0.76, 0.01], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_40c133552346988a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.75, 0.23, 0.01, 0.01], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: over the last hour, during the morning shift. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_635abbcdf94d8d19_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: across all regions, during the system migration. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_523114ae4c36d008_n", "kind": "noul", "options": ["false", "true"], "target": [0.55, 0.45], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: in production only, as part of a compliance sweep. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_672217b2dac8da3f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.0, 0.08, 0.86, 0.06], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, while legacy systems are still active. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_20969bf86f8537fc_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: during the batch window, during an external partner integration. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a8e0822392107bec_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.08, 0.9], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: in production only, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_49cd06ac56cd17ea_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.06, 0.65, 0.26, 0.01], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: in production only, as part of a compliance sweep. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_78a8c1086f17a9a1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.43, 0.44, 0.11, 0.02], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: over the last hour, as part of a compliance sweep. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d5f5748cc374dc99_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.0, 0.04, 0.93, 0.03], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: during the batch window, following a recent audit. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9f576097d3c2da5e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.55, 0.45, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: across all regions, at the end of the fiscal period. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0962e2f707185d80_n", "kind": "noul", "options": ["false", "true"], "target": [0.55, 0.45], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: during the batch window, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fd9177b268c37a08_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.46, 0.54, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during an external partner integration. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ffd54db1c302abbc_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.61, 0.3, 0.06, 0.03], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: over the last hour, immediately after go-live. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7f5b673918fe9809_n", "kind": "noul", "options": ["false", "true"], "target": [0.93, 0.07], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during the system migration. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3d6f6dad2e926cb4_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: across all regions, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0accffe82f8b423e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.19, 0.54, 0.05, 0.22], "state": "Service catalog-sync shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: across all regions, under an active deadline. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_06424dc1a84fc63b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.39, 0.54, 0.06, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: over the last hour, shortly after a software update. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_262c83ad778ebde9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.49, 0.04, 0.02, 0.45], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: across all regions, during the holiday freeze. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_11e442e37771ac24_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, while on-call rotation changed. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_053484595eda5c3c_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fbedb222726e3c66_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.42, 0.54, 0.03, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: in production only, during the morning shift. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8ad646342a5d2f25_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.29, 0.69, 0.01], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: over the last hour, during peak load. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4dd6e467a3aca27d_n", "kind": "noul", "options": ["false", "true"], "target": [0.68, 0.32], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: over the last hour, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4c364664222fa489_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.43, 0.47, 0.1, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: across all regions, with a new vendor onboarded. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b4e2c416f547c80e_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: across all regions, mid-incident. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_047055b1f2df0124_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.07, 0.85, 0.08], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: during the batch window, mid-incident. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_66e5292b9f0c123a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.05, 0.79, 0.16, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: across all regions, with a new vendor onboarded. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6df58db4216cd635_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.89, 0.1, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: over the last hour, during the morning shift. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8528a9e45dccf30e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.16, 0.81, 0.03], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: during the batch window, during peak load. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_40cae5df014e14e3_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.47, 0.5, 0.03, 0.0], "state": "The log shipper matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: across all regions, at the end of the fiscal period. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e0a3d17369be7208_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "Service catalog-sync correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: over the last hour, while on-call rotation changed. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_02e70d71386df51f_n", "kind": "noul", "options": ["false", "true"], "target": [0.58, 0.42], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: during the batch window, as part of a compliance sweep. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e162c1c272515eb3_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.0, 0.07, 0.92], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_59cf98ce906ed507_n", "kind": "noul", "options": ["false", "true"], "target": [0.48, 0.52], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: in production only, following a recent audit. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_25772914d7ca27d1_n", "kind": "noul", "options": ["false", "true"], "target": [0.21, 0.79], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: in production only, during normal operations. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6e7dcb7056a6809b_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: during the batch window, during peak load. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_62f5e555326f4c81_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.49, 0.49, 0.01], "state": "The metrics pipeline flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: across all regions, during the system migration. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cd2837ca730e63eb_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.55, 0.39, 0.04, 0.02], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: over the last hour, following a recent audit. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a7a8aab3da95bb6e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.01, 0.02, 0.39, 0.54, 0.03], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: in production only, during normal operations. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6251472988c03c1a_n", "kind": "noul", "options": ["false", "true"], "target": [0.93, 0.07], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: over the last hour, mid-incident. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_660bb640fe1e5921_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.01, 0.01, 0.94], "state": "The log shipper lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: in production only, as part of a compliance sweep. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fa63b45c46118f50_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, while legacy systems are still active. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eccf4d2cc0213b5f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.98, 0.0, 0.01, 0.01], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during a scheduled maintenance window. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aa09988c9f95d0d6_n", "kind": "noul", "options": ["false", "true"], "target": [0.68, 0.32], "state": "The log shipper shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: in production only, with staffing at reduced levels. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_271cad5572ad01d4_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.87, 0.12, 0.01, 0.0], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, with staffing at reduced levels. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_70b0c11c7c3d0a6a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.02, 0.09, 0.24, 0.55, 0.1, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: across all regions, with a new vendor onboarded. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2fd1e883c11fb411_n", "kind": "noul", "options": ["false", "true"], "target": [0.91, 0.09], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: over the last hour, during the quarterly review. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_542d64ee8fc2efa3_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.13, 0.03, 0.18, 0.66], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: in production only, during the holiday freeze. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_98eeb572a6a387ed_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6cfa2beca82112b4_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.86, 0.12, 0.01, 0.01], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: in production only, immediately after go-live. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e98758c47a7b50a3_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "The log shipper reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: over the last hour, during the holiday freeze. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c24e74df9fbf66d1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.47, 0.51, 0.01], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: during the batch window, at the end of the fiscal period. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d43487580c637577_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: across all regions, as part of a compliance sweep. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d8bdb2b83fda02ea_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: over the last hour, with staffing at reduced levels. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_33c7a3d42f27139b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.16, 0.8, 0.04], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: in production only, with a new vendor onboarded. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ee3659e8cc8f7f0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.1616, 0.8182, 0.0202], "state": "The metrics pipeline lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: during the batch window, under an active deadline. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6405e58deabe4c14_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.01, 0.32, 0.59, 0.07], "state": "The metrics pipeline correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: during the batch window, mid-incident. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a2d7c5bbdcaf2edb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.57, 0.42, 0.0], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during an external partner integration. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8b813f3c190927ad_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.04, 0.85, 0.1], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: across all regions, under an active deadline. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_66504073835d2c6e_n", "kind": "noul", "options": ["false", "true"], "target": [0.56, 0.44], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: during the batch window, during the quarterly review. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_42c2d907b8a801ec_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: across all regions, shortly after a software update. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c61f8ad7a3f3729e_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The log shipper flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: across all regions, under an active deadline. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e869553490e57d4d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.63, 0.36, 0.0], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: during the batch window, shortly after a software update. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9a3b88e23701dace_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.12, 0.58, 0.23, 0.01], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: across all regions, during a scheduled maintenance window. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_49cd6a50a75c581f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.55, 0.32, 0.12, 0.01], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during a scheduled maintenance window. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f8b5603a91f7e25f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.03, 0.54, 0.43, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, following a recent audit. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_35b85705a61db93d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.71, 0.24, 0.0], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5df18bda476b8971_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.08, 0.71, 0.21, 0.0, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: across all regions, during an external partner integration. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f6ba756a5a0b8c71_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: across all regions, under an active deadline. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e817fa8db15da2d9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.33, 0.21, 0.08, 0.38], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: during the batch window, during the morning shift. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_926277f27352de01_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.1, 0.38, 0.51, 0.01, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: in production only, during normal operations. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cf6e6eb7aa805c62_n", "kind": "noul", "options": ["false", "true"], "target": [0.62, 0.38], "state": "The log shipper shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: across all regions, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fe827752ddaf5a89_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.75, 0.21, 0.03, 0.01], "state": "The log shipper reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: over the last hour, immediately after go-live. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fed8c55bb8a3323e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.06, 0.5, 0.41, 0.02], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: during the batch window, mid-incident. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9bbf7a56da71d304_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.22, 0.61, 0.16, 0.0, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: in production only, during the morning shift. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6b9eb51da91f5a45_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.69, 0.28, 0.02, 0.01], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: in production only, during the holiday freeze. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_63045fc69664036c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.01, 0.71, 0.28], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: over the last hour, while legacy systems are still active. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e12976042ae8335e_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Service catalog-sync flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: across all regions, shortly after a software update. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b8671d192b8b5dec_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.2, 0.78, 0.02], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: across all regions, while legacy systems are still active. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_91e6bbc9724f18e3_n", "kind": "noul", "options": ["false", "true"], "target": [0.69, 0.31], "state": "The log shipper matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: during the batch window, during an external partner integration. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4634ee08a504a0fb_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.85, 0.13, 0.01, 0.01], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: across all regions, during the holiday freeze. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d627863a23bc4ed5_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: in production only, during peak load. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cbcdafe7fa93bd97_n", "kind": "noul", "options": ["false", "true"], "target": [0.46, 0.54], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: over the last hour, while legacy systems are still active. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_15cf87675cd63644_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.22, 0.72, 0.05], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: across all regions, during the morning shift. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ee7816cd9003d341_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: in production only, while legacy systems are still active. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1cb8e128731420f4_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, with staffing at reduced levels. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_db824cfa84c7161b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.16, 0.61, 0.23, 0.0, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: during the batch window, during an external partner integration. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a92c71772c3e6fd8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.2, 0.76, 0.02, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: in production only, while on-call rotation changed. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_198397f6e8c8771d_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aaaf68cecbab1d7f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.35, 0.55, 0.08, 0.02], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: across all regions, as part of a compliance sweep. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1798fa40e847b9e8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.2, 0.79, 0.01], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, while legacy systems are still active. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e7c18444cda0eae9_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: during the batch window, as part of a compliance sweep. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_726b819525d6cb0c_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: during the batch window, during a scheduled maintenance window. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_084ff4ce18527269_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.59, 0.4, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: across all regions, while legacy systems are still active. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_da1cce04235ca6f4_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.02, 0.38, 0.57, 0.03], "state": "The log shipper correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: in production only, shortly after a software update. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9369bd6376078484_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Service catalog-sync correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: during the batch window, shortly after a software update. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4c4aecf64f40f659_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: across all regions, immediately after go-live. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e41ece981bb0294d_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: over the last hour, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_79e2542a894980f9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.02, 0.41, 0.54, 0.02], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: across all regions, during the morning shift. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e5deae37445dc8b7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.37, 0.61, 0.01], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the holiday freeze. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6d68242c40d9de68_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "The log shipper lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: over the last hour, while legacy systems are still active. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aa42fc42c8404956_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.94, 0.05, 0.0, 0.01], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: in production only, under an active deadline. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5e946035baf33d20_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the holiday freeze. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_88c5e3292af1da06_n", "kind": "noul", "options": ["false", "true"], "target": [0.49, 0.51], "state": "The log shipper matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: across all regions, as part of a compliance sweep. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_07155236268c03f8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.08, 0.85, 0.07], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during the system migration. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_545525135e4bbee4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.1, 0.72, 0.17, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: over the last hour, while on-call rotation changed. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f83298ba3113b514_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.65, 0.29, 0.06, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: in production only, at the end of the fiscal period. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_303e9f767d4dd8c7_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.18, 0.79, 0.02], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: across all regions, shortly after a software update. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4e147ada80a8dcdb_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.18, 0.17, 0.04, 0.61], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: during the batch window, following a recent audit. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0170bdf896694eb8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.64, 0.33, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during the system migration. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ae322b5b8bb607cc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.26, 0.73, 0.01], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during the morning shift. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a4235990da8291af_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.84, 0.14, 0.01, 0.01], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: across all regions, while on-call rotation changed. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_865bb4d160eec35f_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: during the batch window, while legacy systems are still active. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cb6fd6bb89e5b8ca_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.89, 0.08, 0.0, 0.03], "state": "The log shipper shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_67e63af1cf794458_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.38, 0.55, 0.07, 0.0, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, with staffing at reduced levels. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e128f1c870538474_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.4, 0.59, 0.01], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during normal operations. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_47dd1685305608f5_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.81, 0.15, 0.03, 0.01], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: in production only, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f595ca5db9d813c1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.13, 0.82, 0.05], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during the holiday freeze. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2936ceb17d733c3c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.78, 0.19, 0.03, 0.0], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: in production only, with staffing at reduced levels. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_02b13446645be3cd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.14, 0.71, 0.14, 0.0], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: in production only, with staffing at reduced levels. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_095a09003f8d7b71_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.77, 0.2, 0.03, 0.0], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: in production only, with staffing at reduced levels. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_38d1bb546dca96c7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.1616, 0.8182, 0.0202], "state": "The metrics pipeline lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: in production only, at the end of the fiscal period. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aefdb47bbdf8fa78_n", "kind": "noul", "options": ["false", "true"], "target": [0.59, 0.41], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: during the batch window, with staffing at reduced levels. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c31bb85dc7450e2d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.47, 0.47, 0.0, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: across all regions, while on-call rotation changed. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1469da638a7fa7a5_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.63, 0.3, 0.06, 0.01], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: in production only, during the holiday freeze. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0d53771924d6971a_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, following a recent audit. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_85688f9763147841_n", "kind": "noul", "options": ["false", "true"], "target": [0.9, 0.1], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: over the last hour, shortly after a software update. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_321389d3b31aa722_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.14, 0.83, 0.03], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally flags a step-function change in error slope. Context: during the batch window, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_508c80b4f8c4e90e_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, immediately after go-live. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b346462eb9530065_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.42, 0.41, 0.12, 0.05], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during normal operations. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_47332bf69763991b_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: in production only, mid-incident. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3dbcbe75b3cbf9dc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.7, 0.28, 0.0], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: over the last hour, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d7d47c83f6586b9a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.79, 0.18, 0.0], "state": "The metrics pipeline shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: in production only, during an external partner integration. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_996cbf04f5330895_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.02, 0.64, 0.33, 0.01], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: during the batch window, while on-call rotation changed. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_828b4494a8f3b38f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.19, 0.74, 0.06, 0.01], "state": "Service catalog-sync shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: during the batch window, following a recent audit. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_79e208fcf5e75713_n", "kind": "noul", "options": ["false", "true"], "target": [0.63, 0.37], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: across all regions, at the end of the fiscal period. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_26e332c0615f3a4a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.74, 0.03, 0.2], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: over the last hour, shortly after a software update. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b370d7b306469c20_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.14, 0.82, 0.04], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: in production only, during an external partner integration. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_868bc1367e40c7b1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.81, 0.18, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: in production only, while legacy systems are still active. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cb27d2b12a4d0655_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.55, 0.44, 0.0], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: in production only, during the system migration. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_adbd78996de24721_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.26, 0.5, 0.22, 0.02], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: in production only, immediately after go-live. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_468ca58642b7f647_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.54, 0.41, 0.02, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, with staffing at reduced levels. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_28a2965115a15381_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.86, 0.12, 0.02, 0.0], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: over the last hour, with staffing at reduced levels. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eda7644c1f10379a_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "Service catalog-sync flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: across all regions, during the holiday freeze. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6ecd546ed440f92d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.45, 0.54, 0.01], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, mid-incident. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4793d6c74c3499f4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.52, 0.37, 0.06, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during the morning shift. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b198d34bc3990fb9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.03, 0.19, 0.29, 0.42, 0.06, 0.01], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: over the last hour, as part of a compliance sweep. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_28a2965115a15381_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: over the last hour, with staffing at reduced levels. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cc5ed267b9aaa650_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.06, 0.68, 0.25, 0.0], "state": "The log shipper correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: in production only, under reduced staffing. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca4d74b0fce0bbe4_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.35, 0.43, 0.21, 0.01], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: during the batch window, while on-call rotation changed. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_de7a0cbacbca0cea_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.21, 0.77, 0.02], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: across all regions, mid-incident. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cc7a5a80bb6cb130_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.67, 0.32, 0.0], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: over the last hour, while on-call rotation changed. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3c94befa6c593780_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.62, 0.1, 0.02, 0.26], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during peak load. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3fab96fe7c171b12_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.55, 0.37, 0.03, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: across all regions, under an active deadline. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_91e6bbc9724f18e3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.52, 0.45, 0.01], "state": "The log shipper matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: during the batch window, during an external partner integration. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cb4796f58d149b75_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.25, 0.52, 0.22, 0.0, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: in production only, during the system migration. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_faa0c9d12b8ff945_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: over the last hour, immediately after go-live. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_26667c85f5dd2d6a_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: during the batch window, under reduced staffing. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b18d2feb847fa4ff_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.19, 0.76, 0.04], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the quarterly review. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7cdb1dc3dd91c005_n", "kind": "noul", "options": ["false", "true"], "target": [0.5, 0.5], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: over the last hour, as part of a compliance sweep. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_76588361c48cd90d_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: in production only, under reduced staffing. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f9bde606977d991d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.06, 0.87, 0.07], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during normal operations. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_15d41388f85a1729_n", "kind": "noul", "options": ["false", "true"], "target": [0.43, 0.57], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: over the last hour, under an active deadline. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5cfefea696488038_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.27, 0.54, 0.04, 0.15], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: during the batch window, as part of a compliance sweep. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8abcef8b15663aa6_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.98, 0.0, 0.0, 0.02], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, while on-call rotation changed. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_62ccc306f912a489_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.11, 0.73, 0.15, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: during the batch window, as part of a compliance sweep. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fb1ae7baec9a0c5a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.3, 0.69, 0.01], "state": "The metrics pipeline flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: in production only, immediately after go-live. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d129e39265375f82_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.06, 0.49, 0.34, 0.11, 0.0, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: across all regions, with staffing at reduced levels. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9c23c2dc47f95729_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.19, 0.07, 0.31, 0.43], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, following a recent audit. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2630bb2524a5d830_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.1, 0.85, 0.05], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: in production only, under reduced staffing. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_91a289f380986db0_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: in production only, during normal operations. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3d831cd6f7b6b5d4_n", "kind": "noul", "options": ["false", "true"], "target": [0.52, 0.48], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: during the batch window, at the end of the fiscal period. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_119e9cdd197fe522_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.13, 0.84, 0.03], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, at the end of the fiscal period. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3698195d1535c683_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0202, 0.1717, 0.5657, 0.2323, 0.0101], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: across all regions, during the system migration. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c24e74df9fbf66d1_n", "kind": "noul", "options": ["false", "true"], "target": [0.51, 0.49], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: during the batch window, at the end of the fiscal period. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0904929391d47070_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: in production only, under an active deadline. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_246297b575a73e5b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.19, 0.78, 0.03], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during the system migration. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2fd2970ca94bf937_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, immediately after go-live. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_637fa3b187aa6c15_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "The log shipper returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, shortly after a software update. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ec734d72ffc801ad_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.03, 0.05, 0.48, 0.42, 0.01], "state": "Service catalog-sync correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: over the last hour, as part of a compliance sweep. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_afe0382cc9655d87_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.57, 0.41, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: across all regions, with a new vendor onboarded. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_043b3dfbb10dd9a3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.07, 0.86, 0.07], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during the quarterly review. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_94eb784ba3ff68d0_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: over the last hour, under an active deadline. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_de55e33435b76019_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.04, 0.91, 0.05], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: in production only, under an active deadline. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f59dfb4b64ed591d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.25, 0.68, 0.01, 0.06], "state": "Service catalog-sync shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: in production only, with staffing at reduced levels. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_01b253b5b4a26597_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.07, 0.24, 0.32, 0.37], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: during the batch window, during the holiday freeze. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4f52de9c02c184ee_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.42, 0.44, 0.12, 0.0], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: in production only, under reduced staffing. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4209233e4843f18f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.29, 0.7, 0.01], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during normal operations. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0c09cb7e594778ed_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.97, 0.02, 0.0, 0.01], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, while on-call rotation changed. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_039f2146f7a14c26_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.36, 0.36, 0.23, 0.05], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the system migration. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_913b4247c0a78821_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.2, 0.75, 0.04, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: during the batch window, with a new vendor onboarded. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_db34284446ab4d26_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.1, 0.38, 0.47, 0.05, 0.0], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during an external partner integration. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c9de22acbee7c4dc_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "Node pgsql-14 flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: in production only, immediately after go-live. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fe6798482bfc6dea_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.04, 0.72, 0.24, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: during the batch window, at the end of the fiscal period. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_adbd78996de24721_n", "kind": "noul", "options": ["false", "true"], "target": [0.54, 0.46], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: in production only, immediately after go-live. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bd68a52483624d46_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.04, 0.34, 0.61, 0.01], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1855d0d3b8c06bef_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.88, 0.0, 0.01, 0.11], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: during the batch window, during peak load. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c0a45cdb89379103_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.36, 0.61, 0.01], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: across all regions, while on-call rotation changed. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_45b5b5d537acd377_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.4, 0.3, 0.01, 0.29], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: during the batch window, with staffing at reduced levels. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ef60e75566756c76_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: in production only, with staffing at reduced levels. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_01a35b27674392a1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0404, 0.5556, 0.3333, 0.0707, 0.0], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, with a new vendor onboarded. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_74db072d9fbe9f88_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.34, 0.66, 0.0], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: in production only, at the end of the fiscal period. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9c6de1d6662acc5b_n", "kind": "noul", "options": ["false", "true"], "target": [0.9, 0.1], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally matches last Tuesday's incident signature. Context: over the last hour, under reduced staffing. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_74f8f8d935a47cd0_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.53, 0.41, 0.04, 0.02], "state": "The metrics pipeline flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: across all regions, during normal operations. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5c8c03f883a7b3d0_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.22, 0.04, 0.48, 0.26], "state": "The metrics pipeline correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7b5966e621aeef56_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.38, 0.03, 0.37, 0.22], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: over the last hour, during the holiday freeze. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_115d67f8d0032042_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_495764ea71f54e80_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.53, 0.47, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: over the last hour, immediately after go-live. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_559a73ced4aba2d2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.09, 0.04, 0.23, 0.64], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: over the last hour, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2f6747ae1b83b3ed_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.12, 0.32, 0.09, 0.47], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: during the batch window, mid-incident. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c7e1db94774d2b39_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.23, 0.73, 0.03], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: during the batch window, at the end of the fiscal period. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ede64889bb55c0c4_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.02, 0.61, 0.37, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: over the last hour, during the quarterly review. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2be32b3d16b19764_n", "kind": "noul", "options": ["false", "true"], "target": [0.38, 0.62], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: across all regions, at the end of the fiscal period. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ebbd793f2d5b5fc3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.07, 0.62, 0.27, 0.01], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: during the batch window, during a scheduled maintenance window. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_262558387e04415f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.11, 0.88, 0.0], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a86692e2e4667077_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.77, 0.22, 0.0], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: across all regions, during the system migration. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dec1b0bdd7cc54bf_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.53, 0.44, 0.02], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: across all regions, following a recent audit. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cc149a3eb4870e24_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.88, 0.11, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: over the last hour, during normal operations. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_15ef3693a09d8090_n", "kind": "noul", "options": ["false", "true"], "target": [0.22, 0.78], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, under reduced staffing. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9d04f1361b0be460_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.18, 0.13, 0.22, 0.47], "state": "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, as part of a compliance sweep. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eda7644c1f10379a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.07, 0.46, 0.44, 0.03, 0.0], "state": "Service catalog-sync flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: across all regions, during the holiday freeze. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_62180e0ed67f55af_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.2, 0.69, 0.08, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: across all regions, while on-call rotation changed. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a8b2dca32536fb49_n", "kind": "noul", "options": ["false", "true"], "target": [0.2, 0.8], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_58fd5b58415fc8b7_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.64, 0.34, 0.02, 0.0], "state": "The metrics pipeline shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: during the batch window, during normal operations. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_74161e49d0e4cf6c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.17, 0.8, 0.03], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during the quarterly review. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2d8d9da10247eb1b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.36, 0.56, 0.08, 0.0, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: during the batch window, while on-call rotation changed. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b8cf061fdcdcaecc_n", "kind": "noul", "options": ["false", "true"], "target": [0.55, 0.45], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: over the last hour, at the end of the fiscal period. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4dd7a46f2bf092d4_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "The log shipper returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: across all regions, during peak load. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cb209b96c2f7ac33_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.44, 0.47, 0.08, 0.01], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: over the last hour, shortly after a software update. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_781e354bbbdaa175_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.25, 0.43, 0.24, 0.08], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: over the last hour, while legacy systems are still active. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_262c83ad778ebde9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.5, 0.37, 0.11, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: across all regions, during the holiday freeze. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d1dfcd4b3972e086_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "The log shipper shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: in production only, with staffing at reduced levels. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_59418a57a146b061_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: during the batch window, mid-incident. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a0ea99df027a094b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.0, 0.03, 0.92], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: over the last hour, mid-incident. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7025d60160a8628e_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: during the batch window, under an active deadline. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dc3510bf787a8839_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: in production only, under an active deadline. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cde254bd49761764_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: over the last hour, following a recent audit. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e930831482b59e58_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: in production only, under an active deadline. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_183f3f116dbd9a55_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.26, 0.63, 0.09, 0.0], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: over the last hour, following a recent audit. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_02cdf1d88104f089_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.03, 0.2, 0.28, 0.42, 0.07, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: across all regions, following a recent audit. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3abd2ad4f9802b2c_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: over the last hour, during an external partner integration. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f19f77177f7bd9a7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.13, 0.83, 0.04], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: during the batch window, mid-incident. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4dc26a73df75a210_n", "kind": "noul", "options": ["false", "true"], "target": [0.63, 0.37], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: over the last hour, during the quarterly review. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_76b761f30a9a7c18_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.71, 0.28, 0.0], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: over the last hour, under reduced staffing. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_189f4549a0c9d2e2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.3, 0.57, 0.11, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: during the batch window, during the system migration. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_622ae85dc4e3b148_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The metrics pipeline lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: during the batch window, as part of a compliance sweep. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e422908a07b68972_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.56, 0.42, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: across all regions, during the holiday freeze. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1855d0d3b8c06bef_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.16, 0.77, 0.05, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: during the batch window, during peak load. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a8e9686b9604d1b9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.14, 0.01, 0.1, 0.75], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: across all regions, during the quarterly review. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fed5e0810b51ddc1_n", "kind": "noul", "options": ["false", "true"], "target": [0.9, 0.1], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: in production only, during a scheduled maintenance window. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e9562cb147245077_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.49, 0.43, 0.07, 0.01], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: in production only, during the system migration. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e07935bdabd6ece5_n", "kind": "noul", "options": ["false", "true"], "target": [0.47, 0.53], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: over the last hour, mid-incident. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b02f6c792641cd74_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.69, 0.25, 0.02, 0.0], "state": "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, during an external partner integration. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3e141ec8bff8cbe0_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.91, 0.06, 0.02, 0.01], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: over the last hour, during the system migration. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_800d6f67edc05fbe_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.07, 0.81, 0.12], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: during the batch window, under an active deadline. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_907ebda9248a50ee_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.07, 0.83, 0.09, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: over the last hour, following a recent audit. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e41ae89748af4833_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.2, 0.66, 0.13, 0.0], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: across all regions, under reduced staffing. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c264d463301bf161_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.02, 0.59, 0.37], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: during the batch window, while on-call rotation changed. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b1b90eb819201eea_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.08, 0.87, 0.05], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, under an active deadline. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aa5dbb280d093479_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: over the last hour, as part of a compliance sweep. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c837223c011ee32f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.22, 0.19, 0.01, 0.58], "state": "The log shipper reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: over the last hour, during the quarterly review. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7b8e4d292498c347_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.65, 0.31, 0.03, 0.01], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: in production only, while on-call rotation changed. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_901674df022a7e68_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "Service catalog-sync correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: across all regions, during peak load. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cc950b503b0b144e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.38, 0.43, 0.17, 0.01], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during the quarterly review. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f914b958e844f363_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.07, 0.86, 0.07], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, following a recent audit. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7989573b8beb385a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.69, 0.01, 0.06, 0.24], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: over the last hour, with staffing at reduced levels. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_75b4fb0e52c01163_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.36, 0.47, 0.13, 0.04], "state": "Service catalog-sync correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: during the batch window, mid-incident. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_312b43ff6569d76b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.8, 0.15, 0.03, 0.02], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during the system migration. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6283304cdd46b91f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.09, 0.77, 0.13, 0.0], "state": "Node pgsql-14 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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_14521ab61a1f1333_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.18, 0.72, 0.1, 0.0, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during a scheduled maintenance window. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4191f7719a18a041_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.56, 0.43, 0.0], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: over the last hour, while on-call rotation changed. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cedfd89ef60b48d1_n", "kind": "noul", "options": ["false", "true"], "target": [0.92, 0.08], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: across all regions, while legacy systems are still active. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_abbb664d3015ac68_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: across all regions, during the system migration. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b7d09fae8fc48d6e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.77, 0.21, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: over the last hour, with a new vendor onboarded. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ce79b3d0b1bba8db_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.45, 0.55, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the quarterly review. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2aa5fbee764fdf57_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during the system migration. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b920d987cb55e4c3_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: during the batch window, while legacy systems are still active. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a649a716eddcc566_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.01, 0.28, 0.69], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: across all regions, under reduced staffing. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_49cd6a50a75c581f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.42, 0.56, 0.01], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during a scheduled maintenance window. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8aee2ec7c43a35af_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.2, 0.77, 0.03, 0.0], "state": "The metrics pipeline shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: in production only, as part of a compliance sweep. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c7beaa610ae1942c_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: in production only, during a scheduled maintenance window. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e4b2b625eb33c08f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.07, 0.53, 0.24, 0.15, 0.01, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: in production only, while legacy systems are still active. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_87ab9afb3a19bbd5_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.02, 0.0, 0.98], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: in production only, immediately after go-live. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b198d34bc3990fb9_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.16, 0.6, 0.23, 0.01], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: over the last hour, as part of a compliance sweep. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ef7da40d716fc88e_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: during the batch window, mid-incident. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6d1f28fdb02a4ab3_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Service catalog-sync flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: during the batch window, under an active deadline. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e5f0b2e1373ee2b2_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, with a new vendor onboarded. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b0c73e6d338917e3_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "The log shipper reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: in production only, mid-incident. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c059b5cb4e6adea1_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: over the last hour, while legacy systems are still active. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_14daed94192bd2d9_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.84, 0.14, 0.01, 0.01], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: during the batch window, during an external partner integration. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8fc8d29a6ad476ea_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.56, 0.43, 0.0], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: across all regions, immediately after go-live. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_32e3f751ca931a42_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.51, 0.47, 0.02, 0.0], "state": "The metrics pipeline shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: in production only, under reduced staffing. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_498c5de0fcaefcc9_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: in production only, during the quarterly review. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b19deea4c8771445_n", "kind": "noul", "options": ["false", "true"], "target": [0.43, 0.57], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: across all regions, while legacy systems are still active. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4a63846f26f48b2f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.08, 0.83, 0.07, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: during the batch window, following a recent audit. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_06101dade5ef5aef_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.0, 0.01, 0.94], "state": "The log shipper returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: across all regions, during the quarterly review. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1392f9f34718911a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.47, 0.46, 0.06, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, immediately after go-live. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ae5e4931ec1281f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.99, 0.0, 0.0, 0.01], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during normal operations. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f99f5730e059bc97_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.09, 0.49, 0.23, 0.19], "state": "Service catalog-sync flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: across all regions, during the system migration. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9eb11a6f64f524af_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: in production only, under reduced staffing. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2ada9b258093da08_n", "kind": "noul", "options": ["false", "true"], "target": [0.38, 0.62], "state": "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.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ecc16c2561349445_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.36, 0.5, 0.09], "state": "The log shipper correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: during the batch window, with a new vendor onboarded. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b4a163a140949f74_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during normal operations. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_164c228273e57223_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: during the batch window, during normal operations. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d17f1c21eb063ef2_n", "kind": "noul", "options": ["false", "true"], "target": [0.19, 0.81], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, mid-incident. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a45690d299e1f2a6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.48, 0.49, 0.01], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: in production only, mid-incident. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f601f758371c811b_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: across all regions, mid-incident. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_39d4be40d71b66b3_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.08, 0.67, 0.21, 0.04], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: over the last hour, shortly after a software update. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d4fa236ca777280f_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: over the last hour, at the end of the fiscal period. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_298edecf69f7d6c6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.63, 0.34, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: across all regions, shortly after a software update. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8f8d028e2e679cad_n", "kind": "noul", "options": ["false", "true"], "target": [0.22, 0.78], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: in production only, with a new vendor onboarded. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_60a4bd2e95944acc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.08, 0.18, 0.62, 0.12, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2c4f7fb030eff125_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.09, 0.65, 0.24, 0.02, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: in production only, while on-call rotation changed. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b14add06f66814ff_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.0, 0.58, 0.41], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: over the last hour, at the end of the fiscal period. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_078416288844daee_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, while on-call rotation changed. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c825576abe7da2bf_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.8, 0.18, 0.01, 0.01], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during the system migration. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c7beaa610ae1942c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.42, 0.56], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: in production only, during a scheduled maintenance window. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8483dec0a643d044_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.92, 0.06, 0.02, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: over the last hour, with staffing at reduced levels. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d11d178801815eb9_n", "kind": "noul", "options": ["false", "true"], "target": [0.7, 0.3], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: over the last hour, with a new vendor onboarded. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b676f78d523d53d7_n", "kind": "noul", "options": ["false", "true"], "target": [0.56, 0.44], "state": "The log shipper matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: during the batch window, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e359ee728df10f92_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.07, 0.83, 0.1, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: across all regions, during peak load. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6604a3f32186c6ea_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.24, 0.69, 0.02, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: in production only, while on-call rotation changed. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_da983fdb8edd947b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.95, 0.0, 0.0, 0.05], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, while legacy systems are still active. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3bcc08748451bc0a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.79, 0.18, 0.01, 0.02], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: over the last hour, shortly after a software update. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9c36bfd60aca0063_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.1616, 0.8182, 0.0202], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during the system migration. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bcd2099fd86ecfb1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.31, 0.67, 0.01], "state": "The log shipper flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: in production only, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7d19172e06b9e542_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.16, 0.8, 0.04], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: in production only, mid-incident. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_26eff6995b692b29_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.39, 0.61, 0.0], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: during the batch window, with staffing at reduced levels. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bf64382602706fab_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.58, 0.41, 0.0], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during an external partner integration. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3b854371d3e92f2d_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, following a recent audit. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_335498e1b7cc01fc_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: across all regions, shortly after a software update. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d793baadbb4826d3_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: across all regions, under reduced staffing. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e7eabd7ebe0b1c6c_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "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, under an active deadline. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7bf34953bd349b2b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.03, 0.6, 0.35, 0.01], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: across all regions, as part of a compliance sweep. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0c09cb7e594778ed_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.02, 0.84, 0.14], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, while on-call rotation changed. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_af24d39172949aa2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.58, 0.41, 0.0], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: during the batch window, following a recent audit. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0158bd7e4d395aa9_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "The log shipper matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: in production only, during the holiday freeze. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4116a2f73272e25f_n", "kind": "noul", "options": ["false", "true"], "target": [0.65, 0.35], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: across all regions, during an external partner integration. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e417c87ce8250017_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.59, 0.39, 0.01], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during normal operations. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_96f3b760ba6bbfd6_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: in production only, during the holiday freeze. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_907ebda9248a50ee_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.15, 0.64, 0.18, 0.03], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: over the last hour, following a recent audit. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e455ff57eb833cdb_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.9394, 0.0505, 0.0, 0.0101], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: during the batch window, under an active deadline. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7dab1716961e82a1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.02, 0.12, 0.83], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: across all regions, following a recent audit. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_24527d2fbc5c5385_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.03, 0.85, 0.12], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, with staffing at reduced levels. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aae910bf328fd59b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.0, 0.05, 0.94, 0.01], "state": "The log shipper returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, with a new vendor onboarded. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_71fea8d702466c2f_n", "kind": "noul", "options": ["false", "true"], "target": [0.38, 0.62], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: across all regions, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7241262bc15b1a69_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during an external partner integration. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9bbefa0ae04944d6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.31, 0.66, 0.02], "state": "The metrics pipeline lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: during the batch window, mid-incident. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6bc42debdc385da9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.25, 0.15, 0.01, 0.59], "state": "The log shipper reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: across all regions, as part of a compliance sweep. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_68595eefb765b625_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: during the batch window, during the quarterly review. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a92c71772c3e6fd8_n", "kind": "noul", "options": ["false", "true"], "target": [0.53, 0.47], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: in production only, while on-call rotation changed. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_79e208fcf5e75713_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.26, 0.72, 0.02], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: across all regions, at the end of the fiscal period. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_067232aae04c8d55_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: in production only, while on-call rotation changed. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0e6ab303437251b8_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: across all regions, following a recent audit. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fec0994ead8e5df1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.29, 0.7, 0.01], "state": "Node pgsql-14 correlates with the vendor status page incident; 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 review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d2656f5195e9fed9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.72, 0.27, 0.0], "state": "The metrics pipeline shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: in production only, while on-call rotation changed. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_95f1be7d1178bb9a_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: over the last hour, during an external partner integration. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0904929391d47070_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.97, 0.03, 0.0, 0.0], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: in production only, under an active deadline. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1e783e44639ee69f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.26, 0.71, 0.02], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, following a recent audit. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0dbb5c90e33dd3d5_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.08, 0.01, 0.15, 0.76], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during the holiday freeze. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d12cea274bfd49a9_n", "kind": "noul", "options": ["false", "true"], "target": [0.52, 0.48], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the morning shift. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9189c80d5dbd2386_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.06, 0.55, 0.03, 0.36], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: across all regions, while on-call rotation changed. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d94eb0cdc616e78b_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "Service catalog-sync flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: across all regions, mid-incident. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_12a453bfcf0b453a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.4, 0.57, 0.01], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: across all regions, at the end of the fiscal period. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f8f8235b3a8ec38e_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: during the batch window, with staffing at reduced levels. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a66f0bc423fce0ec_n", "kind": "noul", "options": ["false", "true"], "target": [0.41, 0.59], "state": "The log shipper shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: across all regions, during the system migration. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_02b09493066ade2d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.26, 0.63, 0.08, 0.0], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: across all regions, shortly after a software update. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0e7dcc3a4ef51be4_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.13, 0.26, 0.02, 0.59], "state": "The log shipper lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: in production only, under an active deadline. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a492552add768170_n", "kind": "noul", "options": ["false", "true"], "target": [0.37, 0.63], "state": "The log shipper shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: across all regions, with a new vendor onboarded. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8632beb8b67996da_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.02, 0.64, 0.33, 0.01], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: across all regions, during an external partner integration. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_48edfc4be1bcbf8a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.73, 0.21, 0.06, 0.0], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, under an active deadline. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cda127205fd949cf_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.15, 0.8, 0.04], "state": "The metrics pipeline 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 supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_61c55b61f014a9a4_n", "kind": "noul", "options": ["false", "true"], "target": [0.2, 0.8], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: in production only, during the morning shift. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_60b5549c677fd27f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.35, 0.62, 0.02], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: during the batch window, mid-incident. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_44153cd37285ec04_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.13, 0.85, 0.01], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during a scheduled maintenance window. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4b726c3ecf66c27d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.06, 0.33, 0.59, 0.02], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during peak load. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_56851c965c8684d8_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.59, 0.4, 0.01, 0.0], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: across all regions, during an external partner integration. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0f8f8be3858de579_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.17, 0.8, 0.03], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during peak load. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c94ccb87b60a2083_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.14, 0.04, 0.11, 0.71], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_42687d3a22a345bf_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.82, 0.15, 0.02, 0.01], "state": "The log shipper shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: over the last hour, shortly after a software update. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fe23c7393e8c5f49_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.22, 0.75, 0.03], "state": "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, immediately after go-live. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_95bd04038fdf849a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.04, 0.66, 0.29, 0.01], "state": "The log shipper returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during peak load. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_14b2d53ae1c71c7b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.1, 0.68, 0.08, 0.14], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: in production only, immediately after go-live. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d47e0c7a0ad5ce67_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.01, 0.82, 0.12], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: across all regions, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1912f80da9967b97_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.77, 0.22, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: in production only, during the system migration. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8abcef8b15663aa6_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, while on-call rotation changed. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ea7a2594578937a9_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.59, 0.29, 0.1, 0.02], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, shortly after a software update. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e4b2b625eb33c08f_n", "kind": "noul", "options": ["false", "true"], "target": [0.47, 0.53], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: in production only, while legacy systems are still active. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f7987fdfe8b283a9_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.02, 0.85, 0.13, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: in production only, at the end of the fiscal period. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_58e5f31dd0809b9e_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: in production only, under an active deadline. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c9532bdbeb0d791b_n", "kind": "noul", "options": ["false", "true"], "target": [0.64, 0.36], "state": "The log shipper correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: in production only, while on-call rotation changed. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e548fc1f86152a88_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.02, 0.22, 0.75], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, with a new vendor onboarded. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_456a1d1c0045078a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.91, 0.09, 0.0, 0.0], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: across all regions, under reduced staffing. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_456c1c11ffdf27f0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.07, 0.64, 0.28, 0.0], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: over the last hour, with a new vendor onboarded. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7087b7c9b084b4b0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.03, 0.86, 0.11], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: in production only, with staffing at reduced levels. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b4c095a048c4a176_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.36, 0.56, 0.06, 0.02, 0.0, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: during the batch window, while on-call rotation changed. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f2c15a53a287c548_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.33, 0.66, 0.01], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: during the batch window, during the system migration. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ad4edc0b0bc17579_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: over the last hour, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d611c31c987a6641_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.21, 0.34, 0.42, 0.03], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during a scheduled maintenance window. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2c4b1e7693cb8450_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: during the batch window, under an active deadline. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_efc8b82559ea5806_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.5, 0.32, 0.13, 0.05], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the system migration. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e8c3a0081e4b3c96_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: across all regions, following a recent audit. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1f9e4a2792794a54_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0202, 0.1313, 0.6768, 0.1717, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: in production only, at the end of the fiscal period. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_726f03a40aadff78_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.67, 0.28, 0.0], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: in production only, as part of a compliance sweep. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dec7802417e327dd_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: across all regions, with staffing at reduced levels. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e4f5c886b58543f5_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: across all regions, with staffing at reduced levels. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d0548f550cd06916_n", "kind": "noul", "options": ["false", "true"], "target": [0.64, 0.36], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during peak load. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_47dd1685305608f5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.3, 0.69, 0.01], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: in production only, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e0ef25e61fe69222_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.81, 0.16, 0.02, 0.01], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, shortly after a software update. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1898397db47dcae0_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.75, 0.01, 0.0, 0.24], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: in production only, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9126f6dc3b53a305_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.25, 0.64, 0.08, 0.0], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: over the last hour, during the morning shift. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bf1d34869654cbbf_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: across all regions, at the end of the fiscal period. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_46b7cda5a15425ce_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: during the batch window, while on-call rotation changed. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_71627c66668d1994_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.12, 0.85, 0.03], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, under an active deadline. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d00afa0f3afc1e73_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.24, 0.64, 0.03, 0.09], "state": "Node pgsql-14 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 operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3698195d1535c683_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: across all regions, during the system migration. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e67257cd6da68a23_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: in production only, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_02786852b037af91_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.26, 0.62, 0.09, 0.0], "state": "The log shipper reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: across all regions, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a21ed9efc4287d98_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.04, 0.08, 0.58, 0.28, 0.01], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: in production only, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_22227024cda67999_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.3, 0.65, 0.03], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: in production only, mid-incident. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca1958eaf1b75b2c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.53, 0.4, 0.06, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the morning shift. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4d28dd10f802b020_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.05, 0.84, 0.11], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d627863a23bc4ed5_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.84, 0.02, 0.0, 0.14], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: in production only, during peak load. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca1c9712099a15f0_n", "kind": "noul", "options": ["false", "true"], "target": [0.44, 0.56], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: during the batch window, shortly after a software update. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca22e8ede04e9aa4_n", "kind": "noul", "options": ["false", "true"], "target": [0.59, 0.41], "state": "The log shipper correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: during the batch window, at the end of the fiscal period. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c87654c53254548b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.29, 0.5, 0.04, 0.17], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: during the batch window, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_524d05f2f50ba232_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.12, 0.43, 0.02, 0.43], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: over the last hour, following a recent audit. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_df16f73c93476cf2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.17, 0.8, 0.01, 0.02], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: in production only, with staffing at reduced levels. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bd45e0b43b9a7789_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "The metrics pipeline shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: over the last hour, shortly after a software update. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7a4631603fa4a7d7_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.03, 0.75, 0.21, 0.01], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: across all regions, under reduced staffing. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9189c80d5dbd2386_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.73, 0.23, 0.01, 0.0], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: across all regions, while on-call rotation changed. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c296b1f8567ca3aa_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "The log shipper shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during peak load. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ed6d02519f6e5bb7_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: across all regions, during peak load. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6768b86a2cdb4545_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.08, 0.2, 0.66, 0.06], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: across all regions, mid-incident. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f7987fdfe8b283a9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.59, 0.36, 0.02, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: in production only, at the end of the fiscal period. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d2d3cb4e87f9d420_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.87, 0.12, 0.01, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: over the last hour, while legacy systems are still active. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d54909cdd49e31c0_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during the quarterly review. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2a84b92a71f7d080_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.68, 0.26, 0.03, 0.03], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: in production only, as part of a compliance sweep. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4fcc40cbf1d9ca28_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.11, 0.75, 0.13, 0.01], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: during the batch window, during an external partner integration. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8d160f4342c8fc09_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.3, 0.68, 0.02], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: in production only, following a recent audit. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4179e23937975218_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.36, 0.4, 0.21, 0.01], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during the holiday freeze. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a8a54bac2816a1a8_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.02, 0.2, 0.74, 0.04], "state": "Service catalog-sync flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: across all regions, during the morning shift. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1d17a2265fb7622d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.24, 0.66, 0.07, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: in production only, during an external partner integration. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b811c3508c7b6a71_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.56, 0.32, 0.09, 0.03], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: across all regions, during the holiday freeze. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b84f6638c72bec27_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.09, 0.68, 0.18, 0.05, 0.0, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d4c7ed56f730f470_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.65, 0.3, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: during the batch window, during a scheduled maintenance window. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e0ef25e61fe69222_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.09, 0.88, 0.03], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, shortly after a software update. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_daabd32aac924cfc_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: in production only, during peak load. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a4378eb2592b221b_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: during the batch window, following a recent audit. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b93b35610674efd5_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.02, 0.46, 0.51], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: in production only, with a new vendor onboarded. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_723c1a63c27ae04d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.66, 0.26, 0.01, 0.07], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: across all regions, under reduced staffing. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dbef714b7c0ecc06_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.08, 0.61, 0.28, 0.03], "state": "Service catalog-sync correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: during the batch window, as part of a compliance sweep. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_693dcb1497790085_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.44, 0.56, 0.0], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: in production only, during the morning shift. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9597cca3e1904f43_n", "kind": "noul", "options": ["false", "true"], "target": [0.71, 0.29], "state": "The log shipper correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: in production only, during peak load. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2953a8e88794cc2d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.09, 0.83, 0.0, 0.08], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, shortly after a software update. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a3ff9c1026560def_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: across all regions, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ac269a201ad11ebb_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.23, 0.52, 0.03, 0.22], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: during the batch window, mid-incident. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_08bf1943832b0ed2_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: over the last hour, while on-call rotation changed. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_75b2a76312b611d0_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: across all regions, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_57634c0496e4f3b5_n", "kind": "noul", "options": ["false", "true"], "target": [0.37, 0.63], "state": "Service catalog-sync shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: over the last hour, under an active deadline. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2f019079094a0bc1_n", "kind": "noul", "options": ["false", "true"], "target": [0.4, 0.6], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during the system migration. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c6375aebe32873e6_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.14, 0.5, 0.35, 0.01], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b4309afdabc04b24_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.59, 0.34, 0.02, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: during the batch window, during the quarterly review. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6ecd546ed440f92d_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, mid-incident. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b315feb1b9118c47_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.27, 0.62, 0.09], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, mid-incident. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f5ef7d7c90540f2e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.5, 0.49, 0.0], "state": "The log shipper flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: during the batch window, following a recent audit. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_397746334308f6d5_n", "kind": "noul", "options": ["false", "true"], "target": [0.62, 0.38], "state": "The log shipper matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: during the batch window, during the system migration. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f987cd45cab45131_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.05, 0.71, 0.23, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f3900f85aac5a6bc_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: in production only, under reduced staffing. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b331cc75576b83ca_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.06, 0.72, 0.21, 0.0], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: during the batch window, with staffing at reduced levels. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_912be7e605d79c22_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.67, 0.02, 0.13, 0.18], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: over the last hour, during an external partner integration. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a2a493ecb5a37652_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.53, 0.43, 0.04, 0.0], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: across all regions, while legacy systems are still active. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d643c372e2ea1da9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.55, 0.43, 0.01], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: during the batch window, with a new vendor onboarded. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_95a5403ad65b1be9_n", "kind": "noul", "options": ["false", "true"], "target": [0.4, 0.6], "state": "Service catalog-sync lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: over the last hour, as part of a compliance sweep. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b9d6206ffd8e306f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.26, 0.73, 0.01], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: during the batch window, during peak load. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b1d2d3b4c9c30330_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during the morning shift. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9f4ef17bace861c4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.08, 0.8, 0.12], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: over the last hour, with a new vendor onboarded. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_83a9c92c56a2b5ec_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.19, 0.6, 0.2, 0.0], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: across all regions, shortly after a software update. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9b43c7032ec1dc83_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.24, 0.64, 0.11, 0.01], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, with staffing at reduced levels. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_59df05b7ff77a1e8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.07, 0.66, 0.25, 0.0], "state": "The log shipper reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: in production only, during a scheduled maintenance window. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_827bf7e6e90a2b23_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: across all regions, immediately after go-live. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7e2fc4b1e9460b24_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the system migration. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d5077479eefccca7_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.54, 0.35, 0.11, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: over the last hour, during an external partner integration. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7cb4e7a980f6d8e0_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "Service catalog-sync shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: across all regions, at the end of the fiscal period. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_43431f65a39921a4_n", "kind": "noul", "options": ["false", "true"], "target": [0.51, 0.49], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, while on-call rotation changed. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0a3bf112b019e62a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.02, 0.79, 0.16, 0.03, 0.0, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: across all regions, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_22e8e2d5ea3a6617_n", "kind": "noul", "options": ["false", "true"], "target": [0.63, 0.37], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, at the end of the fiscal period. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c6ec59909cbfc006_n", "kind": "noul", "options": ["false", "true"], "target": [0.48, 0.52], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: in production only, during normal operations. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3bcc08748451bc0a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.58, 0.41, 0.0], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: over the last hour, shortly after a software update. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a1a3b3e19771d15a_n", "kind": "noul", "options": ["false", "true"], "target": [0.57, 0.43], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: across all regions, as part of a compliance sweep. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8654c89c1a9ce524_n", "kind": "noul", "options": ["false", "true"], "target": [0.21, 0.79], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: over the last hour, during normal operations. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_abc06399bac479f3_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.44, 0.32, 0.02, 0.22], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: over the last hour, with staffing at reduced levels. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b99b08e0bcf7c89f_n", "kind": "noul", "options": ["false", "true"], "target": [0.23, 0.77], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: over the last hour, shortly after a software update. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9ad9fee1a68a23cd_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.03, 0.85, 0.12, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: in production only, at the end of the fiscal period. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_988e171846ddba47_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.46, 0.53, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: across all regions, during peak load. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e7c89786e3fe5f4d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.01, 0.62, 0.37], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: in production only, immediately after go-live. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_62ccc306f912a489_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "Service catalog-sync shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: during the batch window, as part of a compliance sweep. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1cf12e67961973be_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.04, 0.61, 0.35, 0.0], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: across all regions, with staffing at reduced levels. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7cbbc4e97cb3cde0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.29, 0.71, 0.0], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: during the batch window, shortly after a software update. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a41c11967d7e7ce0_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: over the last hour, while legacy systems are still active. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_280735b7c9e3176f_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during the holiday freeze. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4604d758f9ad4c28_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0202, 0.0, 0.0404, 0.9394], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: in production only, while on-call rotation changed. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e94814a507b75df6_n", "kind": "noul", "options": ["false", "true"], "target": [0.51, 0.49], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: over the last hour, at the end of the fiscal period. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c4495876b059c476_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.04, 0.48, 0.47, 0.01], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: across all regions, at the end of the fiscal period. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e626b6f2c18bb8e9_n", "kind": "noul", "options": ["false", "true"], "target": [0.7, 0.3], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: over the last hour, under reduced staffing. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_385c5ca7eb9d1253_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.57, 0.38, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally matches last Tuesday's incident signature. Context: during the batch window, under an active deadline. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_489f26b7fb5967a0_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.2, 0.71, 0.09, 0.0], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: across all regions, as part of a compliance sweep. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2b1854e3c1526efc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.2, 0.77, 0.03], "state": "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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ed6266a6519926a5_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: across all regions, during normal operations. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_042137350dc3700f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.0, 0.19, 0.81], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: in production only, while legacy systems are still active. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c84b9d690d2bb238_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.54, 0.46, 0.0], "state": "Node pgsql-14 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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6251472988c03c1a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.04, 0.74, 0.22], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: over the last hour, mid-incident. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6d1f28fdb02a4ab3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.16, 0.82, 0.02], "state": "Service catalog-sync flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: during the batch window, under an active deadline. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f14800d0a9e642c0_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: during the batch window, with a new vendor onboarded. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bd53fda28e41ed01_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "The log shipper flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, under an active deadline. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_77acdec4c70fcacd_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.02, 0.39, 0.57], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: in production only, at the end of the fiscal period. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b9d6206ffd8e306f_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: during the batch window, during peak load. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e79885baf80439d4_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during the morning shift. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e50961d63803a05f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.18, 0.75, 0.06], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: during the batch window, mid-incident. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_23ee7b85cb1292aa_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: during the batch window, during an external partner integration. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9bf81910b00d1383_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.34, 0.65, 0.01], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during an external partner integration. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3f942772df45ce87_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.19, 0.72, 0.06, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: across all regions, with a new vendor onboarded. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_62c9a27c8b40eeef_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.21, 0.75, 0.03, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: across all regions, during the holiday freeze. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8b076748302085c8_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.84, 0.16, 0.0, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: in production only, while legacy systems are still active. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_18a7d3189732ac20_n", "kind": "noul", "options": ["false", "true"], "target": [0.39, 0.61], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: across all regions, during normal operations. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cc47c4e7cecf99a8_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: in production only, with staffing at reduced levels. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7838ddb82d0abc63_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.0, 0.18, 0.82], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: in production only, during an external partner integration. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_85e42931c51afe9c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.74, 0.24, 0.0], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: during the batch window, during a scheduled maintenance window. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eb0785a3ad41025b_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: in production only, shortly after a software update. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_35cd9c5560429633_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.58, 0.41, 0.0], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: over the last hour, shortly after a software update. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2aab6e54b27b1a57_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "The log shipper correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, under reduced staffing. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_726b819525d6cb0c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.17, 0.25, 0.51, 0.06, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: during the batch window, during a scheduled maintenance window. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bbc960615e52174f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.13, 0.18, 0.6, 0.09, 0.0], "state": "The log shipper correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1dc46f6f845e35c5_n", "kind": "noul", "options": ["false", "true"], "target": [0.23, 0.77], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: across all regions, shortly after a software update. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a945a11450ca4edf_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.88, 0.09, 0.01, 0.02], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: over the last hour, during normal operations. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f35184d970045cfe_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.31, 0.51, 0.14, 0.0], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: over the last hour, immediately after go-live. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dc3f2f13f5e5698e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.15, 0.46, 0.39, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: in production only, during normal operations. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d334d1d6b4e3fd1e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.14, 0.22, 0.02, 0.62], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: over the last hour, immediately after go-live. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_23251dca2b44da43_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "The log shipper matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: in production only, as part of a compliance sweep. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3f778fe2ba4b3d77_n", "kind": "noul", "options": ["false", "true"], "target": [0.43, 0.57], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during a scheduled maintenance window. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_57684952aeeb3e85_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.26, 0.71, 0.03], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: during the batch window, mid-incident. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9bc066b2408f2027_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.04, 0.37, 0.52, 0.06, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: over the last hour, with a new vendor onboarded. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_33f650286cf00f43_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.5, 0.41, 0.01, 0.08], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: during the batch window, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dc6bf0bdddc100c1_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: in production only, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b52866d0c098e6d9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.29, 0.7, 0.01], "state": "The log shipper flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: over the last hour, under an active deadline. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e67257cd6da68a23_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.54, 0.44], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: in production only, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1fae858c56df14df_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.81, 0.17, 0.0], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: in production only, while legacy systems are still active. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_27cc53b027e09ca5_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.03, 0.35, 0.6], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: during the batch window, following a recent audit. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5a28a39ba932ae33_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.07, 0.43, 0.46, 0.04], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: across all regions, under reduced staffing. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_00d05c0255a343d3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.12, 0.79, 0.09, 0.0, 0.0], "state": "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, during normal operations. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_150a8aba43875b5a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.92, 0.07, 0.0, 0.01], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: over the last hour, at the end of the fiscal period. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f850a4e079dac855_n", "kind": "noul", "options": ["false", "true"], "target": [0.91, 0.09], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, under an active deadline. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3ea1f47f29d357cf_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.18, 0.09, 0.25, 0.48], "state": "The log shipper 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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_65f8f8d04abdd31e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.69, 0.29], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: over the last hour, during the quarterly review. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ba86727b0ec7d77_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.24, 0.62, 0.11, 0.0], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: across all regions, during the system migration. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d39e9991e68ccf11_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.41, 0.59, 0.0], "state": "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 holiday freeze. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1e62dc24510c8cf2_n", "kind": "noul", "options": ["false", "true"], "target": [0.43, 0.57], "state": "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.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e5eaefe4a478309a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.61, 0.34, 0.0], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f1d87591c1b90962_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.61, 0.39, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: across all regions, during the system migration. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_686f61fe8a96cbf8_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: over the last hour, while on-call rotation changed. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b1be6df2ebc315ab_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "The log shipper reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: over the last hour, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d97af7d578684446_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.23, 0.72, 0.01, 0.04], "state": "Service catalog-sync shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: over the last hour, during the quarterly review. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bbcb92db03191654_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.14, 0.29, 0.47, 0.09, 0.01], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: in production only, during a scheduled maintenance window. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_96f3b760ba6bbfd6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.16, 0.78, 0.05], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: in production only, during the holiday freeze. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3597cd06d52cbaf3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.17, 0.81, 0.02], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally flags a step-function change in error slope. Context: during the batch window, following a recent audit. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_02786852b037af91_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.02, 0.5, 0.43], "state": "The log shipper reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: across all regions, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3d6e20396755e444_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.0, 0.01, 0.98], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: during the batch window, while on-call rotation changed. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0dbed6a05e4c07b6_n", "kind": "noul", "options": ["false", "true"], "target": [0.68, 0.32], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during peak load. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7a4fca3f6c20158d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.85, 0.13, 0.02, 0.0], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: over the last hour, under reduced staffing. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5d4c4393282ef084_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.84, 0.01, 0.0, 0.15], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: across all regions, while legacy systems are still active. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9331bece1dc7261e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.53, 0.46, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: during the batch window, under reduced staffing. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8a32fe9806674f79_n", "kind": "noul", "options": ["false", "true"], "target": [0.66, 0.34], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, following a recent audit. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_78dcad523bfdb292_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: during the batch window, while legacy systems are still active. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e321896e5ce0ac32_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "The metrics pipeline correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: over the last hour, during the quarterly review. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7b26e564228e0ff7_n", "kind": "noul", "options": ["false", "true"], "target": [0.54, 0.46], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: in production only, while legacy systems are still active. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b6646de0624ade50_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.29, 0.33, 0.31, 0.07], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: during the batch window, under an active deadline. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7415478494cc2803_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.33, 0.61, 0.03], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: in production only, mid-incident. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_319f9cf43356acd3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.83, 0.16, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: over the last hour, shortly after a software update. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9003bd7796e32e34_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.07, 0.37, 0.3, 0.24, 0.02, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: over the last hour, as part of a compliance sweep. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2c4c219826f98fd4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.72, 0.25, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: during the batch window, with a new vendor onboarded. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1bbc907370dde24d_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, following a recent audit. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ebbd793f2d5b5fc3_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.1, 0.41, 0.48, 0.01], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: during the batch window, during a scheduled maintenance window. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a13ebcb97ef90039_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "The metrics pipeline lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: in production only, during the morning shift. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b37c42f380f7793a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.53, 0.31, 0.15, 0.01], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: during the batch window, during the system migration. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_01360f5c6c52459a_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "The log shipper shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: across all regions, during the holiday freeze. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_07812d4509d1fe25_n", "kind": "noul", "options": ["false", "true"], "target": [0.53, 0.47], "state": "The log shipper shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: in production only, following a recent audit. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_75dea4ef284873bb_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.29, 0.18, 0.17, 0.36], "state": "Service catalog-sync 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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_98a33d5a00a81ead_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.63, 0.37, 0.0], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the holiday freeze. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ff697dca850bf64c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.72, 0.28, 0.0], "state": "The log shipper flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: over the last hour, following a recent audit. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_27f8c7f7a360b745_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.16, 0.63, 0.19, 0.0], "state": "The log shipper reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: in production only, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_af123adb5b01c0a7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.17, 0.18, 0.5, 0.13, 0.01], "state": "Service catalog-sync correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: during the batch window, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eac204ed8d795d76_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "The log shipper reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: across all regions, during normal operations. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0e88d6bc464c7ea2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.3, 0.56, 0.11, 0.03, 0.0, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: in production only, during the quarterly review. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_70d49e49e5f42c45_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The metrics pipeline shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: over the last hour, with staffing at reduced levels. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4eb9efe535c10960_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.89, 0.06, 0.04, 0.01], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during the system migration. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f4894d5eda76e607_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.14, 0.27, 0.49, 0.1, 0.0], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: over the last hour, during the quarterly review. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7bf2dabf5c336abd_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.79, 0.19, 0.01, 0.01], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, while legacy systems are still active. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6c6ec1dac82fd662_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during the holiday freeze. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_10d200dfe972c644_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during the morning shift. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_22555bf02c5aeb9a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.17, 0.8, 0.03], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: during the batch window, during the holiday freeze. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c4b0beaae4f8368e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.54, 0.38, 0.08, 0.0, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: during the batch window, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_47332bf69763991b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.0, 0.01, 0.97], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: in production only, mid-incident. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3dc0a10afb49324b_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during the holiday freeze. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1bb2241d0d53075a_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The log shipper correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, following a recent audit. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f0a83b00a2361202_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.45, 0.52, 0.01], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: in production only, shortly after a software update. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_47d8e2c3d0a7cd34_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.6, 0.39, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: over the last hour, at the end of the fiscal period. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d80df85652d31fc7_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: over the last hour, as part of a compliance sweep. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9793ccba1a389059_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, while on-call rotation changed. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_56282e68afd98729_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.1, 0.65, 0.2], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: across all regions, during an external partner integration. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e02693215c5a56a6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.06, 0.65, 0.19, 0.1, 0.0, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: over the last hour, under an active deadline. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9cf1c0aef69ec2f9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.49, 0.45, 0.0, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: over the last hour, during the quarterly review. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_08f3b6f97e294c26_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.51, 0.47, 0.02, 0.0], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: in production only, as part of a compliance sweep. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_62dd3bead9de260c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.28, 0.01, 0.41, 0.3], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during an external partner integration. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0a8fd9e5cb6a9b71_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.75, 0.23, 0.0], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: over the last hour, during the system migration. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_399c65059fa89b66_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: over the last hour, shortly after a software update. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_43431f65a39921a4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.12, 0.49, 0.38, 0.01, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, while on-call rotation changed. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1ab978e412d8c9cd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.29, 0.64, 0.07, 0.0, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: across all regions, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d39e9991e68ccf11_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.73, 0.23, 0.04, 0.0], "state": "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 holiday freeze. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_88c12e1079c6885d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.27, 0.71, 0.02], "state": "Service catalog-sync shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: in production only, mid-incident. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_59cf98ce906ed507_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.12, 0.54, 0.31, 0.01], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: in production only, following a recent audit. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_166acde8bedd4350_n", "kind": "noul", "options": ["false", "true"], "target": [0.69, 0.31], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: in production only, during a scheduled maintenance window. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4f6f81272d9c789c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.84, 0.01, 0.01, 0.14], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: in production only, during a scheduled maintenance window. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dc615a99273670b9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.07, 0.22, 0.56, 0.14, 0.01], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: over the last hour, as part of a compliance sweep. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2384e81482b7f811_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.18, 0.79, 0.03], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: during the batch window, under reduced staffing. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d9612a4b0af2378d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.04, 0.7, 0.26, 0.0], "state": "The metrics pipeline shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: in production only, with staffing at reduced levels. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6c73f330ad126ed5_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.6, 0.36, 0.04, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: in production only, during the holiday freeze. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_08456920e5af2956_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.93, 0.05, 0.02, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: across all regions, immediately after go-live. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_53bd5fb5f4404f6e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.21, 0.57, 0.19, 0.03], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, as part of a compliance sweep. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_44153cd37285ec04_n", "kind": "noul", "options": ["false", "true"], "target": [0.7, 0.3], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during a scheduled maintenance window. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_edda8a8f5b22325b_n", "kind": "noul", "options": ["false", "true"], "target": [0.44, 0.56], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: across all regions, during an external partner integration. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ed91f24332039d71_n", "kind": "noul", "options": ["false", "true"], "target": [0.21, 0.79], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: in production only, immediately after go-live. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_88848cce2fd90675_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.77, 0.2, 0.0], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the quarterly review. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7997112f6790fb6e_n", "kind": "noul", "options": ["false", "true"], "target": [0.69, 0.31], "state": "The log shipper flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: in production only, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_434119ea1bca8f26_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.11, 0.48, 0.39, 0.02, 0.0], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: during the batch window, at the end of the fiscal period. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_924f19e9c3bb8928_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.93, 0.05, 0.01, 0.01], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during peak load. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fdb77e1552a4c52e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.55, 0.42, 0.02, 0.01], "state": "Service catalog-sync lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: across all regions, as part of a compliance sweep. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_870e806889159e99_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.84, 0.14, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: during the batch window, while legacy systems are still active. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_545525135e4bbee4_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: over the last hour, while on-call rotation changed. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4e147ada80a8dcdb_n", "kind": "noul", "options": ["false", "true"], "target": [0.4, 0.6], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: during the batch window, following a recent audit. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_70b0c11c7c3d0a6a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.21, 0.65, 0.13, 0.01], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: across all regions, with a new vendor onboarded. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bb8e94f5641551b6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.68, 0.31, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: in production only, shortly after a software update. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ad575291779696e4_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.03, 0.08, 0.84], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during the morning shift. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_912be7e605d79c22_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.16, 0.58, 0.22, 0.01], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: over the last hour, during an external partner integration. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f866b1f076c5de6b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.01, 0.03, 0.58, 0.37, 0.0], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: in production only, during peak load. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9bf3d029423f50a4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.01, 0.02, 0.49, 0.46, 0.01], "state": "The log shipper matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: over the last hour, during the system migration. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d47e0c7a0ad5ce67_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: across all regions, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_47c96f85a4777ca0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.68, 0.31, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: across all regions, during the quarterly review. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_067232aae04c8d55_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.31, 0.68, 0.01], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: in production only, while on-call rotation changed. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_04071ec7e18e13fb_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.14, 0.57, 0.28], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: across all regions, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d25dd9b6cd657aaa_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.05, 0.61, 0.3, 0.04], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: across all regions, during the holiday freeze. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_53bd5fb5f4404f6e_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, as part of a compliance sweep. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_320b1face70bdbab_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.02, 0.77, 0.2, 0.01], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: across all regions, as part of a compliance sweep. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_88c5e3292af1da06_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.02, 0.1, 0.53, 0.32, 0.03, 0.0], "state": "The log shipper matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: across all regions, as part of a compliance sweep. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9422c330c4144ac1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.39, 0.5, 0.09, 0.02], "state": "The log shipper matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during a scheduled maintenance window. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f987cd45cab45131_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.96, 0.0, 0.0, 0.04], "state": "The log shipper lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c0333d784473ef7d_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, with a new vendor onboarded. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_12c0033c065969bc_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.72, 0.14, 0.09], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: during the batch window, shortly after a software update. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c8208014ec0d2544_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.28, 0.59, 0.12, 0.01, 0.0, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during normal operations. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eb6ea5606f235807_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: over the last hour, mid-incident. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7b0b3acd5cd2fcd8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.1, 0.73, 0.17, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, at the end of the fiscal period. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6a030c6611ccec05_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.09, 0.68, 0.21, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: in production only, as part of a compliance sweep. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_166ecf06764ef351_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.39, 0.01, 0.28, 0.32], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during the system migration. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_14fbc33d362fb441_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: over the last hour, during a scheduled maintenance window. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d98299418be0b287_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.03, 0.87, 0.09, 0.01], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, while legacy systems are still active. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ef782d9abc028e10_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.36, 0.62, 0.01], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: across all regions, shortly after a software update. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8700788eb164467b_n", "kind": "noul", "options": ["false", "true"], "target": [0.68, 0.32], "state": "The log shipper correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during a scheduled maintenance window. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d105d2157f67a8ec_n", "kind": "noul", "options": ["false", "true"], "target": [0.67, 0.33], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: over the last hour, at the end of the fiscal period. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ff1d5a64a457a3aa_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.33, 0.66, 0.01], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: in production only, at the end of the fiscal period. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c1db3e5c7ee66cf0_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.71, 0.25, 0.03, 0.01], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, shortly after a software update. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a7a560de3d09e969_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.13, 0.83, 0.04], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: during the batch window, mid-incident. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2979a26c36e1934b_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, following a recent audit. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1a15c6baf15cb8f1_n", "kind": "noul", "options": ["false", "true"], "target": [0.64, 0.36], "state": "The log shipper shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: across all regions, during the morning shift. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_44a353ca23a860f5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.14, 0.79, 0.05, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: during the batch window, during the quarterly review. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_39aeb46f116e7d32_n", "kind": "noul", "options": ["false", "true"], "target": [0.37, 0.63], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during the quarterly review. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_62bcb6b28c7f1ffa_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.59, 0.01, 0.07, 0.33], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during the quarterly review. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cf671050542e265a_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during the system migration. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ffd54db1c302abbc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.74, 0.23, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: over the last hour, immediately after go-live. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_88da666dc225276b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.02, 0.14, 0.72, 0.11, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: across all regions, shortly after a software update. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_237ffdae5de8e1b8_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "Service catalog-sync lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: across all regions, under reduced staffing. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4823de6a955f1d2b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.02, 0.14, 0.2, 0.54, 0.1, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: during the batch window, during the quarterly review. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c2ab008b554293c9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.36, 0.63, 0.01], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: over the last hour, shortly after a software update. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_43825edcc4ba19cf_n", "kind": "noul", "options": ["false", "true"], "target": [0.63, 0.37], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: during the batch window, under reduced staffing. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9d6fda594fc58b03_n", "kind": "noul", "options": ["false", "true"], "target": [0.43, 0.57], "state": "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.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_db578b9fcef917f2_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.94, 0.04, 0.02, 0.0], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: over the last hour, while on-call rotation changed. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1e989f2d86f5bad6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.74, 0.25, 0.0], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: across all regions, at the end of the fiscal period. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8fa997048398aa91_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.46, 0.36, 0.15, 0.03], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: across all regions, during the holiday freeze. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b6ca9a63aae78ed9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.99, 0.0, 0.01], "state": "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, shortly after a software update. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e6f0be0ee26cd291_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Node pgsql-14 flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: during the batch window, at the end of the fiscal period. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2e569a7241a0d41a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.95, 0.0, 0.01, 0.04], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: across all regions, during normal operations. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f600703ac21f8796_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The log shipper shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during an external partner integration. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_08ef56c0f80ef673_n", "kind": "noul", "options": ["false", "true"], "target": [0.63, 0.37], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: during the batch window, under reduced staffing. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c91f7595dfbae429_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.14, 0.78, 0.07], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: in production only, under an active deadline. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c186c37c55649496_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.46, 0.49, 0.04, 0.01], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, following a recent audit. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e6ef5e60b1f1a875_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: across all regions, mid-incident. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c4f2d21e5c9a9086_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.46, 0.5, 0.03, 0.01], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: in production only, shortly after a software update. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aebf9812fc5d1d09_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.5, 0.44, 0.06, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: in production only, during peak load. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3d8d0b2a52741e1d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.25, 0.54, 0.19, 0.01, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: across all regions, immediately after go-live. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2f52988d4facffdb_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: during the batch window, under reduced staffing. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_badd27f64c12a035_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "The log shipper correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: over the last hour, under reduced staffing. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2c007464ba666846_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.56, 0.34, 0.09, 0.01], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: across all regions, during the system migration. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6995010547d0c99f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.07, 0.76, 0.16, 0.01], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: over the last hour, shortly after a software update. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cb7b14485d6ed187_n", "kind": "noul", "options": ["false", "true"], "target": [0.21, 0.79], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: over the last hour, at the end of the fiscal period. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_802319a40832449d_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: across all regions, during the morning shift. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0a3bf112b019e62a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.0, 0.26, 0.73, 0.01], "state": "The log shipper lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: across all regions, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b66270a8773a47b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.69, 0.3, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: over the last hour, during the morning shift. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a40b864642d07031_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "The log shipper shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: in production only, during peak load. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_02b5e2018ace817e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.09, 0.01, 0.36, 0.54], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the quarterly review. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d4df17ac883772e5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.45, 0.53, 0.01], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: over the last hour, during peak load. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_137f7e268343db03_n", "kind": "noul", "options": ["false", "true"], "target": [0.4, 0.6], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during normal operations. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fbe55c81d3079ca8_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.41, 0.54, 0.01, 0.04], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: over the last hour, at the end of the fiscal period. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_80576ba9774ab77f_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, shortly after a software update. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_07e7afa087fbece1_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: across all regions, with staffing at reduced levels. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9d24cfbcc94b5141_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: in production only, under reduced staffing. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_27cc53b027e09ca5_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: during the batch window, following a recent audit. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e774b490445dda10_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.04, 0.7, 0.25, 0.01], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: over the last hour, at the end of the fiscal period. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dec1b0bdd7cc54bf_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.43, 0.48, 0.04, 0.0], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: across all regions, following a recent audit. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cce14a3df4f4873c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.43, 0.57, 0.0], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: during the batch window, with staffing at reduced levels. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_632090753f0a2f31_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.78, 0.19, 0.0], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: over the last hour, during the holiday freeze. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eacad67578dcca81_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.24, 0.59, 0.17, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: in production only, following a recent audit. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fca00df26f3262e6_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.52, 0.11, 0.04, 0.33], "state": "Node pgsql-14 flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: over the last hour, under an active deadline. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_55cf5bca8329e2c0_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: in production only, under an active deadline. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_afcdc63909944fdd_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.83, 0.15, 0.01, 0.01], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e94814a507b75df6_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.29, 0.1, 0.01, 0.6], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: over the last hour, at the end of the fiscal period. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b6119e2a56046946_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.95, 0.03], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: during the batch window, during an external partner integration. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2be32b3d16b19764_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.03, 0.43, 0.52, 0.01], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: across all regions, at the end of the fiscal period. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_50b255c398ac3750_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.36, 0.61, 0.02], "state": "The log shipper correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, as part of a compliance sweep. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_725e9aaf55d22216_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.04, 0.92, 0.04, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: in production only, shortly after a software update. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7f682765c191dd2e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.65, 0.31, 0.04, 0.0], "state": "The log shipper matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: over the last hour, during the system migration. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6c0b27c6f8493c29_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.39, 0.59, 0.01], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the holiday freeze. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e869553490e57d4d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.39, 0.25, 0.35], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: during the batch window, shortly after a software update. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_08c4879e270f947b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.06, 0.07, 0.83, 0.04], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: over the last hour, during an external partner integration. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_84a63d46b5ba5077_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.01, 0.95, 0.04], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally matches last Tuesday's incident signature. Context: in production only, during an external partner integration. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6c0589a8f7672ca7_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "Service catalog-sync 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 operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dca80036fc27653c_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: over the last hour, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d43b58a53f957b11_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.48, 0.49, 0.01, 0.02], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: during the batch window, during peak load. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_321389d3b31aa722_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally flags a step-function change in error slope. Context: during the batch window, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_205e052ad6391b62_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.68, 0.29, 0.03, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: across all regions, while on-call rotation changed. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fa63b45c46118f50_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.28, 0.58, 0.11, 0.03], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, while legacy systems are still active. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9cfb4f84f058c79b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.38, 0.62, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during an external partner integration. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dd3166445708db4c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.9, 0.07, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: in production only, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0f0db5e05eecc9fd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.37, 0.61, 0.01], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: in production only, at the end of the fiscal period. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_53bd5fb5f4404f6e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.6, 0.33, 0.03, 0.0], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, as part of a compliance sweep. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_984688f750256d98_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.06, 0.01, 0.79, 0.14], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ccc5bf228c13a1d7_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.19, 0.02, 0.06, 0.73], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: across all regions, during the system migration. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_657ddbe0fe7a038b_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during the morning shift. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e82dbf70cbabfdee_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.21, 0.77, 0.02], "state": "The log shipper matches last Tuesday's incident signature; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during peak load. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_20bc6be64bf68f40_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.03, 0.67, 0.29, 0.0], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: during the batch window, with a new vendor onboarded. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0accffe82f8b423e_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Service catalog-sync shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: across all regions, under an active deadline. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_095a09003f8d7b71_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: in production only, with staffing at reduced levels. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0abe31ed0208d777_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: across all regions, during normal operations. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f3ead914998e1fee_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.17, 0.8, 0.03], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: over the last hour, with staffing at reduced levels. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_643ee87e852015ef_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: over the last hour, with a new vendor onboarded. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_65f8f8d04abdd31e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.34, 0.64, 0.01], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: over the last hour, during the quarterly review. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_95e3d80e01e422c9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.84, 0.14, 0.0, 0.02], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: during the batch window, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ec2d1f99856a8865_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.49, 0.5, 0.0], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: over the last hour, while on-call rotation changed. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d12e6c036d8cb1b0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.09, 0.3, 0.56, 0.04, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally matches last Tuesday's incident signature. Context: across all regions, during normal operations. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_043f4d0be564ac57_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.25, 0.74, 0.01], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: in production only, during the quarterly review. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cc5ed267b9aaa650_n", "kind": "noul", "options": ["false", "true"], "target": [0.65, 0.35], "state": "The log shipper correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: in production only, under reduced staffing. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_350b71dbffba259a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.07, 0.33, 0.55], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: in production only, following a recent audit. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_da1cce04235ca6f4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.13, 0.69, 0.14, 0.0], "state": "The log shipper correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: in production only, shortly after a software update. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d0548f550cd06916_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.41, 0.44, 0.1, 0.05], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during peak load. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bdf27e54313a0029_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.7, 0.18, 0.11, 0.01], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_60a31bf32c9102ad_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.28, 0.72, 0.0], "state": "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 system migration. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f35184d970045cfe_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: over the last hour, immediately after go-live. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_78b4ef98d6b25c50_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.14, 0.63, 0.17, 0.06], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: over the last hour, during the system migration. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0170bdf896694eb8_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Service catalog-sync lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during the system migration. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2526672dbfe5fd95_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.21, 0.66, 0.13, 0.0, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: over the last hour, with a new vendor onboarded. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b2a7a3827320d39d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.05, 0.53, 0.4, 0.02], "state": "The log shipper flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: during the batch window, at the end of the fiscal period. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_42691896f323a491_n", "kind": "noul", "options": ["false", "true"], "target": [0.55, 0.45], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: in production only, during a scheduled maintenance window. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_79230360afe6ef9f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.58, 0.39, 0.03, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: across all regions, while on-call rotation changed. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4ba14d8db16d29ae_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: across all regions, shortly after a software update. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3d86c711b5b863b9_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.21, 0.62, 0.16, 0.01], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, shortly after a software update. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0e033fed180f3a11_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.22, 0.06, 0.04, 0.68], "state": "Service catalog-sync flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: in production only, during a scheduled maintenance window. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_99faf32861a9e7ae_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.33, 0.0, 0.16, 0.51], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: in production only, during a scheduled maintenance window. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2190c61ba35fcca9_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: during the batch window, during peak load. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8ca21b3ed75eccfe_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: over the last hour, immediately after go-live. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ad080c35e4c0c6ad_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: in production only, under reduced staffing. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_627fc1d0bb79ef39_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: in production only, with staffing at reduced levels. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9374e027075bf9a1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.32, 0.59, 0.08, 0.01], "state": "The log shipper matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, under reduced staffing. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d2dd5a21e104d954_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.78, 0.2, 0.02, 0.0], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, following a recent audit. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_af1e756533f5b96e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.81, 0.15, 0.03, 0.01], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: over the last hour, mid-incident. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c9b7dfe4a12581b6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.37, 0.61, 0.01], "state": "The log shipper correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: in production only, with staffing at reduced levels. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_59c8b931e491b654_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.41, 0.54, 0.04], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: in production only, during a scheduled maintenance window. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6d3b3129ce2d6da5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.31, 0.49, 0.19, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during the quarterly review. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_19d01b965d9c85b5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.33, 0.64, 0.02], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: across all regions, with a new vendor onboarded. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1b98c22b19ae758b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.89, 0.1, 0.0, 0.01], "state": "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, with a new vendor onboarded. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cce6e77b0ca1ddc9_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "The log shipper reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: across all regions, immediately after go-live. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2308046dcdeaacee_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.19, 0.47, 0.33, 0.01, 0.0], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: during the batch window, during the system migration. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7a4fca3f6c20158d_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: over the last hour, under reduced staffing. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eb97c04614140738_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "The log shipper correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: during the batch window, as part of a compliance sweep. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_db824cfa84c7161b_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: during the batch window, during an external partner integration. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7ab84fd2ae8f6b8a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.55, 0.44, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: over the last hour, with a new vendor onboarded. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bef9b191e1d0c70e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.02, 0.59, 0.38, 0.0], "state": "Service catalog-sync flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during a scheduled maintenance window. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d31da26f5f7e79e9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.29, 0.7, 0.01], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_12fd89e71c258770_n", "kind": "noul", "options": ["false", "true"], "target": [0.7, 0.3], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: across all regions, during peak load. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_85b4a7de55c6bae8_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "Service catalog-sync correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: over the last hour, under reduced staffing. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e79885baf80439d4_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.15, 0.56, 0.28, 0.01], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during the morning shift. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4fa9c64ff2b94b10_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.08, 0.83, 0.09, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: over the last hour, during an external partner integration. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0904929391d47070_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.01, 0.74, 0.25], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: in production only, under an active deadline. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e638212cd6faff73_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.09, 0.51, 0.36, 0.01], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: across all regions, as part of a compliance sweep. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6fbc8c0a75976305_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.75, 0.24, 0.0], "state": "Service catalog-sync flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: during the batch window, while on-call rotation changed. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a49f409c5b768314_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.05, 0.91, 0.04], "state": "Service catalog-sync flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: in production only, with a new vendor onboarded. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5526a3623cfc4bd4_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.81, 0.14, 0.04, 0.01], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: during the batch window, mid-incident. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9374e027075bf9a1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.56, 0.42, 0.0], "state": "The log shipper matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, under reduced staffing. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_681e0bca6ec34e87_n", "kind": "noul", "options": ["false", "true"], "target": [0.44, 0.56], "state": "Service catalog-sync lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: during the batch window, as part of a compliance sweep. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d5bebe1b0247211c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.64, 0.34, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: during the batch window, during peak load. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cd8f12694c9c6955_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "Service catalog-sync shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: across all regions, immediately after go-live. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_35f4912499cd4b94_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "The log shipper reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: in production only, at the end of the fiscal period. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_91e8ebd752ab9302_n", "kind": "noul", "options": ["false", "true"], "target": [0.57, 0.43], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: in production only, following a recent audit. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_267f0e5806da91a6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.02, 0.83, 0.15], "state": "The log shipper reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, under an active deadline. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8d7ca293241c40aa_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.37, 0.61, 0.01], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: over the last hour, immediately after go-live. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6ebf8468cfa344aa_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.31, 0.62, 0.06, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: in production only, during peak load. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dad03a35041a0fdb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.0404, 0.8182, 0.1414], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: across all regions, shortly after a software update. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5ea705954bb70a25_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.37, 0.5, 0.07, 0.0], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: across all regions, during the quarterly review. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5df2f3e2efe8689c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.12, 0.52, 0.32, 0.03, 0.0], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: across all regions, during the quarterly review. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1b9d809ba005a2d4_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.04, 0.56, 0.39], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: in production only, during the system migration. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2dd8e73ba12f8e55_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, immediately after go-live. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5ffe803a29767ed2_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.0, 0.23, 0.76, 0.01], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: over the last hour, during normal operations. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5a76d617f90304a7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.62, 0.37, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during normal operations. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_116e048371e09d7f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.29, 0.69, 0.02], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: over the last hour, following a recent audit. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e41c8641faf49f24_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.31, 0.67], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: in production only, with a new vendor onboarded. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9a775181659353d2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.04, 0.92, 0.04, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: over the last hour, while on-call rotation changed. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ba4e20eb6272cef5_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.8, 0.0, 0.01, 0.19], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, while on-call rotation changed. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7796777046413d21_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.02, 0.74, 0.21], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: in production only, during a scheduled maintenance window. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2def5e77f6641a87_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during peak load. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e41c06d8279b9423_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.44, 0.08, 0.45], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: over the last hour, following a recent audit. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4e272a1b98d4e9c8_n", "kind": "noul", "options": ["false", "true"], "target": [0.7, 0.3], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during the quarterly review. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4e55f4c9c32e5985_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: across all regions, during peak load. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ebb9dd2fb6281821_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.61, 0.38, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during the system migration. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b050c0116fc42956_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.49, 0.39, 0.05, 0.07], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: in production only, under reduced staffing. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ffd54db1c302abbc_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: over the last hour, immediately after go-live. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dec7fc902d1dcf13_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.15, 0.82, 0.03], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: over the last hour, with staffing at reduced levels. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_596463621ef4ec46_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: over the last hour, during the system migration. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ea8e29d7c98ac6fd_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.76, 0.23, 0.0, 0.01], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: in production only, as part of a compliance sweep. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_41bc23ba4909fb60_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.18, 0.73, 0.08], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: across all regions, during normal operations. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_620918a8930534d4_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.01, 0.09, 0.85], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: in production only, while on-call rotation changed. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_23aaf4cf1d709fe9_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "Service catalog-sync shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: over the last hour, under an active deadline. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9e32191cad420082_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.51, 0.48, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: during the batch window, under an active deadline. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dd41e431a4723440_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.23, 0.76, 0.01], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the system migration. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_06c2c055397aa08e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.59, 0.39, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during the holiday freeze. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e39a6feee2dfa616_n", "kind": "noul", "options": ["false", "true"], "target": [0.38, 0.62], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: during the batch window, shortly after a software update. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fb8f4c761e0bb2e8_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.39, 0.52, 0.08, 0.01], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: over the last hour, during peak load. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b8903fa1b9b72984_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "The log shipper correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: over the last hour, during peak load. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3053364cf37a1a7b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.11, 0.83, 0.06], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: during the batch window, immediately after go-live. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2e5b071fecbe1572_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.03, 0.64, 0.32, 0.0], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: over the last hour, during a scheduled maintenance window. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6ae34dee4512a1fb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.23, 0.75, 0.02], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: over the last hour, during the system migration. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fbecda3cf5eef00f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.31, 0.68, 0.01], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: over the last hour, while on-call rotation changed. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cffdee363df54ae2_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, with staffing at reduced levels. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5d2ddc53f9f631cb_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.15, 0.1, 0.2, 0.55], "state": "The metrics pipeline shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: in production only, during the system migration. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2014496a9dce3ec4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.11, 0.65, 0.21, 0.01], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: across all regions, shortly after a software update. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b7518a39270d96e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.4, 0.58, 0.01], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: during the batch window, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6a6a0535e93a2fc7_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: during the batch window, following a recent audit. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_570c66f20c5b16c3_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eef5fb97e67f8ba4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.29, 0.7, 0.01], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, at the end of the fiscal period. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2f9b1b3ed919ff21_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.77, 0.17, 0.05, 0.01], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during the system migration. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_64ce0de3a1e55b5b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.0, 0.06, 0.94], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e5e471ada76e6ef2_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: in production only, with staffing at reduced levels. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e29c8667c4bd6feb_n", "kind": "noul", "options": ["false", "true"], "target": [0.58, 0.42], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: across all regions, at the end of the fiscal period. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6d479b6637d93b78_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.61, 0.38, 0.0], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, while on-call rotation changed. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_442baca2c631d496_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.06, 0.52, 0.41, 0.0], "state": "The log shipper correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: across all regions, during peak load. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6873d2081505ef72_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.45, 0.53, 0.01], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during normal operations. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3afeab695af83995_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.23, 0.04, 0.04, 0.69], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: across all regions, during normal operations. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d664c425658d2667_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: across all regions, during the morning shift. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e6617da963f1d26f_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during normal operations. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_37bc51b60bb6e4be_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.1, 0.84, 0.06], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: across all regions, with staffing at reduced levels. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_858e4da56f7a910f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.11, 0.39, 0.48, 0.02, 0.0], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: during the batch window, while on-call rotation changed. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b429f5acc715ca5_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: over the last hour, during the system migration. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2dc8704e2a26c3de_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.02, 0.45, 0.51, 0.01], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: across all regions, shortly after a software update. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_95692f55dad78102_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.11, 0.11, 0.42, 0.36], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during an external partner integration. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_53c4e587a82efb74_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.42, 0.12, 0.01, 0.45], "state": "The log shipper reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: in production only, during peak load. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_234b755e1196f814_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.76, 0.21, 0.03, 0.0], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the morning shift. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c432f5788f6952ab_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.97, 0.03, 0.0, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: across all regions, with staffing at reduced levels. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5df8e2890c108205_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "The log shipper flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: in production only, during a scheduled maintenance window. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cd5d347ba0050b66_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the morning shift. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cc996809a5a87881_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.21, 0.54, 0.22, 0.03], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: during the batch window, during a scheduled maintenance window. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cd5d347ba0050b66_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.44, 0.55, 0.0], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the morning shift. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d06c94469d5ef1e8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.05, 0.7, 0.25, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during peak load. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_97f7e13f477c367e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.69, 0.29, 0.01, 0.01], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: across all regions, shortly after a software update. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_69c45c3caf7d632b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.49, 0.5, 0.0], "state": "The log shipper reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: over the last hour, during normal operations. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_60b5549c677fd27f_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: during the batch window, mid-incident. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_12bc36631f4bb638_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: over the last hour, shortly after a software update. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9f856652dd67bde0_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.0, 0.04, 0.91, 0.05], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: during the batch window, during the holiday freeze. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fb63a6a08bdeefc0_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.03, 0.02, 0.93], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: in production only, following a recent audit. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_82dc141b100e1979_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.06, 0.0, 0.71, 0.23], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: during the batch window, with staffing at reduced levels. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4a05de57be0e607f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.01, 0.27, 0.72], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: over the last hour, following a recent audit. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5dda34188ae3e327_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.35, 0.52, 0.1, 0.03], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, immediately after go-live. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_23f612548dbcc878_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "The log shipper 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 supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c70871659c3c8ff5_n", "kind": "noul", "options": ["false", "true"], "target": [0.23, 0.77], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: during the batch window, shortly after a software update. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4667fbaf100c17ee_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.15, 0.82, 0.03], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: during the batch window, under an active deadline. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ede2d168903bcca5_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.58, 0.07, 0.04, 0.31], "state": "The log shipper shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during normal operations. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_328d8f56b5d3d0ad_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.08, 0.27, 0.6, 0.05], "state": "The log shipper reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: across all regions, mid-incident. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_558898bab8511fd8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.65, 0.34, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: during the batch window, with staffing at reduced levels. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f5557f278413d3bb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.04, 0.65, 0.31, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: across all regions, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6360776fb1e276c2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.08, 0.01, 0.88, 0.03], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: over the last hour, following a recent audit. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e5537aeb17739c05_n", "kind": "noul", "options": ["false", "true"], "target": [0.44, 0.56], "state": "The metrics pipeline flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: in production only, at the end of the fiscal period. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_70af3442ff22c418_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.37, 0.21, 0.39, 0.03], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: across all regions, under reduced staffing. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cc149a3eb4870e24_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: over the last hour, during normal operations. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8115efd3c40ab8c2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.4, 0.53, 0.01, 0.0], "state": "The metrics pipeline flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: during the batch window, under reduced staffing. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8d6150966e165d09_n", "kind": "noul", "options": ["false", "true"], "target": [0.9, 0.1], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, under an active deadline. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ac514e4d4f94e3b8_n", "kind": "noul", "options": ["false", "true"], "target": [0.67, 0.33], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: over the last hour, during the holiday freeze. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_556fea0b65fd6993_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: across all regions, during normal operations. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5e69a82c6a192a1a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.05, 0.42, 0.51, 0.02], "state": "The metrics pipeline flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: over the last hour, while legacy systems are still active. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7d84ac1cd5cc9acd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.33, 0.64, 0.02], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during a scheduled maintenance window. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7110795baa64fd8a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.66, 0.31, 0.03, 0.0], "state": "The metrics pipeline flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: in production only, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2d8d9da10247eb1b_n", "kind": "noul", "options": ["false", "true"], "target": [0.4, 0.6], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: during the batch window, while on-call rotation changed. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2d836752e01e8e6f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.27, 0.53, 0.2, 0.0], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during an external partner integration. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9f6a3e70d748fd2c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.45, 0.31, 0.18, 0.06], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during the holiday freeze. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_64d7a37807ff6ffd_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "The log shipper shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: across all regions, mid-incident. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bac91635a97f1d1b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.44, 0.56, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: across all regions, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7d1add9a463ea921_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.85, 0.15, 0.0, 0.0], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, under reduced staffing. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ab3cf9c690704b74_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.08, 0.56, 0.35, 0.01], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: in production only, at the end of the fiscal period. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6b243ccf8d56a9ed_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.87, 0.01, 0.01, 0.11], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: in production only, as part of a compliance sweep. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bef9b191e1d0c70e_n", "kind": "noul", "options": ["false", "true"], "target": [0.47, 0.53], "state": "Service catalog-sync flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during a scheduled maintenance window. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9917f62ce2c7095a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.79, 0.19, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: across all regions, at the end of the fiscal period. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_53532c3c65dabec7_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "The log shipper reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: across all regions, at the end of the fiscal period. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3afd33334f10c617_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.07, 0.45, 0.44, 0.04, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: over the last hour, mid-incident. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_89926e2d3926f815_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.42, 0.57, 0.01], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: across all regions, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6010e8b7375581f9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.75, 0.2, 0.01, 0.04], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: during the batch window, shortly after a software update. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e5deae37445dc8b7_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.61, 0.33, 0.03, 0.03], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the holiday freeze. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1435a99ea7828863_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "The log shipper returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: over the last hour, with staffing at reduced levels. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e2ebd70cdc50776f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.37, 0.51, 0.12, 0.0, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: during the batch window, during the quarterly review. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d370006c9d89eb00_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: over the last hour, shortly after a software update. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0f012f587812b931_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.02, 0.48, 0.46], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: over the last hour, under reduced staffing. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b08fc882d4e3a646_n", "kind": "noul", "options": ["false", "true"], "target": [0.38, 0.62], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, while legacy systems are still active. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f8f438425cb40297_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.36, 0.62, 0.01], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during peak load. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d4abfded1cdfc7aa_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, at the end of the fiscal period. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f174c7163b0a91f6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.41, 0.52, 0.04, 0.0], "state": "The log shipper reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: over the last hour, during the morning shift. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_41e667b383ea89bd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.74, 0.21, 0.0], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: over the last hour, during a scheduled maintenance window. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_22109dc3b16c5d1e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.44, 0.49, 0.05, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: over the last hour, while legacy systems are still active. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_64bdcffa6827d158_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.05, 0.83, 0.11, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: across all regions, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_edda8a8f5b22325b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.08, 0.47, 0.43, 0.02, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: across all regions, during an external partner integration. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ebb9bb4ea7be31bc_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.02, 0.48, 0.49], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: in production only, immediately after go-live. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9a3a2daba1880fa2_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.97, 0.01, 0.0, 0.02], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: in production only, mid-incident. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_387c4b551ce1141d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.2828, 0.0101, 0.0303, 0.6768], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: in production only, mid-incident. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_321983923609e9b6_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.87, 0.01, 0.0, 0.12], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, as part of a compliance sweep. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0c09cb7e594778ed_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, while on-call rotation changed. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2be32b3d16b19764_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.56, 0.36, 0.07, 0.01], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: across all regions, at the end of the fiscal period. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_456fb1d34f094150_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.07, 0.81, 0.12, 0.0, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during normal operations. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b2a7a3827320d39d_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "The log shipper flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: during the batch window, at the end of the fiscal period. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca0f5d777372d7aa_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.06, 0.0, 0.02, 0.92], "state": "The log shipper returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: across all regions, mid-incident. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_04680219b6ac46a2_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: during the batch window, during a scheduled maintenance window. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4e0e9f5518bfb29f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.75, 0.25, 0.0], "state": "The log shipper flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: over the last hour, during the morning shift. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_adb7bff20102cc07_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, following a recent audit. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3b17ac5a265499ad_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.02, 0.32, 0.63, 0.03], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: during the batch window, under reduced staffing. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_880097f4020db1e5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.62, 0.35, 0.0], "state": "Service catalog-sync correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: in production only, while on-call rotation changed. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_166ecf06764ef351_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during the system migration. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_61c55b61f014a9a4_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.81, 0.16, 0.01, 0.02], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: in production only, during the morning shift. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e0a6ae3682bed2d2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.21, 0.64, 0.1, 0.05, 0.0, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: in production only, during the morning shift. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3d2cc8f4a2d083b8_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: across all regions, under an active deadline. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e95ec390dfc96a85_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.26, 0.72, 0.02], "state": "The log shipper shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: in production only, mid-incident. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e8c6231769567f90_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.07, 0.27, 0.63, 0.03], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: in production only, during the holiday freeze. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f64ea47ebec1b909_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.53, 0.46, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: during the batch window, under reduced staffing. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d06c94469d5ef1e8_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.79, 0.03, 0.01, 0.17], "state": "The log shipper returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during peak load. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_539feeb361eb70c1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.12, 0.57, 0.3, 0.01], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during normal operations. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c848524b4459a509_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.4, 0.48, 0.11, 0.01], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the morning shift. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eba233a568cd214d_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: during the batch window, with staffing at reduced levels. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_04e8f5cd7285c3f5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.47, 0.47, 0.01], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: over the last hour, as part of a compliance sweep. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2a02ff15271547cf_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.29, 0.46, 0.22, 0.03], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5c9857624b6b7335_n", "kind": "noul", "options": ["false", "true"], "target": [0.2, 0.8], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: across all regions, during the system migration. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_14521ab61a1f1333_n", "kind": "noul", "options": ["false", "true"], "target": [0.48, 0.52], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during a scheduled maintenance window. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_33ba0018b4ef327e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.49, 0.45, 0.03, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: in production only, following a recent audit. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c19c21d2a608da19_n", "kind": "noul", "options": ["false", "true"], "target": [0.38, 0.62], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: across all regions, while on-call rotation changed. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_93db406618a09300_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.79, 0.16, 0.04, 0.01], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: over the last hour, during peak load. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cf2527fbacc2c34a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.04, 0.32, 0.63, 0.01], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: during the batch window, during a scheduled maintenance window. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3c3dce01b583d115_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.63, 0.26, 0.09, 0.02], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, as part of a compliance sweep. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a7c7f2b922c368fe_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.38, 0.03, 0.47, 0.12], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: in production only, during the morning shift. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d793467ddf6904ff_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.08, 0.75, 0.17, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c4d9aeb8a7b0b45a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.58, 0.41, 0.0], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: during the batch window, during an external partner integration. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9af65b32402d2397_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "Service catalog-sync lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: during the batch window, during a scheduled maintenance window. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3f778fe2ba4b3d77_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.12, 0.61, 0.25, 0.02, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during a scheduled maintenance window. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fa23cf9ae529de09_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: in production only, shortly after a software update. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9eeefcaf0aee41a9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.41, 0.58, 0.0], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: over the last hour, shortly after a software update. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fa4b475e98f9119a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.41, 0.13, 0.02, 0.44], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3c8054a56a7360ee_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.66, 0.26, 0.06, 0.02], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: in production only, during an external partner integration. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_387c4b551ce1141d_n", "kind": "noul", "options": ["false", "true"], "target": [0.69, 0.31], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: in production only, mid-incident. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_edda8a8f5b22325b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.77, 0.21], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: across all regions, during an external partner integration. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_597f037047e1ee8a_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fca00df26f3262e6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.28, 0.64, 0.05, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: over the last hour, under an active deadline. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0341c9777930bf4e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.29, 0.67, 0.03], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during the holiday freeze. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1a55c7879e72cfc6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.27, 0.7, 0.03], "state": "The log shipper correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: in production only, mid-incident. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_705ec9a7d02ee5ab_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.1, 0.4, 0.48, 0.02], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: during the batch window, during a scheduled maintenance window. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cb7a1f2564ba7d2e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.99, 0.01, 0.0, 0.0], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, immediately after go-live. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9d07c7c3ca39f49a_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, shortly after a software update. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_08c4879e270f947b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.49, 0.51, 0.0], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: over the last hour, during an external partner integration. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5882da9e497469a1_n", "kind": "noul", "options": ["false", "true"], "target": [0.68, 0.32], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: in production only, as part of a compliance sweep. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_57a5c8d70a36cbf7_n", "kind": "noul", "options": ["false", "true"], "target": [0.42, 0.58], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: in production only, while legacy systems are still active. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ccccf8ecaca8821c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.76, 0.21, 0.01, 0.02], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: in production only, during peak load. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cd44d6d05ff598c1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.71, 0.28, 0.01, 0.0], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: across all regions, with staffing at reduced levels. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c4fe45ed4aba8c30_n", "kind": "noul", "options": ["false", "true"], "target": [0.5, 0.5], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: during the batch window, following a recent audit. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_755a10131e0603f8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.11, 0.85, 0.04], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: in production only, during an external partner integration. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d5ccbe15f3edec00_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.0, 0.03, 0.96, 0.01], "state": "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, during a scheduled maintenance window. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_52be48b8f2caf7dc_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.05, 0.71, 0.24, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: over the last hour, following a recent audit. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eb0785a3ad41025b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.64, 0.11, 0.25], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: in production only, shortly after a software update. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ea2bf855f59e3f4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.56, 0.43, 0.0], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: across all regions, under reduced staffing. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_45e77208345803b0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.83, 0.14, 0.0], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during the morning shift. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d856343fe4430ac2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.88, 0.01, 0.06], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: over the last hour, following a recent audit. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2086f85dbeeda4f0_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: in production only, with a new vendor onboarded. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_26667c85f5dd2d6a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.24, 0.7, 0.06, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: during the batch window, under reduced staffing. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_596463621ef4ec46_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.67, 0.32, 0.0], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: over the last hour, during the system migration. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_37e2e80a95b9a970_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.16, 0.02, 0.1, 0.72], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the system migration. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6fb51091ba7bbdc0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.22, 0.77, 0.01], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, while legacy systems are still active. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4191f7719a18a041_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: over the last hour, while on-call rotation changed. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_477dac9879b5628b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.82, 0.15, 0.0], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: during the batch window, while legacy systems are still active. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a3275bad830c6245_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d9d62848c6ae87f0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.66, 0.32, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: in production only, during an external partner integration. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2d836752e01e8e6f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.0, 0.98, 0.01], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during an external partner integration. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_74161e49d0e4cf6c_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during the quarterly review. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b28e2d0ccd3aa9b0_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.02, 0.17, 0.78], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: across all regions, under an active deadline. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_90c6b54ce17e6cbc_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "The log shipper lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: during the batch window, following a recent audit. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f8a81fe24c93b602_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.08, 0.86, 0.06], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, immediately after go-live. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a75162cd3e9a33f0_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.52, 0.16, 0.31], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: during the batch window, shortly after a software update. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d6d83ea1c2e44ed4_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.66, 0.31, 0.03, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: over the last hour, under reduced staffing. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4fd0409603d0714d_n", "kind": "noul", "options": ["false", "true"], "target": [0.41, 0.59], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: across all regions, during the system migration. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ec0f74236b5241f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.46, 0.42, 0.1, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: over the last hour, following a recent audit. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b3a065abe5ac952f_n", "kind": "noul", "options": ["false", "true"], "target": [0.41, 0.59], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: over the last hour, during the system migration. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6ab93b5ad7c4d156_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.04, 0.77, 0.19], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: in production only, mid-incident. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_611781dbf5d6f870_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.57, 0.42, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, following a recent audit. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_581eb6e36d7f091f_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: during the batch window, following a recent audit. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1875f02a27d6242b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.63, 0.34, 0.02], "state": "The log shipper matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: over the last hour, as part of a compliance sweep. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a246203937346e78_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "The log shipper correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: during the batch window, mid-incident. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aac7e59190d56ec7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.23, 0.59, 0.13, 0.0], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: over the last hour, with staffing at reduced levels. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c8d6550a00e3dd9a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.02, 0.65, 0.32, 0.01], "state": "The log shipper returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: across all regions, while legacy systems are still active. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_345914eaa621135a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.09, 0.86, 0.05], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: in production only, under an active deadline. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1e662f3ffa543bd3_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: over the last hour, during an external partner integration. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1a8132136c6768c9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.71, 0.26, 0.0], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: in production only, during the holiday freeze. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_112bccad2b878170_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.92, 0.06, 0.01, 0.01], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during the morning shift. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_39406ae45de15130_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.4, 0.48, 0.1, 0.02], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: during the batch window, as part of a compliance sweep. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ef79b4f0829010d1_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: in production only, with a new vendor onboarded. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dc793a2423dbf41e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.07, 0.03, 0.79, 0.11], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: over the last hour, while legacy systems are still active. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a93ffc9a7eb94c9c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.06, 0.16, 0.31, 0.47], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: across all regions, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c9532bdbeb0d791b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.38, 0.6], "state": "The log shipper correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: in production only, while on-call rotation changed. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9e85c3b0ccf82813_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.58, 0.37, 0.04, 0.01], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, under reduced staffing. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ae9c956bfd8b20c8_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.79, 0.17, 0.01, 0.03], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: across all regions, as part of a compliance sweep. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a63716f851840e37_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: in production only, at the end of the fiscal period. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d91b841ae912b902_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.53, 0.46, 0.0], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: in production only, as part of a compliance sweep. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9c549c42833a7d2d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.02, 0.13, 0.66, 0.17, 0.02, 0.0], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: in production only, during normal operations. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_28ce5a168d2948c9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.32, 0.08, 0.33, 0.27], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the holiday freeze. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_663c06d39654009c_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: over the last hour, during peak load. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_da37e7bdeec730f0_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.11, 0.05, 0.05, 0.79], "state": "The log shipper flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: across all regions, during normal operations. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e08c6b84f129c0ef_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.1, 0.14, 0.15, 0.61], "state": "The log shipper shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: in production only, while legacy systems are still active. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e76253d035ee181b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.53, 0.47, 0.0], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: in production only, shortly after a software update. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_496c99ee79da5311_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.14, 0.49, 0.36, 0.01], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: during the batch window, immediately after go-live. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_14bb8657208eea7e_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "The log shipper correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: in production only, during a scheduled maintenance window. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9c0c0f781124a8fa_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.19, 0.52, 0.02, 0.27], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: across all regions, during a scheduled maintenance window. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a1a3b3e19771d15a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.09, 0.02, 0.01, 0.88], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: across all regions, as part of a compliance sweep. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_037325b106978fda_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b099293a4333e1b1_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "The log shipper correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: over the last hour, under reduced staffing. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_42301bef49629f68_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: in production only, during the quarterly review. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_60f434efdfef0d13_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during the holiday freeze. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4f17ce2244fabb97_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.43, 0.55, 0.01], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: over the last hour, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cf5625720254f9b9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.53, 0.37, 0.07, 0.0], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, following a recent audit. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e8c6231769567f90_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: in production only, during the holiday freeze. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eb150f1628564ea9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.58, 0.39, 0.0], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: across all regions, while on-call rotation changed. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_06db838a044838b2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.29, 0.7, 0.01], "state": "Service catalog-sync correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: during the batch window, during peak load. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7d85d6a60969d515_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: over the last hour, under reduced staffing. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8151614ed408e0bc_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "The log shipper shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: over the last hour, during the system migration. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b0b77bf66bda844_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The log shipper matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: during the batch window, immediately after go-live. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_32ffea3054fc1fd2_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.25, 0.32, 0.34, 0.09], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: during the batch window, under an active deadline. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c892194b64a23f3a_n", "kind": "noul", "options": ["false", "true"], "target": [0.7, 0.3], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: during the batch window, with a new vendor onboarded. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_08bf1943832b0ed2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.56, 0.42, 0.0], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: over the last hour, while on-call rotation changed. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_12d411cbc3e2e6df_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: in production only, during an external partner integration. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_69cb1976f77780b2_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: across all regions, during peak load. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aac77c7dde1aa473_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.22, 0.69, 0.04], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: in production only, during an external partner integration. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cde254bd49761764_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.38, 0.57, 0.01, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: over the last hour, following a recent audit. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_41824fec2c70eead_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.06, 0.78, 0.15, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: during the batch window, during normal operations. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_823c2ef859dc5c5c_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: in production only, as part of a compliance sweep. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aa36a2ba162ebc44_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.09, 0.8, 0.11], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: in production only, mid-incident. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8afe9490163163a5_n", "kind": "noul", "options": ["false", "true"], "target": [0.69, 0.31], "state": "The log shipper flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: across all regions, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_de73388b593aaeef_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: across all regions, under an active deadline. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_49a28c17b6d89e43_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "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.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b1b90eb819201eea_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.53, 0.04, 0.03, 0.4], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, under an active deadline. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4966f68948aa1edd_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.22, 0.76, 0.01], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, at the end of the fiscal period. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2c90bfe51a19f634_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.04, 0.85, 0.11], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: in production only, during the morning shift. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f34761ceb82b0ab0_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.21, 0.27, 0.01, 0.51], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: over the last hour, during normal operations. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_af0a534fc808afa9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.34, 0.63, 0.02], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during a scheduled maintenance window. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6ab93b5ad7c4d156_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: in production only, mid-incident. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_88ea141de90fa34b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.48, 0.37, 0.13, 0.0], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, immediately after go-live. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c1b1c811075a8f55_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: during the batch window, at the end of the fiscal period. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4a939a33ff19ebc4_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.94, 0.06, 0.0, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: in production only, under reduced staffing. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2c4c219826f98fd4_n", "kind": "noul", "options": ["false", "true"], "target": [0.6, 0.4], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: during the batch window, with a new vendor onboarded. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0a7bc4d0e4d42da2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.05, 0.52, 0.41, 0.01], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: in production only, at the end of the fiscal period. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5936a91c770c9731_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.99, 0.0, 0.0, 0.01], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally flags a step-function change in error slope. Context: over the last hour, under an active deadline. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_033149b8bcd98fc1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.12, 0.75, 0.12, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during an external partner integration. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0e5893ed2aba1568_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: over the last hour, during an external partner integration. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b84f6638c72bec27_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dd3166445708db4c_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "The log shipper lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: in production only, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5f18df083fac50c9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.28, 0.65, 0.05, 0.0], "state": "Service catalog-sync flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: in production only, during an external partner integration. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_44872c5979084e16_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.05, 0.67, 0.27, 0.01], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during an external partner integration. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_78b30afe085a4e3c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.17, 0.17, 0.15, 0.51], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally matches last Tuesday's incident signature. Context: across all regions, mid-incident. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f6c88f9551f0205b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.03, 0.35, 0.6], "state": "The log shipper lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: during the batch window, during the holiday freeze. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_99ef288c2e93ce38_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.12, 0.66, 0.22, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: in production only, during the holiday freeze. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ed53c2762bec0dcd_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.46, 0.53, 0.01, 0.0], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: during the batch window, with a new vendor onboarded. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3f7adeb864a7e1f2_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.42, 0.54, 0.03, 0.01], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: in production only, shortly after a software update. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7f42867b99d812f1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.01, 0.7, 0.29], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: across all regions, under an active deadline. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4c3189838fc327dc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.36, 0.35, 0.28, 0.01, 0.0], "state": "The metrics pipeline flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: in production only, during a scheduled maintenance window. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_206be403f749e738_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: across all regions, with staffing at reduced levels. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ab3cf9c690704b74_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: in production only, at the end of the fiscal period. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ff9cb7cda865e323_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.18, 0.75, 0.05, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during normal operations. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b343641b0be50a3_n", "kind": "noul", "options": ["false", "true"], "target": [0.65, 0.35], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: across all regions, during an external partner integration. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_95692f55dad78102_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.25, 0.71, 0.03], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during an external partner integration. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_94c410685d9dcb51_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.0, 0.5, 0.47], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: across all regions, with staffing at reduced levels. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1d8a644ecdddf039_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The log shipper reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: during the batch window, as part of a compliance sweep. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d4abfded1cdfc7aa_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.99, 0.0, 0.0, 0.01], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, at the end of the fiscal period. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fde2bcf5f2bf3e7d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.72, 0.26], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: in production only, at the end of the fiscal period. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ac87df9fb6324d6d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.89, 0.09, 0.0, 0.02], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, while legacy systems are still active. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e244504935e5dee2_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.06, 0.86, 0.07, 0.01], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during the quarterly review. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9369bd6376078484_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.33, 0.66, 0.01], "state": "Service catalog-sync correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: during the batch window, shortly after a software update. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a5ebac9ada98850f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.74, 0.24, 0.02, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: over the last hour, with staffing at reduced levels. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_df7d6d6efb18e11b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.96, 0.0, 0.01, 0.03], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during normal operations. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6d53fb7e00291530_n", "kind": "noul", "options": ["false", "true"], "target": [0.64, 0.36], "state": "Service catalog-sync lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: in production only, shortly after a software update. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e151901d0a38d868_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.13, 0.02, 0.17, 0.68], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: in production only, while legacy systems are still active. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b030858a4608ba2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.07, 0.28, 0.62, 0.03, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: during the batch window, mid-incident. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5ad9ba3b567d3a5f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.37, 0.61, 0.01], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: during the batch window, at the end of the fiscal period. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dd3166445708db4c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.18, 0.02, 0.75], "state": "The log shipper lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: in production only, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3bcc08748451bc0a_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: over the last hour, shortly after a software update. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d3c87cd61b7833da_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.27, 0.7, 0.02], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: over the last hour, following a recent audit. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_988e5797e485e4c0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.21, 0.73, 0.03, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: during the batch window, during the morning shift. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_68e841043ccc5fe5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.21, 0.68, 0.1, 0.01, 0.0], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: in production only, as part of a compliance sweep. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fb04c10f03d2a9e2_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, while legacy systems are still active. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0abe31ed0208d777_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.02, 0.41, 0.55], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: across all regions, during normal operations. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b4c7fe91e9f34870_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.08, 0.32, 0.05, 0.55], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: during the batch window, during normal operations. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_65d420091d685b11_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "The log shipper correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: across all regions, immediately after go-live. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7e4faeaec0b8f83f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.55, 0.39, 0.03, 0.03], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: across all regions, following a recent audit. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4d773927ceb8ea33_n", "kind": "noul", "options": ["false", "true"], "target": [0.71, 0.29], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, immediately after go-live. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3549bc9fbde0f77c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.31, 0.03, 0.04, 0.62], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: over the last hour, under an active deadline. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_92b1f9b106fc6c8b_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, under reduced staffing. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8fc965df426e2755_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.21, 0.77, 0.02], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the morning shift. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_414491a38dcc8e82_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.11, 0.63, 0.13, 0.13], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: across all regions, mid-incident. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_63428c3ec7f0e31c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.35, 0.01, 0.05, 0.59], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: across all regions, during peak load. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3134e8a1d0c0385d_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "The metrics pipeline 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 monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c72c0c108d60f47c_n", "kind": "noul", "options": ["false", "true"], "target": [0.46, 0.54], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: in production only, during an external partner integration. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_19e4768dee9b2567_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.61, 0.36, 0.0], "state": "The log shipper reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: during the batch window, during the quarterly review. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ae205c79667ec1e1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.56, 0.38, 0.04, 0.02], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: during the batch window, during the quarterly review. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1873fee42c08954c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.25, 0.01, 0.2, 0.54], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: over the last hour, during normal operations. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_06e97b9a5af907c6_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.85, 0.12, 0.02, 0.01], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: during the batch window, immediately after go-live. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_db17b3504e14379a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.12, 0.69, 0.18, 0.01], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: during the batch window, following a recent audit. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_be751728064e1ed3_n", "kind": "noul", "options": ["false", "true"], "target": [0.44, 0.56], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: during the batch window, while on-call rotation changed. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fb63a6a08bdeefc0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.3, 0.67, 0.01], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: in production only, following a recent audit. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8d91ec5ab9e4ff9a_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: during the batch window, during the holiday freeze. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fe23c7393e8c5f49_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "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, immediately after go-live. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_22595ea42966dc81_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.2, 0.06, 0.37, 0.37], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: in production only, while on-call rotation changed. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d8bdb2b83fda02ea_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.75, 0.22, 0.02, 0.01], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: over the last hour, with staffing at reduced levels. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_98a85714059cc87d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.11, 0.72, 0.17, 0.0, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: in production only, during normal operations. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_60cd925c448012ee_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: during the batch window, during the holiday freeze. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_53407943d6fc4d96_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.66, 0.31, 0.02], "state": "The log shipper lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: during the batch window, during the holiday freeze. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6e3eafa4f18dae14_n", "kind": "noul", "options": ["false", "true"], "target": [0.42, 0.58], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: in production only, during the morning shift. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e6ef5e60b1f1a875_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.96, 0.03, 0.0, 0.01], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: across all regions, mid-incident. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_41bf928ec411bf61_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "The log shipper matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: during the batch window, mid-incident. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4cae264ba9fa2d9d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.09, 0.54, 0.31, 0.05, 0.0], "state": "The log shipper matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: in production only, during the quarterly review. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6fba0c5727731a7d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.03, 0.86, 0.11], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, shortly after a software update. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3071548093364da5_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.83, 0.16, 0.01, 0.0], "state": "The log shipper matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: across all regions, during peak load. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e5746e898c88847b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.43, 0.57, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: in production only, during an external partner integration. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_28b87ce873ad21ba_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: during the batch window, during peak load. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6e7dcb7056a6809b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.11, 0.86, 0.03], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: during the batch window, during peak load. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8a05b3d630b050ac_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.13, 0.53, 0.06, 0.28], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: across all regions, while on-call rotation changed. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_daabd32aac924cfc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.27, 0.7, 0.02], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: in production only, during peak load. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f89a4dda105c63a9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.23, 0.73, 0.03], "state": "Service catalog-sync correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: during the batch window, under an active deadline. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e55bc18fb598a779_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.04, 0.55, 0.4, 0.01], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during the quarterly review. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_76240ce864fa82d0_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: over the last hour, during the system migration. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_330f5c4ba29fab8b_n", "kind": "noul", "options": ["false", "true"], "target": [0.64, 0.36], "state": "The log shipper shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: over the last hour, during the morning shift. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_419a3153af7004eb_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: over the last hour, mid-incident. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fb791193185fb3f3_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.19, 0.69, 0.1, 0.02], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, with a new vendor onboarded. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6ea9db45eda855e1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.18, 0.73, 0.08], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_94c410685d9dcb51_n", "kind": "noul", "options": ["false", "true"], "target": [0.71, 0.29], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: across all regions, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_09e03f67b8d6e374_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.12, 0.03, 0.82, 0.03], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: during the batch window, immediately after go-live. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4966f68948aa1edd_n", "kind": "noul", "options": ["false", "true"], "target": [0.55, 0.45], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, at the end of the fiscal period. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f8c815a17fd22454_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.14, 0.65, 0.19, 0.02, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: across all regions, following a recent audit. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_292375d644d98adc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.36, 0.63, 0.01], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: during the batch window, under reduced staffing. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4b0224ab8d74df3b_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: across all regions, at the end of the fiscal period. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_20ea0a82af75b82e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.06, 0.03, 0.52, 0.39], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: over the last hour, with staffing at reduced levels. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1a4814e94cce0b1d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.19, 0.74, 0.06], "state": "The log shipper reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: across all regions, immediately after go-live. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d8557dec28ea9ed2_n", "kind": "noul", "options": ["false", "true"], "target": [0.22, 0.78], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, under reduced staffing. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3e99da57536937ff_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.26, 0.0, 0.32, 0.42], "state": "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, during a scheduled maintenance window. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a426fc7a77b786b1_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: in production only, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_674a06c2ce038dac_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.54, 0.4, 0.01], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during a scheduled maintenance window. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8c5ea8f1fad4a22f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.63, 0.32, 0.05, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: during the batch window, at the end of the fiscal period. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_29408bc9bb283b5e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.31, 0.3, 0.01, 0.38], "state": "Node pgsql-14 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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b429f5acc715ca5_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.1, 0.02, 0.08, 0.8], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: over the last hour, during the system migration. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dc3f2f13f5e5698e_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: in production only, during normal operations. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3220100bde8842f0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.27, 0.72, 0.01], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, while on-call rotation changed. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_625fa8f565c2a248_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.61, 0.31, 0.08, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: during the batch window, during normal operations. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4bab92aa72110e07_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.08, 0.88, 0.04], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: in production only, with staffing at reduced levels. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_84264dcf7eb51ac4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.82, 0.17, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: during the batch window, following a recent audit. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_74a869f4406e6e8a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.99, 0.0, 0.0, 0.01], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: in production only, during a scheduled maintenance window. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c8fbd17a379cbad0_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.3, 0.12, 0.53, 0.05], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: during the batch window, with a new vendor onboarded. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4179e23937975218_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during the holiday freeze. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c671edaa285d4eeb_n", "kind": "noul", "options": ["false", "true"], "target": [0.7, 0.3], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, while on-call rotation changed. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_03284d438b2c61b9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.06, 0.67, 0.26, 0.0], "state": "Service catalog-sync flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: in production only, at the end of the fiscal period. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bfeb287e82da70c3_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: in production only, while legacy systems are still active. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_adcef08fe6ecf569_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.05, 0.91, 0.03], "state": "Service catalog-sync flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: during the batch window, with a new vendor onboarded. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca8a4a5d872e469d_n", "kind": "noul", "options": ["false", "true"], "target": [0.71, 0.29], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the morning shift. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fdb77e1552a4c52e_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "Service catalog-sync lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: across all regions, as part of a compliance sweep. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fe23c7393e8c5f49_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.89, 0.11, 0.0, 0.0], "state": "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, immediately after go-live. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a0c43d3f5cb2afed_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: during the batch window, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4db345bd6aa8e39b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.05, 0.84, 0.11], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during the system migration. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_367d46be9cf7e0cd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.52, 0.46, 0.01], "state": "The metrics pipeline flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: in production only, as part of a compliance sweep. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8eb7dbe2cdf78a29_n", "kind": "noul", "options": ["false", "true"], "target": [0.5, 0.5], "state": "The metrics pipeline correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: in production only, during the system migration. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_231bc63070bccc8b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.75, 0.07, 0.13], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: in production only, shortly after a software update. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_638e7fdb5248749f_n", "kind": "noul", "options": ["false", "true"], "target": [0.92, 0.08], "state": "The log shipper reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: over the last hour, mid-incident. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2e569a7241a0d41a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.39, 0.6, 0.01], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: across all regions, during normal operations. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_363847a3be0817a3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.37, 0.57, 0.04, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: across all regions, shortly after a software update. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fc7b57e5e542e5f1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.15, 0.8, 0.05], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: in production only, under an active deadline. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_47b239ad9fae9195_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.12, 0.85, 0.03], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, following a recent audit. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_73c6a7add3479ecd_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_92bdf0f4d628e5bd_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.91, 0.04, 0.01, 0.04], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: during the batch window, under an active deadline. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e0ef25e61fe69222_n", "kind": "noul", "options": ["false", "true"], "target": [0.19, 0.81], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, shortly after a software update. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_83a9c92c56a2b5ec_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: across all regions, shortly after a software update. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d1dfcd4b3972e086_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.19, 0.02, 0.12, 0.67], "state": "The log shipper shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: in production only, with staffing at reduced levels. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2384e81482b7f811_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.78, 0.19, 0.02, 0.01], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: during the batch window, under reduced staffing. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7e2fc4b1e9460b24_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.14, 0.83, 0.03], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the system migration. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_32d548996da2a524_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.04, 0.52, 0.43, 0.01], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during the quarterly review. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_203de1c1941967ba_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3b002d0b93ad4f84_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.89, 0.1, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: during the batch window, during the quarterly review. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4711b30509e98063_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.02, 0.71, 0.27], "state": "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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5bebd3d7f2d6c668_n", "kind": "noul", "options": ["false", "true"], "target": [0.64, 0.36], "state": "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.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_22953d990ae9932a_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: in production only, following a recent audit. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_292375d644d98adc_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: during the batch window, under reduced staffing. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fd6e5af4cf910782_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "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.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_51093287d6f340b9_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "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.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cf0b53949a90140f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.93, 0.02, 0.02, 0.03], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, while legacy systems are still active. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_db996a89acaa3261_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.06, 0.0, 0.75, 0.19], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: in production only, during peak load. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_84d0db155fd6c697_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.74, 0.25, 0.0], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: during the batch window, while on-call rotation changed. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6e01b1a636bafa7f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.63, 0.35, 0.0], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: during the batch window, under reduced staffing. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_32e3f751ca931a42_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The metrics pipeline shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: in production only, under reduced staffing. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7885f1677fba5cb2_n", "kind": "noul", "options": ["false", "true"], "target": [0.6, 0.4], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: across all regions, during the quarterly review. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b7f13b46141fe527_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.0, 0.48, 0.51], "state": "The log shipper correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, as part of a compliance sweep. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_48bc46359d18ce30_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.13, 0.84, 0.03], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during the morning shift. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_06101dade5ef5aef_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "The log shipper returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: across all regions, during the quarterly review. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b29a0c843627ccb2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.18, 0.3, 0.49, 0.02, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: across all regions, during normal operations. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7f2cc0b58144cbed_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.79, 0.18, 0.03, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, under reduced staffing. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ff7ceb3dfc41c44d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.02, 0.63, 0.35, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: over the last hour, during the morning shift. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b02f6c792641cd74_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.39, 0.47, 0.13, 0.01], "state": "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, during an external partner integration. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0877fa1143bac6b6_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, under an active deadline. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e869553490e57d4d_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: during the batch window, shortly after a software update. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7bf34953bd349b2b_n", "kind": "noul", "options": ["false", "true"], "target": [0.39, 0.61], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: across all regions, as part of a compliance sweep. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_34863c051a2d4ba6_n", "kind": "noul", "options": ["false", "true"], "target": [0.21, 0.79], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, mid-incident. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4c4aecf64f40f659_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.33, 0.64, 0.02], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: across all regions, immediately after go-live. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7b817a7b2b5b43bc_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: over the last hour, with staffing at reduced levels. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9cbbd1680620315d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.32, 0.19, 0.44, 0.05], "state": "The log shipper shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, with a new vendor onboarded. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7229b2df6cfa304a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.0, 0.62, 0.38], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during the system migration. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0968341171ac8bb3_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.79, 0.16, 0.04, 0.01], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the morning shift. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eb6f53ddae7e4004_n", "kind": "noul", "options": ["false", "true"], "target": [0.9, 0.1], "state": "The metrics pipeline 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 supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6bb62addc64c5a54_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, mid-incident. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5b52bd3614aea0ae_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.94, 0.0, 0.05, 0.01], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during peak load. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2e89f4d1ee0c5f57_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.12, 0.76, 0.11, 0.01], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: in production only, as part of a compliance sweep. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ad1368e5a5750bc_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.86, 0.01, 0.04, 0.09], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: during the batch window, during peak load. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_53674e7834c3672f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.41, 0.57, 0.01], "state": "The log shipper correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during peak load. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9233c1d4d2cbb9c9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.49, 0.4, 0.06, 0.05], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aa5d18ec98978de7_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.01, 0.61, 0.35], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: over the last hour, under an active deadline. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_166ed5cd125df9d1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.82, 0.14, 0.04, 0.0], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: in production only, with staffing at reduced levels. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_97a558b660ebe2c9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.01, 0.55, 0.44], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: across all regions, during an external partner integration. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_adc6bba1f78247aa_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.07, 0.51, 0.37, 0.05, 0.0], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during peak load. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_82dc141b100e1979_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.04, 0.25, 0.27, 0.4, 0.04, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: during the batch window, with staffing at reduced levels. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3b3f8f2a3a82fb3a_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: across all regions, under an active deadline. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7878bc37e1faf47f_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally flags a step-function change in error slope. Context: across all regions, during the morning shift. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6ea9db45eda855e1_n", "kind": "noul", "options": ["false", "true"], "target": [0.63, 0.37], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f922140e1ab37020_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.09, 0.6, 0.07, 0.24], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: in production only, immediately after go-live. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5954213ea658489c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.58, 0.4, 0.01, 0.01], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: across all regions, at the end of the fiscal period. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_71fea8d702466c2f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.93, 0.06, 0.01, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: across all regions, with staffing at reduced levels. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f7021a2c42aa9e4d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.79, 0.19, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: over the last hour, while legacy systems are still active. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ac7e1b7806206ae0_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.07, 0.08, 0.73, 0.12], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: in production only, during an external partner integration. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5db51a5cbb5c60fb_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: during the batch window, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ac086d809344ab35_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.11, 0.73, 0.02, 0.14], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7dbb694e257a12c2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.17, 0.01, 0.03, 0.79], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, under reduced staffing. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_969e4605fb313e7d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.47, 0.4, 0.08, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: during the batch window, mid-incident. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d664c425658d2667_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.35, 0.62, 0.02], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: across all regions, during the morning shift. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_672217b2dac8da3f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.06, 0.63, 0.26, 0.05, 0.0, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, while legacy systems are still active. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4dfe869f8715374f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.06, 0.24, 0.69], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during normal operations. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d5772b840b4ab866_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.84, 0.14, 0.01, 0.01], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: over the last hour, while on-call rotation changed. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f07d96a3d1239c81_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.11, 0.45, 0.43, 0.01], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: during the batch window, during peak load. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_201c4196616c2a9b_n", "kind": "noul", "options": ["false", "true"], "target": [0.65, 0.35], "state": "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.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_afcdc2d42956e929_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.07, 0.89, 0.04], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, with staffing at reduced levels. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e7c35e9ecc539b64_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: across all regions, mid-incident. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_db996a89acaa3261_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.2, 0.38, 0.38, 0.03, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: in production only, during peak load. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fffe09cb251fe5f8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.44, 0.56, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, with staffing at reduced levels. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_43c9c97b906f0eb3_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.02, 0.28, 0.69, 0.01], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, with staffing at reduced levels. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6d9c67773da404b5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.38, 0.59, 0.01], "state": "The log shipper reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: across all regions, following a recent audit. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2359d166bc00cc05_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Dashboard checkout-funnel 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 automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_06feebd8ee7a4263_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.18, 0.54, 0.27, 0.01], "state": "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, during a scheduled maintenance window. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_99f6d46720facfa5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.39, 0.46, 0.13, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, following a recent audit. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_783d2c3cfc0142b6_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.56, 0.4, 0.02, 0.02], "state": "The metrics pipeline shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during peak load. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b316082ed17d9b70_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.22, 0.67, 0.1, 0.0], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: in production only, during the morning shift. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_62f5e555326f4c81_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "The metrics pipeline flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: across all regions, during the system migration. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ac7e1b7806206ae0_n", "kind": "noul", "options": ["false", "true"], "target": [0.9, 0.1], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: in production only, during an external partner integration. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_695532197963ace8_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, shortly after a software update. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9bbefa0ae04944d6_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.04, 0.02, 0.9], "state": "The metrics pipeline lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: during the batch window, mid-incident. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ba7378867f32f758_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "The log shipper lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the quarterly review. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8905bf85cd6dfd0a_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: in production only, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c53b28285db824fc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.03, 0.42, 0.52, 0.02], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: across all regions, during normal operations. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f9c6743791c50afc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.8, 0.17, 0.0], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_45e86a12b377851d_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during normal operations. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7451fbee72d05a60_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "The metrics pipeline 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 operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ec2d1f99856a8865_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: over the last hour, while on-call rotation changed. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1d17a2265fb7622d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.0, 0.47, 0.53], "state": "The log shipper lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: in production only, during an external partner integration. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_11296670f77e65ee_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.63, 0.33, 0.03, 0.01], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: across all regions, while on-call rotation changed. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e759242ee5a4c92f_n", "kind": "noul", "options": ["false", "true"], "target": [0.67, 0.33], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: during the batch window, during the morning shift. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_913f928375b74eb2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.35, 0.38, 0.24, 0.01], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: in production only, mid-incident. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ee7816cd9003d341_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.75, 0.21, 0.04, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: in production only, while legacy systems are still active. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_608cc46d5f3a30d9_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "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, during peak load. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_335498e1b7cc01fc_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.19, 0.61, 0.19, 0.01], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: across all regions, shortly after a software update. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b8298e43e1e5e5e7_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.01, 0.09, 0.88], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: across all regions, while on-call rotation changed. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7f2ed8eb80037306_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.84, 0.0, 0.02, 0.14], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: in production only, at the end of the fiscal period. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_78a8c1086f17a9a1_n", "kind": "noul", "options": ["false", "true"], "target": [0.42, 0.58], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: over the last hour, as part of a compliance sweep. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5cfefea696488038_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: during the batch window, as part of a compliance sweep. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ccc5bf228c13a1d7_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: across all regions, during the system migration. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_efeed6b3e524f2dd_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.18, 0.09, 0.04, 0.69], "state": "The log shipper shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: in production only, during the quarterly review. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_62bcb6b28c7f1ffa_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.49, 0.51, 0.0], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during the quarterly review. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ab7a336100c02c62_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.03, 0.82, 0.15], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: over the last hour, under an active deadline. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d2750fa8381dd3c2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.03, 0.72, 0.24, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: during the batch window, as part of a compliance sweep. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9a3a2daba1880fa2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.33, 0.66, 0.01], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: in production only, mid-incident. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_66504073835d2c6e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.54, 0.43, 0.01], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: during the batch window, during the quarterly review. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0770212636f5d27c_n", "kind": "noul", "options": ["false", "true"], "target": [0.55, 0.45], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during a scheduled maintenance window. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_539d16d0ced0c1d7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.51, 0.49, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bd4bc9d6d0960f40_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.41, 0.04, 0.38, 0.17], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: across all regions, with staffing at reduced levels. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9121c05c7f9cfe07_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, mid-incident. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5c901e4b4cdbbf66_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: during the batch window, with staffing at reduced levels. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_58bc0c178f0a9b47_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.1, 0.66, 0.23, 0.01], "state": "Node pgsql-14 flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: across all regions, during a scheduled maintenance window. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cb4796f58d149b75_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.13, 0.85], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: in production only, during the system migration. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8eb7dbe2cdf78a29_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.02, 0.67, 0.3], "state": "The metrics pipeline correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: in production only, during the system migration. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0a6556a4f89e8f9f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.07, 0.22, 0.06, 0.65], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: over the last hour, during the quarterly review. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8ec79f61de5e4b47_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.44, 0.56, 0.0], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: during the batch window, shortly after a software update. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_de7a0cbacbca0cea_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.97, 0.01, 0.01, 0.01], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: across all regions, mid-incident. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7878bc37e1faf47f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.25, 0.74, 0.01], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally flags a step-function change in error slope. Context: across all regions, during the morning shift. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b1032c0bf9c49f39_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: across all regions, during the system migration. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_10a82816ac73e3b2_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.53, 0.44, 0.02, 0.01], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: in production only, during an external partner integration. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_504d32baf68334f2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.99, 0.0, 0.01], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: over the last hour, shortly after a software update. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f2cf80535a3d3c07_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.02, 0.44, 0.53], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: over the last hour, following a recent audit. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8eb7dbe2cdf78a29_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.08, 0.33, 0.52, 0.06, 0.0], "state": "The metrics pipeline correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: in production only, during the system migration. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_386aac66aa5e21d7_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.13, 0.31, 0.5, 0.06], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: over the last hour, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_330f5c4ba29fab8b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.92, 0.06, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: over the last hour, during the morning shift. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7bc7b101dcdbe3af_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.21, 0.76, 0.03], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during peak load. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c7786d696b458edc_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.02, 0.34, 0.63], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: in production only, during the morning shift. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_06ddfbdc2832b1a6_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.66, 0.27, 0.06, 0.01], "state": "Service catalog-sync shows clock skew of 800ms across replicas; 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 supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3c5ceb7be4fa63e7_n", "kind": "noul", "options": ["false", "true"], "target": [0.38, 0.62], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: over the last hour, during the quarterly review. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ad82484389d26794_n", "kind": "noul", "options": ["false", "true"], "target": [0.55, 0.45], "state": "The log shipper reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, while on-call rotation changed. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9f171ab6c27b5d16_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: over the last hour, during the system migration. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b4877d16207f58f8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.64, 0.36, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: over the last hour, during an external partner integration. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_04bc125e78dcf00e_n", "kind": "noul", "options": ["false", "true"], "target": [0.55, 0.45], "state": "Service catalog-sync flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: over the last hour, mid-incident. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5cb2e9fc974bc9f2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.01, 0.34, 0.62, 0.02], "state": "The log shipper matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: in production only, with staffing at reduced levels. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d5bebe1b0247211c_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Service catalog-sync lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: during the batch window, during peak load. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6fb51091ba7bbdc0_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, while legacy systems are still active. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4d28dd10f802b020_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_23778d87b6993de8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.21, 0.59, 0.2, 0.0, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: across all regions, with staffing at reduced levels. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c4188a78fa997c1f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.16, 0.62, 0.19, 0.0], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: across all regions, under an active deadline. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_979f44756945490a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.5, 0.44, 0.01], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during a scheduled maintenance window. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_153715564c81edb5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.07, 0.71, 0.21, 0.0], "state": "The log shipper correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: over the last hour, at the end of the fiscal period. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aa69aab3b8d0a7fd_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.06, 0.01, 0.48, 0.45], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: during the batch window, mid-incident. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b658697efc02e29c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.96, 0.0, 0.04], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: across all regions, shortly after a software update. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c186c37c55649496_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.31, 0.68, 0.01], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, following a recent audit. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2dbe58976815a173_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.16, 0.04, 0.1, 0.7], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: over the last hour, under an active deadline. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_88e535ac3e1db8b4_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: in production only, during the morning shift. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9c2970010102bbee_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.63, 0.36, 0.0], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: during the batch window, during an external partner integration. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca1c9712099a15f0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.08, 0.76, 0.16, 0.0], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: during the batch window, shortly after a software update. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5f9e0e10574a1cbb_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.85, 0.14, 0.01, 0.0], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: in production only, following a recent audit. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2733feaf80593d29_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.75, 0.24, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: across all regions, during the quarterly review. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_40a63bb8846bf86a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.9394, 0.0505, 0.0, 0.0101], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, immediately after go-live. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_71e5cfa81743c981_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.07, 0.55, 0.38, 0.0, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: during the batch window, while on-call rotation changed. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_996cbf04f5330895_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.21, 0.7, 0.07, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: during the batch window, while on-call rotation changed. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_92c19f9a4b528733_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.03, 0.01, 0.94], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: in production only, during the morning shift. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0e60701a2768e58a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.37, 0.07, 0.05, 0.51], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, under an active deadline. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_55c606641a6da7e9_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.29, 0.57, 0.12, 0.02], "state": "The log shipper reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during an external partner integration. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca0f5d777372d7aa_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.42, 0.51, 0.03, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: across all regions, mid-incident. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_67e63af1cf794458_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.16, 0.0, 0.02, 0.82], "state": "The log shipper lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, with staffing at reduced levels. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_234b755e1196f814_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the morning shift. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_321389d3b31aa722_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.91, 0.06, 0.01, 0.02], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally flags a step-function change in error slope. Context: during the batch window, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8ebbcd63edc857f5_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.58, 0.37, 0.04, 0.01], "state": "The log shipper reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during normal operations. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aec08ef1761f1453_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.93, 0.07, 0.0, 0.0], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: in production only, under reduced staffing. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0112ab333ed0d80f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.26, 0.5, 0.21, 0.01], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during the system migration. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c8362ddb444df4ab_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.41, 0.59, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, with staffing at reduced levels. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_91e6bbc9724f18e3_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.01, 0.43, 0.56], "state": "The log shipper matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: during the batch window, during an external partner integration. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6d6ab3436bdebeef_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.05, 0.76, 0.19, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: in production only, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_865be2f353f9da04_n", "kind": "noul", "options": ["false", "true"], "target": [0.39, 0.61], "state": "Node pgsql-14 flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: during the batch window, immediately after go-live. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fa5b6971800fa393_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: in production only, under an active deadline. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4fd84c403fe42b2c_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: in production only, at the end of the fiscal period. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9532084c9ed62bdf_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.76, 0.22, 0.0], "state": "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 monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e888ad684ee71b35_n", "kind": "noul", "options": ["false", "true"], "target": [0.53, 0.47], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: in production only, during normal operations. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_01733d259d7619b1_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: in production only, under an active deadline. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b3a065abe5ac952f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.46, 0.51, 0.02], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: over the last hour, during the system migration. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_302d2da1911ae2df_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.67, 0.32, 0.0], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: in production only, during the quarterly review. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3641702b2d37aa09_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.15, 0.29, 0.52, 0.04], "state": "Service catalog-sync shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: over the last hour, during peak load. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0946abd1ce2cba91_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "Service catalog-sync shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_079d55122ae93293_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: during the batch window, during the quarterly review. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_64d7a37807ff6ffd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.59, 0.41, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: across all regions, mid-incident. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3481db3cdf7f5b86_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.23, 0.76, 0.01], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: over the last hour, shortly after a software update. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ed936eb5fe70a25b_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during the quarterly review. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aa79111fde28ddfd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.3, 0.69, 0.01], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: in production only, during the system migration. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_075ac3175d7d18bb_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.21, 0.45, 0.33, 0.01], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, as part of a compliance sweep. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_be180c9265dd3448_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0505, 0.0, 0.0101, 0.9394], "state": "The log shipper returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2277e31551ca9e53_n", "kind": "noul", "options": ["false", "true"], "target": [0.93, 0.07], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: across all regions, under an active deadline. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c5e4db7101cc3109_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "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.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_35fd00d075629b6a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.3, 0.43, 0.26, 0.01], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during the holiday freeze. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fc7b57e5e542e5f1_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: in production only, under an active deadline. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_345914eaa621135a_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: in production only, under an active deadline. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b88c5ea1bf363cd5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.12, 0.84, 0.04], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: in production only, under reduced staffing. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9fce8279a8f3a908_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.9, 0.09, 0.01, 0.0], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during peak load. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3257a5e958713b08_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.94, 0.02, 0.02], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, shortly after a software update. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6305c52dab9e7b2c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.06, 0.21, 0.69, 0.04], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: in production only, during an external partner integration. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_639dbaf110d21248_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.58, 0.38, 0.03, 0.01], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: during the batch window, following a recent audit. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c6375aebe32873e6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.04, 0.21, 0.47, 0.25, 0.03, 0.0], "state": "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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4bfa6531259dad1b_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "The log shipper correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: in production only, during peak load. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cf2527fbacc2c34a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.33, 0.51, 0.16, 0.0, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: during the batch window, during a scheduled maintenance window. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_468b3cac759689bb_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.17, 0.18, 0.03, 0.62], "state": "Service catalog-sync flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: in production only, during normal operations. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_59022f50a2c43bb5_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: during the batch window, during an external partner integration. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0d53771924d6971a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.34, 0.66, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, following a recent audit. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6bdadba36df4874d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.94, 0.06, 0.0, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: across all regions, immediately after go-live. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cfcd325c837c3536_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.15, 0.61, 0.23, 0.0], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: during the batch window, under an active deadline. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c24672b83c43d101_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.38, 0.51, 0.03, 0.08], "state": "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 a scheduled maintenance window. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b0b77bf66bda844_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.79, 0.19, 0.01, 0.01], "state": "The log shipper matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: during the batch window, immediately after go-live. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b8cf061fdcdcaecc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.63, 0.3, 0.01, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: over the last hour, at the end of the fiscal period. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_637fa3b187aa6c15_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.63, 0.28, 0.01, 0.08], "state": "The log shipper returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, shortly after a software update. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_63045fc69664036c_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: over the last hour, while legacy systems are still active. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b566758345efc9ff_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.58, 0.12, 0.01, 0.29], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, with staffing at reduced levels. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ce62d55fd3ddfcff_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.88, 0.08, 0.01, 0.03], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: over the last hour, shortly after a software update. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e1e1bcfd7eca4832_n", "kind": "noul", "options": ["false", "true"], "target": [0.42, 0.58], "state": "The log shipper flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: during the batch window, during the quarterly review. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_18e2129dba1ee58d_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "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.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_116e048371e09d7f_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: over the last hour, following a recent audit. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4bdf70d2990abf2f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.07, 0.73, 0.16], "state": "The log shipper flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: in production only, with a new vendor onboarded. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f2aad7b1c419bfe4_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.46, 0.1, 0.24, 0.2], "state": "The log shipper flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during the holiday freeze. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_de2255cbce7c0320_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.23, 0.18, 0.02, 0.57], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: across all regions, with staffing at reduced levels. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_419a3153af7004eb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.52, 0.45, 0.01], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: over the last hour, mid-incident. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_62e0a52251e8256c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.64, 0.22, 0.1, 0.0], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during peak load. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9d40d10f61934fd6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.07, 0.85, 0.07, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: over the last hour, with a new vendor onboarded. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1e3e5ce32a74a23c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.06, 0.8, 0.14], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during the quarterly review. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ade11d20613f9f34_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.92, 0.0, 0.01, 0.07], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, while legacy systems are still active. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f64ea47ebec1b909_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.9, 0.09, 0.01, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: during the batch window, under reduced staffing. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3e0b261085d79448_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: during the batch window, under reduced staffing. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0054e34ce95304aa_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.47, 0.51, 0.01], "state": "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, during the morning shift. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5529705762f31a4d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.11, 0.82, 0.07], "state": "The metrics pipeline 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 operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_858e4da56f7a910f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.03, 0.27, 0.68, 0.02], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: during the batch window, while on-call rotation changed. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b316082ed17d9b70_n", "kind": "noul", "options": ["false", "true"], "target": [0.52, 0.48], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: in production only, during the morning shift. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b04a416fe1f5d3f5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.22, 0.57, 0.18, 0.01], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: across all regions, under an active deadline. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2251e74fea8f70c1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.97, 0.02, 0.01, 0.0], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, under an active deadline. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_26cea952d7f01ba4_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: across all regions, with staffing at reduced levels. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5dac6b76785e32f7_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.94, 0.06, 0.0, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, under reduced staffing. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_16f85bbb1ed4aa3b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.66, 0.32, 0.02, 0.0], "state": "The log shipper flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: over the last hour, during an external partner integration. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0c56d6c57195d946_n", "kind": "noul", "options": ["false", "true"], "target": [0.69, 0.31], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: across all regions, during the system migration. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b206ce9324c63cc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.36, 0.41, 0.21, 0.01], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during the quarterly review. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f16c1a355b29b809_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.23, 0.65, 0.07, 0.05], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, with a new vendor onboarded. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0692e887285ef586_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.29, 0.43, 0.27, 0.01], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: in production only, during an external partner integration. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7ea28937e847a888_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.54, 0.43, 0.02, 0.01], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: across all regions, during the quarterly review. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_12cbe55c507654bf_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.14, 0.81, 0.04], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: over the last hour, at the end of the fiscal period. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7997112f6790fb6e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.61, 0.38, 0.01, 0.0], "state": "The log shipper flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: in production only, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f7d9a996dabbf780_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, with staffing at reduced levels. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b593e43e14c7af84_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.9, 0.1, 0.0, 0.0], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: across all regions, during the system migration. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ed91f24332039d71_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.08, 0.84, 0.08], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: in production only, immediately after go-live. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_848048a71f969129_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.93, 0.05, 0.01, 0.01], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: over the last hour, immediately after go-live. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fffe09cb251fe5f8_n", "kind": "noul", "options": ["false", "true"], "target": [0.23, 0.77], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, with staffing at reduced levels. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_66392cfefcaa9ea4_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.94, 0.02, 0.01, 0.03], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4462f40a0f6049b7_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.21, 0.69, 0.01, 0.09], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: across all regions, following a recent audit. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_385c5ca7eb9d1253_n", "kind": "noul", "options": ["false", "true"], "target": [0.5, 0.5], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally matches last Tuesday's incident signature. Context: during the batch window, under an active deadline. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_99f2ee62848e722f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.73, 0.24, 0.01, 0.02], "state": "The metrics pipeline 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 review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fd028d56fb7f09dd_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.94, 0.06, 0.0, 0.0], "state": "The log shipper matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: across all regions, under reduced staffing. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fb791193185fb3f3_n", "kind": "noul", "options": ["false", "true"], "target": [0.64, 0.36], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, with a new vendor onboarded. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f16c1a355b29b809_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.24, 0.56, 0.19, 0.0], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, with a new vendor onboarded. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_66f8e652dbf689b9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.83, 0.15, 0.01, 0.01], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, under an active deadline. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b3f19600df86d460_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.16, 0.62, 0.21, 0.01], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, following a recent audit. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e6860f2cdec64992_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.41, 0.54, 0.04, 0.01], "state": "Service catalog-sync shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: across all regions, during the system migration. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_536b0012375d1ea1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.01, 0.71, 0.28], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, immediately after go-live. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e5d7fa621f431d33_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: across all regions, with staffing at reduced levels. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6010e8b7375581f9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.11, 0.83, 0.06], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: during the batch window, shortly after a software update. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6c8905c9b2bd9d8c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.32, 0.65, 0.02], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: across all regions, during a scheduled maintenance window. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f0472f6f927b23db_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.37, 0.6, 0.01], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: in production only, during the quarterly review. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_17e68c1d16b7a83e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.12, 0.02, 0.04, 0.82], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: across all regions, during the system migration. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0010a37e03a70c3f_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: across all regions, during peak load. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7a4fca3f6c20158d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.33, 0.65, 0.01], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: over the last hour, under reduced staffing. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e32d41b698f78d64_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.51, 0.02, 0.18, 0.29], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: in production only, under an active deadline. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_16da5341d8244d31_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.11, 0.75, 0.13, 0.01], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: during the batch window, under an active deadline. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7d85d6a60969d515_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.23, 0.12, 0.03, 0.62], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: over the last hour, under reduced staffing. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_daa4d26635198b5e_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during the quarterly review. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c91a0c6c3b5f61f2_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: over the last hour, shortly after a software update. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8c2981c3aeff9011_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.98, 0.0, 0.0, 0.02], "state": "The metrics pipeline 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 supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2895fc99867f50d5_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.73, 0.24, 0.03, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, with a new vendor onboarded. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_37a17dba460329ee_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.45, 0.54, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during the holiday freeze. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a0eb51a20dfc3ba7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.62, 0.37, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: over the last hour, during the quarterly review. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a9f04fc7714a9d75_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.03, 0.3, 0.64, 0.03], "state": "The log shipper correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: across all regions, with staffing at reduced levels. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d37ec17544ee6504_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.58, 0.26, 0.02, 0.14], "state": "The log shipper shows a slow leak in heap growth; 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 automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9cfb4f84f058c79b_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during an external partner integration. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fed8c55bb8a3323e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.1, 0.54, 0.3, 0.06], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: during the batch window, mid-incident. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_95a5403ad65b1be9_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.22, 0.67, 0.11, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: over the last hour, as part of a compliance sweep. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2895fc99867f50d5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.25, 0.74, 0.01], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, with a new vendor onboarded. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b3c0becc4341b614_n", "kind": "noul", "options": ["false", "true"], "target": [0.66, 0.34], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: during the batch window, during peak load. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0e60701a2768e58a_n", "kind": "noul", "options": ["false", "true"], "target": [0.66, 0.34], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, under an active deadline. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_01ca1a3891187f21_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: during the batch window, while on-call rotation changed. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8ddf9fec21f9c822_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.13, 0.07, 0.05, 0.75], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: in production only, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e12976042ae8335e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.3, 0.69, 0.01], "state": "Service catalog-sync flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: across all regions, shortly after a software update. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_33192132a822fc84_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.21, 0.73, 0.05, 0.01], "state": "The log shipper reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: across all regions, following a recent audit. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2a3ea9df5a1bc6e4_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: during the batch window, following a recent audit. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e48a5c99ac87a31b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.74, 0.21, 0.0], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: across all regions, during normal operations. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_559a73ced4aba2d2_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: over the last hour, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_07e7afa087fbece1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.34, 0.63, 0.02], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: across all regions, with staffing at reduced levels. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cece94212703d62c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.46, 0.47, 0.06, 0.01], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: across all regions, as part of a compliance sweep. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e433e948e8425db3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.56, 0.43, 0.0], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b43bb01678d11fb9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.06, 0.11, 0.45, 0.38], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: during the batch window, following a recent audit. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_99f6d46720facfa5_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, following a recent audit. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_04071ec7e18e13fb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.15, 0.82, 0.03], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: across all regions, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7275e3a614ff1615_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.61, 0.33, 0.05, 0.01], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: during the batch window, during peak load. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9b5204cab2d65615_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.06, 0.78, 0.15, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: during the batch window, during a scheduled maintenance window. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_72b9442266e34810_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.08, 0.56, 0.24, 0.12], "state": "The metrics pipeline flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: in production only, during the system migration. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_90bd84cb4688ba13_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.49, 0.35, 0.15, 0.01], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: in production only, immediately after go-live. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eba233a568cd214d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.04, 0.67, 0.28, 0.01], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: during the batch window, with staffing at reduced levels. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dca80036fc27653c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.06, 0.82, 0.11, 0.0], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: over the last hour, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6dcfaba90c16d99d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.0, 0.93, 0.04], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: over the last hour, during an external partner integration. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5c8a864474e81ef9_n", "kind": "noul", "options": ["false", "true"], "target": [0.5, 0.5], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: in production only, with a new vendor onboarded. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9be2f922951d7d0e_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "The log shipper matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: across all regions, while on-call rotation changed. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ec2d33037ec03cdf_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, immediately after go-live. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e201dbb56cb51406_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.41, 0.39, 0.19, 0.01], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during normal operations. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_22227024cda67999_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.88, 0.08, 0.03, 0.01], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: in production only, mid-incident. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_344346d1dca94942_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.07, 0.02, 0.74, 0.17], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_efc8b82559ea5806_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.28, 0.39, 0.32, 0.01], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the system migration. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7e3e859e419da64f_n", "kind": "noul", "options": ["false", "true"], "target": [0.69, 0.31], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the holiday freeze. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1eec0c816a283727_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.16, 0.71, 0.1, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: in production only, as part of a compliance sweep. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_39855681ce11bfcc_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.21, 0.52, 0.26, 0.01], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: over the last hour, mid-incident. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d321c0674c4ef632_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.67, 0.32, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during the morning shift. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5e4cb06dbd8a7956_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.36, 0.63, 0.01], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, while on-call rotation changed. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8632beb8b67996da_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: across all regions, during an external partner integration. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a8e0822392107bec_n", "kind": "noul", "options": ["false", "true"], "target": [0.42, 0.58], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: in production only, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_149a05711fd8dd9b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.27, 0.71, 0.02], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: during the batch window, during normal operations. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_16979c66622f2388_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The log shipper reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, following a recent audit. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8ad30625f93c1a81_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.66, 0.32, 0.0], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: during the batch window, with a new vendor onboarded. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2def5e77f6641a87_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.25, 0.73, 0.02], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during peak load. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e422908a07b68972_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.63, 0.32, 0.05, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: across all regions, during the holiday freeze. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2e01d35226147b45_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: in production only, while on-call rotation changed. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_404c2ec7405c0220_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.52, 0.47, 0.0], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: across all regions, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_218b498fcde24643_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "The metrics pipeline lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: in production only, during the quarterly review. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9d4df05514fd9267_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.06, 0.82, 0.12], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ea0fc2273e239065_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.37, 0.61, 0.01], "state": "The log shipper matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: across all regions, during an external partner integration. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9731f57ad8294fc5_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, mid-incident. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_01c856536e7ab858_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.17, 0.59, 0.21, 0.0], "state": "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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a4b5e63a9bb5d733_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.56, 0.42, 0.02, 0.0], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: across all regions, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ce97227bb0007987_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.42, 0.53, 0.04, 0.01], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: across all regions, during the quarterly review. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_59418a57a146b061_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.18, 0.47, 0.3, 0.05], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: during the batch window, mid-incident. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_201c4196616c2a9b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.08, 0.66, 0.25, 0.01], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_97a207dec9d37412_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.16, 0.66, 0.17, 0.0], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f8c815a17fd22454_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: across all regions, following a recent audit. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2720998e9b58624a_n", "kind": "noul", "options": ["false", "true"], "target": [0.51, 0.49], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: across all regions, while legacy systems are still active. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d6823ad76f582175_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.29, 0.57, 0.09, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: across all regions, under an active deadline. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e9bd483e36d9f2cc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.05, 0.72, 0.23, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, with staffing at reduced levels. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a107add0ac8184a2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.39, 0.59, 0.01], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: in production only, immediately after go-live. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e50961d63803a05f_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: during the batch window, mid-incident. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0677194a55bab17a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.33, 0.58, 0.07, 0.02], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_18851c15000e8a45_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: in production only, during the morning shift. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b0df5c416572d945_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during an external partner integration. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5895d69a43055346_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.07, 0.75, 0.17, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: during the batch window, shortly after a software update. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_041f72d06d7bda47_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: across all regions, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e8735976824db8bc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.91, 0.04, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: across all regions, as part of a compliance sweep. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6c0589a8f7672ca7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.3, 0.68, 0.01], "state": "Service catalog-sync 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 operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_572ce95f6864df8b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.41, 0.37, 0.16, 0.06], "state": "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, while legacy systems are still active. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_80bafac4c6d50132_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.22, 0.65, 0.13, 0.0, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: across all regions, while on-call rotation changed. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0a5b464eca72683a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.29, 0.09, 0.17, 0.45], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: across all regions, with staffing at reduced levels. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f4894d5eda76e607_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.49, 0.02, 0.01, 0.48], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: over the last hour, during the quarterly review. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_92b531736a70ec94_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.25, 0.64, 0.02, 0.09], "state": "Service catalog-sync shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: over the last hour, as part of a compliance sweep. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_57e52c160f30209f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.07, 0.86, 0.07], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: across all regions, during the morning shift. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_28ce5a168d2948c9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.18, 0.79, 0.03], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the holiday freeze. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6a50051e067b0ab3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.18, 0.81, 0.01], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: in production only, under reduced staffing. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8d078dbfd2394745_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.02, 0.72, 0.24], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: across all regions, with a new vendor onboarded. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_62180e0ed67f55af_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.29, 0.12, 0.05, 0.54], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: across all regions, while on-call rotation changed. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e6c5564f5604e6b4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.15, 0.83, 0.02], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: in production only, under an active deadline. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_441889217d001877_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.98, 0.01, 0.0, 0.01], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: during the batch window, under an active deadline. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d7934a98d9cdd6e0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.64, 0.34, 0.0], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, under reduced staffing. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_db6ae811deaae4ef_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.46, 0.51, 0.01], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, with staffing at reduced levels. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7f5b673918fe9809_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.02, 0.78, 0.2], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during the system migration. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_de1b40b51882af99_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.18, 0.8, 0.01, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: over the last hour, shortly after a software update. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7c99bd388bed486b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.95, 0.04, 0.0, 0.01], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, under reduced staffing. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_22e8e2d5ea3a6617_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.36, 0.56, 0.06, 0.02], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, at the end of the fiscal period. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b6ca9a63aae78ed9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.11, 0.81, 0.08], "state": "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, shortly after a software update. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_90ce4d95cbab93cf_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: during the batch window, mid-incident. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aa42fc42c8404956_n", "kind": "noul", "options": ["false", "true"], "target": [0.2, 0.8], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: in production only, under an active deadline. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a6b0b1cdc95d7c62_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.15, 0.7, 0.15, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during the holiday freeze. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b4c095a048c4a176_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: during the batch window, while on-call rotation changed. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f66833e95002e0c5_n", "kind": "noul", "options": ["false", "true"], "target": [0.5, 0.5], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: in production only, during normal operations. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_850ab3eafa006973_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.23, 0.51, 0.23, 0.02, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during the holiday freeze. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2a5bb884bc0316f5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.18, 0.79, 0.03], "state": "The metrics pipeline correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: over the last hour, following a recent audit. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5f6d2c2cc249978b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.66, 0.33, 0.0], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: over the last hour, following a recent audit. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e7c9f9ceda672ec5_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.85, 0.15, 0.0, 0.0], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: over the last hour, immediately after go-live. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_914c0743867989c6_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.04, 0.74, 0.22, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: in production only, during the quarterly review. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3b6f5fbda4e73f15_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.05, 0.77, 0.17, 0.0], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: during the batch window, during the morning shift. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5d47ce3af524486f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.78, 0.2, 0.0], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: during the batch window, while on-call rotation changed. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0114da06b3ea90fe_n", "kind": "noul", "options": ["false", "true"], "target": [0.66, 0.34], "state": "Service catalog-sync correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: across all regions, while legacy systems are still active. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fe77291f9843805a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.03, 0.74, 0.22, 0.01], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during an external partner integration. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c2c734aedfc85087_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.57, 0.37, 0.06, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: over the last hour, following a recent audit. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2432e7bd05323337_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.24, 0.34, 0.41, 0.01], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8d282d5e07b87b39_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.39, 0.6, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, following a recent audit. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_51c7701a2c066fcb_n", "kind": "noul", "options": ["false", "true"], "target": [0.42, 0.58], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: over the last hour, as part of a compliance sweep. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f4aa0aa6a3f7e670_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.96, 0.02, 0.01, 0.01], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: over the last hour, under an active deadline. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_24317890bc911412_n", "kind": "noul", "options": ["false", "true"], "target": [0.58, 0.42], "state": "Service catalog-sync shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: during the batch window, following a recent audit. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dc6bf0bdddc100c1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.27, 0.05, 0.29, 0.39], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: in production only, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_69bf2d14198e3dad_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.22, 0.76, 0.02], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: in production only, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fada334b3b0dc509_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.44, 0.54, 0.01], "state": "The log shipper matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: over the last hour, under reduced staffing. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d2d3cb4e87f9d420_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: over the last hour, while legacy systems are still active. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2e57b06362c34ff0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.12, 0.82, 0.06], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: over the last hour, with staffing at reduced levels. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4591add51f7fdc1c_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: in production only, during the morning shift. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7d1c950be418f707_n", "kind": "noul", "options": ["false", "true"], "target": [0.9, 0.1], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: across all regions, during an external partner integration. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0946abd1ce2cba91_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.55, 0.44, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_922f4426e125350c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.27, 0.69, 0.03, 0.01], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: across all regions, at the end of the fiscal period. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_68870693804515e6_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.49, 0.12, 0.19, 0.2], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during the holiday freeze. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_363847a3be0817a3_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: across all regions, shortly after a software update. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2ff29ff1fc9d0f16_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.53, 0.01, 0.02, 0.44], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b8e8427e555dae8e_n", "kind": "noul", "options": ["false", "true"], "target": [0.43, 0.57], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, following a recent audit. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f2f342a03b1c7fc8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.09, 0.27, 0.56, 0.07, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: across all regions, immediately after go-live. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b8c1e1782716be55_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.1, 0.86, 0.04], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during an external partner integration. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_17016241ae04a323_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.07, 0.88, 0.05], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: in production only, during the holiday freeze. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2630bb2524a5d830_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.42, 0.26, 0.16, 0.16], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: in production only, under reduced staffing. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0f012f587812b931_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.69, 0.28, 0.0], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: over the last hour, under reduced staffing. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_59022f50a2c43bb5_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.75, 0.01, 0.15, 0.09], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: during the batch window, during an external partner integration. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_97f7e13f477c367e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.26, 0.74, 0.0], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: across all regions, shortly after a software update. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b1032c0bf9c49f39_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.22, 0.05, 0.36, 0.37], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: across all regions, during the system migration. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b421741fab40cad5_n", "kind": "noul", "options": ["false", "true"], "target": [0.23, 0.77], "state": "The log shipper correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: over the last hour, during an external partner integration. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9341eab3032753f3_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: during the batch window, during the morning shift. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_643ee87e852015ef_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.47, 0.47, 0.06, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: over the last hour, with a new vendor onboarded. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5c9857624b6b7335_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.74, 0.21, 0.01, 0.04], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: across all regions, during the system migration. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d441244fd781c36c_n", "kind": "noul", "options": ["false", "true"], "target": [0.2, 0.8], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: during the batch window, as part of a compliance sweep. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_de8b46cc418260bc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.1616, 0.8182, 0.0202], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: in production only, during an external partner integration. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_57a6ffa2fa805af4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.31, 0.68, 0.01], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: over the last hour, during peak load. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4d327cc1eb0401de_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.18, 0.68, 0.13, 0.01], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: over the last hour, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c9f3695f5fd555d6_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ce12491dd3593248_n", "kind": "noul", "options": ["false", "true"], "target": [0.37, 0.63], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: over the last hour, while on-call rotation changed. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8ebbcd63edc857f5_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "The log shipper reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during normal operations. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6a6a0535e93a2fc7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.65, 0.32, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: during the batch window, following a recent audit. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f05f8adfb98c8353_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "Service catalog-sync lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: across all regions, following a recent audit. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7ecac66d833b6fed_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0da7a7904cda1e12_n", "kind": "noul", "options": ["false", "true"], "target": [0.38, 0.62], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, mid-incident. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_695532197963ace8_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.9, 0.09, 0.0, 0.01], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, shortly after a software update. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2953a8e88794cc2d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.02, 0.86, 0.12], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, shortly after a software update. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_58b5b4c43a7b39e9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.05, 0.11, 0.63, 0.19, 0.01], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: across all regions, with a new vendor onboarded. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6237c1ce5bbad329_n", "kind": "noul", "options": ["false", "true"], "target": [0.61, 0.39], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: across all regions, while legacy systems are still active. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1110ef5f9271cdd1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.32, 0.05, 0.06, 0.57], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_823dc7ff82c23dff_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: in production only, under an active deadline. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a3ff9c1026560def_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.06, 0.92, 0.01], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: across all regions, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_27ff8cfde95ffcc9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.54, 0.45, 0.0], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the system migration. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bdd01ab419590571_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.21, 0.75, 0.04], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: over the last hour, with staffing at reduced levels. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b54d93b3f6d29f4b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.57, 0.42, 0.0], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: over the last hour, at the end of the fiscal period. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_af123adb5b01c0a7_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.05, 0.34, 0.56, 0.05], "state": "Service catalog-sync correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: during the batch window, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4fd84c403fe42b2c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.14, 0.76, 0.1, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: in production only, at the end of the fiscal period. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6a50051e067b0ab3_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: in production only, under reduced staffing. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_83c1a04a4d35d43b_n", "kind": "noul", "options": ["false", "true"], "target": [0.51, 0.49], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: over the last hour, under reduced staffing. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a4378eb2592b221b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.6, 0.33, 0.03, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: during the batch window, following a recent audit. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_be751728064e1ed3_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.74, 0.24], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: during the batch window, while on-call rotation changed. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f2b56130a5395fdf_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.91, 0.07, 0.01, 0.01], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during the system migration. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8eccb6032d1e8dad_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: across all regions, while legacy systems are still active. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2a5bb884bc0316f5_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.18, 0.4, 0.4], "state": "The metrics pipeline correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: over the last hour, following a recent audit. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c2c734aedfc85087_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.43, 0.56, 0.01], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: over the last hour, following a recent audit. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f69c2ae15bbceb50_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.15, 0.81, 0.04], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: across all regions, with staffing at reduced levels. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b04a416fe1f5d3f5_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: across all regions, under an active deadline. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6e163621aee8d149_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.87, 0.11, 0.01, 0.01], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during peak load. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9d9a3a664d376955_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "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.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fe09c177a65ed5d6_n", "kind": "noul", "options": ["false", "true"], "target": [0.48, 0.52], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: over the last hour, during the quarterly review. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e4a7b3fa2b0418cf_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.06, 0.82, 0.12, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: in production only, with a new vendor onboarded. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e6ef5e60b1f1a875_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.05, 0.79, 0.16], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: across all regions, mid-incident. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9e52cd550cc9d742_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.07, 0.58, 0.32, 0.03, 0.0], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, while on-call rotation changed. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8df4554cf94edd62_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.51, 0.47, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: in production only, under reduced staffing. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca00c583e378ef59_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.88, 0.1, 0.01, 0.01], "state": "The log shipper correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during peak load. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_44d8ba99e74061f9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.27, 0.71, 0.02], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: in production only, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_29408bc9bb283b5e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.87, 0.1, 0.0], "state": "Node pgsql-14 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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_af24d39172949aa2_n", "kind": "noul", "options": ["false", "true"], "target": [0.61, 0.39], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: during the batch window, following a recent audit. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9fb4c447d2786c27_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.02, 0.54, 0.43, 0.01], "state": "The metrics pipeline shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: over the last hour, shortly after a software update. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6cb82c4e034f1d18_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.63, 0.33, 0.03, 0.01], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during the quarterly review. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_88848cce2fd90675_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.5, 0.42, 0.07, 0.01], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the quarterly review. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_91ab44ea52730b7e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.41, 0.58, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: across all regions, with a new vendor onboarded. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ec3b535540087519_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.97, 0.0, 0.0, 0.03], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: in production only, mid-incident. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_62b43fe04867b058_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.17, 0.79, 0.03], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: in production only, during an external partner integration. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_90a8c0776af1ee46_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "Service catalog-sync flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: across all regions, immediately after go-live. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_313e404e8e6bbfeb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.3, 0.7, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during the system migration. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_31f8ce2e3f35e2b2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.04, 0.11, 0.58, 0.25, 0.01], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: across all regions, under an active deadline. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0a6556a4f89e8f9f_n", "kind": "noul", "options": ["false", "true"], "target": [0.5, 0.5], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: over the last hour, during the quarterly review. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dde1c5d822c29931_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.12, 0.28, 0.02, 0.58], "state": "Service catalog-sync shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: across all regions, following a recent audit. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_545771beb532c6d1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.43, 0.46, 0.1, 0.01], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: in production only, immediately after go-live. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fc6fae9c93dd288d_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "The log shipper shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: in production only, during normal operations. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c4495876b059c476_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: across all regions, at the end of the fiscal period. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca5e4a3ca7da9bf7_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.0, 0.54, 0.41], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during the morning shift. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_92d757301ecf7334_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: in production only, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9388837cbfcb4d48_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.04, 0.64, 0.29], "state": "The log shipper reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: in production only, during an external partner integration. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0a598b617a354a8e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.54, 0.07, 0.25, 0.14], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: during the batch window, while on-call rotation changed. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6ced1e51ac4f26ed_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: over the last hour, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d856343fe4430ac2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.49, 0.51, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: over the last hour, following a recent audit. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4158b18bfcd543f4_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: across all regions, during normal operations. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7a4cdedf5403fe94_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.58, 0.4, 0.01, 0.01], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: during the batch window, during peak load. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4e55f4c9c32e5985_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.24, 0.05, 0.31, 0.4], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: across all regions, during peak load. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_40c133552346988a_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: over the last hour, during the morning shift. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0be0b7c06c040470_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.53, 0.43, 0.03, 0.01], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: during the batch window, during the morning shift. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9ea1da6b72b93ddf_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the holiday freeze. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_983f19e6b04a733a_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: over the last hour, during peak load. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0953579938936ca9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.16, 0.8, 0.04], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: in production only, following a recent audit. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ef82a64766ff1b8b_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The log shipper flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: across all regions, during the holiday freeze. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_06df768e79b9d9a8_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "The log shipper shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: during the batch window, during peak load. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_114c7cbce3b76295_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.12, 0.01, 0.32, 0.55], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: in production only, during the system migration. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9eb56c666e84894c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.7, 0.26, 0.03, 0.01], "state": "Service catalog-sync flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: during the batch window, under reduced staffing. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f914b958e844f363_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, following a recent audit. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fbd200a761682e17_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "The log shipper reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: during the batch window, during normal operations. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aa847cc6c3735195_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.21, 0.71, 0.08, 0.0, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the morning shift. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_12b1ca0108f9d3dc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.07, 0.7, 0.21, 0.0], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: across all regions, as part of a compliance sweep. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_97a207dec9d37412_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "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.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5347d9814bee19d3_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.46, 0.47, 0.07, 0.0], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: across all regions, during an external partner integration. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_93c306d96afebdb6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.24, 0.74, 0.02], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: over the last hour, while on-call rotation changed. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_01962ea974c463f1_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: during the batch window, with a new vendor onboarded. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fc98218fa5c722aa_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.97, 0.02, 0.01, 0.0], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: in production only, during normal operations. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a3dc59b5d6b06448_n", "kind": "noul", "options": ["false", "true"], "target": [0.55, 0.45], "state": "The log shipper lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: across all regions, as part of a compliance sweep. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9c072b71562fa923_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during the system migration. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_76b6cb67c4d65476_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.54, 0.42, 0.01], "state": "The log shipper shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: in production only, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3ea5399fbd4ad000_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.15, 0.57, 0.26, 0.01], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: across all regions, under an active deadline. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_535a0be05bd9c1c3_n", "kind": "noul", "options": ["false", "true"], "target": [0.52, 0.48], "state": "The metrics pipeline flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: over the last hour, during the morning shift. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d3c87cd61b7833da_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.11, 0.13, 0.28, 0.48], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: over the last hour, following a recent audit. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e9f19f49c216e469_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.96, 0.03, 0.0, 0.01], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, immediately after go-live. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eb5e389c3df44f62_n", "kind": "noul", "options": ["false", "true"], "target": [0.64, 0.36], "state": "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.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_add1200b69a1f53f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.18, 0.36, 0.03, 0.43], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: across all regions, mid-incident. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4e4a57a4719829bc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.19, 0.54, 0.27, 0.0, 0.0], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: across all regions, during normal operations. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fbdffc654aa70f03_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.08, 0.41, 0.5, 0.01, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: over the last hour, following a recent audit. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6b3e5b1c8b2742ff_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.23, 0.51, 0.23, 0.03, 0.0], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, as part of a compliance sweep. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_92d757301ecf7334_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.32, 0.66, 0.01], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: in production only, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a2a493ecb5a37652_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: across all regions, while legacy systems are still active. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2fb97583af14319e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.59, 0.32, 0.06, 0.0], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, following a recent audit. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_44a72213db6e07c8_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: across all regions, shortly after a software update. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b5b3d7710aa6ad81_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.07, 0.6, 0.3, 0.01], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: across all regions, during normal operations. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8c84adcada7333c4_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: in production only, during a scheduled maintenance window. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f1f8a47f530c9642_n", "kind": "noul", "options": ["false", "true"], "target": [0.2, 0.8], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: in production only, with staffing at reduced levels. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ede64889bb55c0c4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.1, 0.78, 0.12, 0.0, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: over the last hour, during the quarterly review. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_642ba8e159385f66_n", "kind": "noul", "options": ["false", "true"], "target": [0.45, 0.55], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cfd18f1f91bb687a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.01, 0.06, 0.47, 0.44, 0.01], "state": "The log shipper reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: in production only, as part of a compliance sweep. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2526672dbfe5fd95_n", "kind": "noul", "options": ["false", "true"], "target": [0.43, 0.57], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: over the last hour, with a new vendor onboarded. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e68b5989e2bc26ae_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: across all regions, during an external partner integration. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_62ca2397d7ea004a_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, while legacy systems are still active. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_81bd92ca93f66a16_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.7, 0.27, 0.0], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: across all regions, during normal operations. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_643b0f6292bc9ded_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "Service catalog-sync shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: across all regions, mid-incident. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9dc9baa71baebcb3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.03, 0.16, 0.71, 0.09, 0.0], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: over the last hour, while on-call rotation changed. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b32cb2fd2ae1c20a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.95, 0.0, 0.05], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: during the batch window, shortly after a software update. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_391da02debb82c27_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.11, 0.26, 0.04, 0.59], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: in production only, following a recent audit. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8b29e9a77ec9154c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.14, 0.81, 0.05], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: across all regions, shortly after a software update. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9a4c6c8f98b76f55_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.38, 0.55, 0.02, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: across all regions, during an external partner integration. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_41d57618c7dd9289_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.36, 0.12, 0.35, 0.17], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during the holiday freeze. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_db711bf7b1a5387d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.1, 0.87, 0.03], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, while legacy systems are still active. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ffd83784bc1b9b1c_n", "kind": "noul", "options": ["false", "true"], "target": [0.6, 0.4], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: across all regions, with a new vendor onboarded. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b34b61806288b565_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.54, 0.01, 0.01, 0.44], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: during the batch window, during peak load. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_45b5b5d537acd377_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: during the batch window, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7fcbabbdf44a2632_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.07, 0.5, 0.42, 0.01, 0.0], "state": "The log shipper reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: during the batch window, while legacy systems are still active. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b9a8ffee826f927e_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "The log shipper reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: across all regions, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_30de2b3611a65718_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.89, 0.07, 0.01, 0.03], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during the holiday freeze. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0694db7aff2095ff_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: during the batch window, during the morning shift. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_22e8e2d5ea3a6617_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.54, 0.46, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, at the end of the fiscal period. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_716ee0bd230f6f27_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.67, 0.27, 0.01], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: in production only, during the quarterly review. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_99f2ee62848e722f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.22, 0.76, 0.02], "state": "The metrics pipeline 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 review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e1b0750dd323948a_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: during the batch window, while legacy systems are still active. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_60a31bf32c9102ad_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.59, 0.14, 0.25, 0.02], "state": "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 system migration. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_37bc51b60bb6e4be_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: across all regions, with staffing at reduced levels. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_53674e7834c3672f_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The log shipper correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during peak load. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8b29e9a77ec9154c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.8182, 0.1717, 0.0, 0.0101], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: across all regions, shortly after a software update. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_039f2146f7a14c26_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.74, 0.21, 0.0], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the system migration. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4f36d753fea92451_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.86, 0.13, 0.01, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: over the last hour, shortly after a software update. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bd0eba2064548ae1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.16, 0.8, 0.04], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: in production only, under reduced staffing. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ce79b3d0b1bba8db_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.4, 0.27, 0.01, 0.32], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the quarterly review. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8fc965df426e2755_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.82, 0.14, 0.01, 0.03], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the morning shift. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5526a3623cfc4bd4_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: during the batch window, mid-incident. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a5922e94d551074a_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: over the last hour, with staffing at reduced levels. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_783d2c3cfc0142b6_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "The metrics pipeline shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during peak load. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_08bcbe44d03d599e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.69, 0.0, 0.07, 0.24], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: across all regions, under reduced staffing. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4c06da280a9854e8_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "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, while on-call rotation changed. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fe9df27e1c7fd446_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "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.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e8e31882d7461093_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.37, 0.48, 0.14, 0.01], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: over the last hour, immediately after go-live. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_96d04de87344f636_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.04, 0.63, 0.33, 0.0], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_99a807a1dff5a047_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.55, 0.32, 0.13, 0.0, 0.0], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: across all regions, during a scheduled maintenance window. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2f335d0fc964897d_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, following a recent audit. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4588982227a81cf6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.16, 0.82, 0.02], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, following a recent audit. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_afe0382cc9655d87_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "The log shipper lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: across all regions, with a new vendor onboarded. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_489da28cd4632431_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.35, 0.55, 0.09, 0.01], "state": "The metrics pipeline lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: across all regions, immediately after go-live. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_58dadfd5861b2f57_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.02, 0.59, 0.27, 0.12, 0.0, 0.0], "state": "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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_56088222b0d835e9_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "The log shipper matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: during the batch window, during the holiday freeze. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5dac6b76785e32f7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.18, 0.8, 0.02], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, under reduced staffing. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9cf1c0aef69ec2f9_n", "kind": "noul", "options": ["false", "true"], "target": [0.41, 0.59], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: over the last hour, during the quarterly review. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5bf80dbc65f780e1_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: across all regions, under an active deadline. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e433e948e8425db3_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.81, 0.1, 0.09, 0.0], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9d87bb3b5405569f_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "The log shipper matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: across all regions, under an active deadline. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7982f8d565dc8cb8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.5, 0.49, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: in production only, while legacy systems are still active. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d94eb0cdc616e78b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.88, 0.1, 0.01, 0.01], "state": "Service catalog-sync flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: across all regions, mid-incident. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_81db8384c36f4643_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.65, 0.32, 0.02, 0.01], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: across all regions, during the morning shift. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_948026183c6b5ba3_n", "kind": "noul", "options": ["false", "true"], "target": [0.57, 0.43], "state": "Service catalog-sync lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: across all regions, with a new vendor onboarded. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f46b7b7f7117dbe3_n", "kind": "noul", "options": ["false", "true"], "target": [0.5, 0.5], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: in production only, during peak load. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f2e825d080e92416_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.23, 0.75], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: during the batch window, with a new vendor onboarded. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_04680219b6ac46a2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.47, 0.42, 0.11, 0.0, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: during the batch window, during a scheduled maintenance window. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_85862de7230ae993_n", "kind": "noul", "options": ["false", "true"], "target": [0.93, 0.07], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, immediately after go-live. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_12d5cd5faff2bb64_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: over the last hour, while legacy systems are still active. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_391da02debb82c27_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: in production only, following a recent audit. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_924b0bcead71b0e7_n", "kind": "noul", "options": ["false", "true"], "target": [0.71, 0.29], "state": "The log shipper shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during normal operations. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aace833266e130a9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.02, 0.5, 0.48], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: over the last hour, mid-incident. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2b7a005747dd22c6_n", "kind": "noul", "options": ["false", "true"], "target": [0.71, 0.29], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: across all regions, during the system migration. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0c619429577bda08_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.31, 0.68, 0.01], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: over the last hour, at the end of the fiscal period. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_caa940303ee6411b_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "The log shipper lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: in production only, while on-call rotation changed. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aec8610f6543fe11_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.56, 0.43, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: during the batch window, under an active deadline. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e784c803e5cb8bb7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.08, 0.83, 0.09], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: during the batch window, under an active deadline. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_de73388b593aaeef_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.1, 0.02, 0.25, 0.63], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: across all regions, under an active deadline. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_71f5c4b8f6778c01_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.37, 0.39, 0.07, 0.17], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during the holiday freeze. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_da0f99f458880cd2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.34, 0.65, 0.01], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, under an active deadline. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3dc5bdb51f48200a_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: in production only, while on-call rotation changed. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8b710a9ef2d60041_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.5, 0.44, 0.05, 0.01], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: in production only, during the holiday freeze. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_87140ad0960ddcf1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.16, 0.65, 0.18, 0.01, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, at the end of the fiscal period. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_14ff907d4eb2c923_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.55, 0.43, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: during the batch window, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ade0fbc0c3a1a2c5_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.07, 0.79, 0.13, 0.01], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: in production only, as part of a compliance sweep. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_71627c66668d1994_n", "kind": "noul", "options": ["false", "true"], "target": [0.19, 0.81], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, under an active deadline. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3bb1507f8d990ce1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.56, 0.42, 0.02, 0.0], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: across all regions, during the system migration. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_806a4c7aadc29ca9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.13, 0.81, 0.06], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during the holiday freeze. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c53b28285db824fc_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.57, 0.36, 0.06, 0.01], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: across all regions, during normal operations. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_160cdd3dd043a27d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.08, 0.51, 0.4, 0.01, 0.0], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: over the last hour, during the system migration. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fa63b45c46118f50_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.43, 0.41, 0.14, 0.0], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, while legacy systems are still active. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_40954c272b630d12_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.96, 0.02, 0.01, 0.01], "state": "Service catalog-sync shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: over the last hour, under an active deadline. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b34c139b172551c0_n", "kind": "noul", "options": ["false", "true"], "target": [0.92, 0.08], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: during the batch window, during the quarterly review. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_62dd3bead9de260c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.42, 0.58, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during an external partner integration. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d5ccbe15f3edec00_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "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, during a scheduled maintenance window. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_70dba855f742f405_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.07, 0.62, 0.3, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during a scheduled maintenance window. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_83417674c61ac02e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.79, 0.2, 0.01, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, following a recent audit. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_823dc7ff82c23dff_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.02, 0.05, 0.05, 0.26, 0.54, 0.08], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: in production only, under an active deadline. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5e9d952bf9dc08d7_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.02, 0.33, 0.63, 0.02], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: in production only, during a scheduled maintenance window. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f93a5062e3ab5f9b_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: during the batch window, immediately after go-live. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b7932b2beafa05ca_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.36, 0.23, 0.02, 0.39], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: in production only, during the quarterly review. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bcd2099fd86ecfb1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.05, 0.01, 0.9], "state": "The log shipper flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: in production only, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_16bc14f2836ed622_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: in production only, during peak load. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_039fa142e996e655_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.24, 0.67, 0.09, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, with staffing at reduced levels. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bad31f7da30df058_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.12, 0.82, 0.06], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: in production only, while on-call rotation changed. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_15403d7b1d1f70cd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.14, 0.8, 0.06], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: in production only, during the system migration. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b0ee988fdcd0dd9e_n", "kind": "noul", "options": ["false", "true"], "target": [0.9, 0.1], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, mid-incident. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f2f342a03b1c7fc8_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.65, 0.33, 0.01], "state": "The log shipper returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: across all regions, immediately after go-live. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0df54c65d26d8aad_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.27, 0.7, 0.02], "state": "The log shipper reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: over the last hour, under an active deadline. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f93549a551cfb627_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.26, 0.37, 0.02, 0.35], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the holiday freeze. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_99f3d2731b2ce39a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.03, 0.57, 0.38, 0.02], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during normal operations. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b3a065abe5ac952f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.07, 0.2, 0.68, 0.05, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: over the last hour, during the system migration. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8e70add2b7ab95a2_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during the quarterly review. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7bf2dabf5c336abd_n", "kind": "noul", "options": ["false", "true"], "target": [0.92, 0.08], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, while legacy systems are still active. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_faa0c9d12b8ff945_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.07, 0.49, 0.42, 0.01], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: over the last hour, immediately after go-live. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dad03a35041a0fdb_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: across all regions, shortly after a software update. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1da04e52cc450f8f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.48, 0.4, 0.1, 0.02], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: over the last hour, following a recent audit. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_00bdfdf29e75ccae_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "The log shipper shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: during the batch window, with a new vendor onboarded. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7c7fc28576c8a52e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.77, 0.01, 0.07, 0.15], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: across all regions, with a new vendor onboarded. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_32d548996da2a524_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.14, 0.76, 0.08, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during the quarterly review. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_611781dbf5d6f870_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.25, 0.72, 0.02, 0.01], "state": "The log shipper lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, following a recent audit. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9e1bd1d0b7ac74b9_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "The log shipper flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: in production only, immediately after go-live. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_459f77caccb20912_n", "kind": "noul", "options": ["false", "true"], "target": [0.49, 0.51], "state": "The log shipper matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: across all regions, following a recent audit. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6cc342b089e81b8f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.2, 0.54, 0.25, 0.01, 0.0], "state": "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, during the holiday freeze. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_495296d44a858770_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.12, 0.79, 0.09, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: across all regions, immediately after go-live. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_158aff2274a24460_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.75, 0.24, 0.01, 0.0], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: in production only, with a new vendor onboarded. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5f90afac4d38f712_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: over the last hour, at the end of the fiscal period. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f91f438ad72795db_n", "kind": "noul", "options": ["false", "true"], "target": [0.23, 0.77], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: during the batch window, under an active deadline. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f3fbfe3f13be8618_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.06, 0.6, 0.32, 0.02], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, shortly after a software update. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1cece41bb8882a49_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.56, 0.42, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: over the last hour, during the quarterly review. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_382ea4987732ecb7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.06, 0.28, 0.6, 0.05, 0.0], "state": "The metrics pipeline correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: across all regions, during an external partner integration. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6c0b27c6f8493c29_n", "kind": "noul", "options": ["false", "true"], "target": [0.69, 0.31], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the holiday freeze. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_47a22788d012fdad_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.04, 0.85, 0.11, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: across all regions, while on-call rotation changed. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ffd83784bc1b9b1c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.63, 0.34, 0.0], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: across all regions, with a new vendor onboarded. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3c38daa65961c11c_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "The log shipper matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during an external partner integration. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4e75e7300d0dc4bd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.65, 0.35, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: in production only, while on-call rotation changed. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f1cd3e6c603143d2_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: across all regions, mid-incident. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_37bfb5864df374db_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: across all regions, while on-call rotation changed. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_de3856d8a7d7af71_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.87, 0.11, 0.01, 0.01], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: in production only, under reduced staffing. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d73c6d72a77ca8f6_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "The log shipper matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: across all regions, while on-call rotation changed. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_53d1c4a3a969f2d1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.96, 0.0, 0.0, 0.04], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during peak load. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2bfc7efc31d78a61_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.58, 0.4, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: in production only, as part of a compliance sweep. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dc6a2ddbfcdfd694_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.1, 0.85, 0.05], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: over the last hour, under an active deadline. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f46b7b7f7117dbe3_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.15, 0.33, 0.5, 0.02], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: in production only, during peak load. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e6f70824e113871d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.42, 0.56, 0.01], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: across all regions, with a new vendor onboarded. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_676e54d127c715db_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.21, 0.27, 0.01, 0.51], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: over the last hour, during normal operations. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e2cf82a972782e3e_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: over the last hour, with staffing at reduced levels. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d7616fff436ca2fb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.55, 0.44, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during the quarterly review. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_85e42931c51afe9c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.3, 0.39, 0.04, 0.27], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: during the batch window, during a scheduled maintenance window. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_35dc5d4135893953_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: in production only, while legacy systems are still active. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_58f0cba1a01d3beb_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: in production only, under reduced staffing. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d359e2525c4a5b38_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: over the last hour, while on-call rotation changed. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_49eebbb3924e5ffe_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.31, 0.63, 0.01, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: during the batch window, while on-call rotation changed. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3d71a0710ce451e2_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.29, 0.63, 0.04, 0.04], "state": "Service catalog-sync lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: during the batch window, following a recent audit. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c892194b64a23f3a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.19, 0.1, 0.41, 0.3], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: during the batch window, with a new vendor onboarded. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c43105c2477b140d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.25, 0.0, 0.09, 0.66], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during a scheduled maintenance window. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_98ffdff94b2f3ace_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.03, 0.49, 0.46, 0.01], "state": "The metrics pipeline correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: across all regions, under reduced staffing. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6b6ba21fa496b324_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.53, 0.4, 0.07, 0.0], "state": "Service catalog-sync flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: in production only, during the quarterly review. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0c56d6c57195d946_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.54, 0.45, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: across all regions, during the system migration. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5ad9ba3b567d3a5f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.61, 0.35, 0.02, 0.02], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: during the batch window, at the end of the fiscal period. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a4235990da8291af_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.6, 0.39, 0.0], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: across all regions, while on-call rotation changed. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_72d23f145204e5de_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.17, 0.56, 0.22, 0.01], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: over the last hour, under an active deadline. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_329c2b47632bf512_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.9, 0.0, 0.0, 0.1], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during the holiday freeze. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_42687d3a22a345bf_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.57, 0.41, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: over the last hour, shortly after a software update. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_33192132a822fc84_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "The log shipper reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: across all regions, following a recent audit. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_88e59bf617b7f237_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during the quarterly review. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d99b757add51b1e3_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.51, 0.03, 0.01, 0.45], "state": "The log shipper lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: over the last hour, under reduced staffing. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_68e841043ccc5fe5_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: in production only, as part of a compliance sweep. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a5922e94d551074a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.11, 0.01, 0.84, 0.04], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: over the last hour, with staffing at reduced levels. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_98ffdff94b2f3ace_n", "kind": "noul", "options": ["false", "true"], "target": [0.66, 0.34], "state": "The metrics pipeline correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: across all regions, under reduced staffing. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_86d8cf82e5e3f28b_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, with staffing at reduced levels. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5cb2e9fc974bc9f2_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "The log shipper matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: in production only, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5eb6585f11572cda_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.06, 0.57, 0.35, 0.01], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: across all regions, during the morning shift. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1f75f3df91776261_n", "kind": "noul", "options": ["false", "true"], "target": [0.46, 0.54], "state": "The log shipper flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: across all regions, during the quarterly review. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_780c994c600c207e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.54, 0.35, 0.1, 0.0], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during peak load. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0f0db5e05eecc9fd_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: in production only, at the end of the fiscal period. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_523114ae4c36d008_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.13, 0.06, 0.79], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: in production only, as part of a compliance sweep. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_49eebbb3924e5ffe_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.01, 0.43, 0.54], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: during the batch window, while on-call rotation changed. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aa09988c9f95d0d6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.47, 0.53, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: in production only, with staffing at reduced levels. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3ce4acf51d346757_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.59, 0.41, 0.0, 0.0], "state": "The log shipper reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: during the batch window, during the system migration. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5b23949d7b2ed66d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.25, 0.1, 0.17, 0.48], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: in production only, during the quarterly review. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2630bb2524a5d830_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: in production only, under reduced staffing. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e9d3e82390401326_n", "kind": "noul", "options": ["false", "true"], "target": [0.9, 0.1], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: in production only, under an active deadline. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c4ccfb6b0d5ce71c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.2, 0.77, 0.03], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: over the last hour, at the end of the fiscal period. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e417c87ce8250017_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.35, 0.51, 0.13, 0.01], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during normal operations. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2bb3641a1eb7a94a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.09, 0.8, 0.1, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during an external partner integration. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ff85ab7601af8108_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.12, 0.84, 0.04], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, at the end of the fiscal period. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1f22b8a0b74fd9db_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during the system migration. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ef70e3343e54b02c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.11, 0.15, 0.32, 0.42], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally matches last Tuesday's incident signature. Context: in production only, while legacy systems are still active. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d080312d52c4565a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.53, 0.46, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during an external partner integration. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_730e3426a2252ae4_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.5, 0.48], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: during the batch window, as part of a compliance sweep. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_43368c76580c1474_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.08, 0.87, 0.05], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, with a new vendor onboarded. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9f2b2b697e34f733_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.19, 0.07, 0.7], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: across all regions, following a recent audit. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b6afaf1df11e5af1_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: in production only, while legacy systems are still active. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bef9b191e1d0c70e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.18, 0.08, 0.05, 0.69], "state": "Service catalog-sync flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during a scheduled maintenance window. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bb8e94f5641551b6_n", "kind": "noul", "options": ["false", "true"], "target": [0.65, 0.35], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: in production only, shortly after a software update. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9c072b71562fa923_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.05, 0.82, 0.13], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during the system migration. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bf69ee53b0d543e8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.52, 0.44, 0.02, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: during the batch window, during an external partner integration. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e2b7a60a9f4f4bd5_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "The log shipper reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, with staffing at reduced levels. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_39aeb46f116e7d32_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.25, 0.65, 0.1, 0.0, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during the quarterly review. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bf5572c29b0ec1c1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.53, 0.46, 0.0], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: during the batch window, following a recent audit. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_83dbfe07a39d825b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.64, 0.36, 0.0], "state": "The log shipper flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: in production only, during an external partner integration. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a580bbedec231618_n", "kind": "noul", "options": ["false", "true"], "target": [0.67, 0.33], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: across all regions, under an active deadline. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fe3b1f7d55694093_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.73, 0.14, 0.05, 0.08], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: over the last hour, with staffing at reduced levels. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e7c89786e3fe5f4d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.8, 0.19, 0.0, 0.01], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: in production only, immediately after go-live. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_349eb495867da9be_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.25, 0.73, 0.02], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, following a recent audit. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1b032c047138273a_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "Service catalog-sync flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: across all regions, during the system migration. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1411322a8f5a0b55_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.19, 0.77, 0.04], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: across all regions, mid-incident. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_11e964bfae4d2d86_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.74, 0.21, 0.05, 0.0], "state": "The metrics pipeline correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: in production only, at the end of the fiscal period. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3e99da57536937ff_n", "kind": "noul", "options": ["false", "true"], "target": [0.55, 0.45], "state": "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, during a scheduled maintenance window. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_978885345c00db55_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.02, 0.84, 0.12], "state": "The log shipper flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: over the last hour, during the quarterly review. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0a598b617a354a8e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.09, 0.88, 0.03], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: during the batch window, while on-call rotation changed. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_03eb9e078a1f10e1_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during an external partner integration. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_da464cff8aa41c4a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.1, 0.73, 0.15], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: across all regions, with a new vendor onboarded. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fd10d3a5ff659962_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.54, 0.43, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: during the batch window, during peak load. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_35fe5832ff65d88c_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_65164c533f2393ba_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: in production only, while legacy systems are still active. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c812a58afe61bf79_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.01, 0.6, 0.35], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: across all regions, under reduced staffing. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_70fcab06027d3899_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.54, 0.45, 0.0], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: over the last hour, during the holiday freeze. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_79f01c0f89c28453_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.17, 0.27, 0.04, 0.52], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, immediately after go-live. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f6e28c5d9c22b95b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.17, 0.19, 0.6], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, while legacy systems are still active. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fa187083df92d77e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.28, 0.65, 0.07, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: during the batch window, as part of a compliance sweep. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_67e0e30fbee38639_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: over the last hour, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3da45301c58c42fa_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.6, 0.35, 0.0], "state": "The metrics pipeline correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: over the last hour, under reduced staffing. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aa5d18ec98978de7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.31, 0.66, 0.02], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: over the last hour, under an active deadline. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_47740b1e2abd1e22_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.53, 0.12, 0.07, 0.28], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: in production only, under reduced staffing. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_44a715877fcd8676_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.95, 0.03, 0.01, 0.01], "state": "The metrics pipeline flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: in production only, mid-incident. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2466a8342d40299f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.08, 0.53, 0.37, 0.02, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: during the batch window, at the end of the fiscal period. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5d56181bcae176a6_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "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.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6c0b27c6f8493c29_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.79, 0.17, 0.03, 0.01], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the holiday freeze. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b9fe556e15174b6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.49, 0.48, 0.01], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: during the batch window, during peak load. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_10c2f3f1f35b3d1a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.89, 0.1, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: during the batch window, under reduced staffing. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a2d7c5bbdcaf2edb_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.55, 0.41, 0.03, 0.01], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during an external partner integration. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5f0dae60abf4458c_n", "kind": "noul", "options": ["false", "true"], "target": [0.23, 0.77], "state": "Service catalog-sync lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: during the batch window, during an external partner integration. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6583018f16aa9359_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.4, 0.59, 0.0], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: over the last hour, with staffing at reduced levels. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_222f73525a210641_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.76, 0.22, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: over the last hour, mid-incident. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9d24cfbcc94b5141_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.02, 0.14, 0.22, 0.54, 0.08, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: in production only, under reduced staffing. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_41bf9e113bd3a250_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.52, 0.47, 0.0], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: in production only, with a new vendor onboarded. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_29b1c08efa168ca1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.18, 0.52, 0.3, 0.0, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: over the last hour, as part of a compliance sweep. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_21545266b9a28ef2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.03, 0.75, 0.22], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: in production only, under an active deadline. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_430cf1663cca259e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.26, 0.71, 0.02], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: in production only, following a recent audit. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_42c2d907b8a801ec_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.87, 0.12, 0.0, 0.01], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: across all regions, shortly after a software update. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bcec6f69a8081c83_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.06, 0.83, 0.11], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: across all regions, during the holiday freeze. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_043b3dfbb10dd9a3_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during the quarterly review. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f7987fdfe8b283a9_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: in production only, at the end of the fiscal period. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f1313939091f7e4c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.01, 0.95, 0.04], "state": "Service catalog-sync correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: in production only, during the holiday freeze. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_253dbcccfc42da32_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.16, 0.64, 0.18, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: in production only, immediately after go-live. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9288f70d1659263c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.77, 0.19, 0.02, 0.02], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: in production only, during the holiday freeze. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_792ec7d963d3857a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.05, 0.52, 0.39, 0.01], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: over the last hour, during a scheduled maintenance window. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bc9401edbbc3d49c_n", "kind": "noul", "options": ["false", "true"], "target": [0.43, 0.57], "state": "The log shipper lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: in production only, during peak load. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c6fa919258ccfb20_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.14, 0.07, 0.15, 0.64], "state": "The log shipper flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during a scheduled maintenance window. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d7c31087b955fa59_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.14, 0.82, 0.04], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: across all regions, during the system migration. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3f90bca40ad12a23_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.01, 0.01, 0.21, 0.72, 0.04], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: in production only, during an external partner integration. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_75b2a76312b611d0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.16, 0.8, 0.04], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: across all regions, with staffing at reduced levels. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5de635d89ae898b3_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.27, 0.34, 0.03, 0.36], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: in production only, at the end of the fiscal period. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b88a8c95ac44dff3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.06, 0.41, 0.43, 0.08, 0.01], "state": "The log shipper matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, mid-incident. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_18d7c93f64d3dcc1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.29, 0.7, 0.01], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, immediately after go-live. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5446519d9b810c3e_n", "kind": "noul", "options": ["false", "true"], "target": [0.62, 0.38], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: over the last hour, immediately after go-live. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_76b761f30a9a7c18_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.72, 0.22, 0.05, 0.01], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: over the last hour, under reduced staffing. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_91549f3bc93c3dc1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.22, 0.77, 0.01], "state": "The metrics pipeline flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: during the batch window, shortly after a software update. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7e3a9f077ade4737_n", "kind": "noul", "options": ["false", "true"], "target": [0.51, 0.49], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the holiday freeze. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_455f09eefb92e1fa_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.65, 0.26, 0.09, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: over the last hour, during normal operations. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c83b4d2ba6baf482_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "The log shipper matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: during the batch window, mid-incident. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d85562652e7126d1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.23, 0.01, 0.11, 0.65], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: in production only, at the end of the fiscal period. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8026e20213a82627_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.18, 0.8, 0.02], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: over the last hour, while on-call rotation changed. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1bb2241d0d53075a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.09, 0.41, 0.46, 0.03, 0.0], "state": "The log shipper correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, following a recent audit. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_036c6e90a816311e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.36, 0.21, 0.01, 0.42], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: over the last hour, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5ab9935e50701bc1_n", "kind": "noul", "options": ["false", "true"], "target": [0.54, 0.46], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: over the last hour, with a new vendor onboarded. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5d7aa24ab5384821_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.44, 0.54, 0.01, 0.01], "state": "The log shipper correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: across all regions, with a new vendor onboarded. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b0f8c6e1133385a_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: during the batch window, at the end of the fiscal period. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_78dcad523bfdb292_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.81, 0.01, 0.13, 0.05], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: during the batch window, while legacy systems are still active. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b6687f174cc9f185_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.0, 0.85, 0.15], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: over the last hour, mid-incident. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_db23f7f2e0290efc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.31, 0.67, 0.02], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, immediately after go-live. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_77a43e0b963196a8_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.29, 0.45, 0.06, 0.2], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: in production only, during normal operations. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fb04856443154bd8_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: during the batch window, with a new vendor onboarded. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9ffb5b5d6c4ace52_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.22, 0.03, 0.21, 0.54], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: in production only, during the holiday freeze. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fb591d0b8976cb74_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: over the last hour, with a new vendor onboarded. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_51c7701a2c066fcb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.13, 0.38, 0.47, 0.01, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: over the last hour, as part of a compliance sweep. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b206ce9324c63cc_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.98, 0.0, 0.0, 0.02], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during the quarterly review. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e3a420e8604f6bfb_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during the holiday freeze. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d95a591b3f79cbb1_n", "kind": "noul", "options": ["false", "true"], "target": [0.52, 0.48], "state": "The log shipper matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, under reduced staffing. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d370006c9d89eb00_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.4, 0.3, 0.3], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: over the last hour, shortly after a software update. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_75cf109945554dd7_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.93, 0.06, 0.01, 0.0], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, mid-incident. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f8f8235b3a8ec38e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.59, 0.04, 0.03, 0.34], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: during the batch window, with staffing at reduced levels. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_52b2650c3ba43b93_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.98, 0.01, 0.0, 0.01], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, immediately after go-live. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4dde4a2ef14c7dd4_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, under reduced staffing. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_05960ad92306a4af_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: across all regions, with staffing at reduced levels. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3c38daa65961c11c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.78, 0.2, 0.01, 0.01], "state": "The log shipper matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during an external partner integration. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5de69367a0e305c1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.3, 0.52, 0.13, 0.05], "state": "The log shipper shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during a scheduled maintenance window. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8705e53da2e25089_n", "kind": "noul", "options": ["false", "true"], "target": [0.65, 0.35], "state": "Service catalog-sync shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: over the last hour, following a recent audit. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bdfcb254d9376760_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.46, 0.48, 0.05, 0.01], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: across all regions, as part of a compliance sweep. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c74a3d4e65c9743f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.21, 0.01, 0.28, 0.5], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during a scheduled maintenance window. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8fc965df426e2755_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the morning shift. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e6f70824e113871d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.39, 0.6, 0.01, 0.0], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: across all regions, with a new vendor onboarded. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_04812f79194213ba_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: across all regions, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_547253d9595610e7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.4, 0.53, 0.06, 0.0], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: across all regions, shortly after a software update. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_74c16b94646863db_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: across all regions, during the quarterly review. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_62b43fe04867b058_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.09, 0.53, 0.3, 0.08, 0.0, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: in production only, during an external partner integration. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a7a560de3d09e969_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.95, 0.04, 0.0, 0.01], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: during the batch window, mid-incident. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b4b6f5d7fed02caa_n", "kind": "noul", "options": ["false", "true"], "target": [0.66, 0.34], "state": "The metrics pipeline 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 monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d8fe699ad5d2466e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.1313, 0.8182, 0.0505], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during normal operations. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bf37d4ce777a4153_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.66, 0.31, 0.0], "state": "The log shipper matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: across all regions, during the system migration. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_921101e5a60627a9_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: in production only, while on-call rotation changed. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_164eea183b0fbbef_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.07, 0.89, 0.04], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during the morning shift. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f20c931e3b0c4eff_n", "kind": "noul", "options": ["false", "true"], "target": [0.22, 0.78], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, shortly after a software update. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e60673a904e76c15_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.23, 0.02, 0.01, 0.74], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: in production only, under an active deadline. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_27e558ccf20c20ac_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.1616, 0.8182, 0.0202], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: in production only, during peak load. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_62efc6c17ae9fdcf_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.77, 0.21, 0.0], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: during the batch window, following a recent audit. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_59d4af37f278b8ba_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.06, 0.85, 0.08, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: over the last hour, at the end of the fiscal period. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_60bfb4d08b612946_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.58, 0.41, 0.01, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: during the batch window, with staffing at reduced levels. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_25000f5928f5bef2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.21, 0.77, 0.02], "state": "The log shipper correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during the morning shift. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5b5c228d79a2bd9b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.3, 0.64, 0.02, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: during the batch window, during normal operations. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_44c2fd5fbe4194bc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.44, 0.54, 0.01], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: during the batch window, during normal operations. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_137bc5b4eaa7f808_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.92, 0.06, 0.0, 0.02], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: over the last hour, under reduced staffing. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_69c45c3caf7d632b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.38, 0.11, 0.01, 0.5], "state": "The log shipper reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: over the last hour, during normal operations. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1a29f885c3d05831_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.63, 0.03, 0.31], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: in production only, shortly after a software update. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bf69ee53b0d543e8_n", "kind": "noul", "options": ["false", "true"], "target": [0.44, 0.56], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: during the batch window, during an external partner integration. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9b0c0906c5bc945e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.63, 0.36, 0.01, 0.0], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: in production only, following a recent audit. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f1a9b30315d91a07_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.64, 0.35, 0.0], "state": "The log shipper flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: during the batch window, while legacy systems are still active. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0770212636f5d27c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.05, 0.35, 0.34, 0.25, 0.01, 0.0], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during a scheduled maintenance window. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_91ed4f963370609b_n", "kind": "noul", "options": ["false", "true"], "target": [0.59, 0.41], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: across all regions, shortly after a software update. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0f6b7cca0e439c2c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.59, 0.39, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: across all regions, during the quarterly review. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_250d831c47edb2ac_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.67, 0.31, 0.0], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: during the batch window, with a new vendor onboarded. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e02693215c5a56a6_n", "kind": "noul", "options": ["false", "true"], "target": [0.47, 0.53], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: over the last hour, under an active deadline. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_51595f59048edd37_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.47, 0.15, 0.02, 0.36], "state": "Service catalog-sync flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: across all regions, under reduced staffing. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_08f3b6f97e294c26_n", "kind": "noul", "options": ["false", "true"], "target": [0.66, 0.34], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: in production only, as part of a compliance sweep. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_da3a579b97150681_n", "kind": "noul", "options": ["false", "true"], "target": [0.47, 0.53], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: in production only, during normal operations. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6d9c67773da404b5_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "The log shipper reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: across all regions, following a recent audit. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_245db2010c6eae9a_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, with staffing at reduced levels. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c9cb7279de74fac6_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.15, 0.26, 0.49, 0.1], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: during the batch window, immediately after go-live. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b3cc7f981c5e0a32_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.02, 0.33, 0.62, 0.03], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: over the last hour, while legacy systems are still active. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_be751728064e1ed3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.24, 0.36, 0.38, 0.01, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: during the batch window, while on-call rotation changed. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_21d9312f011dad51_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.93, 0.01, 0.06], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: in production only, shortly after a software update. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_29d8e6db5da11b07_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.8, 0.18, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: across all regions, while on-call rotation changed. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fe77291f9843805a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.04, 0.73, 0.23, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during an external partner integration. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3672ae046d55d2ff_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.21, 0.33, 0.01, 0.45], "state": "The log shipper lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: during the batch window, during normal operations. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_725e9aaf55d22216_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "The log shipper lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: in production only, shortly after a software update. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_32e3f751ca931a42_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.33, 0.67, 0.0], "state": "The metrics pipeline shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: in production only, under reduced staffing. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_02b13446645be3cd_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.19, 0.15, 0.03, 0.63], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: in production only, with staffing at reduced levels. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7f2cc0b58144cbed_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.35, 0.65, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, under reduced staffing. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d5455356765de767_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.25, 0.59, 0.11, 0.0], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: during the batch window, mid-incident. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_21545266b9a28ef2_n", "kind": "noul", "options": ["false", "true"], "target": [0.21, 0.79], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: in production only, under an active deadline. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5c779e882d549770_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The log shipper reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: during the batch window, following a recent audit. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c43c84a42210daa8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.1, 0.48, 0.38, 0.02], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: across all regions, during the holiday freeze. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_35fd00d075629b6a_n", "kind": "noul", "options": ["false", "true"], "target": [0.5, 0.5], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during the holiday freeze. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0a7bc4d0e4d42da2_n", "kind": "noul", "options": ["false", "true"], "target": [0.6, 0.4], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: in production only, at the end of the fiscal period. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fc96fde01460ee2d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.38, 0.6, 0.01], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: in production only, under reduced staffing. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_920f01907e47b37f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.09, 0.82, 0.09], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, while on-call rotation changed. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1563756c8a653554_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "The log shipper matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: over the last hour, during the holiday freeze. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_784e2f3580225024_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.65, 0.35, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: during the batch window, mid-incident. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8abcef8b15663aa6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.09, 0.87, 0.04], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, while on-call rotation changed. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e464111270074045_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.68, 0.14, 0.11, 0.07], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: across all regions, mid-incident. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d9a3e2a7985ac952_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.11, 0.04, 0.36, 0.49], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: across all regions, as part of a compliance sweep. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3f1331550dd99f51_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.15, 0.61, 0.19, 0.05, 0.0, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the system migration. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_37ae90525cfdba8c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.09, 0.86, 0.05], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca65bf31326b313d_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "The log shipper shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: over the last hour, while legacy systems are still active. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_456350603fa2e7af_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.11, 0.62, 0.23, 0.0], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_324d5e3696d6ee1c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.1, 0.5, 0.35, 0.05, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: across all regions, under an active deadline. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_06df768e79b9d9a8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.82, 0.17, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: during the batch window, during peak load. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_af1e756533f5b96e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.32, 0.67, 0.01], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: over the last hour, mid-incident. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_abade13fa03ae66a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.77, 0.21, 0.01, 0.01], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: in production only, during the morning shift. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9ad9fee1a68a23cd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.19, 0.67, 0.12, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: in production only, at the end of the fiscal period. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6fd9db363f662240_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.21, 0.77, 0.02], "state": "The log shipper flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during an external partner integration. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_65356be287049889_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.98, 0.01, 0.0, 0.01], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: during the batch window, under an active deadline. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e8897e368b85ec9d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.7, 0.27, 0.02, 0.01], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: during the batch window, during the morning shift. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d2dd5a21e104d954_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, following a recent audit. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9ea9f6459fd775af_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "Service catalog-sync shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during a scheduled maintenance window. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1461b9acb39f212d_n", "kind": "noul", "options": ["false", "true"], "target": [0.7, 0.3], "state": "Node pgsql-14 flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: during the batch window, during the quarterly review. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a47ca30599e35210_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.58, 0.33, 0.05, 0.0], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the morning shift. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_47fc9d3c64c7766a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.08, 0.24, 0.66, 0.02, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: in production only, during a scheduled maintenance window. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9c57d1b9e77a1d06_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.66, 0.33, 0.0], "state": "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, under reduced staffing. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2277e31551ca9e53_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.03, 0.75, 0.22], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: across all regions, under an active deadline. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c1a96edb63a5a8de_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.14, 0.81, 0.05], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during the holiday freeze. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c825576abe7da2bf_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during the system migration. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d3680106218d9f24_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: during the batch window, under an active deadline. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ae7fc9aa95d5ab94_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.1, 0.45, 0.33, 0.12, 0.0, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, immediately after go-live. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b46a0ac38930c271_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.2, 0.77, 0.03], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: in production only, during the morning shift. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c1b1c811075a8f55_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.07, 0.01, 0.44, 0.48], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: during the batch window, at the end of the fiscal period. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e2b7a60a9f4f4bd5_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.75, 0.21, 0.03, 0.01], "state": "The log shipper reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, with staffing at reduced levels. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8caeff8b6b8dd133_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "The log shipper flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: across all regions, under an active deadline. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6e654852fa039ae2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.01, 0.03, 0.5, 0.43, 0.02], "state": "The log shipper correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: across all regions, during normal operations. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d4d0a1a65fd39dec_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.23, 0.51, 0.02, 0.24], "state": "The log shipper shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: over the last hour, following a recent audit. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e41ae89748af4833_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: across all regions, under reduced staffing. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_52e912d5342d4c2d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.03, 0.28, 0.18, 0.4, 0.1, 0.01], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: over the last hour, during a scheduled maintenance window. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ea344ff006c239a2_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: across all regions, shortly after a software update. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_808ee7ea36c93ce1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.25, 0.73, 0.02], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: across all regions, following a recent audit. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6121fed1bd4f7b28_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.0, 0.85, 0.15], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: over the last hour, during normal operations. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_15301f5d5b06612e_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: in production only, shortly after a software update. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8b67093c7f6d8e83_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.98, 0.0, 0.01, 0.01], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, following a recent audit. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ada90d9e2c31d601_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.06, 0.79, 0.03, 0.12], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, shortly after a software update. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e12e9da43ceff2f2_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.68, 0.26, 0.06, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: over the last hour, with a new vendor onboarded. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f1f8a47f530c9642_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.17, 0.79, 0.04], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: in production only, with staffing at reduced levels. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_de1b40b51882af99_n", "kind": "noul", "options": ["false", "true"], "target": [0.91, 0.09], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: over the last hour, shortly after a software update. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f25b1409884691c8_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "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.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b409eee2b9716b2d_n", "kind": "noul", "options": ["false", "true"], "target": [0.46, 0.54], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: in production only, following a recent audit. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_93fe43f78038bc22_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.45, 0.51, 0.01], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7d5ddbd44240fa6f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.04, 0.79, 0.17, 0.0], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5e946035baf33d20_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.04, 0.81, 0.15], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the holiday freeze. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b566758345efc9ff_n", "kind": "noul", "options": ["false", "true"], "target": [0.61, 0.39], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, with staffing at reduced levels. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3322e5a6225d0c29_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.41, 0.48, 0.08, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: across all regions, with staffing at reduced levels. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d50718657ecf48d7_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.19, 0.26, 0.53], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: across all regions, while on-call rotation changed. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f4894d5eda76e607_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: over the last hour, during the quarterly review. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f14800d0a9e642c0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.44, 0.56, 0.0], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: during the batch window, with a new vendor onboarded. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_76b761f30a9a7c18_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: over the last hour, under reduced staffing. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4bf12119a54b3ced_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.36, 0.52, 0.06, 0.0], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: in production only, during peak load. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cb6fd6bb89e5b8ca_n", "kind": "noul", "options": ["false", "true"], "target": [0.9, 0.1], "state": "The log shipper shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_160cdd3dd043a27d_n", "kind": "noul", "options": ["false", "true"], "target": [0.42, 0.58], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: over the last hour, during the system migration. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c296b1f8567ca3aa_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.5, 0.37, 0.12, 0.01], "state": "The log shipper shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during peak load. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cc6595839cc38d9d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.25, 0.38, 0.3, 0.04], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6dff0b779ba4a8cd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.09, 0.3, 0.59, 0.02, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: across all regions, under reduced staffing. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_95bd04038fdf849a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.16, 0.66, 0.17, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during peak load. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_91e8ebd752ab9302_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.01, 0.04, 0.95], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: in production only, following a recent audit. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c0e9313553ca6a7b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.98, 0.0, 0.0, 0.02], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: over the last hour, with staffing at reduced levels. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e08c6b84f129c0ef_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.71, 0.27, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: in production only, while legacy systems are still active. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c43a00a9b6e3d3c3_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.21, 0.58, 0.01, 0.2], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: in production only, at the end of the fiscal period. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7a4631603fa4a7d7_n", "kind": "noul", "options": ["false", "true"], "target": [0.67, 0.33], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: across all regions, under reduced staffing. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b3c0becc4341b614_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.35, 0.01, 0.29, 0.35], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: during the batch window, during peak load. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0efe7f9f73f1d744_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.21, 0.66, 0.12, 0.01, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: in production only, during the holiday freeze. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f38e1f0c0a985f55_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.55, 0.38, 0.04, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: over the last hour, at the end of the fiscal period. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5f9e0e10574a1cbb_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: in production only, following a recent audit. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_25000f5928f5bef2_n", "kind": "noul", "options": ["false", "true"], "target": [0.22, 0.78], "state": "The log shipper correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during the morning shift. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_52886e4edc0cb23d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.83, 0.15, 0.01, 0.01], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: across all regions, during normal operations. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cad6163bd0701d43_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.01, 0.02, 0.52, 0.43, 0.01], "state": "Service catalog-sync correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: in production only, as part of a compliance sweep. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a5a294bc959609ab_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.16, 0.76, 0.06, 0.02], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, at the end of the fiscal period. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_60bfb4d08b612946_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.36, 0.63, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: during the batch window, with staffing at reduced levels. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_589bd0bdedb33318_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.26, 0.66, 0.06, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: across all regions, under an active deadline. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_88c12e1079c6885d_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "Service catalog-sync shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: in production only, mid-incident. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_702d4cd147cc545d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.21, 0.58, 0.19, 0.01, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: in production only, as part of a compliance sweep. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_15cf87675cd63644_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.24, 0.17, 0.04, 0.55], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: across all regions, during the morning shift. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c264d463301bf161_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.57, 0.42, 0.0], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: during the batch window, while on-call rotation changed. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cd27e84a6dec0bde_n", "kind": "noul", "options": ["false", "true"], "target": [0.71, 0.29], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, following a recent audit. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_298edecf69f7d6c6_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.46, 0.47, 0.03, 0.04], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: across all regions, shortly after a software update. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9a70db0dd23672d5_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "The log shipper shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, shortly after a software update. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_21c9926a6455b119_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.08, 0.29, 0.62, 0.01, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: over the last hour, while on-call rotation changed. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_656bb57d498888ff_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.85, 0.14, 0.01, 0.0], "state": "The log shipper correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: in production only, while legacy systems are still active. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2aebe535c0d5bae6_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.37, 0.0, 0.59, 0.04], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: over the last hour, during peak load. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9b85b736d2fcdf20_n", "kind": "noul", "options": ["false", "true"], "target": [0.56, 0.44], "state": "Service catalog-sync lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: during the batch window, during the system migration. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3f90bca40ad12a23_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.57, 0.41, 0.02, 0.0], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: in production only, during an external partner integration. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9eeefcaf0aee41a9_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: over the last hour, shortly after a software update. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3b9731d64b5da5ff_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.35, 0.62, 0.02], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, shortly after a software update. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cc121195183773d4_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.0, 0.06, 0.89], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: in production only, under an active deadline. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5bebd3d7f2d6c668_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.06, 0.73, 0.2, 0.0], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a9ca016904e3c961_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.14, 0.77, 0.09, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: during the batch window, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_efa38ebe01de4c3e_n", "kind": "noul", "options": ["false", "true"], "target": [0.67, 0.33], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4db345bd6aa8e39b_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during the system migration. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_de3856d8a7d7af71_n", "kind": "noul", "options": ["false", "true"], "target": [0.22, 0.78], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: in production only, under reduced staffing. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ab02b7345f8a9345_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.22, 0.76, 0.02], "state": "The log shipper shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: during the batch window, under an active deadline. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_33beea01e265dd74_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.31, 0.38, 0.29, 0.01], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: over the last hour, immediately after go-live. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7ea28937e847a888_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.03, 0.5, 0.45, 0.01], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: across all regions, during the quarterly review. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e7fea2df5f46fe96_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "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, during the quarterly review. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_beaf10adbf84782a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.58, 0.38, 0.01], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: across all regions, during the morning shift. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_56f6fe7f6e74332a_n", "kind": "noul", "options": ["false", "true"], "target": [0.37, 0.63], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: in production only, during the quarterly review. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f97695a081cbca73_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.36, 0.63, 0.01], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during normal operations. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_db17b3504e14379a_n", "kind": "noul", "options": ["false", "true"], "target": [0.58, 0.42], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: during the batch window, following a recent audit. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7c430d6eb255ba1d_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: in production only, at the end of the fiscal period. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aec08ef1761f1453_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: in production only, under reduced staffing. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b676f78d523d53d7_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.05, 0.54, 0.39, 0.02], "state": "The log shipper matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: during the batch window, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1bb2241d0d53075a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.01, 0.33, 0.66], "state": "The log shipper correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, following a recent audit. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ce09c5375d1e59f8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.56, 0.4, 0.02, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: over the last hour, during the morning shift. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6995010547d0c99f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.09, 0.56, 0.35, 0.0, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: over the last hour, shortly after a software update. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3481db3cdf7f5b86_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.79, 0.19, 0.01, 0.01], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: over the last hour, shortly after a software update. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7116a9645b1a1ab7_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: across all regions, immediately after go-live. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_adfc05087ba60020_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: across all regions, as part of a compliance sweep. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fd73641703dddfa2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.29, 0.02, 0.27, 0.42], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: in production only, during the holiday freeze. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_036e389c7e256b6b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.23, 0.74, 0.02, 0.01], "state": "The log shipper matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: during the batch window, as part of a compliance sweep. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_badd27f64c12a035_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.51, 0.48, 0.0], "state": "The log shipper correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: over the last hour, under reduced staffing. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9f700a50fbba0486_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.05, 0.65, 0.27, 0.03], "state": "The log shipper matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: during the batch window, as part of a compliance sweep. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e7a139f815283fb8_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.0, 0.13, 0.83, 0.04], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, immediately after go-live. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6c973df422aec2b4_n", "kind": "noul", "options": ["false", "true"], "target": [0.57, 0.43], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: across all regions, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_03eb9e078a1f10e1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.59, 0.4, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during an external partner integration. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e6acfb6b116f5df8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.25, 0.74, 0.01], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: over the last hour, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a3c2c989350e98be_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.12, 0.84, 0.04], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, under reduced staffing. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_adfc05087ba60020_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.37, 0.56, 0.02], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: across all regions, as part of a compliance sweep. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cf725733135cc99a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.07, 0.81, 0.1, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during the holiday freeze. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7bec2da789ef6e87_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.4, 0.58, 0.01], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: over the last hour, during the holiday freeze. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5bb92bd1f8c51b1b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.49, 0.04, 0.01, 0.46], "state": "The log shipper lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: across all regions, at the end of the fiscal period. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d7934a98d9cdd6e0_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, under reduced staffing. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_10503ecb519f6583_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.04, 0.85, 0.11], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during peak load. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_44e2ae38c60736df_n", "kind": "noul", "options": ["false", "true"], "target": [0.68, 0.32], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: in production only, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9eb11a6f64f524af_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.6, 0.38, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: in production only, under reduced staffing. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_daa4d26635198b5e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.24, 0.74, 0.02], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during the quarterly review. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_af70750de597baa3_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.29, 0.65, 0.06, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: during the batch window, while on-call rotation changed. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2a63604f303b271f_n", "kind": "noul", "options": ["false", "true"], "target": [0.39, 0.61], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: in production only, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_35bba68ddcf9bf15_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_34bbcf72cba26e7f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.18, 0.75, 0.04, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, with a new vendor onboarded. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_992c93647f6ea09c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.16, 0.67, 0.08, 0.09], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: over the last hour, while legacy systems are still active. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_030d1106cefce8c0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.55, 0.44, 0.0], "state": "The log shipper flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: in production only, following a recent audit. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3b76ef23efbfb7e8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.12, 0.85, 0.03], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: across all regions, under reduced staffing. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d50718657ecf48d7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.53, 0.46, 0.0], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: across all regions, while on-call rotation changed. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fe64019b62b8a2bb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.04, 0.74, 0.22, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during the system migration. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a92c71772c3e6fd8_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.13, 0.68, 0.19, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: in production only, while on-call rotation changed. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_52479c30f023af04_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.51, 0.31, 0.14, 0.04], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: over the last hour, at the end of the fiscal period. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ad5a7826a9ad5645_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.38, 0.6, 0.01], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: over the last hour, with staffing at reduced levels. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5cf8f96dcbc30307_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.44, 0.52, 0.01], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: in production only, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1e4150f7cac3fb69_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, under an active deadline. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_13dbbf2debd8831d_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: during the batch window, while legacy systems are still active. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aa368f98bb0e3dd7_n", "kind": "noul", "options": ["false", "true"], "target": [0.38, 0.62], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: over the last hour, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_04e2d4344a078530_n", "kind": "noul", "options": ["false", "true"], "target": [0.42, 0.58], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during the morning shift. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_82885b53cb60c002_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.57, 0.38, 0.04, 0.01], "state": "The log shipper shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, while legacy systems are still active. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f3ccfadce8fe470a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.53, 0.46, 0.01, 0.0], "state": "The log shipper flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: in production only, as part of a compliance sweep. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8483dec0a643d044_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: over the last hour, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_840b04b0ffcb1a93_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.3, 0.53, 0.16, 0.01], "state": "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, following a recent audit. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d3a2eb231bb2c4b5_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.08, 0.02, 0.02, 0.88], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: across all regions, at the end of the fiscal period. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8803044750369cbb_n", "kind": "noul", "options": ["false", "true"], "target": [0.5, 0.5], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: in production only, as part of a compliance sweep. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5df18bda476b8971_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.06, 0.25, 0.67, 0.02], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: across all regions, during an external partner integration. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_020d5bb9d171472c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.68, 0.28, 0.03, 0.01], "state": "The log shipper shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: during the batch window, during the system migration. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f7e7855fd93498dc_n", "kind": "noul", "options": ["false", "true"], "target": [0.51, 0.49], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: across all regions, while legacy systems are still active. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dd22ad86eccd76de_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: across all regions, under reduced staffing. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_06c2c055397aa08e_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The log shipper lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during the holiday freeze. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fce3179791601617_n", "kind": "noul", "options": ["false", "true"], "target": [0.48, 0.52], "state": "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.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d7124e66f116bcfa_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.2, 0.78, 0.02], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during an external partner integration. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8a1c7d06e85bf1fb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.47, 0.52, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: in production only, during the holiday freeze. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_23aaf4cf1d709fe9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.39, 0.59, 0.01], "state": "Service catalog-sync shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: over the last hour, under an active deadline. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a051f3dbede6022f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.0, 0.73, 0.27], "state": "The log shipper correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: across all regions, during an external partner integration. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d426d5cd2cbd06e9_n", "kind": "noul", "options": ["false", "true"], "target": [0.7, 0.3], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the quarterly review. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5de69367a0e305c1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.51, 0.47, 0.01], "state": "The log shipper shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during a scheduled maintenance window. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5a57bc5668966986_n", "kind": "noul", "options": ["false", "true"], "target": [0.45, 0.55], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: in production only, mid-incident. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f37927b79739b925_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: during the batch window, with staffing at reduced levels. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f1d6a67f50c86bea_n", "kind": "noul", "options": ["false", "true"], "target": [0.18, 0.82], "state": "The metrics pipeline flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: over the last hour, shortly after a software update. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3afd33334f10c617_n", "kind": "noul", "options": ["false", "true"], "target": [0.6, 0.4], "state": "The log shipper shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: over the last hour, mid-incident. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1e632400d4131ecf_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.28, 0.69, 0.01, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: over the last hour, during the system migration. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0d997d51fdd8923d_n", "kind": "noul", "options": ["false", "true"], "target": [0.38, 0.62], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: in production only, with a new vendor onboarded. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d0e948c4d7c2d973_n", "kind": "noul", "options": ["false", "true"], "target": [0.66, 0.34], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the system migration. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fdb9fd30eee93272_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.2, 0.51, 0.27, 0.01], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, immediately after go-live. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d3a2eb231bb2c4b5_n", "kind": "noul", "options": ["false", "true"], "target": [0.91, 0.09], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: across all regions, at the end of the fiscal period. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_072f8c770e3b902e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.2, 0.19, 0.58, 0.03], "state": "Service catalog-sync flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: in production only, mid-incident. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f8bc5094e2ec4b92_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.09, 0.01, 0.41, 0.49], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: during the batch window, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d547e7bf600bc73e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.2, 0.6, 0.2, 0.0, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: in production only, with staffing at reduced levels. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ab9782399cec05f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.06, 0.42, 0.46, 0.05, 0.0], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: during the batch window, during peak load. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d24d4c971fe6f247_n", "kind": "noul", "options": ["false", "true"], "target": [0.4, 0.6], "state": "Node pgsql-14 flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: during the batch window, mid-incident. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ee6e702f9629d850_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.05, 0.54, 0.41, 0.0], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: in production only, during the system migration. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_83527f519ef88177_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.21, 0.55, 0.22, 0.01, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: during the batch window, as part of a compliance sweep. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0df54c65d26d8aad_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "The log shipper reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: over the last hour, under an active deadline. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ed03e282e3184b68_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, under reduced staffing. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8ed9de562d3a6bbc_n", "kind": "noul", "options": ["false", "true"], "target": [0.6, 0.4], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the quarterly review. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ffd85985fcba6aaa_n", "kind": "noul", "options": ["false", "true"], "target": [0.6, 0.4], "state": "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 automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0987f0ea596d295c_n", "kind": "noul", "options": ["false", "true"], "target": [0.55, 0.45], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: across all regions, at the end of the fiscal period. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_79230360afe6ef9f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.88, 0.1, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: across all regions, while on-call rotation changed. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4a2eed05ea3d2edb_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.58, 0.31, 0.11, 0.0], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: in production only, during the holiday freeze. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4b0224ab8d74df3b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.4, 0.58, 0.01], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: across all regions, at the end of the fiscal period. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9abb9af0195b8608_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.23, 0.74, 0.03], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during the quarterly review. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9bef5867ff72ba56_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.5, 0.49, 0.0], "state": "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, during the quarterly review. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c64436abad062a67_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.46, 0.51, 0.03, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: across all regions, during an external partner integration. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eb150f1628564ea9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.03, 0.39, 0.57], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: across all regions, while on-call rotation changed. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aab0393fe585104a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.89, 0.1, 0.01, 0.0], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, under reduced staffing. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3327d1c6941d2af5_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.0, 0.06, 0.94], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: across all regions, at the end of the fiscal period. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_95f1be7d1178bb9a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.56, 0.43, 0.0], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: over the last hour, during an external partner integration. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ac269a201ad11ebb_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: during the batch window, mid-incident. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5f18df083fac50c9_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "Service catalog-sync flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: in production only, during an external partner integration. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4a63846f26f48b2f_n", "kind": "noul", "options": ["false", "true"], "target": [0.44, 0.56], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: during the batch window, following a recent audit. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_628da98585f96231_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: in production only, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b343641b0be50a3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.37, 0.62, 0.01], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: across all regions, during an external partner integration. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7c99bd388bed486b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.03, 0.82, 0.15], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, under reduced staffing. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6e842d6be5fa07d2_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: over the last hour, with a new vendor onboarded. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c296b1f8567ca3aa_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.81, 0.18, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during peak load. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ba3abcf5132b506_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.31, 0.26, 0.03, 0.4], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: over the last hour, as part of a compliance sweep. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e3e7347614a55680_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.09, 0.53, 0.35, 0.03, 0.0], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: in production only, mid-incident. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8bdfeca16a246683_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.6768, 0.2727, 0.0505, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: over the last hour, during the morning shift. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8b9ef5e3c46df5aa_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.38, 0.3, 0.3, 0.02], "state": "The metrics pipeline flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: in production only, under an active deadline. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_29ee6e62a09b9992_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during an external partner integration. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c13fe4bb72684187_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: over the last hour, while legacy systems are still active. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6ebf8468cfa344aa_n", "kind": "noul", "options": ["false", "true"], "target": [0.54, 0.46], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: in production only, during peak load. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ffd85985fcba6aaa_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.04, 0.66, 0.3, 0.0], "state": "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 automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c4c4ae6fff85a41c_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during the quarterly review. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9597cca3e1904f43_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.4, 0.54, 0.05, 0.01], "state": "The log shipper correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: in production only, during peak load. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_489da28cd4632431_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "The metrics pipeline lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: across all regions, immediately after go-live. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e23afe5fa28a8ed8_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: over the last hour, during the quarterly review. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_93c8c870372efff4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.29, 0.58, 0.1, 0.0], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: across all regions, at the end of the fiscal period. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e7cfb2b39213a511_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.1, 0.79, 0.0, 0.11], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: across all regions, following a recent audit. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8e09fff3bee7c0d0_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.59, 0.0, 0.33, 0.08], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: in production only, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d130979aee19c171_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.53, 0.16, 0.02, 0.29], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: over the last hour, with staffing at reduced levels. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_de3f278596b1d4cd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.25, 0.59, 0.15, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: across all regions, under reduced staffing. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_71f5c4b8f6778c01_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during the holiday freeze. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_81db8384c36f4643_n", "kind": "noul", "options": ["false", "true"], "target": [0.41, 0.59], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: across all regions, during the morning shift. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fb04c10f03d2a9e2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.4, 0.0, 0.26, 0.34], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, while legacy systems are still active. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aac75f4672829e71_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.26, 0.35, 0.36, 0.02, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally matches last Tuesday's incident signature. Context: across all regions, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4510d41fe66c2650_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.99, 0.0, 0.0, 0.01], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during the morning shift. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e88d3046f8791d91_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.64, 0.35, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: over the last hour, under reduced staffing. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fbf1d14b9ba40690_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.47, 0.52, 0.0], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: over the last hour, shortly after a software update. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b421741fab40cad5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.68, 0.31, 0.0], "state": "The log shipper correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: over the last hour, during an external partner integration. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2014496a9dce3ec4_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.97, 0.02, 0.01], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: across all regions, shortly after a software update. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca1958eaf1b75b2c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.5556, 0.3939, 0.0505, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the morning shift. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_04c53e20dffe85ee_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.45, 0.49, 0.01], "state": "The metrics pipeline lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: across all regions, as part of a compliance sweep. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_520da00a44ac5fe6_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: across all regions, with a new vendor onboarded. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fe965ce8a13930fe_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.13, 0.35, 0.5, 0.02], "state": "Service catalog-sync flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: in production only, while legacy systems are still active. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fbcfead5e40434d4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.22, 0.7, 0.03, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: in production only, with a new vendor onboarded. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f52cf80f03b2f473_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: over the last hour, while on-call rotation changed. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_868bc1367e40c7b1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.32, 0.5, 0.1, 0.08], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: in production only, while legacy systems are still active. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0e7dcc3a4ef51be4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.71, 0.28, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: in production only, under an active deadline. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d42d19389b606fc1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.2, 0.33, 0.03, 0.44], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: in production only, while on-call rotation changed. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b920d987cb55e4c3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.78, 0.2, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: during the batch window, while legacy systems are still active. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_708e7182c7027705_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: during the batch window, mid-incident. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b4d779a1c56ae22c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.18, 0.8, 0.01], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during a scheduled maintenance window. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_42f0c521fe1af430_n", "kind": "noul", "options": ["false", "true"], "target": [0.42, 0.58], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: over the last hour, during the holiday freeze. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bf64382602706fab_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.12, 0.03, 0.5, 0.35], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during an external partner integration. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3abcf796d0ebfba8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.58, 0.41, 0.0], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: over the last hour, during an external partner integration. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5aa873a353ec7ebd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.41, 0.56, 0.01], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: in production only, with staffing at reduced levels. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3f2a5c0bdb9bd726_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.24, 0.69, 0.06], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during a scheduled maintenance window. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ccb06f9acae4aa61_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.98, 0.0, 0.0, 0.02], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: across all regions, during the system migration. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_967b0b75cee0e199_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.25, 0.71, 0.03], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: over the last hour, during the holiday freeze. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cf671050542e265a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.14, 0.01, 0.35, 0.5], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during the system migration. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7cbf78f145eb9479_n", "kind": "noul", "options": ["false", "true"], "target": [0.68, 0.32], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: in production only, while on-call rotation changed. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f99f5730e059bc97_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "Service catalog-sync flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: across all regions, during the system migration. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_85b4a7de55c6bae8_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.23, 0.0, 0.6, 0.17], "state": "Service catalog-sync correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: over the last hour, under reduced staffing. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5b4ce7af387d2730_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.36, 0.62, 0.01], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the system migration. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_08bcbe44d03d599e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.22, 0.77, 0.01], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: across all regions, under reduced staffing. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_98763e2d62de8ffb_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: over the last hour, under reduced staffing. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_99ef288c2e93ce38_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "The log shipper returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: in production only, during the holiday freeze. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fe3b1f7d55694093_n", "kind": "noul", "options": ["false", "true"], "target": [0.63, 0.37], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: over the last hour, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_476ae933bbb6825b_n", "kind": "noul", "options": ["false", "true"], "target": [0.42, 0.58], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: across all regions, during normal operations. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_914bf5b99076b96c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.01, 0.53, 0.43], "state": "The log shipper reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: across all regions, during the morning shift. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7e592ecde7250f28_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.41, 0.01, 0.32, 0.26], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, mid-incident. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2f019079094a0bc1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.3, 0.69, 0.01], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during the system migration. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f92522f6fe598b8e_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: over the last hour, as part of a compliance sweep. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0d781a6e2622fdfa_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.92, 0.0, 0.05, 0.03], "state": "The log shipper correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during the system migration. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_31f8ce2e3f35e2b2_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: across all regions, under an active deadline. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_094b5bacc52a549b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.37, 0.61], "state": "The log shipper lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: in production only, with a new vendor onboarded. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_35dc5d4135893953_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.2, 0.78, 0.02], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: in production only, while legacy systems are still active. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5b6a6ac106590da5_n", "kind": "noul", "options": ["false", "true"], "target": [0.58, 0.42], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: across all regions, following a recent audit. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_76a1bf515f99e04b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.03, 0.58, 0.36, 0.03], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: during the batch window, at the end of the fiscal period. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9e64bb0a32adacab_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.11, 0.78, 0.11, 0.0, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: across all regions, at the end of the fiscal period. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_497e2a8e51291455_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.34, 0.35, 0.01, 0.3], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: in production only, during peak load. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7663c6bf41f0d559_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: during the batch window, during the system migration. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3273873af4e5532e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.71, 0.26, 0.02, 0.01], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: in production only, while on-call rotation changed. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_92abc61435214c2d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.51, 0.45, 0.01], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: in production only, following a recent audit. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b0ee988fdcd0dd9e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.05, 0.83, 0.12], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, mid-incident. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_28d34e4dc902e383_n", "kind": "noul", "options": ["false", "true"], "target": [0.39, 0.61], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: across all regions, following a recent audit. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0c33d13b463a7892_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.62, 0.29, 0.07, 0.02], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: over the last hour, as part of a compliance sweep. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_db711bf7b1a5387d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.08, 0.0, 0.88, 0.04], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, while legacy systems are still active. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ea95c5e5f83eb24c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.07, 0.87, 0.06], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, while on-call rotation changed. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9ca3bf859c7c0827_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.11, 0.84, 0.05], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: during the batch window, at the end of the fiscal period. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca195f786ef7e800_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.66, 0.33, 0.0], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: during the batch window, while legacy systems are still active. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e2ebd70cdc50776f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.37, 0.41, 0.04, 0.18], "state": "Service catalog-sync shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: during the batch window, during the quarterly review. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_03f55cf13100fdd0_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.69, 0.3, 0.01, 0.0], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: in production only, following a recent audit. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_54f722affb882e3b_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, at the end of the fiscal period. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_12b0430d73fc4b7e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.91, 0.0, 0.0, 0.09], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during peak load. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fce3179791601617_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.36, 0.54, 0.04, 0.0], "state": "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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d0fe9e5e8c6fd465_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.73, 0.24, 0.03, 0.0], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: during the batch window, while on-call rotation changed. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9233c1d4d2cbb9c9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.41, 0.59, 0.0], "state": "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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e5e471ada76e6ef2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.84, 0.05, 0.0, 0.11], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: in production only, with staffing at reduced levels. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bc68020d58b91c74_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The log shipper shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during the holiday freeze. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3383044f30987e33_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.98, 0.02, 0.0, 0.0], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during a scheduled maintenance window. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_22953d990ae9932a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.98, 0.0, 0.0, 0.02], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: in production only, following a recent audit. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e94ddde0794017bf_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.98, 0.01, 0.0, 0.01], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, immediately after go-live. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b2434e9ed31854d1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.34, 0.0, 0.26, 0.4], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: in production only, during peak load. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_978848ce615c3bac_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.81, 0.17, 0.02, 0.0], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: in production only, shortly after a software update. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8254f30160749ee9_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.0101, 0.2727, 0.6869, 0.0303], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: during the batch window, with a new vendor onboarded. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8905bf85cd6dfd0a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.07, 0.29, 0.63, 0.01], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: in production only, with staffing at reduced levels. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9bf047c720af6fa7_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "The log shipper flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, mid-incident. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_39855681ce11bfcc_n", "kind": "noul", "options": ["false", "true"], "target": [0.61, 0.39], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: over the last hour, mid-incident. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_61b08f43844e7291_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "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.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8c2981c3aeff9011_n", "kind": "noul", "options": ["false", "true"], "target": [0.19, 0.81], "state": "The metrics pipeline 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 supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_94bc196e655a8a64_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.14, 0.39, 0.45, 0.02, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during normal operations. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c8203d3a2fe8d894_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "The log shipper returned to baseline after 11 minutes; additionally matches last Tuesday's incident signature. Context: across all regions, while on-call rotation changed. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1f63d2502608b95b_n", "kind": "noul", "options": ["false", "true"], "target": [0.39, 0.61], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: across all regions, following a recent audit. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d2b3ff16e194be62_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.92, 0.06, 0.02, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: in production only, mid-incident. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3a5e19408b2892dd_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: in production only, during the holiday freeze. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cf6e6eb7aa805c62_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.51, 0.45, 0.03, 0.01], "state": "The log shipper shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: across all regions, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6791f4264ae7a939_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.06, 0.01, 0.62, 0.31], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: across all regions, during the morning shift. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b0f8c6e1133385a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.04, 0.45, 0.47], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: during the batch window, at the end of the fiscal period. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1ce4fbb648628d94_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: in production only, with staffing at reduced levels. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b7f13b46141fe527_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.02, 0.2, 0.38, 0.38, 0.02, 0.0], "state": "The log shipper correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, as part of a compliance sweep. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_25e9aa649a52bac8_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "The log shipper correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: across all regions, during the morning shift. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_121e836575d8c3d4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.03, 0.14, 0.54, 0.27, 0.02, 0.0], "state": "The log shipper correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: across all regions, at the end of the fiscal period. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f1313939091f7e4c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.08, 0.21, 0.61, 0.1, 0.0], "state": "Service catalog-sync correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: in production only, during the holiday freeze. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_30ccf5005028298a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.09, 0.6, 0.29, 0.02], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: across all regions, during a scheduled maintenance window. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9f41cd9ffb0db4b3_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.82, 0.0, 0.12, 0.06], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: in production only, as part of a compliance sweep. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6d72a21966b68a17_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.73, 0.24, 0.03, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: in production only, under reduced staffing. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_76a8b4df68809f82_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.29, 0.59, 0.12, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: in production only, while legacy systems are still active. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_38ed57fe11ba1918_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.23, 0.37, 0.37, 0.03], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, mid-incident. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_841c3cd4ebb9bdc0_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: over the last hour, during the morning shift. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_639dbaf110d21248_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.36, 0.62, 0.01], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: during the batch window, following a recent audit. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6c6ec1dac82fd662_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.08, 0.81, 0.11], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during the holiday freeze. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_79522b9794cc46fa_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: during the batch window, while on-call rotation changed. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0d781a6e2622fdfa_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.12, 0.84, 0.04], "state": "The log shipper correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during the system migration. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_042137350dc3700f_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: in production only, while legacy systems are still active. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5611ccd8488a35e0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.74, 0.23, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: in production only, while on-call rotation changed. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c380b0d2befb5070_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.35, 0.65, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: across all regions, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7ec32feaa2ad91d2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.34, 0.65, 0.01], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: across all regions, with a new vendor onboarded. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fe9df27e1c7fd446_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.4, 0.46, 0.11, 0.0], "state": "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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7445d6c551f5ebd5_n", "kind": "noul", "options": ["false", "true"], "target": [0.38, 0.62], "state": "The log shipper shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: during the batch window, during peak load. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_328d8f56b5d3d0ad_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The log shipper reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: across all regions, mid-incident. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_58dadfd5861b2f57_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.19, 0.0, 0.24, 0.57], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_74db072d9fbe9f88_n", "kind": "noul", "options": ["false", "true"], "target": [0.7, 0.3], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: in production only, at the end of the fiscal period. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6b7688f70b233edf_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "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.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_abca85c65c147907_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.14, 0.8, 0.06], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: over the last hour, at the end of the fiscal period. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2936ceb17d733c3c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.37, 0.61, 0.01], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: in production only, with staffing at reduced levels. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0efe7f9f73f1d744_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.08, 0.03, 0.14, 0.75], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: in production only, during the holiday freeze. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7878bc37e1faf47f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.79, 0.19, 0.01, 0.01], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally flags a step-function change in error slope. Context: across all regions, during the morning shift. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0895d7417727ba40_n", "kind": "noul", "options": ["false", "true"], "target": [0.71, 0.29], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: during the batch window, as part of a compliance sweep. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5546744a16703882_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.17, 0.79, 0.04], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: in production only, with a new vendor onboarded. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a42ae064a33d5d0e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.45, 0.55, 0.0], "state": "The metrics pipeline flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: in production only, shortly after a software update. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_21e7ba63ecda4e23_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during a scheduled maintenance window. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cc47c4e7cecf99a8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.2, 0.78, 0.02], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: in production only, with staffing at reduced levels. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0a1d17d256c6fd47_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during a scheduled maintenance window. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca8dba4dcd1ba083_n", "kind": "noul", "options": ["false", "true"], "target": [0.4, 0.6], "state": "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.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bff5b66b8f8b665b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.4, 0.58, 0.02, 0.0], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: over the last hour, following a recent audit. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b811c3508c7b6a71_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: across all regions, during the holiday freeze. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8efea7cd78da752b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.56, 0.37, 0.03, 0.04], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the morning shift. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4e1a247e52a78373_n", "kind": "noul", "options": ["false", "true"], "target": [0.6, 0.4], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, under reduced staffing. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b705d568cb7c4052_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: during the batch window, during peak load. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_059431d566345957_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.0, 0.83, 0.16], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_62ca2397d7ea004a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.52, 0.37, 0.11, 0.0], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, while legacy systems are still active. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fbd200a761682e17_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.04, 0.79, 0.17, 0.0], "state": "The log shipper reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: during the batch window, during normal operations. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e5eaa499f3edc6be_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.04, 0.7, 0.25, 0.01], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during normal operations. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_495764ea71f54e80_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.93, 0.04, 0.02, 0.01], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: over the last hour, immediately after go-live. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6b5407b8a233c55b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.69, 0.29, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally matches last Tuesday's incident signature. Context: over the last hour, with a new vendor onboarded. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b24f3846df5d5918_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "The log shipper reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: over the last hour, during the system migration. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_250d831c47edb2ac_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.58, 0.4], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: during the batch window, with a new vendor onboarded. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d7616fff436ca2fb_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.46, 0.02, 0.01, 0.51], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during the quarterly review. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_61e5f4fbc82a7f1f_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: over the last hour, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c91c50225ad9611d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.62, 0.37, 0.01, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: in production only, shortly after a software update. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0da7a7904cda1e12_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.12, 0.64, 0.21, 0.03, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, mid-incident. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1aebe92b3bf1cbda_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.05, 0.8, 0.14, 0.0], "state": "The metrics pipeline shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: in production only, during a scheduled maintenance window. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b2b0622bcfd9b6db_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.2, 0.74, 0.04, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: in production only, while legacy systems are still active. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aefdb47bbdf8fa78_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.2, 0.52, 0.27, 0.0, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: during the batch window, with staffing at reduced levels. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_01a35b27674392a1_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, with a new vendor onboarded. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0f6b7cca0e439c2c_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: across all regions, during the quarterly review. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0c978cd45b6cb01e_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: during the batch window, shortly after a software update. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_812c5d6a46b04e31_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: during the batch window, under an active deadline. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c8c4fc083424ebda_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.3, 0.57, 0.11, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: in production only, shortly after a software update. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2e57b06362c34ff0_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.16, 0.05, 0.61, 0.18], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: over the last hour, with staffing at reduced levels. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ac87df9fb6324d6d_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, while legacy systems are still active. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8caeff8b6b8dd133_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.18, 0.79, 0.03], "state": "The log shipper flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: across all regions, under an active deadline. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7f5b673918fe9809_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.97, 0.0, 0.02, 0.01], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during the system migration. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0c036f2017501725_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.04, 0.76, 0.2, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: in production only, during normal operations. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca158537feeb0a85_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.5556, 0.1717, 0.2727], "state": "The log shipper shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: in production only, shortly after a software update. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f2d8ef78e21ccef8_n", "kind": "noul", "options": ["false", "true"], "target": [0.22, 0.78], "state": "The metrics pipeline shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: across all regions, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_513e29d2a5d94b3a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.2, 0.57, 0.23, 0.0, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: in production only, while legacy systems are still active. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_53c4e587a82efb74_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The log shipper reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: in production only, during peak load. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b0ae4d79a7556ce6_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.04, 0.76, 0.2, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: in production only, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7be8826494ddc38d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.34, 0.65, 0.01], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d57446422899d7d8_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.14, 0.79, 0.06, 0.01], "state": "The log shipper correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: across all regions, during the holiday freeze. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_275a17c984928081_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: during the batch window, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_57a6ffa2fa805af4_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: over the last hour, during peak load. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_781e354bbbdaa175_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: over the last hour, while legacy systems are still active. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c78f7fa6311228bb_n", "kind": "noul", "options": ["false", "true"], "target": [0.22, 0.78], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: in production only, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e06a3ff86270f6af_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.1111, 0.3232, 0.5556, 0.0101, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: over the last hour, with a new vendor onboarded. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_064917e5efe65c5c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.62, 0.32, 0.01], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: across all regions, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f38e1f0c0a985f55_n", "kind": "noul", "options": ["false", "true"], "target": [0.53, 0.47], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: over the last hour, at the end of the fiscal period. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_16f85bbb1ed4aa3b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.36, 0.64, 0.0], "state": "The log shipper flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: over the last hour, during an external partner integration. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4f17ce2244fabb97_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: over the last hour, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4a47156b24bdf414_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.07, 0.65, 0.19, 0.08, 0.01, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: in production only, under an active deadline. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a58cd5c438d924c0_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the morning shift. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_56528b34b1cf8ef8_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.53, 0.4, 0.05, 0.02], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: during the batch window, during normal operations. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_010714ba5c9c9b84_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.28, 0.64, 0.07, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: across all regions, shortly after a software update. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ad728eb195d5ba7d_n", "kind": "noul", "options": ["false", "true"], "target": [0.64, 0.36], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: in production only, with a new vendor onboarded. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1b032c047138273a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.14, 0.14, 0.06, 0.66], "state": "Service catalog-sync flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: across all regions, during the system migration. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_79c85077e9a3722a_n", "kind": "noul", "options": ["false", "true"], "target": [0.41, 0.59], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during peak load. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d2d3cb4e87f9d420_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.43, 0.55, 0.01], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: over the last hour, while legacy systems are still active. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6d32e300bdb5723f_n", "kind": "noul", "options": ["false", "true"], "target": [0.91, 0.09], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: during the batch window, during the morning shift. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_add6b868ab30f64a_n", "kind": "noul", "options": ["false", "true"], "target": [0.39, 0.61], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during the quarterly review. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e63f88af1fa1404f_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: across all regions, following a recent audit. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aa368f98bb0e3dd7_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.37, 0.01, 0.55, 0.07], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: over the last hour, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f907d8363d30bfd7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.09, 0.88, 0.03], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: during the batch window, while on-call rotation changed. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b9d6206ffd8e306f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.8, 0.18, 0.01, 0.01], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: during the batch window, during peak load. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_db34284446ab4d26_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during an external partner integration. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d0e948c4d7c2d973_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.59, 0.32, 0.07, 0.02], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the system migration. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aa79111fde28ddfd_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.87, 0.12, 0.01, 0.0], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: in production only, during the system migration. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1b251321bbaa4228_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during the morning shift. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b8cf061fdcdcaecc_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.15, 0.42, 0.43, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: over the last hour, at the end of the fiscal period. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_28ce5a168d2948c9_n", "kind": "noul", "options": ["false", "true"], "target": [0.53, 0.47], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the holiday freeze. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a4bf61beafe39a67_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.27, 0.71, 0.02], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during peak load. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_88e99b3c5fa28cb6_n", "kind": "noul", "options": ["false", "true"], "target": [0.45, 0.55], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: over the last hour, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dcfa721e339ad37e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.1, 0.84, 0.06], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: during the batch window, during the quarterly review. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_609dc6d4704804d2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.38, 0.6, 0.01], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9d40d10f61934fd6_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.0, 0.17, 0.83], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: over the last hour, with a new vendor onboarded. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e04fdb4044a6fd94_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5fce97ef2be15620_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.87, 0.13, 0.0, 0.0], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: in production only, while legacy systems are still active. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fe77291f9843805a_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during an external partner integration. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_67b9298660fe6f7b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.8, 0.19, 0.01, 0.0], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: over the last hour, following a recent audit. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8d9e6df9300bb760_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.91, 0.06, 0.01, 0.02], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: during the batch window, mid-incident. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_67a3ef9b5c3333f2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.53, 0.46, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during the quarterly review. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca1958eaf1b75b2c_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the morning shift. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_01cc837a77c9a5e4_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: during the batch window, as part of a compliance sweep. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a77790d1ab9b167d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.08, 0.25, 0.64, 0.03, 0.0], "state": "Service catalog-sync correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: over the last hour, with a new vendor onboarded. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_60503f528a15925f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.12, 0.25, 0.05, 0.58], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: during the batch window, following a recent audit. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_70af6976a8fff361_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.14, 0.59, 0.21, 0.06], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: over the last hour, while legacy systems are still active. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_21a91fd7feb502ee_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.73, 0.26, 0.0], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: during the batch window, during the morning shift. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9ca3bf859c7c0827_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.76, 0.04, 0.13, 0.07], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: during the batch window, at the end of the fiscal period. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8bbcafc2d335d18c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.55, 0.45, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: over the last hour, during peak load. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1f75f3df91776261_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.39, 0.55, 0.06, 0.0], "state": "The log shipper flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: across all regions, during the quarterly review. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7aff109a3e8c36e2_n", "kind": "noul", "options": ["false", "true"], "target": [0.21, 0.79], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: over the last hour, immediately after go-live. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d91b841ae912b902_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.44, 0.49, 0.06, 0.01], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: in production only, as part of a compliance sweep. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9eb11a6f64f524af_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.73, 0.21, 0.04, 0.02], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: in production only, under reduced staffing. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_073b90b4c85288ae_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.13, 0.83, 0.04], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during an external partner integration. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bd53fda28e41ed01_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.36, 0.46, 0.17, 0.0], "state": "The log shipper flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, under an active deadline. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_89673f54ca543ba6_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.75, 0.23, 0.01, 0.01], "state": "Service catalog-sync lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: across all regions, during peak load. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_635abbcdf94d8d19_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.37, 0.61, 0.01], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: across all regions, during the system migration. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_15638b9b736bde40_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: in production only, with a new vendor onboarded. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a4956eee38c9eae1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.06, 0.87, 0.07], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: in production only, during the system migration. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3be979b46f40c800_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.0, 0.65, 0.34], "state": "The log shipper reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: over the last hour, with staffing at reduced levels. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bb469e4d9692e553_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: during the batch window, during the holiday freeze. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d545ca61dd544ece_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.13, 0.81, 0.06], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, shortly after a software update. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7d2ae47cf67ccc60_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.15, 0.54, 0.28, 0.01], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: in production only, mid-incident. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e010bce7a3a7b68a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.17, 0.53, 0.22, 0.08, 0.0, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the holiday freeze. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2c91e806795c3fd8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.6, 0.34, 0.01], "state": "The metrics pipeline flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: across all regions, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4209233e4843f18f_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during normal operations. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bb268e16aa8345f6_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: across all regions, as part of a compliance sweep. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5b5f7f02e116823c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.1, 0.04, 0.62, 0.24], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: across all regions, following a recent audit. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ceda2a9239c50953_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "The log shipper correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: in production only, during an external partner integration. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3dbcbe75b3cbf9dc_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: over the last hour, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4228aaa2e56970be_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.08, 0.24, 0.44, 0.21, 0.02, 0.01], "state": "The log shipper correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during normal operations. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e548fc1f86152a88_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, with a new vendor onboarded. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f5c5f643919c1fa0_n", "kind": "noul", "options": ["false", "true"], "target": [0.45, 0.55], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: across all regions, during the system migration. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b2e688e24a31e3d3_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.33, 0.59, 0.07, 0.01], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: during the batch window, under reduced staffing. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0cb3257fe2e1fb80_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The log shipper returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the morning shift. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6ece76fb8913b976_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.19, 0.27, 0.01, 0.53], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: across all regions, during the quarterly review. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c4a9a26108493ba7_n", "kind": "noul", "options": ["false", "true"], "target": [0.42, 0.58], "state": "The metrics pipeline flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during normal operations. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a8b2dca32536fb49_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.19, 0.06, 0.55, 0.2], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c565dc0ad178473f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0808, 0.5657, 0.1717, 0.1818], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: across all regions, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bca812d5e98769c8_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: across all regions, while on-call rotation changed. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d545ca61dd544ece_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.95, 0.01, 0.03], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, shortly after a software update. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ff7ceb3dfc41c44d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.07, 0.8, 0.13, 0.0, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: over the last hour, during the morning shift. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ae205c79667ec1e1_n", "kind": "noul", "options": ["false", "true"], "target": [0.67, 0.33], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: during the batch window, during the quarterly review. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2a02ff15271547cf_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cf0b53949a90140f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.23, 0.76, 0.01], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, while legacy systems are still active. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bffecabe386dadc7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.39, 0.58, 0.01], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: in production only, at the end of the fiscal period. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b19deea4c8771445_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.21, 0.77], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: across all regions, while legacy systems are still active. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9422c330c4144ac1_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "The log shipper matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during a scheduled maintenance window. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_facda66362759f45_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.19, 0.07, 0.53, 0.21], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the holiday freeze. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e6860f2cdec64992_n", "kind": "noul", "options": ["false", "true"], "target": [0.64, 0.36], "state": "Service catalog-sync shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: across all regions, during the system migration. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3e1649912cda723c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.1, 0.44, 0.43, 0.03, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: over the last hour, while legacy systems are still active. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9aeb8e1ea28c05b8_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: during the batch window, immediately after go-live. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_97d5a11e89a3bdc4_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.04, 0.72, 0.23, 0.01], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: in production only, following a recent audit. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_58f0cba1a01d3beb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.25, 0.38, 0.35, 0.01], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: in production only, under reduced staffing. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ef2f008c09137d3a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.15, 0.8, 0.05], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: over the last hour, at the end of the fiscal period. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ad95b8e13df8563_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.77, 0.01, 0.2], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: over the last hour, immediately after go-live. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0045a4bca93cf802_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.1, 0.81, 0.09], "state": "The metrics pipeline flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: in production only, mid-incident. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_944bcee49c70c2c0_n", "kind": "noul", "options": ["false", "true"], "target": [0.58, 0.42], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: over the last hour, during a scheduled maintenance window. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c61f01fb26fee313_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.86, 0.12, 0.02, 0.0], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during normal operations. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8644b952d3ebaac0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.34, 0.56, 0.1, 0.0, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: during the batch window, while on-call rotation changed. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4ec76076b7e24645_n", "kind": "noul", "options": ["false", "true"], "target": [0.6, 0.4], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during normal operations. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4b93bcb1a0d92877_n", "kind": "noul", "options": ["false", "true"], "target": [0.7, 0.3], "state": "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 monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2acdfd4e4a77c6c9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.1, 0.55, 0.31, 0.01], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: during the batch window, under reduced staffing. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c4cad63dec516304_n", "kind": "noul", "options": ["false", "true"], "target": [0.44, 0.56], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: across all regions, following a recent audit. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b5b3d7710aa6ad81_n", "kind": "noul", "options": ["false", "true"], "target": [0.69, 0.31], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: across all regions, during normal operations. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4b3f263ef6573907_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: across all regions, during normal operations. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_566565f1098d32f8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.53, 0.46, 0.0], "state": "The log shipper matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: in production only, during the system migration. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fdb3f0a51f488cfa_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: across all regions, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b14add06f66814ff_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.35, 0.63, 0.01], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: over the last hour, at the end of the fiscal period. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a3bea62925139cf9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.28, 0.44, 0.27, 0.01], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, while on-call rotation changed. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_26967d4f336328e0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.36, 0.63, 0.01], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during normal operations. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b2bec84b80c0202e_n", "kind": "noul", "options": ["false", "true"], "target": [0.6, 0.4], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, as part of a compliance sweep. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8b3ac1455ee1eaf2_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.53, 0.46, 0.01, 0.0], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: during the batch window, following a recent audit. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bf5d7836c283fcb6_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.72, 0.24, 0.03, 0.01], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: in production only, under an active deadline. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c00de03c779bd135_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.01, 0.1, 0.68, 0.2, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: in production only, as part of a compliance sweep. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_02cb1be8aac19263_n", "kind": "noul", "options": ["false", "true"], "target": [0.42, 0.58], "state": "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, during the holiday freeze. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_17016241ae04a323_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.08, 0.79, 0.03, 0.1], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: in production only, during the holiday freeze. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_abd8539d50bf5dac_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.12, 0.81, 0.06, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: during the batch window, during the system migration. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_07d520da86ff2650_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.88, 0.06, 0.04, 0.02], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: over the last hour, under an active deadline. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_90ce4d95cbab93cf_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.01, 0.38, 0.56], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: during the batch window, mid-incident. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6939c85b4a787f13_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.54, 0.45, 0.0], "state": "The log shipper correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: across all regions, while legacy systems are still active. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_00bf28b49e3b9b78_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, mid-incident. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_271cad5572ad01d4_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_00bf28b49e3b9b78_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.07, 0.69, 0.24, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, mid-incident. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8f169565ba6b09a5_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, at the end of the fiscal period. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aefe78865d7f777c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.36, 0.62, 0.01], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: across all regions, following a recent audit. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_25772914d7ca27d1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.35, 0.63, 0.02], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: in production only, during normal operations. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_35809d69147bb034_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.77, 0.2, 0.02, 0.01], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: over the last hour, with staffing at reduced levels. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8951268fd6299411_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.18, 0.81, 0.01], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: during the batch window, following a recent audit. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6bd0df3ad1ebab1c_n", "kind": "noul", "options": ["false", "true"], "target": [0.54, 0.46], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: in production only, during an external partner integration. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ad080c35e4c0c6ad_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.97, 0.0, 0.0, 0.03], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: in production only, under reduced staffing. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c6fa919258ccfb20_n", "kind": "noul", "options": ["false", "true"], "target": [0.56, 0.44], "state": "The log shipper flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during a scheduled maintenance window. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d648098aad507d59_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.45, 0.55, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, while on-call rotation changed. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_40cc3fe25478bc2e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.56, 0.39, 0.02, 0.03], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: during the batch window, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_12ca318ff98effae_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.46, 0.52, 0.01], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: across all regions, at the end of the fiscal period. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e41c8641faf49f24_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.56, 0.37, 0.02, 0.0], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: in production only, with a new vendor onboarded. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_efc8fcb3cb26ca93_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.19, 0.78, 0.03], "state": "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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_606e9a20dcf9f48e_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: in production only, as part of a compliance sweep. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1b0a6b5386dad7ad_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.15, 0.05, 0.08, 0.72], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: over the last hour, at the end of the fiscal period. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cb5a905c07f38b16_n", "kind": "noul", "options": ["false", "true"], "target": [0.58, 0.42], "state": "The metrics pipeline flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: during the batch window, during a scheduled maintenance window. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8cd00edfb61aa790_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.47, 0.43, 0.09, 0.01], "state": "Service catalog-sync correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: in production only, during the holiday freeze. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2dbe58976815a173_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: over the last hour, under an active deadline. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_55cf5bca8329e2c0_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.09, 0.81, 0.02, 0.08], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: in production only, under an active deadline. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b62c7d585a3696fc_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.98, 0.0, 0.0, 0.02], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, under reduced staffing. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6e95efe5053620b1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.16, 0.79, 0.05], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: over the last hour, under an active deadline. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b409eee2b9716b2d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.16, 0.04, 0.2, 0.6], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: in production only, following a recent audit. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_592c75c437d5b4d7_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.99, 0.0, 0.01], "state": "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, shortly after a software update. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b50f44447cbe894c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.35, 0.63, 0.01], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: in production only, with staffing at reduced levels. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2dbe58976815a173_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.52, 0.36, 0.1, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: over the last hour, under an active deadline. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_898bc52872afa92e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.48, 0.51, 0.0], "state": "The log shipper flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during the quarterly review. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7bb8e1fcdca1c354_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: in production only, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b15276ef517ef6df_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, at the end of the fiscal period. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a62ab8910c8d9272_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.31, 0.55, 0.14, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: in production only, at the end of the fiscal period. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_88da666dc225276b_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: across all regions, shortly after a software update. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8ecfc8dce5a2c073_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "The metrics pipeline correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: in production only, during normal operations. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_85ecefcdbef9fb21_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.19, 0.79, 0.02], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, with staffing at reduced levels. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a7b29fdb6ed24a87_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: over the last hour, immediately after go-live. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ac707ad6ad8b933c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.17, 0.47, 0.35, 0.01], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: over the last hour, during a scheduled maintenance window. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_545771beb532c6d1_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: in production only, immediately after go-live. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca80377af16a4b61_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "The metrics pipeline lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: over the last hour, mid-incident. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8d282d5e07b87b39_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.4, 0.47, 0.07, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, following a recent audit. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca8a4a5d872e469d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.68, 0.0, 0.02, 0.3], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the morning shift. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f2d8ef78e21ccef8_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.38, 0.09, 0.17, 0.36], "state": "The metrics pipeline shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: across all regions, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7d1c950be418f707_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.01, 0.79, 0.18], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: across all regions, during an external partner integration. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7110795baa64fd8a_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "The metrics pipeline flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: in production only, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6148f5c63aeb1104_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.1, 0.85, 0.05], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during peak load. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d40d7ccd24f10882_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.16, 0.79, 0.05], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, at the end of the fiscal period. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c9c4fbd10e3a6440_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The metrics pipeline 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 review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2087f0d847954f04_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.0, 0.0, 0.98], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5446519d9b810c3e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.26, 0.34, 0.01, 0.39], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: over the last hour, immediately after go-live. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cc7a5a80bb6cb130_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: over the last hour, while on-call rotation changed. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9bbefa0ae04944d6_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "The metrics pipeline lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: during the batch window, mid-incident. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6db687f54290167b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.1, 0.74, 0.07, 0.09], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: over the last hour, under an active deadline. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cfc3e64768f94897_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.18, 0.74, 0.08], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_43c9c97b906f0eb3_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, with staffing at reduced levels. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_154bf3fb3e7c649c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.76, 0.22, 0.01, 0.01], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: across all regions, during the holiday freeze. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_82981a27e1eae86c_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: during the batch window, under an active deadline. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dbef714b7c0ecc06_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "Service catalog-sync correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: during the batch window, as part of a compliance sweep. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c671edaa285d4eeb_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.99, 0.0, 0.0, 0.01], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, while on-call rotation changed. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6c01fb2f938e811a_n", "kind": "noul", "options": ["false", "true"], "target": [0.68, 0.32], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: across all regions, while legacy systems are still active. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_20dc48a108093394_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: during the batch window, as part of a compliance sweep. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c9b7dfe4a12581b6_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "The log shipper correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: in production only, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_907ebda9248a50ee_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: over the last hour, following a recent audit. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_28f7f287b7ad5c59_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.61, 0.29, 0.09, 0.01], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: in production only, immediately after go-live. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cdb8f9b457ecbb19_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: during the batch window, as part of a compliance sweep. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8d7074f1ceb7e28a_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "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.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fcbfde8cc9d3ed1e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.12, 0.85, 0.03], "state": "The log shipper correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, while on-call rotation changed. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0401571343adeda6_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: across all regions, during normal operations. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d2daeaf32c6f1c4f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.27, 0.71, 0.01], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: in production only, following a recent audit. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f9384266eddbe211_n", "kind": "noul", "options": ["false", "true"], "target": [0.41, 0.59], "state": "The log shipper matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: across all regions, at the end of the fiscal period. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7be8826494ddc38d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.83, 0.13, 0.02, 0.02], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_22953d990ae9932a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.42, 0.36, 0.2, 0.01], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: in production only, following a recent audit. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6768b86a2cdb4545_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.28, 0.53, 0.16, 0.0], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: across all regions, mid-incident. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_31a72894c028bd0d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.97, 0.0, 0.0, 0.03], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: in production only, during normal operations. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e32ef1e1fed78397_n", "kind": "noul", "options": ["false", "true"], "target": [0.59, 0.41], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: in production only, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f5516e642cdae6be_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.39, 0.11, 0.02, 0.48], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: in production only, during the morning shift. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_99f4926a28da3e72_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.28, 0.71, 0.01], "state": "The log shipper flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: in production only, shortly after a software update. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c8d3a88ec4e4ab77_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.02, 0.67, 0.3], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: during the batch window, during an external partner integration. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3f90bca40ad12a23_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: in production only, during an external partner integration. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_333059e1fc2e58ed_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: across all regions, during the system migration. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ab9782399cec05f_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: during the batch window, during peak load. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_19933be1a64d35aa_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "The log shipper shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: during the batch window, under an active deadline. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7e974876a8103eda_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: over the last hour, during peak load. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_881292248a6bb1b4_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: in production only, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4e88f6b96494f179_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.32, 0.62, 0.06, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: during the batch window, during the morning shift. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ffe07fc5c83e212c_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: in production only, with staffing at reduced levels. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ec0d5e1348186e49_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.0, 0.32, 0.67], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: over the last hour, during a scheduled maintenance window. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8caecf8f5f0117cc_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: across all regions, under an active deadline. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b4877d16207f58f8_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.74, 0.21, 0.05, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: over the last hour, during an external partner integration. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_216093cc0efc502f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.4, 0.58, 0.01], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: in production only, following a recent audit. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a3275bad830c6245_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.15, 0.81, 0.04], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_69429f4259b7c1c8_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.28, 0.06, 0.41, 0.25], "state": "The metrics pipeline correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: during the batch window, while on-call rotation changed. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_65d420091d685b11_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.04, 0.46, 0.5], "state": "The log shipper correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: across all regions, immediately after go-live. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_afd87f8fdf55b851_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.4, 0.58, 0.01], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: during the batch window, shortly after a software update. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d0eaff04e4823fc8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.55, 0.43, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: over the last hour, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_34bbcf72cba26e7f_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, with a new vendor onboarded. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a41c11967d7e7ce0_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.07, 0.6, 0.29], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: over the last hour, while legacy systems are still active. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7cdb1dc3dd91c005_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.02, 0.37, 0.6, 0.01], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: over the last hour, as part of a compliance sweep. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_42e149363a519e75_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.63, 0.29, 0.05, 0.03], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during the holiday freeze. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fe5d1a897a972bd3_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: in production only, under reduced staffing. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b62d224e1129a318_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.94, 0.0, 0.0, 0.06], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, while legacy systems are still active. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4a84bcf25bcb06cb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.5, 0.43, 0.02], "state": "The log shipper matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: over the last hour, immediately after go-live. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_37cf5fda142ee2d9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.52, 0.47, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during the holiday freeze. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_67b9298660fe6f7b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.18, 0.8, 0.02], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: over the last hour, following a recent audit. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_94e09ad0b5782a30_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.48, 0.52, 0.0], "state": "The metrics pipeline flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: in production only, while on-call rotation changed. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e128f1c870538474_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.85, 0.1, 0.04, 0.01], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during normal operations. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7bc7b101dcdbe3af_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during peak load. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d9e74ceba11e7d0c_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: across all regions, during the quarterly review. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_db769b16385b31ad_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.0, 0.06, 0.9, 0.04], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, at the end of the fiscal period. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d9d62848c6ae87f0_n", "kind": "noul", "options": ["false", "true"], "target": [0.68, 0.32], "state": "The log shipper shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: in production only, during an external partner integration. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_efc678416d230d59_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.0, 0.01, 0.39, 0.57, 0.02], "state": "The metrics pipeline shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: in production only, immediately after go-live. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4fd84c403fe42b2c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.11, 0.67, 0.2, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: in production only, at the end of the fiscal period. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_35fd00d075629b6a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.53, 0.35, 0.09, 0.0], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during the holiday freeze. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e6c3845770cae3d1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.1, 0.25, 0.56, 0.09, 0.0], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: during the batch window, shortly after a software update. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ac707ad6ad8b933c_n", "kind": "noul", "options": ["false", "true"], "target": [0.4, 0.6], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: over the last hour, during a scheduled maintenance window. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7dab1716961e82a1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.55, 0.43, 0.0], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: across all regions, following a recent audit. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_547253d9595610e7_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.57, 0.37, 0.05, 0.01], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: across all regions, shortly after a software update. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_61679747d28e5ac0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.13, 0.83, 0.04], "state": "Node pgsql-14 correlates with the vendor status page incident; 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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0770212636f5d27c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.06, 0.08, 0.17, 0.69], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during a scheduled maintenance window. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e191545f5efd4adc_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: in production only, at the end of the fiscal period. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3672ae046d55d2ff_n", "kind": "noul", "options": ["false", "true"], "target": [0.49, 0.51], "state": "The log shipper lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: during the batch window, during normal operations. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b4877d16207f58f8_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: over the last hour, during an external partner integration. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_42e149363a519e75_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.38, 0.61, 0.01], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during the holiday freeze. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c8d6550a00e3dd9a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.25, 0.71, 0.02, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: across all regions, while legacy systems are still active. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f4d553a4e7c1708d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.05, 0.79, 0.15, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: over the last hour, as part of a compliance sweep. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_76bdd9f766d045c3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.49, 0.5, 0.0], "state": "The log shipper reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: during the batch window, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8eabafb20ab993ac_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "Service catalog-sync flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: in production only, mid-incident. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6c3c8312a7b7ee96_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.08, 0.29, 0.59, 0.04, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; 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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_af1e756533f5b96e_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: over the last hour, mid-incident. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_620918a8930534d4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.35, 0.63, 0.01], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: in production only, while on-call rotation changed. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0a638fbb87921849_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: over the last hour, during the holiday freeze. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_53f914db37d4a5de_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "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.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c6ec59909cbfc006_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.31, 0.62, 0.06, 0.01], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: in production only, during normal operations. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e6acfb6b116f5df8_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: over the last hour, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0e77bc02de5b7405_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.91, 0.07, 0.01, 0.01], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: over the last hour, during the holiday freeze. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8654c89c1a9ce524_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.32, 0.57, 0.09, 0.02], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: over the last hour, during normal operations. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b087eafd33e8f843_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, mid-incident. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e07935bdabd6ece5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.21, 0.41, 0.23, 0.14, 0.01, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: over the last hour, mid-incident. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_082781777b5ddd99_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: over the last hour, during peak load. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cc950b503b0b144e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.2, 0.72, 0.07, 0.01], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during the quarterly review. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d648098aad507d59_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.97, 0.02, 0.01, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, while on-call rotation changed. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e404b58732f62eef_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.2, 0.78, 0.02], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during an external partner integration. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4d291bb2bb8bde41_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: over the last hour, while legacy systems are still active. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_56528b34b1cf8ef8_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: during the batch window, during normal operations. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fbdffc654aa70f03_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.03, 0.73, 0.24, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: over the last hour, following a recent audit. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4cae264ba9fa2d9d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.09, 0.67, 0.24, 0.0], "state": "The log shipper matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: in production only, during the quarterly review. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a63716f851840e37_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.27, 0.64, 0.09, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: in production only, at the end of the fiscal period. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dc2f0c6dddb325ca_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.38, 0.6, 0.01], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: in production only, during normal operations. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_60ca8bad0e69c424_n", "kind": "noul", "options": ["false", "true"], "target": [0.67, 0.33], "state": "The log shipper shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: over the last hour, shortly after a software update. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a4bb529c22bf8a2e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.16, 0.81, 0.03], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: across all regions, during the morning shift. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dd97a7644ebbc681_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: in production only, during peak load. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ee82c9b5033842cc_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.83, 0.11, 0.05, 0.01], "state": "The log shipper shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: over the last hour, under an active deadline. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c121cb4bd7c416f0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.11, 0.85, 0.04], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: across all regions, immediately after go-live. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c1db3e5c7ee66cf0_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, shortly after a software update. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_98eeb572a6a387ed_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.11, 0.03, 0.52, 0.34], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3c9a9ac252417e4c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.73, 0.05, 0.01, 0.21], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: across all regions, as part of a compliance sweep. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ed57ecd87040f97c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.98, 0.01, 0.0, 0.01], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: over the last hour, mid-incident. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cedfd89ef60b48d1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.25, 0.74, 0.01], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: across all regions, while legacy systems are still active. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7f7f4d11d4dc8bee_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "The log shipper reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: during the batch window, under an active deadline. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2e1d1517a60fb1ef_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: over the last hour, under an active deadline. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_37bc51b60bb6e4be_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.19, 0.04, 0.65, 0.12], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: across all regions, with staffing at reduced levels. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1873fee42c08954c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.09, 0.43, 0.45, 0.03, 0.0], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: over the last hour, during normal operations. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_45e86a12b377851d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.06, 0.41, 0.52, 0.01], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during normal operations. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b6e603096ce8f68a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.42, 0.45, 0.12, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: over the last hour, immediately after go-live. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2fd2970ca94bf937_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.14, 0.59, 0.24, 0.01], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, immediately after go-live. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c122da7d0e940ed8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.02, 0.6, 0.31, 0.07, 0.0, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: across all regions, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f22b696c8ad01f8d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.83, 0.13, 0.04, 0.0], "state": "Service catalog-sync correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: over the last hour, mid-incident. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4049b2027d639a83_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.48, 0.51, 0.0], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: across all regions, during the quarterly review. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6939c85b4a787f13_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "The log shipper correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: across all regions, while legacy systems are still active. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_949ffb792b47aacd_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.48, 0.08, 0.01, 0.43], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: across all regions, as part of a compliance sweep. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fd73641703dddfa2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.29, 0.7, 0.01], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: in production only, during the holiday freeze. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_566565f1098d32f8_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "The log shipper matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: in production only, during the system migration. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_619efcbc566a9e25_n", "kind": "noul", "options": ["false", "true"], "target": [0.51, 0.49], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: in production only, at the end of the fiscal period. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a54a770ab43ec38f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.92, 0.04, 0.02, 0.02], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7445d6c551f5ebd5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.12, 0.49, 0.39, 0.0, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: during the batch window, during peak load. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0a15b7e22dde6c69_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.56, 0.44, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: over the last hour, with staffing at reduced levels. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f9cbf7da1cc37d74_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.79, 0.19, 0.01, 0.01], "state": "The log shipper matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: across all regions, during peak load. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6d191dd289c4ca26_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: across all regions, under reduced staffing. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_feaf5d052abfc4f4_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: over the last hour, during an external partner integration. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c4fe45ed4aba8c30_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.11, 0.41, 0.14, 0.34], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: during the batch window, following a recent audit. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5106d0b9782340ac_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.14, 0.79, 0.03, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: across all regions, during normal operations. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e1d3c56502e47eb2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.02, 0.12, 0.77, 0.08, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: in production only, while legacy systems are still active. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_12d411cbc3e2e6df_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.69, 0.3, 0.01, 0.0], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: in production only, during an external partner integration. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c4a9a26108493ba7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.49, 0.51, 0.0], "state": "The metrics pipeline flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during normal operations. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_75b2a76312b611d0_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.71, 0.0, 0.18, 0.11], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: across all regions, with staffing at reduced levels. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_15d1d04c17f926ec_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.08, 0.66, 0.25, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: over the last hour, as part of a compliance sweep. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ea95c5e5f83eb24c_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, while on-call rotation changed. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3e08344f71faeefd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.4, 0.58, 0.01], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ebe8321726c860a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.19, 0.63, 0.17, 0.01, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: in production only, at the end of the fiscal period. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e39a6feee2dfa616_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.0, 0.01, 0.49, 0.48, 0.01], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: during the batch window, shortly after a software update. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_399c65059fa89b66_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.35, 0.64, 0.01], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: over the last hour, shortly after a software update. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f4aa0aa6a3f7e670_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: over the last hour, under an active deadline. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_67ccf4b8a02c6960_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: in production only, during the quarterly review. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b93cccd8137900bd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.24, 0.54, 0.17, 0.01], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6efbe7753cc413fc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.27, 0.61, 0.08, 0.0], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, while legacy systems are still active. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8803044750369cbb_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.16, 0.04, 0.02, 0.78], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: in production only, as part of a compliance sweep. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1898397db47dcae0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.11, 0.81, 0.08], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: in production only, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_93ec4830fbf491e1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.27, 0.38, 0.33, 0.01], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, under an active deadline. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a40b864642d07031_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.68, 0.29, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: in production only, during peak load. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ac707ad6ad8b933c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.07, 0.15, 0.65, 0.13, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: over the last hour, during a scheduled maintenance window. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_52d88160702ee1e8_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: over the last hour, under reduced staffing. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bb0fbbfbdb697cb8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.04, 0.81, 0.15, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: across all regions, while on-call rotation changed. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6febbf9e643d1b73_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.74, 0.22, 0.03, 0.01], "state": "The log shipper reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, while on-call rotation changed. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b1d2d3b4c9c30330_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.29, 0.7, 0.01], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during the morning shift. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0c134def800aa1c9_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.6, 0.33, 0.06], "state": "The log shipper matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: during the batch window, shortly after a software update. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bf38b3e21bbd4c13_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.15, 0.66, 0.19, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, shortly after a software update. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cd8ea6a5eb6c1279_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.96, 0.03, 0.0, 0.01], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally flags a step-function change in error slope. Context: during the batch window, during normal operations. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6ac38d4bce2e7cdf_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.66, 0.33, 0.0], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: across all regions, following a recent audit. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ee3659e8cc8f7f0_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "The metrics pipeline lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: during the batch window, under an active deadline. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_628da98585f96231_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.81, 0.19, 0.0, 0.0], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: in production only, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_13144f828cc41e78_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.84, 0.12, 0.03, 0.01], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during peak load. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4ec76076b7e24645_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.21, 0.05, 0.71], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during normal operations. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_21c9926a6455b119_n", "kind": "noul", "options": ["false", "true"], "target": [0.48, 0.52], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: over the last hour, while on-call rotation changed. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2053e3f435637359_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.06, 0.05, 0.47, 0.39, 0.02], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: over the last hour, as part of a compliance sweep. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4117b7e7a759d4a8_n", "kind": "noul", "options": ["false", "true"], "target": [0.37, 0.63], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: across all regions, under reduced staffing. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1daa4561fd5f4cb0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.16, 0.32, 0.47, 0.05, 0.0], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: during the batch window, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_06236d48ad247d84_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.07, 0.33, 0.45, 0.14, 0.01], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during a scheduled maintenance window. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8d7b1a12446e5cdd_n", "kind": "noul", "options": ["false", "true"], "target": [0.66, 0.34], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: over the last hour, following a recent audit. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8b180fc0ed960ca0_n", "kind": "noul", "options": ["false", "true"], "target": [0.48, 0.52], "state": "The log shipper lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: in production only, during the quarterly review. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0e781677058aae26_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.09, 0.73, 0.18, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: over the last hour, while legacy systems are still active. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_93db406618a09300_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: over the last hour, during peak load. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0a598b617a354a8e_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: during the batch window, while on-call rotation changed. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a0748c3ca4594d4d_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: across all regions, under reduced staffing. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_65164c533f2393ba_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.1, 0.85, 0.05], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: in production only, while legacy systems are still active. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_18fda9a7e70ed3b2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.6, 0.0, 0.33, 0.07], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: in production only, while on-call rotation changed. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8151614ed408e0bc_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.08, 0.02, 0.23, 0.67], "state": "The log shipper shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: over the last hour, during the system migration. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7ec32feaa2ad91d2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.88, 0.0, 0.04, 0.08], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: across all regions, with a new vendor onboarded. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4e0e9f5518bfb29f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.57, 0.37, 0.06, 0.0], "state": "The log shipper flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: over the last hour, during the morning shift. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_975da4fa25118d20_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: in production only, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c83bfa4f23bdafa6_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.0, 0.34, 0.64, 0.02], "state": "The log shipper shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: during the batch window, during the morning shift. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_30292a804880b775_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.02, 0.74, 0.24, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: over the last hour, with a new vendor onboarded. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b46a0ac38930c271_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: in production only, during the morning shift. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6eb9dba9ab856ff6_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.11, 0.79, 0.1], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: across all regions, during an external partner integration. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3273873af4e5532e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.45, 0.53, 0.01], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: in production only, while on-call rotation changed. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e9d3e82390401326_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.13, 0.79, 0.08], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: in production only, under an active deadline. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6abdd07f3694153e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.44, 0.33, 0.21, 0.02], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: across all regions, under an active deadline. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6237c1ce5bbad329_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.12, 0.34, 0.52, 0.02], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: across all regions, while legacy systems are still active. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7e8f6be2bf0bdf97_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.2, 0.67, 0.09, 0.04], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: across all regions, as part of a compliance sweep. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_60ca8bad0e69c424_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.64, 0.35, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: over the last hour, shortly after a software update. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a4969c7289a63af4_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.23, 0.43, 0.29, 0.05], "state": "The log shipper shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: across all regions, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3c9a9ac252417e4c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.18, 0.75, 0.06], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: across all regions, as part of a compliance sweep. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_82af816a7946017e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.37, 0.61, 0.01], "state": "The metrics pipeline correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: during the batch window, following a recent audit. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e5c6eee36852ab2f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.02, 0.67, 0.29, 0.02], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_61679747d28e5ac0_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Node pgsql-14 correlates with the vendor status page incident; 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.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f7e7855fd93498dc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.05, 0.79, 0.15, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: across all regions, while legacy systems are still active. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b39a58650d0a51f1_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during the morning shift. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fe64019b62b8a2bb_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.98, 0.0, 0.01, 0.01], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during the system migration. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8365c8575c91c116_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.02, 0.33, 0.64, 0.01], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, as part of a compliance sweep. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2019fc4fdfc5baaa_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.02, 0.02, 0.08, 0.63, 0.25, 0.0], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: in production only, during an external partner integration. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_48ee605a64b55f7b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.48, 0.52, 0.0], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_238ce2e06ddb6af4_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.7, 0.28], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: in production only, during normal operations. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ac3b2f0fee6e63db_n", "kind": "noul", "options": ["false", "true"], "target": [0.5, 0.5], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: over the last hour, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9f0b1100b9ccfa39_n", "kind": "noul", "options": ["false", "true"], "target": [0.92, 0.08], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, mid-incident. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f6e28c5d9c22b95b_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, while legacy systems are still active. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ce98cdc48a8f7f10_n", "kind": "noul", "options": ["false", "true"], "target": [0.52, 0.48], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: during the batch window, while on-call rotation changed. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d793467ddf6904ff_n", "kind": "noul", "options": ["false", "true"], "target": [0.44, 0.56], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f42c74d501ac94a9_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: across all regions, with staffing at reduced levels. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cd0cd6709908bf4d_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "The log shipper shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: in production only, immediately after go-live. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_65ca17f9372e1113_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.32, 0.68, 0.0], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: during the batch window, with staffing at reduced levels. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ea71e8c67d2fa6df_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.76, 0.21, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the holiday freeze. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fc6fae9c93dd288d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.49, 0.45, 0.06, 0.0, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: in production only, during normal operations. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3b854371d3e92f2d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.25, 0.03, 0.14, 0.58], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, following a recent audit. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d426d5cd2cbd06e9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.03, 0.66, 0.3], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the quarterly review. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_44a715877fcd8676_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "The metrics pipeline flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: in production only, mid-incident. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d49495b23fb3f83a_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: in production only, immediately after go-live. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_242c8bdf74d35e85_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.95, 0.04, 0.0, 0.01], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: over the last hour, under an active deadline. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0694db7aff2095ff_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.42, 0.58, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: during the batch window, during the morning shift. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b0f8c6e1133385a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.35, 0.62, 0.01], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: during the batch window, at the end of the fiscal period. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_08adbaf45c80c98f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.97, 0.02, 0.01, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during peak load. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bd80b5eee25864f1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.49, 0.31, 0.04, 0.16], "state": "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, while on-call rotation changed. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2979a26c36e1934b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.07, 0.47, 0.45, 0.01], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, following a recent audit. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dc6bf0bdddc100c1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.44, 0.53, 0.01], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: in production only, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_93fe43f78038bc22_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f9448e26ddb2fe9b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.42, 0.52, 0.04, 0.02], "state": "The log shipper reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: in production only, shortly after a software update. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cefc46d1289e89e2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.1, 0.5, 0.38, 0.02, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: across all regions, with staffing at reduced levels. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_70af3442ff22c418_n", "kind": "noul", "options": ["false", "true"], "target": [0.61, 0.39], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: across all regions, under reduced staffing. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_20574748795f05ef_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.08, 0.46, 0.45], "state": "The log shipper reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: over the last hour, while legacy systems are still active. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7132abf43f1ec5eb_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: over the last hour, during an external partner integration. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1be9baac9f657dc9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.72, 0.27, 0.0], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: during the batch window, following a recent audit. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3ef81b5d239fce3c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.92, 0.04, 0.01, 0.03], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, mid-incident. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8d91ec5ab9e4ff9a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.39, 0.49, 0.11, 0.01], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: during the batch window, during the holiday freeze. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_04c53e20dffe85ee_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.04, 0.03, 0.91], "state": "The metrics pipeline lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: across all regions, as part of a compliance sweep. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c6273579a445e029_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "The log shipper flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: over the last hour, during an external partner integration. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2308046dcdeaacee_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: during the batch window, during the system migration. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_723c1a63c27ae04d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.15, 0.4, 0.42, 0.02], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: across all regions, under reduced staffing. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ad0e854f5e3d1299_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.11, 0.84, 0.05], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: during the batch window, during the quarterly review. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f6c88f9551f0205b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.05, 0.78, 0.17, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: during the batch window, during the holiday freeze. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_28f7f287b7ad5c59_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: in production only, immediately after go-live. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8b29e9a77ec9154c_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: across all regions, shortly after a software update. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2551c0b08cab3e12_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.11, 0.57, 0.3, 0.02], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: during the batch window, mid-incident. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7d37fbf63f0dee75_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.91, 0.05, 0.01, 0.03], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: during the batch window, while legacy systems are still active. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2f9b56e7ef8f3e7c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.59, 0.38, 0.02, 0.01], "state": "The metrics pipeline shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: in production only, shortly after a software update. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_053484595eda5c3c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.23, 0.74, 0.02], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b4309afdabc04b24_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.68, 0.3], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: during the batch window, during the quarterly review. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a89b7747919e89e5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.7, 0.29, 0.0], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: over the last hour, following a recent audit. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7e1e862e853db28f_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: across all regions, during the quarterly review. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_30de2b3611a65718_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during the holiday freeze. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c8203d3a2fe8d894_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.07, 0.77, 0.15, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally matches last Tuesday's incident signature. Context: across all regions, while on-call rotation changed. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2dd8e73ba12f8e55_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.32, 0.5, 0.17, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, immediately after go-live. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3df20839b079da87_n", "kind": "noul", "options": ["false", "true"], "target": [0.37, 0.63], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: across all regions, during the quarterly review. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_85ecefcdbef9fb21_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.96, 0.0, 0.0, 0.04], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, with staffing at reduced levels. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2086f85dbeeda4f0_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.93, 0.06, 0.01, 0.0], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: in production only, with a new vendor onboarded. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d4fa236ca777280f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.41, 0.58, 0.01], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: over the last hour, at the end of the fiscal period. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca22e8ede04e9aa4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.08, 0.7, 0.21, 0.0], "state": "The log shipper correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: during the batch window, at the end of the fiscal period. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3c94befa6c593780_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.43, 0.45, 0.11, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during peak load. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e7173d97184683b8_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.04, 0.4, 0.55, 0.01], "state": "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, during the morning shift. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_de0afa4ae7ab87ff_n", "kind": "noul", "options": ["false", "true"], "target": [0.22, 0.78], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: during the batch window, under reduced staffing. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a4378eb2592b221b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.12, 0.12, 0.05, 0.71], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: during the batch window, following a recent audit. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2359d166bc00cc05_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.1, 0.81, 0.09], "state": "Dashboard checkout-funnel 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 automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_246297b575a73e5b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.76, 0.17, 0.02, 0.05], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during the system migration. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e6a70f212b29c37f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.35, 0.56, 0.06, 0.03], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: during the batch window, as part of a compliance sweep. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_67ac392549e72423_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: across all regions, during the holiday freeze. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7cc38c6039be78ed_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.52, 0.29, 0.18, 0.01], "state": "The log shipper reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: in production only, during the holiday freeze. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fc714cc230b209b8_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e9bd483e36d9f2cc_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.99, 0.0, 0.0, 0.01], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, with staffing at reduced levels. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_802319a40832449d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.09, 0.85, 0.06], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: across all regions, during the morning shift. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8df7d1ab3fcf6704_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "The log shipper correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during the holiday freeze. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b24a498fc67ae71d_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Node pgsql-14 flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: over the last hour, during the system migration. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6c0589a8f7672ca7_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.25, 0.15, 0.18, 0.42], "state": "Service catalog-sync 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 operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_91a6cbeabcbdbf56_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The log shipper shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: across all regions, while legacy systems are still active. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ad1368e5a5750bc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.26, 0.65, 0.07, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: during the batch window, during peak load. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ba6246cfc8df2c60_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: over the last hour, while on-call rotation changed. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_18f7bf8ac018bee5_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.73, 0.25, 0.02, 0.0], "state": "The metrics pipeline correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: during the batch window, at the end of the fiscal period. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7a46391bdb0054ac_n", "kind": "noul", "options": ["false", "true"], "target": [0.65, 0.35], "state": "The log shipper shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: in production only, with a new vendor onboarded. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fb1ae7baec9a0c5a_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "The metrics pipeline flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: in production only, immediately after go-live. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3def9c518bb7fdc1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.72, 0.27, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: across all regions, during the holiday freeze. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aeaae2abc7c01adb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.03, 0.09, 0.16, 0.45, 0.25, 0.02], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: over the last hour, during peak load. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_834c30aeb041a20f_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: across all regions, mid-incident. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_03284d438b2c61b9_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Service catalog-sync flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: in production only, at the end of the fiscal period. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d3681233b25a784b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.02, 0.48, 0.45], "state": "The log shipper reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: during the batch window, under reduced staffing. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b421741fab40cad5_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.52, 0.39, 0.09, 0.0], "state": "The log shipper correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: over the last hour, during an external partner integration. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_04e2d4344a078530_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.07, 0.69, 0.05, 0.19], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during the morning shift. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7744676a7b52bd13_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0202, 0.3939, 0.5657, 0.0202], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: over the last hour, under an active deadline. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9fd26bc8a4b18ae8_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.41, 0.56, 0.02], "state": "The log shipper correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: over the last hour, during the morning shift. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a262d3fd496342a2_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.78, 0.19, 0.03, 0.0], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: during the batch window, during the quarterly review. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_efa38ebe01de4c3e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.18, 0.5, 0.29, 0.03, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7663c6bf41f0d559_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.73, 0.24, 0.02, 0.01], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: during the batch window, during the system migration. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a8a54bac2816a1a8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.43, 0.49, 0.03, 0.0], "state": "Service catalog-sync flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: across all regions, during the morning shift. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_574d2d1727166f0e_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "The log shipper lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during a scheduled maintenance window. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_58fd5b58415fc8b7_n", "kind": "noul", "options": ["false", "true"], "target": [0.67, 0.33], "state": "The metrics pipeline shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: during the batch window, during normal operations. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b2e688e24a31e3d3_n", "kind": "noul", "options": ["false", "true"], "target": [0.51, 0.49], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: during the batch window, under reduced staffing. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fe43d435020c821f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.23, 0.66, 0.06, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: across all regions, during normal operations. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1c30f122c6ddbb0f_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ada669e16345170d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.5, 0.47, 0.01], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: in production only, during the holiday freeze. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9a3d44ae6c26dc29_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.55, 0.44, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: over the last hour, during peak load. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ab467b76bb5b3efe_n", "kind": "noul", "options": ["false", "true"], "target": [0.45, 0.55], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: in production only, during the quarterly review. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6e95efe5053620b1_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: over the last hour, under an active deadline. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_349b2dd10020ca1c_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: in production only, with a new vendor onboarded. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7847c6638d2d7245_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.24, 0.74, 0.01, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: over the last hour, while legacy systems are still active. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c837223c011ee32f_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "The log shipper reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: over the last hour, during the quarterly review. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6ac38d4bce2e7cdf_n", "kind": "noul", "options": ["false", "true"], "target": [0.57, 0.43], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: across all regions, following a recent audit. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_95bd04038fdf849a_n", "kind": "noul", "options": ["false", "true"], "target": [0.91, 0.09], "state": "The log shipper returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during peak load. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e359ee728df10f92_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: across all regions, during peak load. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5d7ce2b7d51b3a4d_n", "kind": "noul", "options": ["false", "true"], "target": [0.19, 0.81], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, while legacy systems are still active. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_489da28cd4632431_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.13, 0.65, 0.2, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: across all regions, immediately after go-live. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bff5b66b8f8b665b_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: over the last hour, following a recent audit. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f0510f5114fb2d5e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.09, 0.86, 0.05], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: across all regions, with a new vendor onboarded. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0cd957283bca381a_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: in production only, following a recent audit. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4c3189838fc327dc_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.18, 0.03, 0.34, 0.45], "state": "The metrics pipeline flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: in production only, during a scheduled maintenance window. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_064917e5efe65c5c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.49, 0.34, 0.13, 0.04], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: across all regions, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8f0ef10d2a34443c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.09, 0.0, 0.06, 0.85], "state": "The log shipper lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during the holiday freeze. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0efe7f9f73f1d744_n", "kind": "noul", "options": ["false", "true"], "target": [0.45, 0.55], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: in production only, during the holiday freeze. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f60c955a34ab25dc_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: during the batch window, mid-incident. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0076d0b941179d9f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.43, 0.56, 0.0], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: over the last hour, during the system migration. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0987f0ea596d295c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.21, 0.73, 0.04, 0.02], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: across all regions, at the end of the fiscal period. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6f245f84a003d876_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: during the batch window, during normal operations. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9d52780aed8ad930_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.81, 0.17, 0.01, 0.01], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: in production only, during the system migration. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_13469f2dbd5a6ea2_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the holiday freeze. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3c3dce01b583d115_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, as part of a compliance sweep. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b7ab1229ac0e1c4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.07, 0.62, 0.3, 0.01, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: during the batch window, during peak load. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_574342a250015f84_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.47, 0.52, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: across all regions, while legacy systems are still active. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7d19172e06b9e542_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.99, 0.01, 0.0, 0.0], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: in production only, mid-incident. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9c0c0f781124a8fa_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.11, 0.73, 0.16, 0.0, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: across all regions, during a scheduled maintenance window. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8a1c7d06e85bf1fb_n", "kind": "noul", "options": ["false", "true"], "target": [0.6, 0.4], "state": "The log shipper shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: in production only, during the holiday freeze. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_608cc46d5f3a30d9_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.9, 0.09, 0.01, 0.0], "state": "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, during peak load. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e2ebd70cdc50776f_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Service catalog-sync shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: during the batch window, during the quarterly review. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_05266732ea7c0c47_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0202, 0.2222, 0.5455, 0.202, 0.0101, 0.0], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during normal operations. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f91f438ad72795db_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.01, 0.53, 0.44], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: during the batch window, under an active deadline. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c6a353e612fb4672_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.25, 0.62, 0.04, 0.09], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: across all regions, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_47c96f85a4777ca0_n", "kind": "noul", "options": ["false", "true"], "target": [0.49, 0.51], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: across all regions, during the quarterly review. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5446519d9b810c3e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.15, 0.8, 0.05], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: over the last hour, immediately after go-live. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ff502dd9e03f8734_n", "kind": "noul", "options": ["false", "true"], "target": [0.48, 0.52], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: over the last hour, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e244504935e5dee2_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during the quarterly review. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9b3dc593e72a6352_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "The log shipper shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: in production only, mid-incident. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cee24fa5ca3ef226_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: in production only, during the system migration. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ac7e1b7806206ae0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.25, 0.73, 0.02], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: in production only, during an external partner integration. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_36e4399890860f43_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.52, 0.48, 0.0], "state": "The log shipper matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: in production only, at the end of the fiscal period. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_512a73e3b12d522d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.54, 0.39, 0.06, 0.01], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during normal operations. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d545ca61dd544ece_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, shortly after a software update. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1f024b689f270178_n", "kind": "noul", "options": ["false", "true"], "target": [0.23, 0.77], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: across all regions, shortly after a software update. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7d30c93dec6b73cb_n", "kind": "noul", "options": ["false", "true"], "target": [0.66, 0.34], "state": "The log shipper returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: over the last hour, mid-incident. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d589afe22bb15347_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.24, 0.75, 0.01], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: during the batch window, while on-call rotation changed. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3e141ec8bff8cbe0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.28, 0.71, 0.01], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: over the last hour, during the system migration. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e5c6eee36852ab2f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.16, 0.8, 0.02, 0.0], "state": "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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_01b253b5b4a26597_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.69, 0.29, 0.0], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: during the batch window, during the holiday freeze. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a6ece2c054abb7f5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.45, 0.55, 0.0], "state": "The metrics pipeline shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: across all regions, under an active deadline. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_267f0e5806da91a6_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.52, 0.01, 0.22, 0.25], "state": "The log shipper reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, under an active deadline. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_062e6ffb1e13c0cf_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during the system migration. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ed6d02519f6e5bb7_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.85, 0.14, 0.0, 0.01], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: across all regions, during peak load. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c9cb7279de74fac6_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: during the batch window, immediately after go-live. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_008849a1db9ef8be_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.83, 0.02, 0.1, 0.05], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: in production only, with a new vendor onboarded. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6556a6387cda0578_n", "kind": "noul", "options": ["false", "true"], "target": [0.69, 0.31], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: in production only, during peak load. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8eb27cc5bd011ff9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.48, 0.52, 0.0], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: in production only, shortly after a software update. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5b5c228d79a2bd9b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.22, 0.31, 0.2, 0.27], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: during the batch window, during normal operations. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7e978c76f3b72f57_n", "kind": "noul", "options": ["false", "true"], "target": [0.9, 0.1], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally matches last Tuesday's incident signature. Context: during the batch window, with staffing at reduced levels. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2267eea9d102d78d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.05, 0.86, 0.08, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: over the last hour, following a recent audit. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f91f438ad72795db_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.27, 0.71, 0.02], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: during the batch window, under an active deadline. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bad31f7da30df058_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.88, 0.1, 0.01, 0.01], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: in production only, while on-call rotation changed. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_44ad51df16072829_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.12, 0.76, 0.1, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: in production only, following a recent audit. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3abd2ad4f9802b2c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.41, 0.49, 0.05], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: over the last hour, during an external partner integration. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d793467ddf6904ff_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.59, 0.33, 0.06, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6dbd3b7f659a3008_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.25, 0.24, 0.03, 0.48], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: across all regions, during the holiday freeze. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_14ff907d4eb2c923_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The log shipper shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: during the batch window, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_92b1f9b106fc6c8b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.52, 0.47, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, under reduced staffing. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3b4437b87cdbe174_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.76, 0.14, 0.02, 0.08], "state": "The log shipper shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the morning shift. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_792ec7d963d3857a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.01, 0.55, 0.44], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: over the last hour, during a scheduled maintenance window. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4f207dc26fda8cd1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.0, 0.85, 0.15], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during normal operations. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5a76d617f90304a7_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.11, 0.27, 0.03, 0.59], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during normal operations. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a6fb2e1c6ce2dcb8_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "The log shipper lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: during the batch window, during peak load. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_12c0033c065969bc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.37, 0.63, 0.0], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: during the batch window, shortly after a software update. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_456c1c11ffdf27f0_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: over the last hour, with a new vendor onboarded. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e232cdcc94d54785_n", "kind": "noul", "options": ["false", "true"], "target": [0.42, 0.58], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: across all regions, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5b23949d7b2ed66d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.73, 0.18, 0.04, 0.0], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: in production only, during the quarterly review. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3bb1507f8d990ce1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.18, 0.81, 0.01], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: across all regions, during the system migration. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6010e8b7375581f9_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: during the batch window, shortly after a software update. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0f0db5e05eecc9fd_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.75, 0.19, 0.06, 0.0], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: in production only, at the end of the fiscal period. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f24379de7d51da06_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.68, 0.3, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: across all regions, during the holiday freeze. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7e3a9f077ade4737_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.26, 0.02, 0.07, 0.65], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the holiday freeze. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca298c74eb4f719a_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "The log shipper reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: over the last hour, during the morning shift. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6d479b6637d93b78_n", "kind": "noul", "options": ["false", "true"], "target": [0.42, 0.58], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, while on-call rotation changed. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ed03e282e3184b68_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.72, 0.26, 0.0, 0.02], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, under reduced staffing. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3b9731d64b5da5ff_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.84, 0.14, 0.01, 0.01], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, shortly after a software update. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3a5e19408b2892dd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.13, 0.6, 0.24, 0.02, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: in production only, during the holiday freeze. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_90cdcea7d09d9275_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.44, 0.55, 0.01, 0.0], "state": "The log shipper flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: during the batch window, during an external partner integration. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3327d1c6941d2af5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.19, 0.57, 0.22, 0.01, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: across all regions, at the end of the fiscal period. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b7d09fae8fc48d6e_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: over the last hour, with a new vendor onboarded. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f8bc5094e2ec4b92_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: during the batch window, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_214cf9eb8da30da8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.02, 0.14, 0.25, 0.53, 0.06, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: during the batch window, during the morning shift. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_adadb78e16f3a478_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.04, 0.76, 0.2, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: during the batch window, during an external partner integration. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_493188b3cdd6eb3f_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The metrics pipeline flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: across all regions, with staffing at reduced levels. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c837223c011ee32f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.2, 0.76, 0.03], "state": "The log shipper reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: over the last hour, during the quarterly review. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f89a4dda105c63a9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.06, 0.03, 0.84, 0.07], "state": "Service catalog-sync correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: during the batch window, under an active deadline. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e94814a507b75df6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.03, 0.54, 0.41, 0.01], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: over the last hour, at the end of the fiscal period. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_597f037047e1ee8a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.94, 0.0, 0.04, 0.02], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_daf4a129c3d845c3_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.9, 0.0, 0.09, 0.01], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: across all regions, during an external partner integration. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9f0b1100b9ccfa39_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.03, 0.77, 0.2], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, mid-incident. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7e15f6b732303291_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Service catalog-sync correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: across all regions, during the morning shift. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2f6ff01413ae0a8c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.09, 0.01, 0.02, 0.88], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: during the batch window, as part of a compliance sweep. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e1d3c56502e47eb2_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.34, 0.59, 0.05, 0.02], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: in production only, while legacy systems are still active. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b9f4ac98f99f094b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.36, 0.49, 0.14, 0.01], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: during the batch window, during the holiday freeze. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e9562cb147245077_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: in production only, during the system migration. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ea8e29d7c98ac6fd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.24, 0.71, 0.04], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: in production only, as part of a compliance sweep. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_60ebf4e98066460e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0303, 0.5657, 0.404, 0.0], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: during the batch window, under an active deadline. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b8cc3cd06a9ebaf2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.52, 0.38, 0.08, 0.0], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during an external partner integration. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a96867d88435ebe3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.2, 0.75, 0.04], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: in production only, under an active deadline. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4352b20a148e8169_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.17, 0.56, 0.27, 0.0, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: during the batch window, with staffing at reduced levels. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7e592ecde7250f28_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, mid-incident. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c41083d6a30290a7_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.59, 0.36, 0.04, 0.01], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: over the last hour, while legacy systems are still active. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4228aaa2e56970be_n", "kind": "noul", "options": ["false", "true"], "target": [0.47, 0.53], "state": "The log shipper correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during normal operations. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8366a007668671a0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.05, 0.53, 0.4, 0.01], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: across all regions, during normal operations. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_90a8c0776af1ee46_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.31, 0.66, 0.03], "state": "Service catalog-sync flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: across all regions, immediately after go-live. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e7cd76bf37d59c5b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.33, 0.59, 0.07, 0.01], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: across all regions, as part of a compliance sweep. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6d72a21966b68a17_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.72, 0.26, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: in production only, under reduced staffing. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7dc7ead57a2f6174_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.28, 0.62, 0.1, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: in production only, during normal operations. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e406804a28d03521_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.73, 0.23, 0.03, 0.01], "state": "The metrics pipeline lost 4 minutes of trace data; 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 automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c61f8ad7a3f3729e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.22, 0.43, 0.03, 0.32], "state": "The log shipper flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: across all regions, under an active deadline. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c94d07b1f6a847c3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.14, 0.64, 0.17, 0.0], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: during the batch window, during a scheduled maintenance window. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3b3f8f2a3a82fb3a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.3, 0.67, 0.02], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: across all regions, under an active deadline. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5b12bab349135e1a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.0, 0.01, 0.98], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: across all regions, as part of a compliance sweep. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ac514e4d4f94e3b8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.41, 0.56, 0.01], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: over the last hour, during the holiday freeze. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2c3418ea1663c143_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.19, 0.79, 0.02], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: in production only, under reduced staffing. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5526a3623cfc4bd4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.54, 0.45, 0.0], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: during the batch window, mid-incident. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1b126806088abe2b_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "The log shipper lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: over the last hour, under an active deadline. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cbd0ea7a4a3caa80_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: in production only, under reduced staffing. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4dc2c3d9d295fc4f_n", "kind": "noul", "options": ["false", "true"], "target": [0.4, 0.6], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, following a recent audit. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6bd0df3ad1ebab1c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.12, 0.64, 0.23, 0.01], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: in production only, during an external partner integration. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_56a9c3acbff7a655_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.04, 0.62, 0.34, 0.0], "state": "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 operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a91ff7f327926f23_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.07, 0.34, 0.52, 0.07, 0.0], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: over the last hour, as part of a compliance sweep. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b76bed787bae2704_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: across all regions, with staffing at reduced levels. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7d75b0710d84c256_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "The log shipper reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: during the batch window, with a new vendor onboarded. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cefc46d1289e89e2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.16, 0.01, 0.01, 0.82], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: across all regions, with staffing at reduced levels. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cff0debea5b0a5e3_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.06, 0.73, 0.21, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: in production only, during the system migration. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6421fa2479e9fe3a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.07, 0.05, 0.8, 0.08], "state": "The log shipper shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: across all regions, during an external partner integration. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d5aa1e3dfeff8809_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.07, 0.67, 0.25, 0.0], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: during the batch window, during the quarterly review. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e4614c35d8ee9572_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.03, 0.76, 0.21], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally flags a step-function change in error slope. Context: during the batch window, immediately after go-live. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5b76cb8697cff7ab_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.62, 0.32, 0.03, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: in production only, during the system migration. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_69429f4259b7c1c8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.37, 0.62, 0.01], "state": "The metrics pipeline correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: during the batch window, while on-call rotation changed. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9a3d44ae6c26dc29_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.8, 0.17, 0.03, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: over the last hour, during peak load. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e58f1e8b5e5bbfad_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.84, 0.13, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: over the last hour, during the quarterly review. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_087f18c219b31896_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.2, 0.76, 0.04], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally flags a step-function change in error slope. Context: across all regions, as part of a compliance sweep. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ade8caae7b6af3b6_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: across all regions, mid-incident. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_785dfa5b87bec041_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.02, 0.7, 0.28], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, under an active deadline. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3071548093364da5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.37, 0.62, 0.01], "state": "The log shipper matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: across all regions, during peak load. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_164c228273e57223_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.32, 0.65, 0.02], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: during the batch window, during normal operations. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4c691a13d8b242d3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.49, 0.41, 0.07, 0.0], "state": "The log shipper reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the holiday freeze. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d547e7bf600bc73e_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: in production only, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_75dea4ef284873bb_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "Service catalog-sync 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.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5fe199c2f77c4167_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.71, 0.27, 0.02, 0.0], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: in production only, while on-call rotation changed. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5f9e0e10574a1cbb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.15, 0.81, 0.04], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: in production only, following a recent audit. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_48edfc4be1bcbf8a_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, under an active deadline. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8eb27cc5bd011ff9_n", "kind": "noul", "options": ["false", "true"], "target": [0.61, 0.39], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: in production only, shortly after a software update. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fca572de5a213c93_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.06, 0.74, 0.19, 0.0], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_21e6a43cded08e7e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.13, 0.45, 0.38, 0.04, 0.0], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: in production only, during an external partner integration. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d2dd5a21e104d954_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.38, 0.61, 0.01], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, following a recent audit. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3d831cd6f7b6b5d4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.51, 0.4, 0.05, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: during the batch window, at the end of the fiscal period. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6bc42debdc385da9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.31, 0.62, 0.02], "state": "The log shipper reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: across all regions, as part of a compliance sweep. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fd10d3a5ff659962_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: during the batch window, during peak load. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2f019079094a0bc1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.06, 0.0, 0.36, 0.58], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during the system migration. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7f7ef4f001d86676_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.04, 0.8, 0.16], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during the quarterly review. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a151b1edfba19449_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.76, 0.01, 0.15, 0.08], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: during the batch window, during the holiday freeze. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0e781677058aae26_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: over the last hour, while legacy systems are still active. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_95a60f4c4bddab26_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.9, 0.0, 0.08, 0.02], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, while legacy systems are still active. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_030d1106cefce8c0_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "The log shipper flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: in production only, following a recent audit. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_037325b106978fda_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.96, 0.04, 0.0, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, with staffing at reduced levels. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1392f9f34718911a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.54, 0.18, 0.28, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, immediately after go-live. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3d98b92468216098_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.89, 0.09, 0.02, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, immediately after go-live. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6b579976843d1062_n", "kind": "noul", "options": ["false", "true"], "target": [0.91, 0.09], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: during the batch window, during normal operations. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b0a7ab85acf14d98_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, while on-call rotation changed. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2e89f4d1ee0c5f57_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.79, 0.16, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: in production only, as part of a compliance sweep. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c58194d84ea71f80_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: in production only, mid-incident. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cffdee363df54ae2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.16, 0.73, 0.08, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, with staffing at reduced levels. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_20574748795f05ef_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "The log shipper reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: over the last hour, while legacy systems are still active. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d129e39265375f82_n", "kind": "noul", "options": ["false", "true"], "target": [0.43, 0.57], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: across all regions, with staffing at reduced levels. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d5aa1e3dfeff8809_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.22, 0.23, 0.24, 0.31], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: during the batch window, during the quarterly review. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_77acdec4c70fcacd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.07, 0.52, 0.37, 0.04, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: in production only, at the end of the fiscal period. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b51203e090bb5e3_n", "kind": "noul", "options": ["false", "true"], "target": [0.39, 0.61], "state": "The metrics pipeline shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_41ba49f42d60bbdd_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.03, 0.79, 0.17, 0.01], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during a scheduled maintenance window. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_85f5bc5391744c82_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.31, 0.67, 0.01], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: in production only, while on-call rotation changed. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d0eaff04e4823fc8_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: over the last hour, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6647ce193f53feda_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.07, 0.56, 0.35, 0.01], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: during the batch window, following a recent audit. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_60141a44e3b59106_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.82, 0.15, 0.02, 0.01], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: across all regions, during normal operations. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ffb25ddf3ac1c9a5_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.19, 0.27, 0.53, 0.01], "state": "The log shipper shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: over the last hour, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_33beea01e265dd74_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: over the last hour, immediately after go-live. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6d75fe6a611dab9b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.18, 0.81, 0.01], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, shortly after a software update. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aa76e1b08be64164_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.47, 0.49, 0.03, 0.01], "state": "Service catalog-sync shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: during the batch window, under reduced staffing. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b77c3ff272871e88_n", "kind": "noul", "options": ["false", "true"], "target": [0.56, 0.44], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: across all regions, at the end of the fiscal period. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9b85b736d2fcdf20_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.28, 0.58, 0.1, 0.04], "state": "Service catalog-sync lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: during the batch window, during the system migration. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b1534353421146be_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The log shipper returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: in production only, under reduced staffing. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c4c4ae6fff85a41c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.97, 0.0, 0.0, 0.03], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during the quarterly review. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6c6ec1dac82fd662_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.79, 0.01, 0.0, 0.2], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during the holiday freeze. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6604a3f32186c6ea_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.1, 0.47, 0.42, 0.01], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: in production only, while on-call rotation changed. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f7021a2c42aa9e4d_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: over the last hour, while legacy systems are still active. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8e3cc5c08a03272b_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: across all regions, at the end of the fiscal period. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_35b85705a61db93d_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "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.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b2434e9ed31854d1_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: in production only, during peak load. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5b23949d7b2ed66d_n", "kind": "noul", "options": ["false", "true"], "target": [0.57, 0.43], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: in production only, during the quarterly review. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_831ed8c8932bcf7c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.02, 0.9, 0.08], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: in production only, during an external partner integration. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cf8ba037ff802f40_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "Service catalog-sync shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: during the batch window, as part of a compliance sweep. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1b8eaa85db6cb04f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.51, 0.48, 0.0], "state": "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 supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4e56f946c3cc47ae_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.56, 0.43, 0.0], "state": "The log shipper matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: over the last hour, during the system migration. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_62efc6c17ae9fdcf_n", "kind": "noul", "options": ["false", "true"], "target": [0.46, 0.54], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: during the batch window, following a recent audit. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_313e404e8e6bbfeb_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during the system migration. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3d2cc8f4a2d083b8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.09, 0.75, 0.15, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: across all regions, under an active deadline. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_476ae933bbb6825b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.32, 0.3, 0.02, 0.36], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: across all regions, during normal operations. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6758e4fb9ad82d86_n", "kind": "noul", "options": ["false", "true"], "target": [0.46, 0.54], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: during the batch window, during the quarterly review. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_091896d507eec22b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.75, 0.19, 0.0, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: across all regions, during the holiday freeze. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_88da666dc225276b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.81, 0.15, 0.04], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: across all regions, shortly after a software update. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4107636d7031933a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.0, 0.6, 0.37], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: across all regions, with a new vendor onboarded. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0cd957283bca381a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.12, 0.66, 0.21, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: in production only, following a recent audit. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_321983923609e9b6_n", "kind": "noul", "options": ["false", "true"], "target": [0.58, 0.42], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, as part of a compliance sweep. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cdb8f9b457ecbb19_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.46, 0.52, 0.01], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: during the batch window, as part of a compliance sweep. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7064f2258799ca77_n", "kind": "noul", "options": ["false", "true"], "target": [0.46, 0.54], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: over the last hour, during peak load. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6be6ecf80d315a7d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.42, 0.56, 0.01], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: in production only, under an active deadline. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cb09c555c844d984_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.33, 0.63, 0.03], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, immediately after go-live. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_615204ccced27a63_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.8081, 0.1111, 0.0707, 0.0101], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: over the last hour, while on-call rotation changed. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_59c8b931e491b654_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.32, 0.46, 0.21, 0.0, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: in production only, during a scheduled maintenance window. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1bbc907370dde24d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.14, 0.1, 0.44, 0.32], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, following a recent audit. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0c912fb531a9a1c0_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.31, 0.09, 0.02, 0.58], "state": "The log shipper lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: across all regions, under an active deadline. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_137f7e268343db03_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.37, 0.56, 0.06, 0.01], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during normal operations. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9b356b5f4371089a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.37, 0.61, 0.01], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_12fd89e71c258770_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.02, 0.08, 0.1, 0.35, 0.4, 0.05], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: across all regions, during peak load. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a8e9968846bc963c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.13, 0.81, 0.06], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during the quarterly review. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d5455356765de767_n", "kind": "noul", "options": ["false", "true"], "target": [0.56, 0.44], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: during the batch window, mid-incident. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6f6c1e78524580ff_n", "kind": "noul", "options": ["false", "true"], "target": [0.23, 0.77], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during an external partner integration. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0657f95d47a7e93a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.56, 0.34, 0.08, 0.02], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: over the last hour, while legacy systems are still active. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e93a7b5ee9686a1f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.11, 0.85, 0.04], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: across all regions, with a new vendor onboarded. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b658697efc02e29c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.22, 0.72, 0.04, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: across all regions, shortly after a software update. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_db4bba3f01b6fc7f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.41, 0.49, 0.1, 0.0], "state": "The metrics pipeline flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: across all regions, at the end of the fiscal period. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5dd7a15b977983e3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.53, 0.43, 0.01], "state": "The log shipper reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: during the batch window, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1daa4561fd5f4cb0_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: during the batch window, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_00dfb172536b037c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.14, 0.73, 0.1, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: during the batch window, at the end of the fiscal period. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_89673f54ca543ba6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.03, 0.48, 0.47, 0.01], "state": "Service catalog-sync lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: across all regions, during peak load. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b370d7b306469c20_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: in production only, during an external partner integration. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_12403c7f07468569_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.6, 0.38, 0.01], "state": "The log shipper returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: across all regions, shortly after a software update. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1b9d809ba005a2d4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.04, 0.39, 0.55, 0.02], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: in production only, during the system migration. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7982f8d565dc8cb8_n", "kind": "noul", "options": ["false", "true"], "target": [0.9, 0.1], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: in production only, while legacy systems are still active. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_37b77ed14c3ac6cc_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.38, 0.14, 0.03, 0.45], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: across all regions, while on-call rotation changed. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8f77efe77d58fdec_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.84, 0.02, 0.13], "state": "Node pgsql-14 flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: in production only, shortly after a software update. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e5d7fa621f431d33_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.25, 0.72, 0.02], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: across all regions, with staffing at reduced levels. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cb27d2b12a4d0655_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: in production only, during the system migration. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6df58db4216cd635_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.49, 0.4, 0.1, 0.01], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: over the last hour, during the morning shift. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_15ccc3ec72d606b9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.06, 0.42, 0.48], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: in production only, during the quarterly review. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fdb9fd30eee93272_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.98, 0.01, 0.0, 0.01], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, immediately after go-live. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1c30f122c6ddbb0f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.15, 0.54, 0.24, 0.07], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f0087aa3d312df23_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.09, 0.81, 0.08, 0.02, 0.0, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: across all regions, during the system migration. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9fd01f76ec84cf3c_n", "kind": "noul", "options": ["false", "true"], "target": [0.46, 0.54], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, as part of a compliance sweep. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0158bd7e4d395aa9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.09, 0.88, 0.03], "state": "The log shipper matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: in production only, during the holiday freeze. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8a471ef95a0ece3c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.07, 0.77, 0.15], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: in production only, mid-incident. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e40a73688c998852_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.17, 0.78, 0.05], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during an external partner integration. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2785e65a9c0c0f37_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.32, 0.43, 0.19, 0.04, 0.01], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: in production only, during a scheduled maintenance window. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ad445fd6c49f2c88_n", "kind": "noul", "options": ["false", "true"], "target": [0.44, 0.56], "state": "Service catalog-sync shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: in production only, during the quarterly review. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2466a8342d40299f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.29, 0.01, 0.05, 0.65], "state": "The metrics pipeline lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: during the batch window, at the end of the fiscal period. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_766c5de04e34fd1c_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: in production only, at the end of the fiscal period. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_30ccf5005028298a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.09, 0.62, 0.26, 0.03, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: across all regions, during a scheduled maintenance window. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3afaf2a4d79d6160_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.0808, 0.8182, 0.101], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6d191dd289c4ca26_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.29, 0.69, 0.01], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: across all regions, under reduced staffing. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bd8faeadb33166f2_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.33, 0.53, 0.13, 0.01], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: across all regions, with staffing at reduced levels. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3bac710ac65352a9_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.85, 0.12, 0.03, 0.0], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: in production only, under reduced staffing. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fc8c8f644eab98cb_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.0, 0.63, 0.37], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: over the last hour, during an external partner integration. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b413ba0305cd020d_n", "kind": "noul", "options": ["false", "true"], "target": [0.61, 0.39], "state": "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.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d5bb62c28ad9e0c3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.04, 0.75, 0.21, 0.0], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: over the last hour, during the holiday freeze. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_371f9b65d076919c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.23, 0.74, 0.02], "state": "Service catalog-sync lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: in production only, under an active deadline. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_43af7cd8ac59d578_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.3, 0.69, 0.01], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: over the last hour, under an active deadline. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f3cf1d526c85b8b0_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: during the batch window, during the morning shift. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3bb1507f8d990ce1_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: across all regions, during the system migration. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9331bece1dc7261e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.54, 0.43, 0.02, 0.01], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: during the batch window, under reduced staffing. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8d0ab85e9cbcb251_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.95, 0.04, 0.0, 0.01], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: across all regions, immediately after go-live. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bb268e16aa8345f6_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.25, 0.2, 0.01, 0.54], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: across all regions, as part of a compliance sweep. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_93c306d96afebdb6_n", "kind": "noul", "options": ["false", "true"], "target": [0.71, 0.29], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: over the last hour, while on-call rotation changed. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a744cd6437e7c82f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.6, 0.39, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: during the batch window, while on-call rotation changed. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ac552ffd8f24efe_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "The log shipper flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: in production only, under reduced staffing. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0d329ba81bc3a874_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.46, 0.51, 0.01], "state": "The log shipper reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: over the last hour, during the quarterly review. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_afd87f8fdf55b851_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: during the batch window, shortly after a software update. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5a76d617f90304a7_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during normal operations. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ae2a070a1caa4457_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.86, 0.12, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: during the batch window, while legacy systems are still active. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ba86727b0ec7d77_n", "kind": "noul", "options": ["false", "true"], "target": [0.4, 0.6], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: across all regions, during the system migration. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_111d67ddf223d927_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.16, 0.78, 0.06], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: across all regions, under an active deadline. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b413ba0305cd020d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.54, 0.45, 0.0], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aceabe8eaecd69ed_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: in production only, under reduced staffing. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_65ae26714f6df693_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.24, 0.74, 0.02], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the system migration. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_556c80c853a5e281_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.03, 0.09, 0.61, 0.25, 0.01], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: over the last hour, under reduced staffing. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2aa5fbee764fdf57_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.94, 0.01, 0.01, 0.04], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during the system migration. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_961c4e5381856f9e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.46, 0.53, 0.0], "state": "The log shipper matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: in production only, while on-call rotation changed. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4f6f3bd7b7c5ab70_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.14, 0.84, 0.02], "state": "The log shipper flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: in production only, following a recent audit. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ff85ab7601af8108_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, at the end of the fiscal period. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_02cdf1d88104f089_n", "kind": "noul", "options": ["false", "true"], "target": [0.45, 0.55], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: across all regions, following a recent audit. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_70dba855f742f405_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.48, 0.3, 0.21, 0.01], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during a scheduled maintenance window. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9aa69dcc2f37800a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.74, 0.24, 0.01], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, following a recent audit. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_657b4dd659333261_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.48, 0.29, 0.22, 0.01], "state": "The metrics pipeline flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: during the batch window, mid-incident. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2b137f3aa877f9ff_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.12, 0.84, 0.04], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: in production only, during an external partner integration. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c8fbd17a379cbad0_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: during the batch window, with a new vendor onboarded. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1a15c6baf15cb8f1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.49, 0.4, 0.01, 0.1], "state": "The log shipper shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: across all regions, during the morning shift. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d627863a23bc4ed5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.37, 0.61, 0.01], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: in production only, during peak load. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3f5db9c342ca4315_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: in production only, shortly after a software update. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_011a3de7240e2672_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.07, 0.43, 0.39, 0.1, 0.01], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, as part of a compliance sweep. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e7173d97184683b8_n", "kind": "noul", "options": ["false", "true"], "target": [0.42, 0.58], "state": "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, during the morning shift. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ceda2a9239c50953_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.0, 0.76, 0.24], "state": "The log shipper correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: in production only, during an external partner integration. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5fce97ef2be15620_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: in production only, while legacy systems are still active. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_04812f79194213ba_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.06, 0.84, 0.1], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: across all regions, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5a28a39ba932ae33_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: across all regions, under reduced staffing. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_546cbcb774596f37_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: over the last hour, during normal operations. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_22109dc3b16c5d1e_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: over the last hour, while legacy systems are still active. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1563756c8a653554_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.26, 0.7, 0.03], "state": "The log shipper matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: over the last hour, during the holiday freeze. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6d99814a6e888011_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.55, 0.45, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: in production only, during peak load. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bbc960615e52174f_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "The log shipper correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ac0593ef408a0576_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.46, 0.44, 0.04, 0.0], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: across all regions, while on-call rotation changed. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_02b09493066ade2d_n", "kind": "noul", "options": ["false", "true"], "target": [0.4, 0.6], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: across all regions, shortly after a software update. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5b5c228d79a2bd9b_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: during the batch window, during normal operations. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d00afa0f3afc1e73_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.86, 0.11, 0.0], "state": "Node pgsql-14 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 operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5d7ce2b7d51b3a4d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.97, 0.0, 0.02, 0.01], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, while legacy systems are still active. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4634ee08a504a0fb_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: across all regions, during the holiday freeze. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_14fbc33d362fb441_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.11, 0.0, 0.72, 0.17], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: over the last hour, during a scheduled maintenance window. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5da7a731d5765fd9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.66, 0.33, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during peak load. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7b975c276134fb03_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.01, 0.29, 0.66], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: across all regions, during the holiday freeze. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b731e1d576c176a3_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "The log shipper shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: during the batch window, during normal operations. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bc84ff902854fa73_n", "kind": "noul", "options": ["false", "true"], "target": [0.47, 0.53], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_545771beb532c6d1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.1, 0.61, 0.27, 0.01], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: in production only, immediately after go-live. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bc956fa83e9fd6d5_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.04, 0.53, 0.4, 0.03], "state": "The log shipper reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: in production only, as part of a compliance sweep. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_987e55620e201bdb_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.49, 0.03, 0.03, 0.45], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, under an active deadline. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3c2c67e4ba2eed32_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.56, 0.28, 0.14, 0.02], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: over the last hour, as part of a compliance sweep. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9792ab8840958b1e_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: during the batch window, during the system migration. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_af08ddb14f69a289_n", "kind": "noul", "options": ["false", "true"], "target": [0.9, 0.1], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, immediately after go-live. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9a4445224650c1fe_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: in production only, at the end of the fiscal period. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9e32191cad420082_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.9, 0.05, 0.04, 0.01], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: during the batch window, under an active deadline. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ffd83784bc1b9b1c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.04, 0.64, 0.31], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: across all regions, with a new vendor onboarded. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_af123adb5b01c0a7_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "Service catalog-sync correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: during the batch window, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d2daeaf32c6f1c4f_n", "kind": "noul", "options": ["false", "true"], "target": [0.37, 0.63], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: in production only, following a recent audit. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c121cb4bd7c416f0_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: across all regions, immediately after go-live. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_313e404e8e6bbfeb_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.67, 0.12, 0.19, 0.02], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during the system migration. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_be2dfe3232ca0925_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.44, 0.54, 0.01], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: in production only, mid-incident. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_29a091039fd3a398_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during peak load. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b160c7b04d538eb5_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "The log shipper shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: over the last hour, during the holiday freeze. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dae5f96b7576b97a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.13, 0.56, 0.3, 0.01, 0.0], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: in production only, during the morning shift. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_efeed6b3e524f2dd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.75, 0.23, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: in production only, during the quarterly review. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cd27e84a6dec0bde_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.3, 0.68, 0.02], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, following a recent audit. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_493188b3cdd6eb3f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.26, 0.73, 0.01], "state": "The metrics pipeline flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: across all regions, with staffing at reduced levels. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4793d6c74c3499f4_n", "kind": "noul", "options": ["false", "true"], "target": [0.47, 0.53], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during the morning shift. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6ef967fe36a54c57_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.36, 0.58, 0.04, 0.02], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: during the batch window, with a new vendor onboarded. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a0eb51a20dfc3ba7_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.58, 0.4], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: over the last hour, during the quarterly review. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_baee2cba13535c6f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.6, 0.27, 0.11, 0.02], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, while on-call rotation changed. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_496c99ee79da5311_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.02, 0.23, 0.34, 0.36, 0.04, 0.01], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: during the batch window, immediately after go-live. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3f1331550dd99f51_n", "kind": "noul", "options": ["false", "true"], "target": [0.9, 0.1], "state": "The log shipper returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the system migration. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9e15201c112f413a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.1616, 0.8182, 0.0202], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eea110eb87dd5a7f_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: in production only, during an external partner integration. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4158b18bfcd543f4_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.05, 0.34, 0.59, 0.02], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: across all regions, during normal operations. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_31fc0aa79f95762a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.07, 0.83, 0.1], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: across all regions, during peak load. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0a15b7e22dde6c69_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.68, 0.25, 0.07, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: over the last hour, with staffing at reduced levels. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1c1d90041d10626c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.98, 0.02, 0.0, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: in production only, under an active deadline. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7415478494cc2803_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: in production only, mid-incident. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1435a99ea7828863_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.39, 0.07, 0.02, 0.52], "state": "The log shipper returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: over the last hour, with staffing at reduced levels. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0d691a6b849ceb78_n", "kind": "noul", "options": ["false", "true"], "target": [0.9, 0.1], "state": "The log shipper lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during the morning shift. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_21e6a43cded08e7e_n", "kind": "noul", "options": ["false", "true"], "target": [0.44, 0.56], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: in production only, during an external partner integration. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8ad646342a5d2f25_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.84, 0.15, 0.01, 0.0], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: over the last hour, during peak load. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b99b08e0bcf7c89f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.72, 0.23, 0.02, 0.03], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: over the last hour, shortly after a software update. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_730e3426a2252ae4_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: during the batch window, as part of a compliance sweep. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3dcfc9c612e22cea_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.01, 0.03, 0.46, 0.47, 0.02], "state": "The log shipper correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: across all regions, during normal operations. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d47e0c7a0ad5ce67_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.12, 0.31, 0.51, 0.05, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: across all regions, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d4df17ac883772e5_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: over the last hour, during peak load. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8df7816c5c79884c_n", "kind": "noul", "options": ["false", "true"], "target": [0.67, 0.33], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: over the last hour, shortly after a software update. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_657b4dd659333261_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "The metrics pipeline flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: during the batch window, mid-incident. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0d568a1e2db91f59_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.01, 0.01, 0.95], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: in production only, mid-incident. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_10483eb5269bbe86_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.29, 0.68, 0.02], "state": "The log shipper shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: over the last hour, under an active deadline. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c480c95278615ad0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.6, 0.39, 0.0], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: over the last hour, mid-incident. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4c364664222fa489_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: across all regions, with a new vendor onboarded. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6983ecc844d545ea_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.51, 0.36, 0.08, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: in production only, immediately after go-live. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_01c856536e7ab858_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "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.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_06cdae4e93e4966a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.99, 0.0, 0.0, 0.01], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, while on-call rotation changed. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e06a3ff86270f6af_n", "kind": "noul", "options": ["false", "true"], "target": [0.49, 0.51], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: over the last hour, with a new vendor onboarded. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_39aeb46f116e7d32_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.01, 0.15, 0.82], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during the quarterly review. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7e8f6be2bf0bdf97_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.12, 0.69, 0.18, 0.01, 0.0], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: across all regions, as part of a compliance sweep. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_adb7bff20102cc07_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.29, 0.58, 0.02, 0.11], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, following a recent audit. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dcf345bc0fc88370_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.17, 0.55, 0.27, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, shortly after a software update. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f5557f278413d3bb_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: across all regions, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_110eef25c8924319_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.82, 0.15, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: over the last hour, during the morning shift. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_48ed8e6a3c640e11_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.41, 0.53, 0.05, 0.01], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during an external partner integration. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b66270a8773a47b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.54, 0.43, 0.03, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: over the last hour, during the morning shift. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1cf9f0d3cfca3e8a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.16, 0.81, 0.03], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during the quarterly review. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_67ccf4b8a02c6960_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.16, 0.29, 0.03, 0.52], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: in production only, during the quarterly review. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0d53771924d6971a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.36, 0.46, 0.09, 0.09], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, following a recent audit. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_167bc7e35521c5df_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: over the last hour, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_388a4f2353f5407c_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the system migration. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9ce93d49d2f29bc8_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.27, 0.0, 0.37, 0.36], "state": "The metrics pipeline lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: in production only, during peak load. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c432f5788f6952ab_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.25, 0.74, 0.01], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: across all regions, with staffing at reduced levels. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bcec6f69a8081c83_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.47, 0.14, 0.02, 0.37], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: across all regions, during the holiday freeze. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_011a3de7240e2672_n", "kind": "noul", "options": ["false", "true"], "target": [0.64, 0.36], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, as part of a compliance sweep. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_38d1bb546dca96c7_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.64, 0.35, 0.01, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: in production only, at the end of the fiscal period. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_74694fd8b8f973ce_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, under reduced staffing. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f5557f278413d3bb_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.73, 0.24, 0.03, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: across all regions, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_953db24316107fda_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Node pgsql-14 flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: across all regions, as part of a compliance sweep. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d7970b88840122a1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.62, 0.27, 0.11, 0.0], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b050c0116fc42956_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.25, 0.75, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: in production only, under reduced staffing. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f388432d9def5579_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.54, 0.43, 0.03, 0.0], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: across all regions, as part of a compliance sweep. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_07f97b8fb0268895_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.02, 0.49, 0.48, 0.01], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: in production only, following a recent audit. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_88e535ac3e1db8b4_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.3, 0.04, 0.02, 0.64], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: in production only, during the morning shift. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f00cab47410d53e3_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.22, 0.63, 0.13, 0.02], "state": "The log shipper correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: during the batch window, during the quarterly review. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1ab979a6a834fbe1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.7, 0.29, 0.01, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1b126806088abe2b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.61, 0.35, 0.03, 0.01], "state": "The log shipper lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: over the last hour, under an active deadline. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9793ccba1a389059_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.2, 0.79, 0.01], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, while on-call rotation changed. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b1756f75650effe_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.45, 0.38, 0.16, 0.01], "state": "The metrics pipeline correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: in production only, mid-incident. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_59022f50a2c43bb5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.09, 0.58, 0.31, 0.01], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: during the batch window, during an external partner integration. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9aa9fc0a73ad009f_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: across all regions, during the morning shift. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cc180ce1eff32f15_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.91, 0.06, 0.03, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: over the last hour, mid-incident. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9f76bbbc933d1976_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "The log shipper matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: over the last hour, shortly after a software update. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_98204fad5a3a3e7a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.03, 0.33, 0.63], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: over the last hour, as part of a compliance sweep. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_53e99d6b0d57041f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.07, 0.24, 0.67], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: in production only, following a recent audit. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_451153f4c5128750_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.94, 0.03, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: over the last hour, during the system migration. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1b92df4264a99dcf_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.77, 0.19, 0.02, 0.02], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, as part of a compliance sweep. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0abe31ed0208d777_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.61, 0.35, 0.01], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: across all regions, during normal operations. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8e09fff3bee7c0d0_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: in production only, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a1ebc50d954ea3b0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.11, 0.8, 0.08, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: across all regions, during the holiday freeze. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_508c80b4f8c4e90e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.08, 0.88, 0.04], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, immediately after go-live. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dcba489931d6439d_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: in production only, while on-call rotation changed. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_276fc9aeb1983cc1_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, shortly after a software update. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ae8204ec1186e041_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.1, 0.76, 0.13, 0.0], "state": "The log shipper matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: over the last hour, during the morning shift. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_14fda788ea4a1301_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.1, 0.82, 0.08], "state": "The log shipper correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, immediately after go-live. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c94222e015712dde_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.79, 0.21, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: during the batch window, during normal operations. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_94e09ad0b5782a30_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "The metrics pipeline flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: in production only, while on-call rotation changed. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a5922e94d551074a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.21, 0.77, 0.02], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: over the last hour, with staffing at reduced levels. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4bf12119a54b3ced_n", "kind": "noul", "options": ["false", "true"], "target": [0.55, 0.45], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: in production only, during peak load. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_46fc6b5934e4b648_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.01, 0.69, 0.28], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: across all regions, during the quarterly review. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_459f77caccb20912_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.06, 0.01, 0.92], "state": "The log shipper matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: across all regions, following a recent audit. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_183f3f116dbd9a55_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: over the last hour, following a recent audit. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bac91635a97f1d1b_n", "kind": "noul", "options": ["false", "true"], "target": [0.68, 0.32], "state": "The log shipper shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: across all regions, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ff9cb7cda865e323_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during normal operations. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fe6798482bfc6dea_n", "kind": "noul", "options": ["false", "true"], "target": [0.41, 0.59], "state": "Node pgsql-14 flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: during the batch window, at the end of the fiscal period. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ab601c1ac485840d_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the holiday freeze. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3c01467228a86e07_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.13, 0.81, 0.05, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: over the last hour, while on-call rotation changed. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9e52cd550cc9d742_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.13, 0.27, 0.6, 0.0], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, while on-call rotation changed. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8d9e6df9300bb760_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.12, 0.84, 0.04], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: during the batch window, mid-incident. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_841c3cd4ebb9bdc0_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.87, 0.12, 0.01, 0.0], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: over the last hour, during the morning shift. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c8362ddb444df4ab_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.58, 0.39, 0.02, 0.01], "state": "The log shipper lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, with staffing at reduced levels. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_069762646f419472_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.28, 0.67, 0.03, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: over the last hour, during the morning shift. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e774b490445dda10_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.11, 0.79, 0.09, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: over the last hour, at the end of the fiscal period. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_38cf6a8fdc7d74e2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.52, 0.47, 0.0], "state": "Service catalog-sync flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: during the batch window, while on-call rotation changed. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9158e154d727eeb3_n", "kind": "noul", "options": ["false", "true"], "target": [0.7, 0.3], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: in production only, during normal operations. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5b31e2e9fd7f2b0a_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: across all regions, while on-call rotation changed. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6d53fb7e00291530_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.68, 0.29, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: in production only, shortly after a software update. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9e01b76ac1d2fe41_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.33, 0.63, 0.03, 0.01], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b82820cab21b5aee_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.12, 0.79, 0.08, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: across all regions, during the system migration. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_37c3f5ed1c53d327_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.01, 0.03, 0.34, 0.6, 0.01], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: in production only, during peak load. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c1cfa35019e12fc2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.0, 0.32, 0.63], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: during the batch window, during the system migration. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b050c0116fc42956_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: in production only, under reduced staffing. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_114c7cbce3b76295_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.1414, 0.6768, 0.1717, 0.0101, 0.0], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: in production only, during the system migration. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f43efce8babe58d6_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.51, 0.38, 0.11, 0.0], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the morning shift. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d2656f5195e9fed9_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The metrics pipeline shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: in production only, while on-call rotation changed. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_08ef56c0f80ef673_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.79, 0.17, 0.03, 0.01], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: during the batch window, under reduced staffing. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_66e5292b9f0c123a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.04, 0.9, 0.06, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: across all regions, with a new vendor onboarded. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0877fa1143bac6b6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.02, 0.85, 0.13], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, under an active deadline. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aa36a2ba162ebc44_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: in production only, mid-incident. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_529b143127e6bfc9_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.0101, 0.2828, 0.6869, 0.0202], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: during the batch window, following a recent audit. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c0994cd7f6b4611a_n", "kind": "noul", "options": ["false", "true"], "target": [0.67, 0.33], "state": "The log shipper correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: in production only, with staffing at reduced levels. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e5746e898c88847b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.55, 0.41, 0.03, 0.01], "state": "The log shipper shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: in production only, during an external partner integration. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e709f3d55bcce818_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.06, 0.23, 0.68], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: over the last hour, as part of a compliance sweep. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_36723f448ba45f01_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.04, 0.77, 0.19], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: across all regions, during the holiday freeze. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f34761ceb82b0ab0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.67, 0.32, 0.0], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: over the last hour, during normal operations. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_363847a3be0817a3_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.99, 0.0, 0.01], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: across all regions, shortly after a software update. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ac514e4d4f94e3b8_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.53, 0.36, 0.09, 0.02], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: over the last hour, during the holiday freeze. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_85f079c40373b807_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.32, 0.51, 0.17, 0.0, 0.0], "state": "The log shipper reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: during the batch window, during a scheduled maintenance window. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f196ae510768623a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.34, 0.63, 0.02, 0.01], "state": "The metrics pipeline shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: in production only, following a recent audit. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_44ad51df16072829_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.68, 0.3, 0.01], "state": "The log shipper returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: in production only, following a recent audit. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6c1f7a7112b072ba_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.33, 0.57, 0.05, 0.0], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: during the batch window, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b5c37c44cf8ce1ca_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.36, 0.55, 0.07, 0.02], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_26667c85f5dd2d6a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.06, 0.86, 0.07, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: during the batch window, under reduced staffing. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1eeb38bf0f8ec343_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during normal operations. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ba820cbbd74bbbe2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.02, 0.07, 0.89], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: in production only, following a recent audit. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_55ccd2f7e1b06f79_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.17, 0.17, 0.49, 0.15, 0.01], "state": "Service catalog-sync correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: across all regions, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ce62293b097c6114_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.06, 0.88, 0.05], "state": "Service catalog-sync flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: over the last hour, during normal operations. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_de90092fcc6136a3_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.84, 0.14, 0.01, 0.01], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: in production only, during peak load. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e7cd76bf37d59c5b_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: across all regions, as part of a compliance sweep. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c6a353e612fb4672_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.61, 0.37, 0.0], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: across all regions, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e759242ee5a4c92f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.0, 0.31, 0.68], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: during the batch window, during the morning shift. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_53a869627becc0c8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.35, 0.64, 0.01], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, with a new vendor onboarded. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3c6fa5b454b1960f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.72, 0.22, 0.01, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the quarterly review. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d95a23a39934bd33_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.04, 0.74, 0.2, 0.02], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: during the batch window, during the quarterly review. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e670cd89105aaf80_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.68, 0.28, 0.02, 0.02], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: during the batch window, during the morning shift. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_771c6f611e5fbb5c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.98, 0.02, 0.0, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during peak load. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5f581f00af3017d1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.6, 0.39, 0.0], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: over the last hour, shortly after a software update. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8fe04c1c6d6ea837_n", "kind": "noul", "options": ["false", "true"], "target": [0.66, 0.34], "state": "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.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_156ce471cf9938c3_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.97, 0.02, 0.01, 0.0], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, mid-incident. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_075ac3175d7d18bb_n", "kind": "noul", "options": ["false", "true"], "target": [0.5, 0.5], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, as part of a compliance sweep. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0076d0b941179d9f_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: over the last hour, during the system migration. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_20bc6be64bf68f40_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.33, 0.63, 0.02, 0.02], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: during the batch window, with a new vendor onboarded. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ffd85985fcba6aaa_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.19, 0.2, 0.53, 0.08], "state": "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 automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aae910bf328fd59b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.1, 0.6, 0.26, 0.04, 0.0, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, with a new vendor onboarded. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bca812d5e98769c8_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.78, 0.0, 0.21, 0.01], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: across all regions, while on-call rotation changed. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_96a63b219bc5c215_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.53, 0.46, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: in production only, while on-call rotation changed. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_95a5403ad65b1be9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.05, 0.83, 0.12, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: over the last hour, as part of a compliance sweep. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d9d62848c6ae87f0_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.14, 0.28, 0.48, 0.1], "state": "The log shipper shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: in production only, during an external partner integration. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_386aac66aa5e21d7_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: over the last hour, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_58b5b4c43a7b39e9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.05, 0.4, 0.54], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: across all regions, with a new vendor onboarded. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_924f19e9c3bb8928_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during peak load. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_988b1a8138cf2d11_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: across all regions, while on-call rotation changed. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_89f30119524ce2dd_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: in production only, shortly after a software update. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_db996a89acaa3261_n", "kind": "noul", "options": ["false", "true"], "target": [0.42, 0.58], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: in production only, during peak load. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7a0356cd898b698d_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "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, with staffing at reduced levels. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2b5e426e13e4097f_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during peak load. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d342bd2d1e301a7a_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: across all regions, mid-incident. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0cd87bd885fc91fe_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.18, 0.56, 0.19, 0.01], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: in production only, at the end of the fiscal period. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1985208fb93b453d_n", "kind": "noul", "options": ["false", "true"], "target": [0.37, 0.63], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: during the batch window, during a scheduled maintenance window. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a107add0ac8184a2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.38, 0.01, 0.59], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: in production only, immediately after go-live. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_40954c272b630d12_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "Service catalog-sync shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: over the last hour, under an active deadline. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_91c596a7efc2f706_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.81, 0.16, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: over the last hour, while on-call rotation changed. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9fce8279a8f3a908_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.27, 0.72, 0.01], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during peak load. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a35ae03469d0f602_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.94, 0.06, 0.0, 0.0], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: during the batch window, while on-call rotation changed. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1ebba6cfc3480f5c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.86, 0.13, 0.01, 0.0], "state": "Service catalog-sync flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: over the last hour, during the quarterly review. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_124c471e8040ac78_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.71, 0.26, 0.0], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: across all regions, during the system migration. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d0937a022615166d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.97, 0.02, 0.0, 0.01], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, under an active deadline. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a21ed9efc4287d98_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.63, 0.3, 0.07, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: in production only, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fbf1d14b9ba40690_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: over the last hour, shortly after a software update. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4fa9c64ff2b94b10_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.14, 0.06, 0.7, 0.1], "state": "The log shipper shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: over the last hour, during an external partner integration. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b88a8c95ac44dff3_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The log shipper matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, mid-incident. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0df354a23be51f0f_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "The log shipper returned to baseline after 11 minutes; additionally matches last Tuesday's incident signature. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7e3e859e419da64f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.1, 0.02, 0.02, 0.86], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the holiday freeze. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c41083d6a30290a7_n", "kind": "noul", "options": ["false", "true"], "target": [0.66, 0.34], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: over the last hour, while legacy systems are still active. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a3275bad830c6245_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.68, 0.21, 0.05, 0.06], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_559a73ced4aba2d2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.84, 0.15, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: over the last hour, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2e01d35226147b45_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.17, 0.32, 0.47, 0.04], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: in production only, while on-call rotation changed. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c565dc0ad178473f_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: across all regions, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_01cb87f57400e18e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.25, 0.02, 0.28, 0.45], "state": "The log shipper shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: over the last hour, while legacy systems are still active. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_477dac9879b5628b_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: during the batch window, while legacy systems are still active. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ee3659e8cc8f7f0_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.94, 0.06, 0.0, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: during the batch window, under an active deadline. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4dcef18f0c1f2438_n", "kind": "noul", "options": ["false", "true"], "target": [0.45, 0.55], "state": "Service catalog-sync shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: during the batch window, while legacy systems are still active. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b84f6638c72bec27_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.21, 0.0, 0.09, 0.7], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_39855681ce11bfcc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.09, 0.55, 0.34, 0.01], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: over the last hour, mid-incident. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c31f7ce2fa687714_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "The log shipper returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: across all regions, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a257fcfa0baa6053_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.11, 0.8, 0.08, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: over the last hour, shortly after a software update. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0e033fed180f3a11_n", "kind": "noul", "options": ["false", "true"], "target": [0.44, 0.56], "state": "Service catalog-sync flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: in production only, during a scheduled maintenance window. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0341c9777930bf4e_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during the holiday freeze. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_23d0d911e1afcbc5_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.88, 0.1, 0.02, 0.0], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: during the batch window, under an active deadline. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4b901bd4111c39a6_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.71, 0.09, 0.04, 0.16], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: during the batch window, at the end of the fiscal period. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b0a7ab85acf14d98_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.21, 0.61, 0.18, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, while on-call rotation changed. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2688bef52a52abd1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.22, 0.03, 0.01, 0.74], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: across all regions, at the end of the fiscal period. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8e09fff3bee7c0d0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.02, 0.35, 0.6, 0.02], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: in production only, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1324bf37b00890e0_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.03, 0.31, 0.63, 0.03], "state": "The log shipper reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: across all regions, during the morning shift. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cd9d72a8e6de77a6_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: across all regions, while on-call rotation changed. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_23d70d31b8ac949a_n", "kind": "noul", "options": ["false", "true"], "target": [0.23, 0.77], "state": "The log shipper correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: across all regions, shortly after a software update. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a6e103bb450f7d5d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.09, 0.32, 0.52, 0.07], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: across all regions, under reduced staffing. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ea20420b7e883739_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.97, 0.01, 0.0, 0.02], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: over the last hour, during a scheduled maintenance window. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_964ba3537197a273_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.44, 0.56, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, with a new vendor onboarded. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6a63d3469ffb55aa_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.1, 0.62, 0.26, 0.02, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: in production only, during a scheduled maintenance window. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6bc42debdc385da9_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "The log shipper reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: across all regions, as part of a compliance sweep. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6d75fe6a611dab9b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.94, 0.04, 0.01, 0.01], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, shortly after a software update. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f3cf1d526c85b8b0_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.52, 0.33, 0.14, 0.01], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: during the batch window, during the morning shift. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e5eaefe4a478309a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.3, 0.02, 0.03, 0.65], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5cdb1fae2f20fdb9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.27, 0.71, 0.02], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, at the end of the fiscal period. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c4d9aeb8a7b0b45a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.0, 0.45, 0.54], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: during the batch window, during an external partner integration. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ae40cf170ae906d3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.06, 0.74, 0.19, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: over the last hour, while legacy systems are still active. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b827af4f5d711d9d_n", "kind": "noul", "options": ["false", "true"], "target": [0.38, 0.62], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: across all regions, during an external partner integration. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3d98b92468216098_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, immediately after go-live. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8365c8575c91c116_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.19, 0.31, 0.46, 0.04, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, as part of a compliance sweep. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_14ff907d4eb2c923_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.41, 0.44, 0.13, 0.02], "state": "The log shipper shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: during the batch window, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_020fde0acf241c91_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally flags a step-function change in error slope. Context: in production only, following a recent audit. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f34747d1bc1a436f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.2, 0.52, 0.27, 0.01, 0.0], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: during the batch window, during an external partner integration. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_216093cc0efc502f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.11, 0.87], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: in production only, following a recent audit. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_43825edcc4ba19cf_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.53, 0.46, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: during the batch window, under reduced staffing. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a54a770ab43ec38f_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9d40d10f61934fd6_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: over the last hour, with a new vendor onboarded. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a74a5846c0d519b2_n", "kind": "noul", "options": ["false", "true"], "target": [0.39, 0.61], "state": "The metrics pipeline flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: during the batch window, during the quarterly review. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_78b4ef98d6b25c50_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.26, 0.7, 0.01, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: over the last hour, during the system migration. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_349eb495867da9be_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.1, 0.08, 0.05, 0.77], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, following a recent audit. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3022b2cba57e00f9_n", "kind": "noul", "options": ["false", "true"], "target": [0.66, 0.34], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the system migration. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_56282e68afd98729_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.78, 0.21, 0.0], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: across all regions, during an external partner integration. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4e4a57a4719829bc_n", "kind": "noul", "options": ["false", "true"], "target": [0.45, 0.55], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: across all regions, during normal operations. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b9a8ffee826f927e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.11, 0.05, 0.41, 0.43], "state": "The log shipper reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: across all regions, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0114da06b3ea90fe_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.46, 0.52, 0.01], "state": "Service catalog-sync correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: across all regions, while legacy systems are still active. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7b975c276134fb03_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: across all regions, during the holiday freeze. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_51e5daf9cf251ae9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.0, 0.12, 0.87], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: in production only, following a recent audit. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_03eb9e078a1f10e1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.44, 0.53, 0.02, 0.01], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during an external partner integration. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9ca3bf859c7c0827_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: during the batch window, at the end of the fiscal period. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5bb92bd1f8c51b1b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.71, 0.27, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: across all regions, at the end of the fiscal period. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b3c0becc4341b614_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.5, 0.49, 0.0], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: during the batch window, during peak load. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b1fcc16f8deb2040_n", "kind": "noul", "options": ["false", "true"], "target": [0.45, 0.55], "state": "The log shipper reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: during the batch window, as part of a compliance sweep. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c9c4fbd10e3a6440_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.06, 0.84, 0.1, 0.0], "state": "The metrics pipeline 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 review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_04c24b382d8c57df_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.19, 0.63, 0.15, 0.0], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: across all regions, under reduced staffing. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3d6f6dad2e926cb4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.17, 0.79, 0.03], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: across all regions, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3053364cf37a1a7b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.48, 0.39, 0.09], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: during the batch window, immediately after go-live. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d1f023c009d65819_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.81, 0.18, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: during the batch window, at the end of the fiscal period. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_094b5bacc52a549b_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The log shipper lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: in production only, with a new vendor onboarded. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6df58db4216cd635_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: over the last hour, during the morning shift. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_74e48815b9763eb5_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The log shipper matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: over the last hour, at the end of the fiscal period. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ada669e16345170d_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: in production only, during the holiday freeze. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f42d2e2f3c2fad01_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.32, 0.46, 0.19, 0.03], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the system migration. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_431a66b17ed96ca5_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.88, 0.1, 0.01, 0.01], "state": "The log shipper reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: during the batch window, during the system migration. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_88a74779fae07bf6_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.79, 0.2, 0.01, 0.0], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: during the batch window, following a recent audit. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e50961d63803a05f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.82, 0.16, 0.01, 0.01], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: during the batch window, mid-incident. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eea110eb87dd5a7f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.0, 0.01, 0.28, 0.68, 0.02], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: in production only, during an external partner integration. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ed53c2762bec0dcd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.45, 0.54, 0.0], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: during the batch window, with a new vendor onboarded. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_90f1bbe49bb23f91_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.15, 0.02, 0.15, 0.68], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: in production only, during the system migration. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4586cd9210939cd7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.42, 0.48, 0.08, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: across all regions, immediately after go-live. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7c430d6eb255ba1d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.31, 0.66, 0.02], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: in production only, at the end of the fiscal period. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_beb05f659f3c2cd6_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.14, 0.01, 0.06, 0.79], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: across all regions, following a recent audit. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dc2f0c6dddb325ca_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.72, 0.27, 0.01, 0.0], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: in production only, during normal operations. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4fb099f8520ab2dd_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.38, 0.09, 0.02, 0.51], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: over the last hour, at the end of the fiscal period. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_726b819525d6cb0c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.07, 0.11, 0.1, 0.72], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: during the batch window, during a scheduled maintenance window. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_116e048371e09d7f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.7, 0.28, 0.01, 0.01], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: over the last hour, following a recent audit. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9d07c7c3ca39f49a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.69, 0.24, 0.06, 0.01], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, shortly after a software update. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b0b1324bb5485df7_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.31, 0.23, 0.29, 0.17], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: across all regions, during a scheduled maintenance window. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5e9d952bf9dc08d7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.23, 0.34, 0.43, 0.0, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: in production only, during a scheduled maintenance window. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_01cb87f57400e18e_n", "kind": "noul", "options": ["false", "true"], "target": [0.61, 0.39], "state": "The log shipper shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: over the last hour, while legacy systems are still active. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9cf9e625a0af11a4_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.62, 0.1, 0.01, 0.27], "state": "The log shipper shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: during the batch window, during the morning shift. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2fd1e883c11fb411_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.91, 0.06, 0.0, 0.03], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: over the last hour, during the quarterly review. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_68870693804515e6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.37, 0.61, 0.01], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during the holiday freeze. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5f90afac4d38f712_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.38, 0.6, 0.01], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: over the last hour, at the end of the fiscal period. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_53d83ba39ce2df30_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.63, 0.34, 0.01, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, shortly after a software update. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a63716f851840e37_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.08, 0.85, 0.05, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: in production only, at the end of the fiscal period. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aab0393fe585104a_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, under reduced staffing. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b23250c791b5e544_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.58, 0.41, 0.0], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: in production only, during the morning shift. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5129834c2be66d95_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.01, 0.97, 0.02], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: across all regions, with a new vendor onboarded. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7cc38c6039be78ed_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.44, 0.53, 0.01], "state": "The log shipper reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: in production only, during the holiday freeze. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9d4df05514fd9267_n", "kind": "noul", "options": ["false", "true"], "target": [0.2, 0.8], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2e56f45b3ba05ac5_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "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.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_94bc196e655a8a64_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during normal operations. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e010bce7a3a7b68a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.25, 0.02, 0.03, 0.7], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the holiday freeze. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1eec0c816a283727_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.05, 0.75, 0.2, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: in production only, as part of a compliance sweep. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aa847cc6c3735195_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the morning shift. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cd4dbd8bb1645b31_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.48, 0.37, 0.14, 0.01], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: in production only, during the system migration. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_90e3a7e12df5e349_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.66, 0.28, 0.01, 0.05], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: across all regions, shortly after a software update. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_af7fa10f09678d47_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.47, 0.52, 0.0], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: during the batch window, shortly after a software update. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_46fc6b5934e4b648_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.04, 0.59, 0.37, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: across all regions, during the quarterly review. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7fcbabbdf44a2632_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.2, 0.76, 0.03], "state": "The log shipper reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: during the batch window, while legacy systems are still active. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d00afddde3c90466_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.1, 0.4, 0.45, 0.05, 0.0], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: in production only, immediately after go-live. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0bb7bd9d8a3b5adb_n", "kind": "noul", "options": ["false", "true"], "target": [0.61, 0.39], "state": "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.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7d6816a68c2b92c1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.53, 0.45], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: across all regions, with a new vendor onboarded. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f93301907c97a5a7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.05, 0.85, 0.1], "state": "The metrics pipeline flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: across all regions, under an active deadline. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f05f8adfb98c8353_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.01, 0.4, 0.59], "state": "Service catalog-sync lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: across all regions, following a recent audit. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca00c583e378ef59_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "The log shipper correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during peak load. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bd0eba2064548ae1_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: in production only, under reduced staffing. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_268d94dd53f57fe3_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: across all regions, following a recent audit. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5b31e2e9fd7f2b0a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.65, 0.33, 0.0], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: across all regions, while on-call rotation changed. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9e52cd550cc9d742_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, while on-call rotation changed. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f7d57590bd644635_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.12, 0.8, 0.08], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: across all regions, under an active deadline. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_944bcee49c70c2c0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.37, 0.52, 0.11, 0.0, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: over the last hour, during a scheduled maintenance window. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cf8ba037ff802f40_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.87, 0.12, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: during the batch window, as part of a compliance sweep. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5ea705954bb70a25_n", "kind": "noul", "options": ["false", "true"], "target": [0.44, 0.56], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: across all regions, during the quarterly review. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_451153f4c5128750_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.11, 0.11, 0.07, 0.71], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: over the last hour, during the system migration. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ff502dd9e03f8734_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.25, 0.55, 0.19, 0.01], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: over the last hour, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e0ae7820f9a081bf_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during a scheduled maintenance window. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bbd0487aab7f6f49_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.41, 0.49, 0.09, 0.01], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: during the batch window, during the system migration. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_35fe5832ff65d88c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.85, 0.05, 0.0, 0.1], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, with staffing at reduced levels. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f0472f6f927b23db_n", "kind": "noul", "options": ["false", "true"], "target": [0.67, 0.33], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: in production only, during the quarterly review. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca298c74eb4f719a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.27, 0.7, 0.02], "state": "The log shipper reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: over the last hour, during the morning shift. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6662573648e8c782_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.19, 0.61, 0.19, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, with a new vendor onboarded. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ff7506f888122260_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.21, 0.04, 0.12, 0.63], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, while legacy systems are still active. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_84d0db155fd6c697_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.38, 0.58, 0.04, 0.0], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: during the batch window, while on-call rotation changed. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a0b95efe4d304143_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.06, 0.73, 0.16, 0.05, 0.0, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: over the last hour, under an active deadline. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_12b0430d73fc4b7e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.09, 0.86, 0.05], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during peak load. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6de561fa5caf14c8_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.21, 0.55, 0.21, 0.03], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: over the last hour, while on-call rotation changed. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9bf047c720af6fa7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.22, 0.76, 0.02], "state": "The log shipper flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, mid-incident. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f83298ba3113b514_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.49, 0.51, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: in production only, at the end of the fiscal period. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4d43d3bf973f0738_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "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, immediately after go-live. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_800d6f67edc05fbe_n", "kind": "noul", "options": ["false", "true"], "target": [0.2, 0.8], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: during the batch window, under an active deadline. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b9fa97166bf14d04_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.86, 0.13, 0.01, 0.0], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: in production only, with staffing at reduced levels. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_abdfc795f51f9d49_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.78, 0.19, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: over the last hour, while on-call rotation changed. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4db345bd6aa8e39b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.93, 0.05, 0.0, 0.02], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during the system migration. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d4fa236ca777280f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.21, 0.75, 0.01, 0.03], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: over the last hour, at the end of the fiscal period. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_48881da220e866d7_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.22, 0.05, 0.05, 0.68], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during the quarterly review. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_56b98ac626c74c7e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.21, 0.26, 0.03, 0.5], "state": "The log shipper shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: across all regions, immediately after go-live. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_23251dca2b44da43_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.07, 0.03, 0.89], "state": "The log shipper matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: in production only, as part of a compliance sweep. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ed19a5f53c241b52_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: during the batch window, mid-incident. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_68b798b2fcbb5d51_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, immediately after go-live. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dd41e431a4723440_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the system migration. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_099423b4fe8cd332_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: across all regions, following a recent audit. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_198189809cde8bd4_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: across all regions, during the quarterly review. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6556a6387cda0578_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.67, 0.31, 0.01, 0.01], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: in production only, during peak load. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ce12491dd3593248_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.23, 0.72, 0.02, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: over the last hour, while on-call rotation changed. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e76253d035ee181b_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: in production only, shortly after a software update. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_615204ccced27a63_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.66, 0.33, 0.0], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: over the last hour, while on-call rotation changed. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_547253d9595610e7_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: across all regions, shortly after a software update. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9a0fa95d9c4c64d5_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "The log shipper lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: in production only, under an active deadline. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a581eb07fe826a0a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.13, 0.57, 0.3, 0.0, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: across all regions, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_25b6653b60b2bc3f_n", "kind": "noul", "options": ["false", "true"], "target": [0.57, 0.43], "state": "The log shipper lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: in production only, during the quarterly review. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_783d2c3cfc0142b6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.32, 0.67, 0.01], "state": "The metrics pipeline shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during peak load. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eef5fb97e67f8ba4_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.43, 0.02, 0.02, 0.53], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, at the end of the fiscal period. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4dd7a46f2bf092d4_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.25, 0.6, 0.13, 0.02], "state": "The log shipper returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: across all regions, during peak load. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b8457396d6c277df_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.44, 0.05, 0.49], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: in production only, shortly after a software update. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca65bf31326b313d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.69, 0.31, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: over the last hour, while legacy systems are still active. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_48bc46359d18ce30_n", "kind": "noul", "options": ["false", "true"], "target": [0.21, 0.79], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during the morning shift. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dcfa721e339ad37e_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: during the batch window, during the quarterly review. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_574e439a4ef2018c_n", "kind": "noul", "options": ["false", "true"], "target": [0.39, 0.61], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: across all regions, during the system migration. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c85324fa69061251_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: across all regions, while on-call rotation changed. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_47e144991d782291_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, while legacy systems are still active. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0c33d13b463a7892_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.05, 0.51, 0.42, 0.01], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: over the last hour, as part of a compliance sweep. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_88b87e1f46325cfc_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.13, 0.08, 0.43, 0.36], "state": "Service catalog-sync shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: over the last hour, with a new vendor onboarded. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_36e4399890860f43_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.26, 0.45, 0.02, 0.27], "state": "The log shipper matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: in production only, at the end of the fiscal period. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3d86c711b5b863b9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.57, 0.42, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, shortly after a software update. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b823c5d2c4c506a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.1, 0.84, 0.06], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: in production only, immediately after go-live. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_360d267f752d655d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.57, 0.42, 0.01, 0.0], "state": "The log shipper matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: in production only, while on-call rotation changed. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_947c78c18a199170_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "The metrics pipeline lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: across all regions, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1a55c7879e72cfc6_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.7, 0.22, 0.06, 0.02], "state": "The log shipper correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: in production only, mid-incident. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5b12bab349135e1a_n", "kind": "noul", "options": ["false", "true"], "target": [0.37, 0.63], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: across all regions, as part of a compliance sweep. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_231bc63070bccc8b_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: in production only, shortly after a software update. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7961c1ea1ee2e8e8_n", "kind": "noul", "options": ["false", "true"], "target": [0.5, 0.5], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the morning shift. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d121442ff2aac3fc_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.02, 0.92, 0.06], "state": "Service catalog-sync correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: across all regions, during the system migration. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b7592a9bb394666a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.07, 0.33, 0.5, 0.1, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: in production only, as part of a compliance sweep. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cfcd325c837c3536_n", "kind": "noul", "options": ["false", "true"], "target": [0.37, 0.63], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: during the batch window, under an active deadline. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_74f8f8d935a47cd0_n", "kind": "noul", "options": ["false", "true"], "target": [0.39, 0.61], "state": "The metrics pipeline flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: across all regions, during normal operations. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_47b239ad9fae9195_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.78, 0.2, 0.01, 0.01], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, following a recent audit. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b33828d12e995afa_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.42, 0.58, 0.0], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: in production only, immediately after go-live. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e1b0750dd323948a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.34, 0.65, 0.01], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: during the batch window, while legacy systems are still active. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ec2d33037ec03cdf_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.89, 0.11, 0.0, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, immediately after go-live. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1209640699cdf9a3_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.68, 0.06, 0.01, 0.25], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during peak load. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_156ce471cf9938c3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.13, 0.8, 0.07], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, mid-incident. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_575e5ca6751b20b8_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: in production only, during the morning shift. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_008849a1db9ef8be_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.1, 0.86, 0.04], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: in production only, with a new vendor onboarded. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4bab92aa72110e07_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: in production only, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_83417674c61ac02e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.12, 0.85, 0.03], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, following a recent audit. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5c5597af9d332f68_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: during the batch window, during the holiday freeze. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_afcdc2d42956e929_n", "kind": "noul", "options": ["false", "true"], "target": [0.92, 0.08], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, with staffing at reduced levels. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b14add06f66814ff_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: over the last hour, at the end of the fiscal period. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b4d779a1c56ae22c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.03, 0.49, 0.32, 0.16, 0.0, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during a scheduled maintenance window. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_84a89e92a2b1200a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.06, 0.71, 0.22, 0.0], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: in production only, during normal operations. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6692ec315001119e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.21, 0.66, 0.12, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during the quarterly review. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6861f37adea39929_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.22, 0.04, 0.28, 0.46], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: in production only, while on-call rotation changed. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ac0c9e827cfa0342_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.95, 0.0, 0.01, 0.04], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: in production only, while legacy systems are still active. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e2a3a1a75445e8b9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.31, 0.06, 0.35, 0.28], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: over the last hour, as part of a compliance sweep. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_025f00cdf95d94c1_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during the system migration. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4cce35ce6e2fcbf5_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.93, 0.0, 0.03, 0.04], "state": "The log shipper correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, following a recent audit. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8bc827cdd986f5de_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.39, 0.59, 0.01], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: in production only, during the quarterly review. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_18d7c93f64d3dcc1_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, immediately after go-live. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d24481041f98bbfb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.73, 0.25, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the system migration. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ade3aa4a1933fd0c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.37, 0.62, 0.01], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: during the batch window, under an active deadline. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_802319a40832449d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.85, 0.0, 0.13, 0.02], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: across all regions, during the morning shift. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f93a5062e3ab5f9b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.1414, 0.8081, 0.0505], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: during the batch window, immediately after go-live. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9126f6dc3b53a305_n", "kind": "noul", "options": ["false", "true"], "target": [0.9, 0.1], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: over the last hour, during the morning shift. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e0a6ae3682bed2d2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.19, 0.04, 0.02, 0.75], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: in production only, during the morning shift. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_64c1d92a14f97bad_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.88, 0.0, 0.08, 0.04], "state": "The log shipper correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during the morning shift. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5da7a731d5765fd9_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during peak load. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_15301f5d5b06612e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.09, 0.86, 0.05], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: in production only, shortly after a software update. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9288f70d1659263c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.23, 0.75, 0.02], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: in production only, during the holiday freeze. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_37187f705c5e6ef5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.1, 0.67, 0.18, 0.0], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: during the batch window, during a scheduled maintenance window. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a09944e314d7ad09_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "The log shipper reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: across all regions, following a recent audit. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2dd8e73ba12f8e55_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.52, 0.37, 0.09, 0.02], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, immediately after go-live. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_922f4426e125350c_n", "kind": "noul", "options": ["false", "true"], "target": [0.61, 0.39], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: across all regions, at the end of the fiscal period. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6ced1e51ac4f26ed_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.87, 0.1, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: over the last hour, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f2e825d080e92416_n", "kind": "noul", "options": ["false", "true"], "target": [0.42, 0.58], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: during the batch window, with a new vendor onboarded. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a6b0b1cdc95d7c62_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during the holiday freeze. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_154bf3fb3e7c649c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.29, 0.68, 0.02], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: across all regions, during the holiday freeze. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a581eb07fe826a0a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.17, 0.53, 0.1, 0.2], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: across all regions, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_58b5b4c43a7b39e9_n", "kind": "noul", "options": ["false", "true"], "target": [0.45, 0.55], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: across all regions, with a new vendor onboarded. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dcba489931d6439d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.6, 0.19, 0.19, 0.02], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: in production only, while on-call rotation changed. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5a491e04822d7dce_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: over the last hour, under reduced staffing. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_91c596a7efc2f706_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.02, 0.36, 0.61], "state": "The log shipper lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: over the last hour, while on-call rotation changed. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_65ae26714f6df693_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the system migration. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6e654852fa039ae2_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "The log shipper correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: across all regions, during normal operations. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6be6ecf80d315a7d_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: in production only, under an active deadline. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8d91ec5ab9e4ff9a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.7, 0.29, 0.0], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: during the batch window, during the holiday freeze. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3c01e06ec51286ab_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.3, 0.04, 0.01, 0.65], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the quarterly review. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6d3b3129ce2d6da5_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.99, 0.0, 0.0, 0.01], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during the quarterly review. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_44a72213db6e07c8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.04, 0.76, 0.2], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: across all regions, shortly after a software update. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_add6b868ab30f64a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.32, 0.57, 0.06, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during the quarterly review. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7a4cdedf5403fe94_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.52, 0.47, 0.0], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: during the batch window, during peak load. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8f8d028e2e679cad_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.71, 0.26, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: in production only, with a new vendor onboarded. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e295f7bde693147f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.28, 0.71, 0.01], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: over the last hour, while legacy systems are still active. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_574d2d1727166f0e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.73, 0.25, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during a scheduled maintenance window. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dc6a2ddbfcdfd694_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.95, 0.04, 0.01, 0.0], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: over the last hour, under an active deadline. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1bf61105ff21c8f7_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.48, 0.38, 0.12, 0.02], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during a scheduled maintenance window. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0df354a23be51f0f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.18, 0.04, 0.04, 0.74], "state": "The log shipper returned to baseline after 11 minutes; additionally matches last Tuesday's incident signature. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_36923e671b026ebe_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.16, 0.81, 0.03], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: over the last hour, during peak load. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dbbac309ee66ee9a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.4, 0.58, 0.01], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, as part of a compliance sweep. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_19c6fb9194210aff_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.39, 0.55, 0.02, 0.0], "state": "The metrics pipeline shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: in production only, while on-call rotation changed. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6bb62addc64c5a54_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.69, 0.28, 0.01, 0.02], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, mid-incident. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_43825edcc4ba19cf_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.54, 0.42, 0.03, 0.01], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: during the batch window, under reduced staffing. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_52479c30f023af04_n", "kind": "noul", "options": ["false", "true"], "target": [0.4, 0.6], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: over the last hour, at the end of the fiscal period. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3b6f5fbda4e73f15_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.04, 0.42, 0.51], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: during the batch window, during the morning shift. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e4f5c886b58543f5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.07, 0.89, 0.04], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: across all regions, with staffing at reduced levels. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_77daea2b4f824801_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.15, 0.32, 0.52, 0.01], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: over the last hour, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_407f524abe95fe94_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.83, 0.16, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: across all regions, shortly after a software update. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6fba0c5727731a7d_n", "kind": "noul", "options": ["false", "true"], "target": [0.93, 0.07], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, shortly after a software update. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_947c78c18a199170_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.02, 0.07, 0.89], "state": "The metrics pipeline lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: across all regions, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_70af6976a8fff361_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: over the last hour, while legacy systems are still active. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c91f7595dfbae429_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: in production only, under an active deadline. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d254c5640cb44c16_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.02, 0.37, 0.6], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: over the last hour, during normal operations. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ba906ede36fc534a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.27, 0.48, 0.24, 0.01], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a476ff22e4b40a3d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.51, 0.49, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: across all regions, under an active deadline. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d643c372e2ea1da9_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: during the batch window, with a new vendor onboarded. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cd9d72a8e6de77a6_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.14, 0.03, 0.06, 0.77], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: across all regions, while on-call rotation changed. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f47fa71025a1ebd7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.5, 0.49, 0.0], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: over the last hour, under reduced staffing. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9e15201c112f413a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.71, 0.0, 0.16, 0.13], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e41472fb4e217242_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.26, 0.71, 0.02], "state": "The log shipper lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: in production only, immediately after go-live. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7982f8d565dc8cb8_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.27, 0.54, 0.07, 0.12], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: in production only, while legacy systems are still active. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b25717431c67c519_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: in production only, during the quarterly review. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ff1d5a64a457a3aa_n", "kind": "noul", "options": ["false", "true"], "target": [0.7, 0.3], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: in production only, at the end of the fiscal period. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_62dd3bead9de260c_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during an external partner integration. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_26eff6995b692b29_n", "kind": "noul", "options": ["false", "true"], "target": [0.9, 0.1], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: during the batch window, with staffing at reduced levels. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7d1c950be418f707_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.33, 0.52, 0.11, 0.04, 0.0, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: across all regions, during an external partner integration. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2b06737ffdd3d9ae_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.03, 0.54, 0.42, 0.0], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, under reduced staffing. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_53674e7834c3672f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.61, 0.33, 0.04, 0.02], "state": "The log shipper correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during peak load. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f566513f84940757_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.38, 0.55, 0.04, 0.03], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: over the last hour, following a recent audit. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8fd9ab28d9118180_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.02, 0.42, 0.53, 0.02], "state": "The metrics pipeline correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: in production only, during the holiday freeze. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4604d758f9ad4c28_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.79, 0.16, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: in production only, while on-call rotation changed. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b04a416fe1f5d3f5_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.47, 0.39, 0.13, 0.01], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: across all regions, under an active deadline. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_44ac967da236b9b4_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.09, 0.02, 0.08, 0.81], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: across all regions, immediately after go-live. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_74a869f4406e6e8a_n", "kind": "noul", "options": ["false", "true"], "target": [0.92, 0.08], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: in production only, during a scheduled maintenance window. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_33ba0018b4ef327e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.87, 0.12, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: in production only, following a recent audit. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ed57ecd87040f97c_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: over the last hour, mid-incident. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3f0f5aee4c1d740c_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during peak load. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_323a55f575902780_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.06, 0.27, 0.63], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: across all regions, during the holiday freeze. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ac0593ef408a0576_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.0, 0.89, 0.11], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: across all regions, while on-call rotation changed. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_823ace2b5495f647_n", "kind": "noul", "options": ["false", "true"], "target": [0.7, 0.3], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: during the batch window, while on-call rotation changed. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a4956eee38c9eae1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.97, 0.0, 0.0, 0.03], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: in production only, during the system migration. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ad82484389d26794_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.54, 0.39, 0.04, 0.0], "state": "The log shipper reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, while on-call rotation changed. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_920f01907e47b37f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.48, 0.1, 0.0, 0.42], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, while on-call rotation changed. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4352b20a148e8169_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.51, 0.33, 0.04, 0.12], "state": "Service catalog-sync shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: during the batch window, with staffing at reduced levels. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_04680219b6ac46a2_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.52, 0.45, 0.02], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: during the batch window, during a scheduled maintenance window. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8ed9de562d3a6bbc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.31, 0.68, 0.01], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the quarterly review. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_39adb0862e1684ba_n", "kind": "noul", "options": ["false", "true"], "target": [0.37, 0.63], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: during the batch window, during the system migration. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_45a67cad1ce04c85_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during the morning shift. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6c73f330ad126ed5_n", "kind": "noul", "options": ["false", "true"], "target": [0.4, 0.6], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: in production only, during the holiday freeze. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_961b0853111a061d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.93, 0.05, 0.0, 0.02], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, mid-incident. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_adc6bba1f78247aa_n", "kind": "noul", "options": ["false", "true"], "target": [0.6, 0.4], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during peak load. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_772a46962736a64d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.32, 0.01, 0.02, 0.65], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: in production only, under reduced staffing. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9e15201c112f413a_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6b5407b8a233c55b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.05, 0.91, 0.04], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally matches last Tuesday's incident signature. Context: over the last hour, with a new vendor onboarded. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6647ce193f53feda_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.04, 0.68, 0.24, 0.04], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: during the batch window, following a recent audit. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2cf9127aec9bb01c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.21, 0.04, 0.61, 0.14], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: over the last hour, with staffing at reduced levels. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1985208fb93b453d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.38, 0.39, 0.19, 0.04], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: during the batch window, during a scheduled maintenance window. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b8298e43e1e5e5e7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.26, 0.6, 0.14, 0.0, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: across all regions, while on-call rotation changed. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7e45a3f0b745f909_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "The log shipper correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: across all regions, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4dc2c3d9d295fc4f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.56, 0.37, 0.05, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, following a recent audit. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_70af6976a8fff361_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.04, 0.58, 0.37, 0.01], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: over the last hour, while legacy systems are still active. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bca812d5e98769c8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.09, 0.83, 0.08], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: across all regions, while on-call rotation changed. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1fae858c56df14df_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: in production only, while legacy systems are still active. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c812a58afe61bf79_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.32, 0.65, 0.02], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: across all regions, under reduced staffing. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ed57ecd87040f97c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.22, 0.72, 0.05], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: over the last hour, mid-incident. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_53a869627becc0c8_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, with a new vendor onboarded. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f50c34ff5582d036_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "The log shipper reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: during the batch window, during peak load. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ad080c35e4c0c6ad_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.09, 0.85, 0.06], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: in production only, under reduced staffing. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7e15f6b732303291_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.72, 0.26, 0.02, 0.0], "state": "Service catalog-sync correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: across all regions, during the morning shift. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_06236d48ad247d84_n", "kind": "noul", "options": ["false", "true"], "target": [0.9, 0.1], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during a scheduled maintenance window. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_79230360afe6ef9f_n", "kind": "noul", "options": ["false", "true"], "target": [0.53, 0.47], "state": "The log shipper shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: across all regions, while on-call rotation changed. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_32b54e582bdefe39_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: during the batch window, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4586cd9210939cd7_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.65, 0.2, 0.14, 0.01], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: across all regions, immediately after go-live. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bbcb92db03191654_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.75, 0.01, 0.01, 0.23], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: in production only, during a scheduled maintenance window. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1f22b8a0b74fd9db_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.18, 0.8, 0.02], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during the system migration. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c09ae2db19be2204_n", "kind": "noul", "options": ["false", "true"], "target": [0.48, 0.52], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: over the last hour, during the holiday freeze. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b294d1dde75285c6_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.26, 0.08, 0.3, 0.36], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: during the batch window, following a recent audit. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_59c2a47c4ac0dacc_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.02, 0.65, 0.31], "state": "Service catalog-sync 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 review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9bef5867ff72ba56_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "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, during the quarterly review. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_812a1f9f8adef74b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.02, 0.72, 0.25, 0.01], "state": "The log shipper returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: over the last hour, during an external partner integration. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8bf5e929e40df477_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the morning shift. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b791279c53844568_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: during the batch window, with a new vendor onboarded. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_36232c7517c2d7a7_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.61, 0.07, 0.28], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: over the last hour, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ed19a5f53c241b52_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.12, 0.02, 0.81], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: during the batch window, mid-incident. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cf899c2c42d90245_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.41, 0.47, 0.09, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during the morning shift. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2989f48a4e8b00a4_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.8, 0.18, 0.01, 0.01], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: during the batch window, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_db999562405ac966_n", "kind": "noul", "options": ["false", "true"], "target": [0.61, 0.39], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: during the batch window, while legacy systems are still active. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9f856652dd67bde0_n", "kind": "noul", "options": ["false", "true"], "target": [0.19, 0.81], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: during the batch window, during the holiday freeze. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c2af400c0ab39ff3_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.03, 0.37, 0.59, 0.01], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, with staffing at reduced levels. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_23e1c2a1840c2833_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.68, 0.23, 0.08, 0.01], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during peak load. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_189f4549a0c9d2e2_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: during the batch window, during the system migration. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_15d1d04c17f926ec_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.34, 0.55, 0.1, 0.01], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: over the last hour, as part of a compliance sweep. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9c6de1d6662acc5b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.75, 0.22, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally matches last Tuesday's incident signature. Context: over the last hour, under reduced staffing. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f93301907c97a5a7_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The metrics pipeline flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: across all regions, under an active deadline. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3c5ceb7be4fa63e7_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.0, 0.98, 0.02], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: over the last hour, during the quarterly review. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fdb06f8787c48d91_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.06, 0.76, 0.18, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: across all regions, during the morning shift. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b2538a9e84cc9461_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.28, 0.08, 0.44, 0.2], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: during the batch window, at the end of the fiscal period. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3d86c711b5b863b9_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, shortly after a software update. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8ce647d9c7167076_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.03, 0.67, 0.3, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; 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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_12cbe55c507654bf_n", "kind": "noul", "options": ["false", "true"], "target": [0.37, 0.63], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: over the last hour, at the end of the fiscal period. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_99013ca6d731cb82_n", "kind": "noul", "options": ["false", "true"], "target": [0.53, 0.47], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during a scheduled maintenance window. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bee02318a3c9a9f8_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: across all regions, shortly after a software update. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9b8adf337dc171bb_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.03, 0.63, 0.33, 0.01], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: across all regions, during the morning shift. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ce98cdc48a8f7f10_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.12, 0.31, 0.5, 0.07, 0.0], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: during the batch window, while on-call rotation changed. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c78f7fa6311228bb_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.98, 0.0, 0.0, 0.02], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: in production only, with staffing at reduced levels. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9d9a3a664d376955_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.18, 0.47, 0.33, 0.02], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f519a0039b1664cb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.29, 0.71, 0.0], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: in production only, with a new vendor onboarded. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_af08ddb14f69a289_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.21, 0.42, 0.36, 0.01], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, immediately after go-live. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_51595f59048edd37_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "Service catalog-sync flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: across all regions, under reduced staffing. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dd808d0547fa88ef_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.24, 0.74, 0.02], "state": "The log shipper reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during the morning shift. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_303e9f767d4dd8c7_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: across all regions, shortly after a software update. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_198397f6e8c8771d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.51, 0.46, 0.01], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4e272a1b98d4e9c8_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.86, 0.11, 0.02, 0.01], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during the quarterly review. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e75832a0890e034f_n", "kind": "noul", "options": ["false", "true"], "target": [0.43, 0.57], "state": "The metrics pipeline flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: over the last hour, during the system migration. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6ad6a5a621285968_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during a scheduled maintenance window. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b1fcc16f8deb2040_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.23, 0.7, 0.06], "state": "The log shipper reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: during the batch window, as part of a compliance sweep. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_10d200dfe972c644_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.52, 0.44, 0.03, 0.01], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during the morning shift. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c6ec59909cbfc006_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.04, 0.84, 0.12, 0.0], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: in production only, during normal operations. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1a8132136c6768c9_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: in production only, during the holiday freeze. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2b1ca094d49a6fda_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.62, 0.35, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during peak load. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9bc066b2408f2027_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: over the last hour, with a new vendor onboarded. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_206be403f749e738_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.36, 0.56, 0.07, 0.01], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: across all regions, with staffing at reduced levels. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_745f9e31eea67a99_n", "kind": "noul", "options": ["false", "true"], "target": [0.21, 0.79], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: during the batch window, while legacy systems are still active. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e4a7b3fa2b0418cf_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.03, 0.8, 0.17, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: in production only, with a new vendor onboarded. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fe95596ba68177bc_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.37, 0.03, 0.19, 0.41], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during the system migration. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8f8d028e2e679cad_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.03, 0.53, 0.43], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: in production only, with a new vendor onboarded. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aae910bf328fd59b_n", "kind": "noul", "options": ["false", "true"], "target": [0.45, 0.55], "state": "The log shipper returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, with a new vendor onboarded. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_74fb6a159a931ff2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.74, 0.25, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: over the last hour, with staffing at reduced levels. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e032e061bd2cd86b_n", "kind": "noul", "options": ["false", "true"], "target": [0.71, 0.29], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: over the last hour, under an active deadline. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e7eabd7ebe0b1c6c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.11, 0.58, 0.3, 0.0], "state": "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, under an active deadline. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9bc066b2408f2027_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.09, 0.05, 0.23, 0.63], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: over the last hour, with a new vendor onboarded. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_add1200b69a1f53f_n", "kind": "noul", "options": ["false", "true"], "target": [0.45, 0.55], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: across all regions, mid-incident. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8facfb2d805b6094_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.43, 0.03, 0.34, 0.2], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e0a6ae3682bed2d2_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: in production only, during the morning shift. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d98299418be0b287_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, while legacy systems are still active. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_716ee0bd230f6f27_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: in production only, during the quarterly review. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_12a453bfcf0b453a_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: across all regions, at the end of the fiscal period. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c1cfa35019e12fc2_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: during the batch window, during the system migration. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_db999562405ac966_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.32, 0.57, 0.08, 0.0], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: during the batch window, while legacy systems are still active. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3ea1f47f29d357cf_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.85, 0.14, 0.0], "state": "The log shipper 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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9d767bf30b014062_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.04, 0.31, 0.29, 0.34, 0.02, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: during the batch window, following a recent audit. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c812a58afe61bf79_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: across all regions, under reduced staffing. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fa9325ae329daf1e_n", "kind": "noul", "options": ["false", "true"], "target": [0.4, 0.6], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: over the last hour, while legacy systems are still active. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d9a3e2a7985ac952_n", "kind": "noul", "options": ["false", "true"], "target": [0.47, 0.53], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: across all regions, as part of a compliance sweep. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ac3e76047bdb94a8_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.76, 0.0, 0.0, 0.24], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, as part of a compliance sweep. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_abca85c65c147907_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.73, 0.01, 0.19, 0.07], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: over the last hour, at the end of the fiscal period. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3b76ef23efbfb7e8_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.43, 0.15, 0.01, 0.41], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: across all regions, under reduced staffing. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_360d267f752d655d_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "The log shipper matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: in production only, while on-call rotation changed. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b99b08e0bcf7c89f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.64, 0.35, 0.0], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: over the last hour, shortly after a software update. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f566513f84940757_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.73, 0.25, 0.0], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: over the last hour, following a recent audit. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e69b00e4c5dec16a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.01, 0.04, 0.61, 0.32, 0.01], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: during the batch window, as part of a compliance sweep. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_afb3603dd1abfd50_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.22, 0.13, 0.61], "state": "Service catalog-sync 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 supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9018d507e426d4df_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.02, 0.36, 0.59], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: across all regions, mid-incident. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_71816d5a66a5e2c9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.6, 0.38], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: in production only, as part of a compliance sweep. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c2c734aedfc85087_n", "kind": "noul", "options": ["false", "true"], "target": [0.41, 0.59], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: over the last hour, following a recent audit. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cb209b96c2f7ac33_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.27, 0.6, 0.12, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: over the last hour, shortly after a software update. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e93a7b5ee9686a1f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.77, 0.21, 0.01, 0.01], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: across all regions, with a new vendor onboarded. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_def972e268d20ccb_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: in production only, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d2daeaf32c6f1c4f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.69, 0.3, 0.01, 0.0], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: in production only, following a recent audit. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b705d568cb7c4052_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.79, 0.2, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: during the batch window, during peak load. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b7a892b2f526cadf_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.16, 0.36, 0.47, 0.01, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: during the batch window, during a scheduled maintenance window. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ef30cd0d3607ee62_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.54, 0.38, 0.05, 0.03], "state": "The log shipper reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: in production only, during the system migration. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c809391ee7fd89fa_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.22, 0.01, 0.08, 0.69], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: during the batch window, during normal operations. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e4190c0eafcc34e7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.07, 0.85, 0.08], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, mid-incident. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b25717431c67c519_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.85, 0.15, 0.0, 0.0], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: in production only, during the quarterly review. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3a42dfa097784dad_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.44, 0.54, 0.01], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: over the last hour, during normal operations. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f1b858230c69f5c6_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.12, 0.64, 0.21, 0.03], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during a scheduled maintenance window. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_78fb08c3d4f4706e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.71, 0.25, 0.03, 0.01], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the morning shift. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7e9a8d9a8eb1316c_n", "kind": "noul", "options": ["false", "true"], "target": [0.61, 0.39], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: during the batch window, while on-call rotation changed. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_236179a567f39fc9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.19, 0.2, 0.52, 0.08, 0.0], "state": "The log shipper flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: across all regions, during a scheduled maintenance window. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f22b696c8ad01f8d_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Service catalog-sync correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: over the last hour, mid-incident. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fbf1d14b9ba40690_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.83, 0.04, 0.11], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: over the last hour, shortly after a software update. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_997648e0ee6b8ec5_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: across all regions, during an external partner integration. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9fac15c07e33765e_n", "kind": "noul", "options": ["false", "true"], "target": [0.51, 0.49], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during peak load. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6bdadba36df4874d_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: across all regions, immediately after go-live. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0692e887285ef586_n", "kind": "noul", "options": ["false", "true"], "target": [0.71, 0.29], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: in production only, during an external partner integration. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5f6d2c2cc249978b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.15, 0.34, 0.44, 0.07], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: over the last hour, following a recent audit. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dcf345bc0fc88370_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, shortly after a software update. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2a208ac07afc7b0f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.12, 0.32, 0.52, 0.03, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: in production only, as part of a compliance sweep. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ccccf8ecaca8821c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.07, 0.88, 0.05], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: in production only, during peak load. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3692e15ea4220a74_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.84, 0.16, 0.0, 0.0], "state": "The metrics pipeline correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: across all regions, with staffing at reduced levels. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dde53effbf8fe07b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.38, 0.44, 0.17, 0.0], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, while on-call rotation changed. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8115efd3c40ab8c2_n", "kind": "noul", "options": ["false", "true"], "target": [0.38, 0.62], "state": "The metrics pipeline flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: during the batch window, under reduced staffing. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d92f11306bff162f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.16, 0.05, 0.53, 0.26], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: over the last hour, while on-call rotation changed. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ccb06f9acae4aa61_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.13, 0.8, 0.07], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: across all regions, during the system migration. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_70fcab06027d3899_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: over the last hour, during the holiday freeze. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_38a900fb92b93a92_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.53, 0.44, 0.02, 0.01], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: in production only, following a recent audit. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_30a9f599e64f3200_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.06, 0.12, 0.11, 0.71], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: in production only, during a scheduled maintenance window. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b46a0ac38930c271_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.76, 0.0, 0.04, 0.2], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: in production only, during the morning shift. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_13dbbf2debd8831d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.72, 0.26, 0.02, 0.0], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: during the batch window, while legacy systems are still active. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_73a30f32ebe7d993_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: in production only, as part of a compliance sweep. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_455f09eefb92e1fa_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: over the last hour, during normal operations. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_082781777b5ddd99_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.34, 0.62, 0.01, 0.03], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: over the last hour, during peak load. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ef60429fd299ea53_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.85, 0.15, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: over the last hour, with staffing at reduced levels. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3e1649912cda723c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.01, 0.07, 0.89], "state": "The log shipper lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: over the last hour, while legacy systems are still active. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b9f4ac98f99f094b_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: during the batch window, during the holiday freeze. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8afe9490163163a5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.76, 0.23, 0.0], "state": "The log shipper flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: across all regions, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_76320323facabee7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.83, 0.16, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: across all regions, during the system migration. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_786793717d5bfc6a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.17, 0.03, 0.06, 0.74], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; 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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_865be2f353f9da04_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.8182, 0.1717, 0.0101, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: during the batch window, immediately after go-live. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7e2fc4b1e9460b24_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.75, 0.2, 0.04, 0.01], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the system migration. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_df7d6d6efb18e11b_n", "kind": "noul", "options": ["false", "true"], "target": [0.23, 0.77], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during normal operations. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_524d05f2f50ba232_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.55, 0.44, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: over the last hour, following a recent audit. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6cfa2beca82112b4_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: in production only, immediately after go-live. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_371f9b65d076919c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.06, 0.05, 0.88], "state": "Service catalog-sync lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: in production only, under an active deadline. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e036bbb287e88fa6_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.16, 0.15, 0.02, 0.67], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the quarterly review. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c9995ce3b68dba4c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.11, 0.83, 0.06], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, shortly after a software update. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c7786d696b458edc_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: in production only, during the morning shift. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_37bfb5864df374db_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.16, 0.11, 0.12, 0.61], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: across all regions, while on-call rotation changed. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_56ec38af968872e3_n", "kind": "noul", "options": ["false", "true"], "target": [0.4, 0.6], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: over the last hour, during the holiday freeze. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6873d2081505ef72_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during normal operations. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b2b0622bcfd9b6db_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.42, 0.16, 0.16, 0.26], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: in production only, while legacy systems are still active. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4727001c7d64a364_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, with a new vendor onboarded. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a0c43d3f5cb2afed_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.86, 0.12, 0.01, 0.01], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: during the batch window, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_80576ba9774ab77f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.02, 0.83, 0.15], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, shortly after a software update. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a0b95efe4d304143_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: over the last hour, under an active deadline. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e2a3a1a75445e8b9_n", "kind": "noul", "options": ["false", "true"], "target": [0.58, 0.42], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: over the last hour, as part of a compliance sweep. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b3536e6c95425187_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: over the last hour, while legacy systems are still active. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3220100bde8842f0_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, while on-call rotation changed. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6e01b1a636bafa7f_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: during the batch window, under reduced staffing. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_55cf5bca8329e2c0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.0202, 0.8081, 0.1717], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: in production only, under an active deadline. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5b6a6ac106590da5_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.29, 0.66, 0.03, 0.02], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: across all regions, following a recent audit. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7e974876a8103eda_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.51, 0.47, 0.01], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: over the last hour, during peak load. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8efea7cd78da752b_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the morning shift. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_11244bfc18f198c0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.49, 0.51, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: during the batch window, while on-call rotation changed. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_02b13446645be3cd_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: in production only, with staffing at reduced levels. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_786fd6c9b705d052_n", "kind": "noul", "options": ["false", "true"], "target": [0.47, 0.53], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: during the batch window, as part of a compliance sweep. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1123e19ede1128a0_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.44, 0.46, 0.05, 0.05], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: over the last hour, as part of a compliance sweep. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2dc6b620fa20ca5d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.99, 0.01, 0.0, 0.0], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: in production only, immediately after go-live. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0a1d17d256c6fd47_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.29, 0.35, 0.3, 0.06], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during a scheduled maintenance window. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f97695a081cbca73_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during normal operations. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fae7c98b7af23f3f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.56, 0.43, 0.0], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: across all regions, during the morning shift. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fc7b57e5e542e5f1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.0, 0.87, 0.13], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: in production only, under an active deadline. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_93c8c870372efff4_n", "kind": "noul", "options": ["false", "true"], "target": [0.37, 0.63], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: across all regions, at the end of the fiscal period. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_14daed94192bd2d9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.2, 0.78, 0.02], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: during the batch window, during an external partner integration. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_55c9eb3999cbdfc0_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.44, 0.0, 0.33, 0.23], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during peak load. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a42ae064a33d5d0e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.72, 0.0, 0.28], "state": "The metrics pipeline flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: in production only, shortly after a software update. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e93a7b5ee9686a1f_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: across all regions, with a new vendor onboarded. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d4e6234994855e22_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.06, 0.25, 0.67, 0.02], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: across all regions, during a scheduled maintenance window. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_41f1416b8b74b8e4_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.07, 0.26, 0.31, 0.36], "state": "The log shipper correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: across all regions, during the morning shift. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c91f7595dfbae429_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.22, 0.06, 0.7], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: in production only, under an active deadline. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_37bfb5864df374db_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.47, 0.53, 0.0], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: across all regions, while on-call rotation changed. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c94d07b1f6a847c3_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: during the batch window, during a scheduled maintenance window. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_29d8e6db5da11b07_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The log shipper shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: across all regions, while on-call rotation changed. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_56b98ac626c74c7e_n", "kind": "noul", "options": ["false", "true"], "target": [0.5, 0.5], "state": "The log shipper shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: across all regions, immediately after go-live. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4179e23937975218_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.35, 0.44, 0.15, 0.06], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during the holiday freeze. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4bd38927d42d4903_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "The metrics pipeline shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: over the last hour, during the holiday freeze. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_609dc6d4704804d2_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.51, 0.35, 0.11, 0.03], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1216e41e760ddc18_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.26, 0.73, 0.01], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, while legacy systems are still active. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d969e5d48e90c358_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during the morning shift. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d24481041f98bbfb_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "The log shipper lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the system migration. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_06ddfbdc2832b1a6_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "Service catalog-sync shows clock skew of 800ms across replicas; 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 supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aaaf68cecbab1d7f_n", "kind": "noul", "options": ["false", "true"], "target": [0.7, 0.3], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: across all regions, as part of a compliance sweep. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0393f26486638091_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.65, 0.23, 0.09, 0.03], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during an external partner integration. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d359e2525c4a5b38_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.16, 0.8, 0.04], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: over the last hour, while on-call rotation changed. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d321c0674c4ef632_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during the morning shift. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1b5ad631cf962775_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.14, 0.03, 0.02, 0.81], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e5537aeb17739c05_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.68, 0.27, 0.04, 0.01], "state": "The metrics pipeline flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: in production only, at the end of the fiscal period. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_833dc0d74faeac74_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.27, 0.5, 0.21, 0.02], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: across all regions, during a scheduled maintenance window. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8700788eb164467b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.06, 0.55, 0.37, 0.01], "state": "The log shipper correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during a scheduled maintenance window. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a945a11450ca4edf_n", "kind": "noul", "options": ["false", "true"], "target": [0.91, 0.09], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: over the last hour, during normal operations. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0de7bfa8739d0f18_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: over the last hour, during the morning shift. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eae2faba9ae45163_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.07, 0.73, 0.17, 0.0], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: in production only, during a scheduled maintenance window. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b6119e2a56046946_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: during the batch window, during an external partner integration. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a246203937346e78_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.34, 0.63, 0.02], "state": "The log shipper correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: during the batch window, mid-incident. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9aeb8e1ea28c05b8_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.09, 0.71, 0.02, 0.18], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: during the batch window, immediately after go-live. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2f5540b961126783_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.52, 0.4, 0.07, 0.01], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: during the batch window, at the end of the fiscal period. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d11d178801815eb9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.68, 0.29, 0.0], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: over the last hour, with a new vendor onboarded. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_28f6438fe60d04f9_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: across all regions, under reduced staffing. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6405e58deabe4c14_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.67, 0.24, 0.09, 0.0], "state": "The metrics pipeline correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: during the batch window, mid-incident. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e9bef21b6ca42f7c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.6, 0.36, 0.02, 0.02], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: during the batch window, shortly after a software update. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c3389c61e89d727a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.43, 0.55, 0.01], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during the holiday freeze. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e332ef97e5a1eace_n", "kind": "noul", "options": ["false", "true"], "target": [0.21, 0.79], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during the morning shift. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aace833266e130a9_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: over the last hour, mid-incident. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8c0cdfa317141def_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.79, 0.2, 0.0], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: during the batch window, shortly after a software update. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5c8a864474e81ef9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.09, 0.61, 0.29, 0.01, 0.0], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: in production only, with a new vendor onboarded. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fd73641703dddfa2_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: in production only, during the holiday freeze. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_02cb1be8aac19263_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.32, 0.01, 0.35, 0.32], "state": "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, during the holiday freeze. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cc180ce1eff32f15_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.55, 0.44, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: over the last hour, mid-incident. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f88f92947aa0bcea_n", "kind": "noul", "options": ["false", "true"], "target": [0.37, 0.63], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: across all regions, during a scheduled maintenance window. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_85f079c40373b807_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.0, 0.11, 0.84, 0.05], "state": "The log shipper reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: during the batch window, during a scheduled maintenance window. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f1042f6841ea4699_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: over the last hour, during peak load. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_03408b5a97e22ddd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.26, 0.74, 0.0], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b1bde925828e7967_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: during the batch window, mid-incident. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c586de37fdbd4980_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.87, 0.12, 0.01, 0.0], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: across all regions, during peak load. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7f6e48708ae5e353_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.27, 0.04, 0.49, 0.2], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the morning shift. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_58b4747db20229df_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.4, 0.44, 0.15, 0.01], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: in production only, during the system migration. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c31bb85dc7450e2d_n", "kind": "noul", "options": ["false", "true"], "target": [0.45, 0.55], "state": "Service catalog-sync shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: across all regions, while on-call rotation changed. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fc6fae9c93dd288d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.2, 0.16, 0.04, 0.6], "state": "The log shipper shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: in production only, during normal operations. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_027c9763cef774d4_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.02, 0.53, 0.44], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: in production only, with staffing at reduced levels. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f03d9859a36bf9c7_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: over the last hour, as part of a compliance sweep. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ef2f008c09137d3a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.05, 0.48, 0.45], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: over the last hour, at the end of the fiscal period. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_10c2f3f1f35b3d1a_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "The log shipper shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: during the batch window, under reduced staffing. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_02b5e2018ace817e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.28, 0.71, 0.01], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the quarterly review. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_978848ce615c3bac_n", "kind": "noul", "options": ["false", "true"], "target": [0.15, 0.85], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: in production only, shortly after a software update. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_97f4ad10da01e9d3_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.76, 0.2, 0.02, 0.02], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: over the last hour, following a recent audit. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_26276d48f610b8d0_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: over the last hour, mid-incident. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bbe480e6e4fb9f6f_n", "kind": "noul", "options": ["false", "true"], "target": [0.42, 0.58], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: over the last hour, during peak load. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_46b7cda5a15425ce_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.13, 0.78, 0.08, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: during the batch window, while on-call rotation changed. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6dbd3b7f659a3008_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.06, 0.84, 0.09, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: across all regions, during the holiday freeze. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4333b632dc8104dd_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.1, 0.47, 0.41, 0.02], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: in production only, during the quarterly review. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_49cb1d19fa66a9a1_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: over the last hour, during an external partner integration. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_80250e528411ed5c_n", "kind": "noul", "options": ["false", "true"], "target": [0.39, 0.61], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: across all regions, under an active deadline. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8fd9ab28d9118180_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.62, 0.3, 0.07, 0.01], "state": "The metrics pipeline correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: in production only, during the holiday freeze. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9288f70d1659263c_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: in production only, during the holiday freeze. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f5c5f643919c1fa0_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.14, 0.54, 0.32, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: across all regions, during the system migration. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fe786f31cdc86e52_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during an external partner integration. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_49cd6a50a75c581f_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during a scheduled maintenance window. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4fee1d651251efd4_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: across all regions, shortly after a software update. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_608cc46d5f3a30d9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.22, 0.74, 0.03], "state": "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, during peak load. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a068a3e8abd279b5_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: over the last hour, under reduced staffing. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a426fc7a77b786b1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.11, 0.83, 0.06], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: in production only, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a580bbedec231618_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.0, 0.0, 0.99], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: across all regions, under an active deadline. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_68595eefb765b625_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.22, 0.66, 0.12, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: during the batch window, during the quarterly review. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_479bc5901d292b5f_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: in production only, during a scheduled maintenance window. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1898397db47dcae0_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: in production only, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_12ca318ff98effae_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.63, 0.33, 0.02, 0.02], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: across all regions, at the end of the fiscal period. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_42f0c521fe1af430_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.38, 0.51, 0.11, 0.0, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: over the last hour, during the holiday freeze. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0393f26486638091_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.75, 0.24, 0.0], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during an external partner integration. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a0c43d3f5cb2afed_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.48, 0.46, 0.01], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: during the batch window, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_497e2a8e51291455_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.34, 0.38, 0.22, 0.02], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: in production only, during peak load. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_570c66f20c5b16c3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.05, 0.84, 0.11], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b4309afdabc04b24_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: during the batch window, during the quarterly review. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_abb2bb19d1559b45_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "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 an external partner integration. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2190c61ba35fcca9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.33, 0.56, 0.05, 0.0], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: during the batch window, during peak load. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_90cdcea7d09d9275_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The log shipper flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: during the batch window, during an external partner integration. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bce89431712dd5fb_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.02, 0.34, 0.62], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: across all regions, under an active deadline. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_10a82816ac73e3b2_n", "kind": "noul", "options": ["false", "true"], "target": [0.7, 0.3], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: in production only, during an external partner integration. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b8e8427e555dae8e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.26, 0.57, 0.13, 0.01], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, following a recent audit. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cff0debea5b0a5e3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.59, 0.37, 0.02, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: in production only, during the system migration. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c0094f1664e73fe5_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: during the batch window, at the end of the fiscal period. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fd028d56fb7f09dd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.17, 0.79, 0.04], "state": "The log shipper matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: across all regions, under reduced staffing. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_40f648521fead275_n", "kind": "noul", "options": ["false", "true"], "target": [0.39, 0.61], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: in production only, during the morning shift. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1e4150f7cac3fb69_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.99, 0.01, 0.0, 0.0], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, under an active deadline. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5fe6eeeb3ee53d02_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.23, 0.58, 0.1, 0.09], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: over the last hour, during the quarterly review. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b9f4ac98f99f094b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.46, 0.51, 0.01], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: during the batch window, during the holiday freeze. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1eeb38bf0f8ec343_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.23, 0.52, 0.23, 0.01, 0.0], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during normal operations. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_12b0430d73fc4b7e_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during peak load. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_abbb664d3015ac68_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.08, 0.4, 0.45, 0.06, 0.0], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: across all regions, during the system migration. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7f2ed8eb80037306_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.1, 0.83, 0.07], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: in production only, at the end of the fiscal period. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1be9baac9f657dc9_n", "kind": "noul", "options": ["false", "true"], "target": [0.55, 0.45], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: during the batch window, following a recent audit. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5347d9814bee19d3_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: across all regions, during an external partner integration. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0f169180279b0e05_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: in production only, during an external partner integration. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9d04f1361b0be460_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "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, as part of a compliance sweep. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e43d4740833e8d5b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.45, 0.21, 0.01, 0.33], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: across all regions, under reduced staffing. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c9c4fbd10e3a6440_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.0, 0.15, 0.83], "state": "The metrics pipeline 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 review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_37e2e80a95b9a970_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the system migration. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_048b05e123f76f50_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.45, 0.5, 0.04, 0.01], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: during the batch window, with a new vendor onboarded. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_456c1c11ffdf27f0_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.12, 0.72, 0.12, 0.04], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: over the last hour, with a new vendor onboarded. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8b3ac1455ee1eaf2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.34, 0.64, 0.01], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: during the batch window, following a recent audit. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_83a9c92c56a2b5ec_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.63, 0.34, 0.02, 0.01], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: across all regions, shortly after a software update. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_08f3b6f97e294c26_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.01, 0.02, 0.35, 0.59, 0.02], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: in production only, as part of a compliance sweep. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_91a83a210b68feaa_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.12, 0.84, 0.04], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, under an active deadline. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_99676f46df41db7d_n", "kind": "noul", "options": ["false", "true"], "target": [0.37, 0.63], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during an external partner integration. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_47d8e2c3d0a7cd34_n", "kind": "noul", "options": ["false", "true"], "target": [0.68, 0.32], "state": "Service catalog-sync shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: over the last hour, at the end of the fiscal period. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eb24bc1e23923820_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during the morning shift. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8a7810bd7055a8b1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.43, 0.33, 0.22, 0.01], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, at the end of the fiscal period. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca195f786ef7e800_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.37, 0.61], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: during the batch window, while legacy systems are still active. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_64d30da221b9c18b_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: in production only, following a recent audit. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_af0a534fc808afa9_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during a scheduled maintenance window. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1b126806088abe2b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.04, 0.74, 0.22, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: over the last hour, under an active deadline. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c50e3c902ea23020_n", "kind": "noul", "options": ["false", "true"], "target": [0.42, 0.58], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: in production only, during the holiday freeze. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f3b71d43160443f9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.1, 0.8, 0.1], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: in production only, mid-incident. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aac77c7dde1aa473_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.66, 0.28, 0.0, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: in production only, during an external partner integration. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b791279c53844568_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.48, 0.5, 0.01], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: during the batch window, with a new vendor onboarded. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_388a4f2353f5407c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.13, 0.59, 0.27, 0.01, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the system migration. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_493188b3cdd6eb3f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.7, 0.28, 0.02, 0.0], "state": "The metrics pipeline flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: across all regions, with staffing at reduced levels. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_124c471e8040ac78_n", "kind": "noul", "options": ["false", "true"], "target": [0.63, 0.37], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: across all regions, during the system migration. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4462f40a0f6049b7_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: across all regions, following a recent audit. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cf5625720254f9b9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.06, 0.49, 0.43], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, following a recent audit. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_44c2fd5fbe4194bc_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.99, 0.0, 0.0, 0.01], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: during the batch window, during normal operations. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8e770a834f9d8039_n", "kind": "noul", "options": ["false", "true"], "target": [0.68, 0.32], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: in production only, immediately after go-live. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2dc6b620fa20ca5d_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: in production only, immediately after go-live. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ab467b76bb5b3efe_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.2, 0.7, 0.1, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: in production only, during the quarterly review. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c43a00a9b6e3d3c3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0303, 0.5556, 0.3939, 0.0202, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: in production only, at the end of the fiscal period. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_055e1a0cf92a7d2b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.13, 0.83, 0.04], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: in production only, with staffing at reduced levels. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_53ff01805160aa1f_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: over the last hour, during normal operations. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1cd6e2261f731d88_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, with a new vendor onboarded. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_513e29d2a5d94b3a_n", "kind": "noul", "options": ["false", "true"], "target": [0.42, 0.58], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: in production only, while legacy systems are still active. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f07d96a3d1239c81_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: during the batch window, during peak load. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6e508750f8b38761_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.48, 0.52, 0.0], "state": "The log shipper reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: in production only, during peak load. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0e5893ed2aba1568_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.02, 0.29, 0.64, 0.05], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: over the last hour, during an external partner integration. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dec7fc902d1dcf13_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: over the last hour, with staffing at reduced levels. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_00d05c0255a343d3_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.41, 0.4, 0.18, 0.01], "state": "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, during normal operations. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_60afcd5960d0a748_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "The metrics pipeline correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: across all regions, during normal operations. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_50b255c398ac3750_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "The log shipper correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, as part of a compliance sweep. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_360d267f752d655d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.43, 0.54, 0.01], "state": "The log shipper matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: in production only, while on-call rotation changed. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_17a28e940c3858ab_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.47, 0.51, 0.01], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during normal operations. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_26f0f108f603a02c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.56, 0.38, 0.05, 0.01], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_23f612548dbcc878_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.35, 0.57, 0.07, 0.01], "state": "The log shipper 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 supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d3b5c90e93d85e69_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: over the last hour, while legacy systems are still active. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6671c30b7e2b8817_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: over the last hour, at the end of the fiscal period. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c84b9d690d2bb238_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "Node pgsql-14 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.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_806a4c7aadc29ca9_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during the holiday freeze. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aa4d8d773423cce2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.34, 0.65, 0.01], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: in production only, shortly after a software update. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c39afb7c8182f63c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.68, 0.29, 0.02, 0.01], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: across all regions, during peak load. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_78dcad523bfdb292_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.16, 0.81, 0.03], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: during the batch window, while legacy systems are still active. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6f7469e5d8b071cb_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: during the batch window, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_166ed5cd125df9d1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.27, 0.71, 0.02], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: in production only, with staffing at reduced levels. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b93b35610674efd5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.17, 0.82, 0.01], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: in production only, with a new vendor onboarded. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_31fc0aa79f95762a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.49, 0.07, 0.16, 0.28], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: across all regions, during peak load. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_489f26b7fb5967a0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.69, 0.29, 0.0], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: across all regions, as part of a compliance sweep. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_60d0ae0935021130_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.03, 0.42, 0.54], "state": "The log shipper matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: in production only, during normal operations. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a77c072b668561ff_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.3, 0.54, 0.16, 0.0, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: across all regions, during a scheduled maintenance window. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_20f9e4f9fbd9818c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.54, 0.37, 0.09, 0.0], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: in production only, while legacy systems are still active. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2b68debf5a99a940_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c825576abe7da2bf_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.07, 0.82, 0.11], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during the system migration. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ff0a156c64e53236_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.34, 0.12, 0.12, 0.42], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d31da26f5f7e79e9_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e786f58ccb822066_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.26, 0.7, 0.03], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: across all regions, while on-call rotation changed. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_22f8e532376a35cb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.46, 0.52, 0.01], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: over the last hour, while legacy systems are still active. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5186af0fc495ef1f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.75, 0.01, 0.11, 0.13], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: in production only, during normal operations. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b3a6eb992b3c23ac_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.34, 0.63, 0.02], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during normal operations. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_72b9442266e34810_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.13, 0.85, 0.02], "state": "The metrics pipeline flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: in production only, during the system migration. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5ffe803a29767ed2_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: over the last hour, during normal operations. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_60a4bd2e95944acc_n", "kind": "noul", "options": ["false", "true"], "target": [0.59, 0.41], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9bfee9027cafea34_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.12, 0.34, 0.51, 0.03, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: across all regions, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5d2ddc53f9f631cb_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "The metrics pipeline shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: in production only, during the system migration. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5f10d7085b230712_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.52, 0.47, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the system migration. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f914b958e844f363_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.86, 0.01, 0.01, 0.12], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, following a recent audit. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_beaf10adbf84782a_n", "kind": "noul", "options": ["false", "true"], "target": [0.7, 0.3], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: across all regions, during the morning shift. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_267f0e5806da91a6_n", "kind": "noul", "options": ["false", "true"], "target": [0.91, 0.09], "state": "The log shipper reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, under an active deadline. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_90bd84cb4688ba13_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.24, 0.47, 0.23, 0.01], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: in production only, immediately after go-live. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a7856975ff1b23e6_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.15, 0.2, 0.63, 0.02], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: over the last hour, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9a68d716cb05bb30_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.53, 0.41, 0.05, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: across all regions, mid-incident. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_df1a1ada49983578_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.34, 0.46, 0.18, 0.02], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during the quarterly review. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_971982240c76a7a1_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: across all regions, following a recent audit. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0158bd7e4d395aa9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.18, 0.44, 0.04, 0.34], "state": "The log shipper matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: in production only, during the holiday freeze. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_59a947f70c5fc15d_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Service catalog-sync correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: in production only, during a scheduled maintenance window. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f03d9859a36bf9c7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.02, 0.35, 0.59, 0.03], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: over the last hour, as part of a compliance sweep. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bffecabe386dadc7_n", "kind": "noul", "options": ["false", "true"], "target": [0.65, 0.35], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: in production only, at the end of the fiscal period. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_76b9aa21e53b6b67_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.11, 0.05, 0.27, 0.57], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: over the last hour, with a new vendor onboarded. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_baf4d6220323e5a5_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.99, 0.0, 0.0, 0.01], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during peak load. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_56b5cde3bac64c44_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.75, 0.23, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e63f88af1fa1404f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.02, 0.94, 0.04], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: across all regions, following a recent audit. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cc996809a5a87881_n", "kind": "noul", "options": ["false", "true"], "target": [0.62, 0.38], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: during the batch window, during a scheduled maintenance window. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3c8b4b16e98eed67_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.34, 0.09, 0.5, 0.07], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: during the batch window, with a new vendor onboarded. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5cbedb575cb6174b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.98, 0.02, 0.0, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during peak load. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2390665307c1e28e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.04, 0.44, 0.49], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: in production only, during the quarterly review. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0be0dd120daa6d13_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.48, 0.51, 0.0], "state": "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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_59c8b931e491b654_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: in production only, during a scheduled maintenance window. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca506297b3ad9fb6_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.38, 0.29, 0.32], "state": "Service catalog-sync flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: during the batch window, shortly after a software update. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5669f50f0831c0f7_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.15, 0.04, 0.54, 0.27], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_14fbc33d362fb441_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.1313, 0.1919, 0.5657, 0.1111, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: over the last hour, during a scheduled maintenance window. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1984e9933d68155f_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: in production only, during a scheduled maintenance window. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9d75fd8975599d47_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, shortly after a software update. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1fef59a7e048d966_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "The metrics pipeline shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: in production only, during the holiday freeze. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e9e90b5e08ad951e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.48, 0.49, 0.01, 0.02], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: across all regions, following a recent audit. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f3ccfadce8fe470a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.53, 0.44, 0.01], "state": "The log shipper flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: in production only, as part of a compliance sweep. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1d9d7ec7d9b7f95e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.59, 0.21, 0.01, 0.19], "state": "Service catalog-sync shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: during the batch window, at the end of the fiscal period. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ff71206b0fcbdf2f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.15, 0.83, 0.02], "state": "Service catalog-sync flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: in production only, during peak load. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_97001f04aa21e0f7_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.26, 0.18, 0.02, 0.54], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, immediately after go-live. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f25e2709953b37cb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.18, 0.45, 0.21, 0.14, 0.02, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: in production only, mid-incident. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9bf047c720af6fa7_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.68, 0.06, 0.11, 0.15], "state": "The log shipper flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, mid-incident. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5bf80dbc65f780e1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.01, 0.56, 0.4], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: across all regions, under an active deadline. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a767b3c09a149c00_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.12, 0.71, 0.13, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: in production only, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_55c9eb3999cbdfc0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.39, 0.59, 0.01], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during peak load. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_92d757301ecf7334_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.07, 0.5, 0.3, 0.13], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: in production only, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fed8c55bb8a3323e_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: during the batch window, mid-incident. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f90304720e25103d_n", "kind": "noul", "options": ["false", "true"], "target": [0.53, 0.47], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: over the last hour, during peak load. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_adca8a0ea05bc659_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.21, 0.05, 0.08, 0.66], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bc9401edbbc3d49c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.15, 0.0, 0.0, 0.85], "state": "The log shipper lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: in production only, during peak load. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_caa940303ee6411b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.41, 0.57, 0.01], "state": "The log shipper lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: in production only, while on-call rotation changed. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_06b26597ccd037f7_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: over the last hour, mid-incident. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5a57bc5668966986_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.19, 0.55, 0.17, 0.09, 0.0, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: in production only, mid-incident. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_55416dd8c1b0adb5_n", "kind": "noul", "options": ["false", "true"], "target": [0.37, 0.63], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the morning shift. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fbcfead5e40434d4_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.05, 0.74, 0.2, 0.01], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: in production only, with a new vendor onboarded. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d50718657ecf48d7_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: across all regions, while on-call rotation changed. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8ce647d9c7167076_n", "kind": "noul", "options": ["false", "true"], "target": [0.69, 0.31], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; 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.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bc268bff73441d3a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.12, 0.67, 0.19, 0.0], "state": "The log shipper matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: in production only, during the holiday freeze. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2c90bfe51a19f634_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.66, 0.05, 0.0, 0.29], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: in production only, during the morning shift. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d0937a022615166d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.09, 0.86, 0.05], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, under an active deadline. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_535dc7fd36cac5fa_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "The metrics pipeline shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during peak load. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cad6163bd0701d43_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.53, 0.4, 0.07, 0.0], "state": "Service catalog-sync correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: in production only, as part of a compliance sweep. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ca77e8f387bcdd3_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: over the last hour, during an external partner integration. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_625fa8f565c2a248_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: during the batch window, during normal operations. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_38ed57fe11ba1918_n", "kind": "noul", "options": ["false", "true"], "target": [0.23, 0.77], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, mid-incident. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_06feebd8ee7a4263_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.05, 0.68, 0.25, 0.0], "state": "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, during a scheduled maintenance window. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3188e8874bce1a97_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.45, 0.35, 0.19, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: across all regions, under an active deadline. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d2a7c0ecfca93e8e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.24, 0.29, 0.12, 0.35], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: over the last hour, during the holiday freeze. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_606e9a20dcf9f48e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.38, 0.47, 0.13, 0.01, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: in production only, as part of a compliance sweep. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0f8f375aa4cdcd9c_n", "kind": "noul", "options": ["false", "true"], "target": [0.6, 0.4], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: in production only, under an active deadline. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_20757a8833b86768_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "The log shipper matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: across all regions, immediately after go-live. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f2790d0c8cc45d38_n", "kind": "noul", "options": ["false", "true"], "target": [0.41, 0.59], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: over the last hour, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cb9e4d37d9f78573_n", "kind": "noul", "options": ["false", "true"], "target": [0.56, 0.44], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: during the batch window, under reduced staffing. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2e04a3979da02b02_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: over the last hour, under reduced staffing. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0d486d0b7385002c_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, under reduced staffing. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9c36bfd60aca0063_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.47, 0.04, 0.37, 0.12], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during the system migration. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_31930b4c6eb826fe_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.55, 0.44, 0.01, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: in production only, with a new vendor onboarded. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ac269a201ad11ebb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.61, 0.38, 0.0], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: during the batch window, mid-incident. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_91a289f380986db0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.17, 0.78, 0.05], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: in production only, during normal operations. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a7c6dc939f337830_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: during the batch window, while legacy systems are still active. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7cae19e01cc96fb5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.48, 0.49, 0.01], "state": "The log shipper shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: in production only, during the morning shift. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e63f88af1fa1404f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.14, 0.72, 0.1, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: across all regions, following a recent audit. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e8c3a0081e4b3c96_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.01, 0.31, 0.64, 0.03], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: across all regions, following a recent audit. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9fb4c447d2786c27_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "The metrics pipeline shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: over the last hour, shortly after a software update. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2720998e9b58624a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.13, 0.32, 0.18, 0.37], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: across all regions, while legacy systems are still active. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a5a294bc959609ab_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.38, 0.37, 0.23, 0.01], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, at the end of the fiscal period. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a1309467849eac7b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.33, 0.62, 0.05, 0.0], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_565edaa049f70cd9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.09, 0.13, 0.46, 0.3, 0.02], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fc96fde01460ee2d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.01, 0.53, 0.41], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: in production only, under reduced staffing. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e4190c0eafcc34e7_n", "kind": "noul", "options": ["false", "true"], "target": [0.93, 0.07], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, mid-incident. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5eb498820be4cc14_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.36, 0.62, 0.01], "state": "The log shipper flags a step-function change in error slope; 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 on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ed03e282e3184b68_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.12, 0.85, 0.03], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, under reduced staffing. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_37e710e3d7077bfa_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.53, 0.4, 0.07, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: in production only, during peak load. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_57e3a1384f9b1f95_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: over the last hour, with staffing at reduced levels. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ac552ffd8f24efe_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.38, 0.24, 0.02, 0.36], "state": "The log shipper flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: in production only, under reduced staffing. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5840917e4f6e4358_n", "kind": "noul", "options": ["false", "true"], "target": [0.22, 0.78], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: in production only, mid-incident. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2382d88f8fd7ecc3_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "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.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bcd2099fd86ecfb1_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "The log shipper flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: in production only, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fa5b6971800fa393_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.85, 0.09, 0.02, 0.04], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: in production only, under an active deadline. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6fafca8f08e1c6ff_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.05, 0.49, 0.45, 0.01], "state": "The log shipper returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: in production only, under an active deadline. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_942325462431fba5_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: over the last hour, with staffing at reduced levels. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ee31bb406560e2c8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.45, 0.36, 0.18, 0.0], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: in production only, following a recent audit. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_71816d5a66a5e2c9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.7, 0.27, 0.0], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: in production only, as part of a compliance sweep. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_581eb6e36d7f091f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.55, 0.42, 0.01], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: during the batch window, following a recent audit. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f42c74d501ac94a9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.07, 0.88, 0.05], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: across all regions, with staffing at reduced levels. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_323a55f575902780_n", "kind": "noul", "options": ["false", "true"], "target": [0.55, 0.45], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: across all regions, during the holiday freeze. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2aeea829b43dd105_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.13, 0.68, 0.18, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: across all regions, with staffing at reduced levels. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d40d7ccd24f10882_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.86, 0.12, 0.01, 0.01], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, at the end of the fiscal period. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c9f4f3cfde85f2b5_n", "kind": "noul", "options": ["false", "true"], "target": [0.48, 0.52], "state": "Node pgsql-14 flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: during the batch window, following a recent audit. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6c8905c9b2bd9d8c_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: across all regions, during a scheduled maintenance window. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_84f7679c565901d5_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: over the last hour, while legacy systems are still active. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3c8b4b16e98eed67_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0202, 0.1414, 0.8081, 0.0303, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: during the batch window, with a new vendor onboarded. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_25b6653b60b2bc3f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.77, 0.2, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: in production only, during the quarterly review. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_468b3cac759689bb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.54, 0.44, 0.01], "state": "Service catalog-sync flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: in production only, during normal operations. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9592d32f8fccfaa8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.03, 0.45, 0.5, 0.01], "state": "Service catalog-sync 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 automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4bf12119a54b3ced_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.05, 0.16, 0.78, 0.01], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: in production only, during peak load. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8d160f4342c8fc09_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.71, 0.25, 0.04, 0.0], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: in production only, following a recent audit. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_97d5a11e89a3bdc4_n", "kind": "noul", "options": ["false", "true"], "target": [0.55, 0.45], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: in production only, following a recent audit. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_79f01c0f89c28453_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.35, 0.5, 0.09, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, immediately after go-live. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_53d9e41d178b5151_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.56, 0.44, 0.0], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: over the last hour, following a recent audit. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8bc827cdd986f5de_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.68, 0.06, 0.01, 0.25], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: in production only, during the quarterly review. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_91ed4f963370609b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.64, 0.07, 0.25], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: across all regions, shortly after a software update. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_84d0db155fd6c697_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: during the batch window, while on-call rotation changed. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_099423b4fe8cd332_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.8, 0.17, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: across all regions, following a recent audit. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d7934a98d9cdd6e0_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.92, 0.03, 0.01, 0.04], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, under reduced staffing. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c53b28285db824fc_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: across all regions, during normal operations. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_33c7a3d42f27139b_n", "kind": "noul", "options": ["false", "true"], "target": [0.91, 0.09], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: in production only, with a new vendor onboarded. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d99b757add51b1e3_n", "kind": "noul", "options": ["false", "true"], "target": [0.61, 0.39], "state": "The log shipper lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: over the last hour, under reduced staffing. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7847c6638d2d7245_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.05, 0.7, 0.25, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: over the last hour, while legacy systems are still active. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_12d6b12542b29960_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.79, 0.11, 0.07, 0.03], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during a scheduled maintenance window. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9e51802b54417469_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.6, 0.39, 0.0], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: during the batch window, during an external partner integration. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_47b239ad9fae9195_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, following a recent audit. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ee8b35a2aee97538_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: over the last hour, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_59545ae9cc955ee1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.53, 0.35, 0.11, 0.0], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during the quarterly review. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_de0afa4ae7ab87ff_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.11, 0.84, 0.05], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: during the batch window, under reduced staffing. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_978885345c00db55_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "The log shipper flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: over the last hour, during the quarterly review. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2f852bd8fcc44797_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.11, 0.65, 0.21, 0.0], "state": "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 an active deadline. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_66f8e652dbf689b9_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, under an active deadline. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_246b4b115e9dc514_n", "kind": "noul", "options": ["false", "true"], "target": [0.62, 0.38], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: over the last hour, at the end of the fiscal period. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_483e39930950ec13_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.75, 0.22, 0.02, 0.01], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: during the batch window, during peak load. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2720998e9b58624a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.17, 0.76, 0.05, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: across all regions, while legacy systems are still active. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5c779e882d549770_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.07, 0.23, 0.27, 0.43], "state": "The log shipper reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: during the batch window, following a recent audit. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_078416288844daee_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.43, 0.56, 0.0], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, while on-call rotation changed. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ec8f59d40bbe9c49_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.19, 0.52, 0.17, 0.11, 0.01, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: in production only, immediately after go-live. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ad575291779696e4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.34, 0.59, 0.01, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during the morning shift. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aa847cc6c3735195_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.6, 0.38, 0.01], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the morning shift. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2526672dbfe5fd95_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.1, 0.53, 0.36, 0.01], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: over the last hour, with a new vendor onboarded. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d2656f5195e9fed9_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.65, 0.29, 0.06, 0.0], "state": "The metrics pipeline shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: in production only, while on-call rotation changed. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_558898bab8511fd8_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.8, 0.18, 0.02, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: during the batch window, with staffing at reduced levels. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d01f6b8a39b5a531_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.03, 0.72, 0.25], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: over the last hour, immediately after go-live. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ddd53badb1354305_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.91, 0.0, 0.0, 0.09], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during the holiday freeze. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6eb9dba9ab856ff6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.55, 0.41, 0.01, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: across all regions, during an external partner integration. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_71c948f698498ece_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.3939, 0.0202, 0.0303, 0.5556], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: over the last hour, while legacy systems are still active. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8d160f4342c8fc09_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: in production only, following a recent audit. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6e01b1a636bafa7f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.42, 0.5, 0.07, 0.01], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: during the batch window, under reduced staffing. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_18c36210a27910f6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.27, 0.6, 0.07, 0.0], "state": "The log shipper reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: in production only, under reduced staffing. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d2a7c0ecfca93e8e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.1, 0.67, 0.21, 0.02, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: over the last hour, during the holiday freeze. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7c430d6eb255ba1d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.06, 0.01, 0.53, 0.4], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: in production only, at the end of the fiscal period. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1f22b8a0b74fd9db_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.99, 0.0, 0.01, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during the system migration. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3c94befa6c593780_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during peak load. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cc16eebfc031642b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.34, 0.54, 0.09, 0.0], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: over the last hour, during the quarterly review. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1411322a8f5a0b55_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.18, 0.03, 0.12, 0.67], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: across all regions, mid-incident. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ae9c956bfd8b20c8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.2, 0.74, 0.05], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: across all regions, as part of a compliance sweep. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_597f43800d3b3d80_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: in production only, shortly after a software update. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_75b4fb0e52c01163_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "Service catalog-sync correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: during the batch window, mid-incident. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8eabafb20ab993ac_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.23, 0.2, 0.53, 0.04], "state": "Service catalog-sync flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: in production only, mid-incident. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d8e8cc48cc1147cf_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.53, 0.45, 0.0], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: during the batch window, with a new vendor onboarded. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0cb3257fe2e1fb80_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.43, 0.06, 0.02, 0.49], "state": "The log shipper returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the morning shift. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_18851c15000e8a45_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.06, 0.9, 0.04], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: in production only, during the morning shift. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2390665307c1e28e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.59, 0.31, 0.06, 0.0], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: in production only, during the quarterly review. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_427718e03b89aa72_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "The log shipper reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: over the last hour, while legacy systems are still active. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fdd67927938aa961_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.17, 0.8, 0.03], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, while on-call rotation changed. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a96867d88435ebe3_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: in production only, under an active deadline. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1eee00fd316ed8cf_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.97, 0.02, 0.0, 0.01], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, under an active deadline. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_26f0f108f603a02c_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "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.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_55ccd2f7e1b06f79_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "Service catalog-sync correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: across all regions, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e0157b39cf4a9495_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.64, 0.34, 0.01, 0.01], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: across all regions, under reduced staffing. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_949ffb792b47aacd_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: across all regions, as part of a compliance sweep. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2d1ad33be094d480_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2c3418ea1663c143_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: in production only, under reduced staffing. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a8dba6d576872de7_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.01, 0.83, 0.13], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during the holiday freeze. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3f71b728b03afc43_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.19, 0.8, 0.01], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: in production only, shortly after a software update. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ecf4bac04640e56_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.39, 0.61, 0.0], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: in production only, with a new vendor onboarded. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_df0841f7f2f41879_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.4, 0.12, 0.04, 0.44], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_78b30afe085a4e3c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.01, 0.06, 0.57, 0.34, 0.01], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally matches last Tuesday's incident signature. Context: across all regions, mid-incident. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f866b1f076c5de6b_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: in production only, during peak load. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_12bc36631f4bb638_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.17, 0.79, 0.04], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: over the last hour, shortly after a software update. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_037c1fd004394ee6_n", "kind": "noul", "options": ["false", "true"], "target": [0.91, 0.09], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, under an active deadline. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1b0a6b5386dad7ad_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: over the last hour, at the end of the fiscal period. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b755661e9924a290_n", "kind": "noul", "options": ["false", "true"], "target": [0.47, 0.53], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: over the last hour, during the system migration. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e8aafe32aa2fbbc0_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.02, 0.88, 0.1], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: over the last hour, during a scheduled maintenance window. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3383044f30987e33_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.07, 0.47, 0.43, 0.01], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during a scheduled maintenance window. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_43517daf835f7502_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.02, 0.21, 0.41, 0.33, 0.03, 0.0], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, as part of a compliance sweep. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5f0dae60abf4458c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.02, 0.55, 0.42], "state": "Service catalog-sync lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: during the batch window, during an external partner integration. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9341eab3032753f3_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.13, 0.15, 0.42, 0.3], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: during the batch window, during the morning shift. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b1621a960a29320e_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: in production only, under an active deadline. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3698195d1535c683_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.41, 0.4, 0.17, 0.02], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: across all regions, during the system migration. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_95a60f4c4bddab26_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.17, 0.8, 0.03], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, while legacy systems are still active. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e075f121146bac62_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.71, 0.27, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: during the batch window, during normal operations. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dc793a2423dbf41e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.28, 0.69, 0.02], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: over the last hour, while legacy systems are still active. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_55c606641a6da7e9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.59, 0.33, 0.03, 0.0], "state": "The log shipper reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during an external partner integration. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b42d3a1d02e12882_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "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.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8afe9490163163a5_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.25, 0.54, 0.04, 0.17], "state": "The log shipper flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: across all regions, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f2aad7b1c419bfe4_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "The log shipper flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during the holiday freeze. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_df0841f7f2f41879_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.06, 0.86, 0.07, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ad61efb97e1f4ef9_n", "kind": "noul", "options": ["false", "true"], "target": [0.4, 0.6], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: across all regions, following a recent audit. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_55b8102604cb0612_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: across all regions, during the morning shift. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_953db24316107fda_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.56, 0.37, 0.07, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: across all regions, as part of a compliance sweep. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4e272a1b98d4e9c8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.37, 0.62, 0.01], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during the quarterly review. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bdd01ab419590571_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.06, 0.0, 0.37, 0.57], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: over the last hour, with staffing at reduced levels. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f8f8235b3a8ec38e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.54, 0.45, 0.0], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: during the batch window, with staffing at reduced levels. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bacfa983d36c7daf_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.07, 0.65, 0.27, 0.01], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: across all regions, while legacy systems are still active. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_27f8c7f7a360b745_n", "kind": "noul", "options": ["false", "true"], "target": [0.53, 0.47], "state": "The log shipper reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: in production only, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2c90bfe51a19f634_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: in production only, during the morning shift. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9eb51876d64dd7ff_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.32, 0.61, 0.01, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: across all regions, during a scheduled maintenance window. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5bb92bd1f8c51b1b_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "The log shipper lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: across all regions, at the end of the fiscal period. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e30155814afc346d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.23, 0.76, 0.01], "state": "The log shipper shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, under reduced staffing. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6522af16a7f4eb1d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.24, 0.56, 0.19, 0.01, 0.0], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: over the last hour, immediately after go-live. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c83a62c743bf4e55_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.16, 0.72, 0.09, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: during the batch window, following a recent audit. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_654786f006ac574a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.74, 0.23, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: across all regions, with staffing at reduced levels. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8115efd3c40ab8c2_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.03, 0.5, 0.45, 0.02], "state": "The metrics pipeline flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: during the batch window, under reduced staffing. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_928dce781c980e91_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.77, 0.21, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: during the batch window, during the holiday freeze. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c90a0a59b7619521_n", "kind": "noul", "options": ["false", "true"], "target": [0.52, 0.48], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during the quarterly review. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fc8c8f644eab98cb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.42, 0.56, 0.01], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: over the last hour, during an external partner integration. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2c9823436b1dea76_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.08, 0.05, 0.83, 0.04], "state": "The metrics pipeline flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: across all regions, during the holiday freeze. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aa72a0886afb4d0c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.04, 0.78, 0.18], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: across all regions, with staffing at reduced levels. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9e64bb0a32adacab_n", "kind": "noul", "options": ["false", "true"], "target": [0.56, 0.44], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: across all regions, at the end of the fiscal period. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_75e75101abce3e10_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.06, 0.74, 0.19, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: during the batch window, while on-call rotation changed. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d7124e66f116bcfa_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.01, 0.31, 0.64], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during an external partner integration. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_99013ca6d731cb82_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.0, 0.02, 0.98], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during a scheduled maintenance window. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3a42dfa097784dad_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.59, 0.39], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: over the last hour, during normal operations. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_69bf2d14198e3dad_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.33, 0.02, 0.1, 0.55], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: in production only, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9e9308d8a2dc38e8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.36, 0.63, 0.01], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during normal operations. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c480c95278615ad0_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.12, 0.57, 0.04, 0.27], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: over the last hour, mid-incident. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ae8204ec1186e041_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.02, 0.53, 0.41, 0.04], "state": "The log shipper matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: over the last hour, during the morning shift. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dbbac309ee66ee9a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.2, 0.24, 0.09, 0.47], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, as part of a compliance sweep. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_038ae8f8c83a3da7_n", "kind": "noul", "options": ["false", "true"], "target": [0.54, 0.46], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: in production only, while legacy systems are still active. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_914c0743867989c6_n", "kind": "noul", "options": ["false", "true"], "target": [0.4, 0.6], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: in production only, during the quarterly review. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b88c5ea1bf363cd5_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: in production only, under reduced staffing. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_63428c3ec7f0e31c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.09, 0.86, 0.05], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: across all regions, during peak load. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_78fb08c3d4f4706e_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the morning shift. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e670cd89105aaf80_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.65, 0.34, 0.0], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: during the batch window, during the morning shift. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b08fc882d4e3a646_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.07, 0.6, 0.32, 0.01], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, while legacy systems are still active. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0877fa1143bac6b6_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.94, 0.04, 0.01, 0.01], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, under an active deadline. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_463189e2ceebff58_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.37, 0.04, 0.26, 0.33], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: in production only, at the end of the fiscal period. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_069b055d1fda653b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.01, 0.01, 0.3, 0.64, 0.03], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2f476a7b8bb3fa8c_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: over the last hour, mid-incident. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8d66c145f5cfa212_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "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.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b755661e9924a290_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.1, 0.8, 0.09, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: over the last hour, during the system migration. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a75162cd3e9a33f0_n", "kind": "noul", "options": ["false", "true"], "target": [0.54, 0.46], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: during the batch window, shortly after a software update. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_df7d6d6efb18e11b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.07, 0.84, 0.09], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during normal operations. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3efcf68eec5da020_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.55, 0.44, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: across all regions, during peak load. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b9805bade1c8d8ce_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.97, 0.03, 0.0, 0.0], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7b8e4d292498c347_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.22, 0.77, 0.01], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: in production only, while on-call rotation changed. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_01c3e7bc20a468cc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0101, 0.0808, 0.6869, 0.2222, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally matches last Tuesday's incident signature. Context: during the batch window, under an active deadline. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f51bdb8c25ef04ab_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.79, 0.21, 0.0, 0.0], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: over the last hour, while on-call rotation changed. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_48e03a68bc1d9ba6_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "The metrics pipeline lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: in production only, immediately after go-live. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4e7bc91902129acb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.51, 0.47, 0.01], "state": "The log shipper correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: across all regions, during an external partner integration. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ad266a43f2d8dfac_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: over the last hour, as part of a compliance sweep. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4fb099f8520ab2dd_n", "kind": "noul", "options": ["false", "true"], "target": [0.42, 0.58], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: over the last hour, at the end of the fiscal period. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4c00123562ef3c4e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.16, 0.69, 0.13, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: in production only, shortly after a software update. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6fa5fda86d36b09f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.08, 0.4, 0.51, 0.01, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: across all regions, during normal operations. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2785e65a9c0c0f37_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.06, 0.12, 0.81, 0.01], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: in production only, during a scheduled maintenance window. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c7e1db94774d2b39_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.8, 0.18, 0.01, 0.01], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: during the batch window, at the end of the fiscal period. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0401571343adeda6_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.65, 0.01, 0.25, 0.09], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: across all regions, during normal operations. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a262d3fd496342a2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.18, 0.8, 0.02], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: during the batch window, during the quarterly review. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ddadfca7416d7644_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.53, 0.45, 0.01], "state": "The log shipper reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: during the batch window, following a recent audit. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9f76bbbc933d1976_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.14, 0.83, 0.03], "state": "The log shipper matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: over the last hour, shortly after a software update. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e6a70f212b29c37f_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: during the batch window, as part of a compliance sweep. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f1b858230c69f5c6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.06, 0.44, 0.38, 0.1, 0.01], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during a scheduled maintenance window. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_319f9cf43356acd3_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.82, 0.01, 0.16], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: over the last hour, shortly after a software update. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9b356b5f4371089a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.49, 0.45, 0.06, 0.0], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_10bf3efab86ff6a0_n", "kind": "noul", "options": ["false", "true"], "target": [0.49, 0.51], "state": "Service catalog-sync lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: during the batch window, with staffing at reduced levels. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ee31bb406560e2c8_n", "kind": "noul", "options": ["false", "true"], "target": [0.56, 0.44], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: in production only, following a recent audit. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fdb06f8787c48d91_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.34, 0.15, 0.01, 0.5], "state": "Node pgsql-14 flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: across all regions, during the morning shift. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_333059e1fc2e58ed_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.02, 0.03, 0.94], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: across all regions, during the system migration. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_49eebbb3924e5ffe_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: during the batch window, while on-call rotation changed. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9dc9baa71baebcb3_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.23, 0.19, 0.11, 0.47], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: over the last hour, while on-call rotation changed. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7cbbc4e97cb3cde0_n", "kind": "noul", "options": ["false", "true"], "target": [0.23, 0.77], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: during the batch window, shortly after a software update. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5693c7d309454c00_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.15, 0.71, 0.11, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally matches last Tuesday's incident signature. Context: across all regions, during the morning shift. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_71813b934378a2fc_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.67, 0.3, 0.02, 0.01], "state": "The metrics pipeline correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: across all regions, immediately after go-live. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d9032299425a26a2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.33, 0.63, 0.02], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: over the last hour, immediately after go-live. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d49495b23fb3f83a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.3, 0.69, 0.01], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: in production only, immediately after go-live. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9fd26bc8a4b18ae8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.33, 0.58, 0.03, 0.0], "state": "The log shipper correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: over the last hour, during the morning shift. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_31f8ce2e3f35e2b2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.01, 0.9, 0.05], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: across all regions, under an active deadline. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_419a3153af7004eb_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.5, 0.48], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: over the last hour, mid-incident. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a86692e2e4667077_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.2, 0.65, 0.07, 0.08], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: across all regions, during the system migration. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_16ffffbd9705bf8b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.64, 0.34, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: over the last hour, while legacy systems are still active. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_60979879de07aeae_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "Dashboard checkout-funnel 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 operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2a3ea9df5a1bc6e4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.5, 0.47, 0.01], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: during the batch window, following a recent audit. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1773e44d7f04a9f7_n", "kind": "noul", "options": ["false", "true"], "target": [0.91, 0.09], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: across all regions, during the system migration. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ebb9dd2fb6281821_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.31, 0.51, 0.16, 0.02], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during the system migration. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_58fd5b58415fc8b7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.62, 0.35, 0.0], "state": "The metrics pipeline shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: during the batch window, during normal operations. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_774e8481d67f4166_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.26, 0.66, 0.08, 0.0, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: in production only, immediately after go-live. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6ad6a5a621285968_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.74, 0.24, 0.01], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during a scheduled maintenance window. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b0b1324bb5485df7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.05, 0.73, 0.21, 0.0], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: across all regions, during a scheduled maintenance window. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d969e5d48e90c358_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.45, 0.01, 0.15, 0.39], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during the morning shift. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a53ae687e89e5ae9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.88, 0.09, 0.0], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b24f3846df5d5918_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.0, 0.12, 0.84, 0.04], "state": "The log shipper reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: over the last hour, during the system migration. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_60a4bd2e95944acc_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.1, 0.38, 0.51, 0.01], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7b975c276134fb03_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.49, 0.4, 0.05, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: across all regions, during the holiday freeze. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_28a2965115a15381_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.41, 0.59, 0.0], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: over the last hour, with staffing at reduced levels. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cfc3e64768f94897_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.86, 0.03, 0.0, 0.11], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c70871659c3c8ff5_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.79, 0.18, 0.01, 0.02], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: during the batch window, shortly after a software update. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_099423b4fe8cd332_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.04, 0.94], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: across all regions, following a recent audit. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b15276ef517ef6df_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.62, 0.31, 0.01, 0.06], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, at the end of the fiscal period. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_878f63570c9ca2cd_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: in production only, during an external partner integration. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f9046674ef545000_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, under reduced staffing. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cedfd89ef60b48d1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.38, 0.59, 0.02, 0.01], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: across all regions, while legacy systems are still active. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9bfac4de582550ed_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.6, 0.37, 0.03, 0.0], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: across all regions, following a recent audit. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4727001c7d64a364_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.09, 0.09, 0.79, 0.03], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, with a new vendor onboarded. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2e5b071fecbe1572_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.44, 0.3, 0.21, 0.05], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: over the last hour, during a scheduled maintenance window. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f2cf80535a3d3c07_n", "kind": "noul", "options": ["false", "true"], "target": [0.62, 0.38], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: over the last hour, following a recent audit. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0694db7aff2095ff_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.79, 0.15, 0.05, 0.01], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: during the batch window, during the morning shift. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a7856975ff1b23e6_n", "kind": "noul", "options": ["false", "true"], "target": [0.57, 0.43], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: over the last hour, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e201dbb56cb51406_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during normal operations. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_010714ba5c9c9b84_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: across all regions, shortly after a software update. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_349b2dd10020ca1c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.03, 0.84, 0.13, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: in production only, with a new vendor onboarded. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cc950b503b0b144e_n", "kind": "noul", "options": ["false", "true"], "target": [0.9, 0.1], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during the quarterly review. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_64c1d92a14f97bad_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The log shipper correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during the morning shift. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5f10d7085b230712_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the system migration. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_12d5cd5faff2bb64_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.58, 0.31, 0.1, 0.01], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: over the last hour, while legacy systems are still active. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9a2dd2384612bc89_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.72, 0.26, 0.01, 0.01], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: across all regions, during the holiday freeze. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1985208fb93b453d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.12, 0.51, 0.31, 0.01], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: during the batch window, during a scheduled maintenance window. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c848524b4459a509_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.65, 0.31, 0.02, 0.0], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the morning shift. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0eb8dc03a6d9403e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.41, 0.59, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, while on-call rotation changed. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e45e4e003d661c54_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.9, 0.08, 0.0, 0.02], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: across all regions, under reduced staffing. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9c23c2dc47f95729_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, following a recent audit. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7c99bd388bed486b_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, under reduced staffing. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_92b531736a70ec94_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "Service catalog-sync shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: over the last hour, as part of a compliance sweep. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_167bc7e35521c5df_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.07, 0.61, 0.3, 0.02, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: over the last hour, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2bcb2c106496e532_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: in production only, mid-incident. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_404c2ec7405c0220_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: across all regions, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f1cd3e6c603143d2_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.92, 0.04, 0.02, 0.02], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: across all regions, mid-incident. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e29c8667c4bd6feb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.52, 0.47, 0.0], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: across all regions, at the end of the fiscal period. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_53ff01805160aa1f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.29, 0.7, 0.01], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: over the last hour, during normal operations. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_62c9a27c8b40eeef_n", "kind": "noul", "options": ["false", "true"], "target": [0.38, 0.62], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: across all regions, during the holiday freeze. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_979f44756945490a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.49, 0.28, 0.22, 0.01], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during a scheduled maintenance window. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6bdadba36df4874d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.16, 0.79, 0.05], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: across all regions, immediately after go-live. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3200b294ae89a7ba_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.23, 0.03, 0.13, 0.61], "state": "The log shipper shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: during the batch window, during normal operations. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_64323ef9c51a5279_n", "kind": "noul", "options": ["false", "true"], "target": [0.41, 0.59], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: over the last hour, following a recent audit. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3e6afe433b454e31_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.27, 0.55, 0.12, 0.06, 0.0, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: during the batch window, with staffing at reduced levels. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b18d2feb847fa4ff_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the quarterly review. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4f36d753fea92451_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: over the last hour, shortly after a software update. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_93fe43f78038bc22_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.75, 0.14, 0.08, 0.03], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_19c6fb9194210aff_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.07, 0.48, 0.44, 0.01], "state": "The metrics pipeline shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: in production only, while on-call rotation changed. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c52e59a9ad46c8c9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.55, 0.27, 0.15, 0.01], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, immediately after go-live. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b0c73e6d338917e3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.59, 0.4, 0.0], "state": "The log shipper reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: in production only, mid-incident. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5b6a6ac106590da5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.54, 0.43, 0.01], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: across all regions, following a recent audit. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3be979b46f40c800_n", "kind": "noul", "options": ["false", "true"], "target": [0.23, 0.77], "state": "The log shipper reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: over the last hour, with staffing at reduced levels. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0e781677058aae26_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.16, 0.09, 0.12, 0.63], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: over the last hour, while legacy systems are still active. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_85f079c40373b807_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "The log shipper reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: during the batch window, during a scheduled maintenance window. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d5aa1e3dfeff8809_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: during the batch window, during the quarterly review. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_333059e1fc2e58ed_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.47, 0.47, 0.01], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: across all regions, during the system migration. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_85e42931c51afe9c_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: during the batch window, during a scheduled maintenance window. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9158e154d727eeb3_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.01, 0.63, 0.33], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: in production only, during normal operations. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0a5b464eca72683a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.32, 0.66, 0.01], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: across all regions, with staffing at reduced levels. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7bf2dabf5c336abd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.16, 0.82, 0.02], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, while legacy systems are still active. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_73e8f2c7f6e13828_n", "kind": "noul", "options": ["false", "true"], "target": [0.16, 0.84], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: across all regions, mid-incident. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e677b2e9f6a4e03c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.22, 0.75, 0.03], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: across all regions, during peak load. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fc98218fa5c722aa_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.12, 0.84, 0.04], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: in production only, during normal operations. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0f5af912a31989af_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.59, 0.37, 0.03, 0.01], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, while legacy systems are still active. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9793ccba1a389059_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.98, 0.0, 0.0, 0.02], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, while on-call rotation changed. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca158537feeb0a85_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "The log shipper shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: in production only, shortly after a software update. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_237ffdae5de8e1b8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0101, 0.0505, 0.798, 0.1414, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: across all regions, under reduced staffing. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_112bccad2b878170_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.1, 0.85, 0.05], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during the morning shift. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c97be4dbb893c35a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.34, 0.65, 0.01], "state": "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 an external partner integration. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8db6b2cca5f9bd42_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "The log shipper flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: in production only, as part of a compliance sweep. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c423434da9e809a6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.59, 0.41, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: over the last hour, during an external partner integration. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e12e9da43ceff2f2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.68, 0.29, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: over the last hour, with a new vendor onboarded. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f1042f6841ea4699_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.91, 0.08, 0.01, 0.0], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: over the last hour, during peak load. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6bb62addc64c5a54_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.13, 0.82, 0.05], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, mid-incident. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3f7adeb864a7e1f2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.79, 0.2, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: in production only, shortly after a software update. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_512814574df99005_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: across all regions, with staffing at reduced levels. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c182c441d16581a5_n", "kind": "noul", "options": ["false", "true"], "target": [0.9, 0.1], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, under an active deadline. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b7518a39270d96e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.21, 0.77, 0.02, 0.0], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: during the batch window, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c43c84a42210daa8_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: across all regions, during the holiday freeze. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eaef7a4eac24b05b_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "The log shipper correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: in production only, during peak load. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c62d202fc8b58c56_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: during the batch window, with staffing at reduced levels. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3b17ac5a265499ad_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: during the batch window, under reduced staffing. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_41bf9e113bd3a250_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.13, 0.62, 0.21], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: in production only, with a new vendor onboarded. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a7856975ff1b23e6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.03, 0.23, 0.23, 0.4, 0.1, 0.01], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: over the last hour, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bc92d0c302846595_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.59, 0.38, 0.01, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: in production only, while legacy systems are still active. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5dfccb36cbc1710f_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "The log shipper correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: across all regions, during the morning shift. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bacfa983d36c7daf_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: across all regions, while legacy systems are still active. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_45a67cad1ce04c85_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.58, 0.26, 0.08, 0.08], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during the morning shift. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cbc0c992dcb4a7f6_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: during the batch window, shortly after a software update. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f47fa71025a1ebd7_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: over the last hour, under reduced staffing. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_17f11895cf0d4697_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.57, 0.42, 0.01, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: in production only, with a new vendor onboarded. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dd97a7644ebbc681_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.37, 0.63, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: in production only, during peak load. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f25e2709953b37cb_n", "kind": "noul", "options": ["false", "true"], "target": [0.59, 0.41], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: in production only, mid-incident. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3e1649912cda723c_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "The log shipper lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: over the last hour, while legacy systems are still active. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4dfe869f8715374f_n", "kind": "noul", "options": ["false", "true"], "target": [0.55, 0.45], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during normal operations. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_23d0d911e1afcbc5_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: during the batch window, under an active deadline. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_463189e2ceebff58_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.46, 0.52, 0.01], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: in production only, at the end of the fiscal period. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cb7b14485d6ed187_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.15, 0.71, 0.11, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: over the last hour, at the end of the fiscal period. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9b0c0906c5bc945e_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: in production only, following a recent audit. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aac7e59190d56ec7_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.23, 0.44, 0.28, 0.05], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: over the last hour, with staffing at reduced levels. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_969e4605fb313e7d_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: during the batch window, mid-incident. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1875f02a27d6242b_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "The log shipper matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: over the last hour, as part of a compliance sweep. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0968341171ac8bb3_n", "kind": "noul", "options": ["false", "true"], "target": [0.71, 0.29], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the morning shift. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1b57621f08128cb1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.79, 0.21, 0.0, 0.0], "state": "The log shipper reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: over the last hour, under reduced staffing. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1f9e4a2792794a54_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.15, 0.0, 0.78, 0.07], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: in production only, at the end of the fiscal period. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a6ce3ebdc670834f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.07, 0.89, 0.01, 0.03], "state": "The log shipper shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, immediately after go-live. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5ea33814cbb065e7_n", "kind": "noul", "options": ["false", "true"], "target": [0.91, 0.09], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: over the last hour, under an active deadline. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f9c6743791c50afc_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.1, 0.51, 0.34], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_74360a146f22d76c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.16, 0.69, 0.1, 0.05, 0.0, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: over the last hour, during the morning shift. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e036bbb287e88fa6_n", "kind": "noul", "options": ["false", "true"], "target": [0.51, 0.49], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the quarterly review. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6f35375bb2aeb954_n", "kind": "noul", "options": ["false", "true"], "target": [0.22, 0.78], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during normal operations. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5aa873a353ec7ebd_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: in production only, with staffing at reduced levels. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_44872c5979084e16_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.23, 0.66, 0.11, 0.0, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during an external partner integration. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_74898790f362a8e2_n", "kind": "noul", "options": ["false", "true"], "target": [0.68, 0.32], "state": "The log shipper reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: across all regions, during an external partner integration. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2432e7bd05323337_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c7bd7ca1bc56f2a0_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: in production only, during an external partner integration. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_19933be1a64d35aa_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.78, 0.19, 0.02, 0.01], "state": "The log shipper shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: during the batch window, under an active deadline. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_89145242e68e8fb6_n", "kind": "noul", "options": ["false", "true"], "target": [0.52, 0.48], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, while on-call rotation changed. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_04c53e20dffe85ee_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "The metrics pipeline lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: across all regions, as part of a compliance sweep. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fdd67927938aa961_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, while on-call rotation changed. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_01733d259d7619b1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.0, 0.01, 0.17, 0.76, 0.05], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: in production only, under an active deadline. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_12ca318ff98effae_n", "kind": "noul", "options": ["false", "true"], "target": [0.7, 0.3], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: across all regions, at the end of the fiscal period. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5c8c03f883a7b3d0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.05, 0.61, 0.32, 0.0], "state": "The metrics pipeline correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4cfa80aef832f05a_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: over the last hour, under an active deadline. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e5d7fa621f431d33_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.65, 0.33, 0.02, 0.0], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: across all regions, with staffing at reduced levels. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3e6afe433b454e31_n", "kind": "noul", "options": ["false", "true"], "target": [0.5, 0.5], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: during the batch window, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_db9aa15d151d6cac_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.86, 0.03, 0.0, 0.11], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: over the last hour, immediately after go-live. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_76a826f3f2704ba8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.94, 0.05, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: during the batch window, under reduced staffing. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_abc06399bac479f3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.77, 0.23, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: over the last hour, with staffing at reduced levels. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d589afe22bb15347_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.89, 0.1, 0.01, 0.0], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: during the batch window, while on-call rotation changed. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9d04f1361b0be460_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.65, 0.33, 0.0], "state": "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, as part of a compliance sweep. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_31a72894c028bd0d_n", "kind": "noul", "options": ["false", "true"], "target": [0.19, 0.81], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: in production only, during normal operations. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a8e9968846bc963c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.88, 0.11, 0.0, 0.01], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during the quarterly review. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a968e8086ac57b95_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.12, 0.41, 0.46, 0.01], "state": "Service catalog-sync flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: across all regions, during a scheduled maintenance window. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_85a6c91be08caada_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Node pgsql-14 flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the holiday freeze. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ed06191f323926de_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.13, 0.29, 0.54], "state": "The log shipper correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: over the last hour, during a scheduled maintenance window. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_566565f1098d32f8_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.46, 0.5, 0.04, 0.0], "state": "The log shipper matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: in production only, during the system migration. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6a030c6611ccec05_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "Service catalog-sync lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: in production only, as part of a compliance sweep. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1ab978e412d8c9cd_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.0, 0.0, 0.99], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: across all regions, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_abca85c65c147907_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: over the last hour, at the end of the fiscal period. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6db687f54290167b_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: over the last hour, under an active deadline. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_35bba68ddcf9bf15_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.03, 0.38, 0.59, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7bb8e1fcdca1c354_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.12, 0.63, 0.19, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: in production only, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fd6e5af4cf910782_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.02, 0.37, 0.59], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5a28a39ba932ae33_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.25, 0.58, 0.14, 0.0], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: across all regions, under reduced staffing. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ef2f008c09137d3a_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: over the last hour, at the end of the fiscal period. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eaef7a4eac24b05b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.33, 0.22, 0.2, 0.25], "state": "The log shipper correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: in production only, during peak load. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e67257cd6da68a23_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.06, 0.58, 0.3, 0.01], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: in production only, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4a46b6016deb8b3b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.39, 0.52, 0.03, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: during the batch window, at the end of the fiscal period. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_56b5cde3bac64c44_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.43, 0.45, 0.12, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a8b2dca32536fb49_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.06, 0.77, 0.17], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_079d55122ae93293_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.07, 0.86, 0.06, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: during the batch window, during the quarterly review. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b34c139b172551c0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.19, 0.73, 0.06, 0.02, 0.0, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: during the batch window, during the quarterly review. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5fb88450f8bbbf1e_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "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, following a recent audit. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2e1d1517a60fb1ef_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.31, 0.58, 0.11, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: over the last hour, under an active deadline. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ab3cf9c690704b74_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.32, 0.54, 0.13, 0.0, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: in production only, at the end of the fiscal period. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_60ca8bad0e69c424_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.59, 0.39, 0.01, 0.01], "state": "The log shipper shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: over the last hour, shortly after a software update. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_97f4ad10da01e9d3_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: over the last hour, following a recent audit. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6f04216405832758_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.9, 0.01, 0.04], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: over the last hour, immediately after go-live. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d00afa0f3afc1e73_n", "kind": "noul", "options": ["false", "true"], "target": [0.42, 0.58], "state": "Node pgsql-14 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 operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_827bf7e6e90a2b23_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.96, 0.03, 0.0, 0.01], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: across all regions, immediately after go-live. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aa4d8d773423cce2_n", "kind": "noul", "options": ["false", "true"], "target": [0.69, 0.31], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: in production only, shortly after a software update. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_155a9a01e72a50b9_n", "kind": "noul", "options": ["false", "true"], "target": [0.9, 0.1], "state": "The log shipper matches last Tuesday's incident signature; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during a scheduled maintenance window. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3095aa37879e8a08_n", "kind": "noul", "options": ["false", "true"], "target": [0.54, 0.46], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: across all regions, during the quarterly review. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_13e9b2a5dc8ab04e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.57, 0.42, 0.0], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: in production only, following a recent audit. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b19deea4c8771445_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.14, 0.7, 0.15, 0.01, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: across all regions, while legacy systems are still active. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cd4dbd8bb1645b31_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.49, 0.47, 0.01], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: in production only, during the system migration. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_13dbbf2debd8831d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.44, 0.55, 0.0], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: during the batch window, while legacy systems are still active. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9126f6dc3b53a305_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.43, 0.55, 0.01], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: over the last hour, during the morning shift. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8884f7eabea204de_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.1, 0.72, 0.16, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: across all regions, during normal operations. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aefe78865d7f777c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.93, 0.0, 0.0, 0.07], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: across all regions, following a recent audit. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aec98a3a9e3f1f1f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.81, 0.19, 0.0, 0.0], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e12976042ae8335e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.53, 0.19, 0.28], "state": "Service catalog-sync flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: across all regions, shortly after a software update. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_15a92085135dac36_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.03, 0.52, 0.44, 0.01], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: over the last hour, during an external partner integration. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0d0751f20335acfb_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.82, 0.09, 0.07, 0.02], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, immediately after go-live. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_19e4768dee9b2567_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.01, 0.41, 0.55], "state": "The log shipper reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: during the batch window, during the quarterly review. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_14fd7fd348ed406c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.77, 0.18, 0.05, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: during the batch window, while on-call rotation changed. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5dd7a15b977983e3_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "The log shipper reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: during the batch window, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e61ce4baa570a6ae_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: in production only, following a recent audit. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_29b325db92776c1b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.39, 0.59, 0.01], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, while on-call rotation changed. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e04fdb4044a6fd94_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.1616, 0.6768, 0.1414, 0.0202, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e3e7347614a55680_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.12, 0.14, 0.69, 0.05], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: in production only, mid-incident. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_74fb6a159a931ff2_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.43, 0.45, 0.11, 0.01], "state": "The log shipper shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: over the last hour, with staffing at reduced levels. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9388837cbfcb4d48_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "The log shipper reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: in production only, during an external partner integration. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2a84b92a71f7d080_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0101, 0.2727, 0.6869, 0.0303], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: in production only, as part of a compliance sweep. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_268890b8a75f59ff_n", "kind": "noul", "options": ["false", "true"], "target": [0.46, 0.54], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: during the batch window, under reduced staffing. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_637fc0288a3bf1c0_n", "kind": "noul", "options": ["false", "true"], "target": [0.22, 0.78], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during the morning shift. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fdb9fd30eee93272_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, immediately after go-live. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4116a2f73272e25f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.38, 0.6, 0.01], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: across all regions, during an external partner integration. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4793d6c74c3499f4_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.21, 0.04, 0.22, 0.53], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during the morning shift. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1280069eac0fbae6_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, with a new vendor onboarded. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dadf724772a36d6d_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: in production only, during an external partner integration. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_071a266928eeba09_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: in production only, while legacy systems are still active. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0895d7417727ba40_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.1, 0.62, 0.23, 0.0], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: during the batch window, as part of a compliance sweep. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_74a869f4406e6e8a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.23, 0.72, 0.04], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: in production only, during a scheduled maintenance window. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_654786f006ac574a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.36, 0.36, 0.01, 0.27], "state": "Service catalog-sync shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: across all regions, with staffing at reduced levels. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6fafca8f08e1c6ff_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.24, 0.12, 0.02, 0.62], "state": "The log shipper returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: in production only, under an active deadline. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_69bf2d14198e3dad_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: in production only, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c84b9d690d2bb238_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.62, 0.33, 0.05, 0.0], "state": "Node pgsql-14 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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1d8a644ecdddf039_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.02, 0.49, 0.47, 0.01], "state": "The log shipper reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: during the batch window, as part of a compliance sweep. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_61679747d28e5ac0_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.75, 0.21, 0.04, 0.0], "state": "Node pgsql-14 correlates with the vendor status page incident; 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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_20dc48a108093394_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.67, 0.11, 0.01, 0.21], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: during the batch window, as part of a compliance sweep. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bd68a52483624d46_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0101, 0.101, 0.2626, 0.5556, 0.0707, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b827af4f5d711d9d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.51, 0.39, 0.04, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: across all regions, during an external partner integration. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f5a51e4b5b1a51ae_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.01, 0.49, 0.46], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: in production only, while on-call rotation changed. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8c5ea8f1fad4a22f_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: during the batch window, at the end of the fiscal period. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b6687f174cc9f185_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: over the last hour, mid-incident. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a945668295e4f718_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.03, 0.83, 0.14, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: during the batch window, while on-call rotation changed. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c408e7af0ba3b01f_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: during the batch window, shortly after a software update. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2019fc4fdfc5baaa_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.404, 0.5354, 0.0505, 0.0101], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: in production only, during an external partner integration. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fbe55c81d3079ca8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.52, 0.47, 0.0], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: over the last hour, at the end of the fiscal period. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5a00a871f09e89bb_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.62, 0.16, 0.01, 0.21], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: in production only, during peak load. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f174c7163b0a91f6_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.2, 0.12, 0.02, 0.66], "state": "The log shipper reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: over the last hour, during the morning shift. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ba8f014ff71356c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.17, 0.8, 0.03], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, under reduced staffing. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8a7fb46eb1c83e28_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.64, 0.35, 0.0], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: during the batch window, during peak load. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c1cfa35019e12fc2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.36, 0.6, 0.02], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: during the batch window, during the system migration. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca8dba4dcd1ba083_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.74, 0.22, 0.01, 0.0], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c51953862a36f52a_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: during the batch window, during the system migration. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a4bf61beafe39a67_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during peak load. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bf5d7836c283fcb6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.3, 0.49, 0.18, 0.01], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: in production only, under an active deadline. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c0094f1664e73fe5_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.3, 0.09, 0.13, 0.48], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: during the batch window, at the end of the fiscal period. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9422c330c4144ac1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.03, 0.44, 0.51, 0.01], "state": "The log shipper matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during a scheduled maintenance window. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f230eda2e67546ff_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during the holiday freeze. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_440d56252ff6d322_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.54, 0.45, 0.0], "state": "The log shipper reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: across all regions, under reduced staffing. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a051f3dbede6022f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.49, 0.49, 0.01], "state": "The log shipper correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: across all regions, during an external partner integration. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_485e312d96b768a6_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: in production only, during an external partner integration. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_071a266928eeba09_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.1, 0.21, 0.63, 0.06], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: in production only, while legacy systems are still active. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_57a6ffa2fa805af4_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.44, 0.31, 0.21, 0.04], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: over the last hour, during peak load. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_397746334308f6d5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.53, 0.44, 0.0], "state": "The log shipper matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: during the batch window, during the system migration. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3f0f5aee4c1d740c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.76, 0.22, 0.0, 0.02], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during peak load. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_43083e3d91c8c547_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.01, 0.54, 0.43], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, with a new vendor onboarded. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f230eda2e67546ff_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.36, 0.62, 0.01], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during the holiday freeze. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a4235990da8291af_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: across all regions, while on-call rotation changed. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_43af7cd8ac59d578_n", "kind": "noul", "options": ["false", "true"], "target": [0.23, 0.77], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: over the last hour, under an active deadline. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6d53fb7e00291530_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.4, 0.18, 0.42], "state": "Service catalog-sync lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: in production only, shortly after a software update. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7efce999ad7f183a_n", "kind": "noul", "options": ["false", "true"], "target": [0.65, 0.35], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: over the last hour, during a scheduled maintenance window. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e40ea791579aa67e_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: over the last hour, shortly after a software update. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1528d2a2f47bd904_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.34, 0.64, 0.01], "state": "The log shipper reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: over the last hour, during the holiday freeze. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a57cfce0db3b0427_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.13, 0.8, 0.06, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: in production only, during an external partner integration. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f71aecac8178fd49_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.02, 0.17, 0.8, 0.01], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during a scheduled maintenance window. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_15638b9b736bde40_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.49, 0.47, 0.01], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: in production only, with a new vendor onboarded. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7064f2258799ca77_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.08, 0.47, 0.4, 0.04, 0.0], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: over the last hour, during peak load. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_87c3482f5b2a1dd3_n", "kind": "noul", "options": ["false", "true"], "target": [0.64, 0.36], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: over the last hour, mid-incident. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7a0356cd898b698d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.95, 0.04, 0.0, 0.01], "state": "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, with staffing at reduced levels. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_adadb78e16f3a478_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The log shipper lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: during the batch window, during an external partner integration. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4107636d7031933a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.31, 0.67, 0.01], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: across all regions, with a new vendor onboarded. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6d68242c40d9de68_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.1, 0.5, 0.39, 0.01, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: over the last hour, while legacy systems are still active. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_65ca17f9372e1113_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.94, 0.04, 0.01, 0.01], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: during the batch window, with staffing at reduced levels. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0df354a23be51f0f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.03, 0.11, 0.68, 0.17, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally matches last Tuesday's incident signature. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5264c43db0d2c701_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.01, 0.02, 0.28, 0.64, 0.04], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: in production only, as part of a compliance sweep. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_60c0abbb70fed2e9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.56, 0.43, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: in production only, during the quarterly review. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9a68d716cb05bb30_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: across all regions, mid-incident. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7c6361f77d49fde9_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: across all regions, during an external partner integration. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_adca8a0ea05bc659_n", "kind": "noul", "options": ["false", "true"], "target": [0.66, 0.34], "state": "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.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_987e55620e201bdb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.06, 0.87, 0.07], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, under an active deadline. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_28d34e4dc902e383_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.77, 0.2, 0.02, 0.01], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: across all regions, following a recent audit. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eccf4d2cc0213b5f_n", "kind": "noul", "options": ["false", "true"], "target": [0.54, 0.46], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during a scheduled maintenance window. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_83527f519ef88177_n", "kind": "noul", "options": ["false", "true"], "target": [0.62, 0.38], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: during the batch window, as part of a compliance sweep. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_08456920e5af2956_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: across all regions, immediately after go-live. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2c4f7fb030eff125_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.32, 0.46, 0.21, 0.01], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: in production only, while on-call rotation changed. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4cdad156cf9c9766_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.69, 0.29, 0.01, 0.01], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: in production only, while legacy systems are still active. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_80094e3d5dddb5c0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.88, 0.1, 0.0], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_091896d507eec22b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.28, 0.62, 0.01, 0.09], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: across all regions, during the holiday freeze. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c8089628aeaff1a5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.72, 0.27, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: in production only, during the morning shift. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5f467367354d8ee2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.12, 0.18, 0.51, 0.17, 0.01], "state": "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, during a scheduled maintenance window. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_13144f828cc41e78_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during peak load. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_234b755e1196f814_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.26, 0.73, 0.01], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the morning shift. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5936a91c770c9731_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally flags a step-function change in error slope. Context: over the last hour, under an active deadline. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ad4edc0b0bc17579_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.44, 0.21, 0.02, 0.33], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: over the last hour, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_29b1c08efa168ca1_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: over the last hour, as part of a compliance sweep. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_34bbcf72cba26e7f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.58, 0.02, 0.33, 0.07], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, with a new vendor onboarded. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_baf4d6220323e5a5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.18, 0.79, 0.03], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during peak load. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e2d08655d2028dec_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.41, 0.55, 0.02], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: in production only, mid-incident. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_639dbaf110d21248_n", "kind": "noul", "options": ["false", "true"], "target": [0.65, 0.35], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: during the batch window, following a recent audit. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b90be77501694dc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.36, 0.63, 0.01], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during an external partner integration. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8427d38227d31588_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.52, 0.26, 0.03, 0.19], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: in production only, with staffing at reduced levels. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ba4ac7a5ef0c9344_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.17, 0.01, 0.26, 0.56], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f25b1409884691c8_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.18, 0.23, 0.55, 0.04], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ac9bbe311a4a14ee_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, while legacy systems are still active. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_539d16d0ced0c1d7_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.51, 0.2, 0.14, 0.15], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_99a807a1dff5a047_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.0, 0.46, 0.53], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: across all regions, during a scheduled maintenance window. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cb5f8301b187a435_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: in production only, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f8119d431f51d5a4_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.64, 0.32, 0.0, 0.04], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during normal operations. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_68663830b170d3e6_n", "kind": "noul", "options": ["false", "true"], "target": [0.22, 0.78], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: across all regions, mid-incident. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_868bc1367e40c7b1_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: in production only, while legacy systems are still active. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_daa4d26635198b5e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.92, 0.05, 0.03, 0.0], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during the quarterly review. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3ed77c902cb513e4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.53, 0.45, 0.01], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: in production only, while on-call rotation changed. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_224fa9977b916206_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during a scheduled maintenance window. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5669f50f0831c0f7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.56, 0.43, 0.0], "state": "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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_766c5de04e34fd1c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.12, 0.01, 0.04, 0.83], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: in production only, at the end of the fiscal period. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_19933be1a64d35aa_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.67, 0.33, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: during the batch window, under an active deadline. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_74c16b94646863db_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.15, 0.8, 0.05], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: across all regions, during the quarterly review. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_448a13b1040cc306_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: in production only, during peak load. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_08adbaf45c80c98f_n", "kind": "noul", "options": ["false", "true"], "target": [0.7, 0.3], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during peak load. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4e0e9f5518bfb29f_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "The log shipper flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: over the last hour, during the morning shift. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b50f44447cbe894c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.31, 0.01, 0.07, 0.61], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: in production only, with staffing at reduced levels. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_929cdb50e988d398_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: during the batch window, shortly after a software update. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_988e5797e485e4c0_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.01, 0.49, 0.47], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: during the batch window, during the morning shift. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c5dc4663b70cf323_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: during the batch window, shortly after a software update. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c6ba71f63fc6f142_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.53, 0.06, 0.04, 0.37], "state": "The log shipper shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: during the batch window, under an active deadline. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b0df5c416572d945_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.44, 0.45, 0.09, 0.02], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during an external partner integration. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6f26a11ee442fa08_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.79, 0.17, 0.01, 0.03], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during the holiday freeze. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7efce999ad7f183a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.46, 0.4, 0.12, 0.02], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: over the last hour, during a scheduled maintenance window. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7ab84fd2ae8f6b8a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.13, 0.01, 0.24, 0.62], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: over the last hour, with a new vendor onboarded. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ff7ceb3dfc41c44d_n", "kind": "noul", "options": ["false", "true"], "target": [0.9, 0.1], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: over the last hour, during the morning shift. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_66bb7c13ab3eebe2_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: across all regions, while legacy systems are still active. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5219773b91ab11e3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.04, 0.84, 0.12, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: during the batch window, while on-call rotation changed. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5c5597af9d332f68_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.83, 0.14, 0.03, 0.0], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: during the batch window, during the holiday freeze. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_571e7ac77aa147fc_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.9, 0.06, 0.0, 0.04], "state": "The log shipper shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4b3f9b34813daa14_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.12, 0.02, 0.14, 0.72], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, at the end of the fiscal period. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_71c948f698498ece_n", "kind": "noul", "options": ["false", "true"], "target": [0.61, 0.39], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: over the last hour, while legacy systems are still active. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_619efcbc566a9e25_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.55, 0.37, 0.03, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: in production only, at the end of the fiscal period. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c26fd5e560a04499_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: in production only, immediately after go-live. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_52b2650c3ba43b93_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, immediately after go-live. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1984e9933d68155f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.38, 0.46, 0.14, 0.02], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: in production only, during a scheduled maintenance window. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_961b0853111a061d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.03, 0.76, 0.21], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, mid-incident. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4b93bcb1a0d92877_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.94, 0.03, 0.01, 0.02], "state": "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 monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e02693215c5a56a6_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.24, 0.06, 0.05, 0.65], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: over the last hour, under an active deadline. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_17f11895cf0d4697_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.71, 0.28, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: in production only, with a new vendor onboarded. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e9f19f49c216e469_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.07, 0.83, 0.1], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, immediately after go-live. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2953a8e88794cc2d_n", "kind": "noul", "options": ["false", "true"], "target": [0.91, 0.09], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, shortly after a software update. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c19c21d2a608da19_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.84, 0.15, 0.01, 0.0], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: across all regions, while on-call rotation changed. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_48bba1ea6b87b3a1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.7, 0.28, 0.0], "state": "The log shipper reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: across all regions, during the system migration. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_31041d976e2fc465_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.37, 0.45, 0.03, 0.15], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4116a2f73272e25f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.57, 0.41], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: across all regions, during an external partner integration. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8e3cc5c08a03272b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.67, 0.32, 0.0], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: across all regions, at the end of the fiscal period. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_37024efe4bc0be10_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "The metrics pipeline correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: in production only, immediately after go-live. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_afb3603dd1abfd50_n", "kind": "noul", "options": ["false", "true"], "target": [0.47, 0.53], "state": "Service catalog-sync 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 supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d8bdb2b83fda02ea_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.65, 0.34, 0.0], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: over the last hour, with staffing at reduced levels. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b9fa97166bf14d04_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.42, 0.56, 0.01], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: in production only, with staffing at reduced levels. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_04e8f5cd7285c3f5_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: over the last hour, as part of a compliance sweep. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ab7a336100c02c62_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: over the last hour, under an active deadline. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f07d96a3d1239c81_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.16, 0.3, 0.48, 0.05, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: during the batch window, during peak load. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e032e061bd2cd86b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.1, 0.85, 0.05], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: over the last hour, under an active deadline. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2c91e806795c3fd8_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.25, 0.68, 0.07, 0.0], "state": "The metrics pipeline flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: across all regions, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7d37fbf63f0dee75_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.31, 0.68, 0.01], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: during the batch window, while legacy systems are still active. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4ad997a34ce9a3c9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.4, 0.02, 0.03, 0.55], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during the morning shift. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3fab96fe7c171b12_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.26, 0.66, 0.0, 0.08], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: across all regions, under an active deadline. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4462f40a0f6049b7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.09, 0.78, 0.13, 0.0, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: across all regions, following a recent audit. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bd68a52483624d46_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d99970ae3f1a446d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.16, 0.81, 0.03], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during peak load. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_74db072d9fbe9f88_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.65, 0.15, 0.04, 0.16], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: in production only, at the end of the fiscal period. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5b2deedde26fa3f5_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: in production only, with a new vendor onboarded. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cc121195183773d4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.01, 0.02, 0.39, 0.56, 0.01], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: in production only, under an active deadline. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e6acfb6b116f5df8_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.37, 0.58, 0.02, 0.03], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: over the last hour, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_637cd14b331077a7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.25, 0.74, 0.01], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, immediately after go-live. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_671d511c1c777f75_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: in production only, during peak load. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2320f5aecd351132_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: in production only, with a new vendor onboarded. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_00dfb172536b037c_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: during the batch window, at the end of the fiscal period. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9369bd6376078484_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.83, 0.16, 0.01], "state": "Service catalog-sync correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: during the batch window, shortly after a software update. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4634ee08a504a0fb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.15, 0.81, 0.04], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: across all regions, during the holiday freeze. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a744cd6437e7c82f_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "The log shipper shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: during the batch window, while on-call rotation changed. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a77790d1ab9b167d_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "Service catalog-sync correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: over the last hour, with a new vendor onboarded. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_33ff6bc9795e087c_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: in production only, while legacy systems are still active. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a4be6fe8811ae7c1_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "The log shipper shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: over the last hour, while on-call rotation changed. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7cc84cecf82b5ec6_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.04, 0.27, 0.64, 0.05], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: across all regions, during a scheduled maintenance window. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4049b2027d639a83_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: across all regions, during the quarterly review. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bff5b66b8f8b665b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.46, 0.48, 0.01], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: over the last hour, following a recent audit. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_280735b7c9e3176f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.18, 0.1, 0.22, 0.5], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during the holiday freeze. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_17c7e4a4a80c79d3_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "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 review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fbecda3cf5eef00f_n", "kind": "noul", "options": ["false", "true"], "target": [0.23, 0.77], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: over the last hour, while on-call rotation changed. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_49bec1a0a15e0f83_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.15, 0.2, 0.58, 0.07, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: in production only, during a scheduled maintenance window. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4e27d9c356ed44bc_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.92, 0.07, 0.01, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: over the last hour, during peak load. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6fd9db363f662240_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "The log shipper flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during an external partner integration. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_50b255c398ac3750_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.52, 0.37, 0.1, 0.01], "state": "The log shipper correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, as part of a compliance sweep. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_971982240c76a7a1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.52, 0.45, 0.01, 0.02], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: across all regions, following a recent audit. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8fa997048398aa91_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: across all regions, during the holiday freeze. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_01c3e7bc20a468cc_n", "kind": "noul", "options": ["false", "true"], "target": [0.6, 0.4], "state": "The log shipper returned to baseline after 11 minutes; additionally matches last Tuesday's incident signature. Context: during the batch window, under an active deadline. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7229b2df6cfa304a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.03, 0.7, 0.26, 0.0], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during the system migration. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cd2837ca730e63eb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.43, 0.55, 0.01], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: over the last hour, following a recent audit. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5037335403753775_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.07, 0.57, 0.36, 0.0], "state": "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, with a new vendor onboarded. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5643c936177f0ea7_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: across all regions, during a scheduled maintenance window. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b5c37c44cf8ce1ca_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5f467367354d8ee2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.11, 0.0, 0.09, 0.8], "state": "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, during a scheduled maintenance window. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4e7bc91902129acb_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "The log shipper correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: across all regions, during an external partner integration. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a54a770ab43ec38f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.35, 0.63, 0.01], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2b1162807cb82ecf_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.25, 0.13, 0.03, 0.59], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during the holiday freeze. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b8cc3cd06a9ebaf2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.91, 0.0, 0.05, 0.04], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during an external partner integration. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ad4edc0b0bc17579_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.36, 0.64, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: over the last hour, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_60afcd5960d0a748_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.02, 0.03, 0.39, 0.49, 0.06], "state": "The metrics pipeline correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: across all regions, during normal operations. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_76a826f3f2704ba8_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.21, 0.71, 0.08, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: during the batch window, under reduced staffing. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8caeff8b6b8dd133_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.92, 0.06, 0.01, 0.01], "state": "The log shipper flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: across all regions, under an active deadline. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8facfb2d805b6094_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_88c3e6db5bc225ed_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.78, 0.2, 0.01, 0.01], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: in production only, as part of a compliance sweep. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dc3510bf787a8839_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0101, 0.0808, 0.5657, 0.3333, 0.0101], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: in production only, under an active deadline. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_456a1d1c0045078a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.31, 0.66, 0.02], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: across all regions, under reduced staffing. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a3c8c3db4c9a575d_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during an external partner integration. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_823dc7ff82c23dff_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.88, 0.05, 0.05, 0.02], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: in production only, under an active deadline. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5e9d952bf9dc08d7_n", "kind": "noul", "options": ["false", "true"], "target": [0.38, 0.62], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: in production only, during a scheduled maintenance window. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ee3e059761003426_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.52, 0.46, 0.02, 0.0], "state": "The metrics pipeline flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: during the batch window, during the holiday freeze. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a45690d299e1f2a6_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: in production only, mid-incident. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_33beea01e265dd74_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.07, 0.31, 0.01, 0.61], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: over the last hour, immediately after go-live. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b6e57017b17b04be_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.68, 0.25, 0.03, 0.04], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, while legacy systems are still active. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_831ed8c8932bcf7c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.18, 0.79, 0.03], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: in production only, during an external partner integration. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9b8adf337dc171bb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.33, 0.58, 0.09, 0.0, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: across all regions, during the morning shift. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_52faf49e5db7130b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.4, 0.6, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: over the last hour, with staffing at reduced levels. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ea71e8c67d2fa6df_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.01, 0.09, 0.85], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the holiday freeze. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_04b9059eddd942ca_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.16, 0.79, 0.05], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, under an active deadline. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_115d67f8d0032042_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.41, 0.23, 0.35, 0.01], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_db769b16385b31ad_n", "kind": "noul", "options": ["false", "true"], "target": [0.91, 0.09], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, at the end of the fiscal period. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6b9eb51da91f5a45_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.01, 0.02, 0.32, 0.62, 0.02], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: in production only, during the holiday freeze. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a048eae1fe84eb0b_n", "kind": "noul", "options": ["false", "true"], "target": [0.37, 0.63], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, following a recent audit. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3b76ef23efbfb7e8_n", "kind": "noul", "options": ["false", "true"], "target": [0.65, 0.35], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: across all regions, under reduced staffing. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_524d05f2f50ba232_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: over the last hour, following a recent audit. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0054e34ce95304aa_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "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, during the morning shift. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5a3646aa4cab7454_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.46, 0.54, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: in production only, under an active deadline. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c8c4fc083424ebda_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: in production only, shortly after a software update. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b3a6eb992b3c23ac_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.6, 0.37, 0.02, 0.01], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during normal operations. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1cf12e67961973be_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: across all regions, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9af65b32402d2397_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.0, 0.29, 0.68, 0.03], "state": "Service catalog-sync lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: during the batch window, during a scheduled maintenance window. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8849fd2195514c3e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.77, 0.2, 0.02, 0.01], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: over the last hour, during the system migration. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4bba3cc77a32e022_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.23, 0.07, 0.37, 0.33], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: during the batch window, during the quarterly review. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9c549c42833a7d2d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.17, 0.59, 0.23, 0.01], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: in production only, during normal operations. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_adbd78996de24721_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.29, 0.53, 0.12, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: in production only, immediately after go-live. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_60141a44e3b59106_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: across all regions, during normal operations. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_93ef5a84e6de6317_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.22, 0.25, 0.53, 0.0], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: across all regions, mid-incident. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_57b179edc1fdbf9a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.15, 0.48, 0.36, 0.01], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: in production only, following a recent audit. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ae50ac925428e3aa_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.34, 0.65, 0.01], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during normal operations. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7f682765c191dd2e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.52, 0.47, 0.0], "state": "The log shipper matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: over the last hour, during the system migration. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_913f928375b74eb2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.02, 0.61, 0.36], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: in production only, mid-incident. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_542d64ee8fc2efa3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.26, 0.63, 0.07, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: in production only, during the holiday freeze. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4789c62be23dc7ce_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.72, 0.23, 0.01, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: during the batch window, during the quarterly review. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f37927b79739b925_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.72, 0.26, 0.0], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: during the batch window, with staffing at reduced levels. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_47cbadcb91c14c54_n", "kind": "noul", "options": ["false", "true"], "target": [0.66, 0.34], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: in production only, under reduced staffing. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_07812d4509d1fe25_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.69, 0.3, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: in production only, following a recent audit. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0cb3257fe2e1fb80_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.08, 0.76, 0.16, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the morning shift. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eb0785a3ad41025b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.39, 0.51, 0.09, 0.0], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: in production only, shortly after a software update. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_324d5e3696d6ee1c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.58, 0.3, 0.1, 0.02], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: across all regions, under an active deadline. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1a95450d51ad667c_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "The log shipper shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: during the batch window, mid-incident. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_17f11895cf0d4697_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "The log shipper lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: in production only, with a new vendor onboarded. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0410c076b8450bc0_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, with a new vendor onboarded. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f8b5603a91f7e25f_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, following a recent audit. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1902c7f37ac21995_n", "kind": "noul", "options": ["false", "true"], "target": [0.17, 0.83], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: in production only, with a new vendor onboarded. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_11296670f77e65ee_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: across all regions, while on-call rotation changed. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c8208014ec0d2544_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.0, 0.0, 0.98, 0.02], "state": "The log shipper returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during normal operations. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_64d7a37807ff6ffd_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.61, 0.29, 0.09, 0.01], "state": "The log shipper shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: across all regions, mid-incident. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c64436abad062a67_n", "kind": "noul", "options": ["false", "true"], "target": [0.39, 0.61], "state": "The log shipper shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: across all regions, during an external partner integration. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_76240ce864fa82d0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.02, 0.31, 0.63, 0.03], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: over the last hour, during the system migration. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d334d1d6b4e3fd1e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.08, 0.48, 0.39, 0.05, 0.0], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: over the last hour, immediately after go-live. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cb7a1f2564ba7d2e_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, immediately after go-live. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6c38529665fae474_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.13, 0.73, 0.13, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: in production only, under an active deadline. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ae322b5b8bb607cc_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.97, 0.0, 0.01, 0.02], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during the morning shift. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5d4c4393282ef084_n", "kind": "noul", "options": ["false", "true"], "target": [0.49, 0.51], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: across all regions, while legacy systems are still active. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3a175b815d50ffa3_n", "kind": "noul", "options": ["false", "true"], "target": [0.5, 0.5], "state": "The log shipper lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: in production only, at the end of the fiscal period. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0050c0907da73be7_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The log shipper reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: during the batch window, shortly after a software update. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d9612a4b0af2378d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.64, 0.31, 0.05, 0.0], "state": "The metrics pipeline shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: in production only, with staffing at reduced levels. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_73a30f32ebe7d993_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.21, 0.7, 0.03, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: in production only, as part of a compliance sweep. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_303e9f767d4dd8c7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.08, 0.62, 0.2, 0.1, 0.0, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: across all regions, shortly after a software update. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5186af0fc495ef1f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.22, 0.75, 0.03], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: in production only, during normal operations. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_15ccc3ec72d606b9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.48, 0.51, 0.0], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: in production only, during the quarterly review. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_11e67c763449ec23_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: during the batch window, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_50b80b47106921e4_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.67, 0.3, 0.02, 0.01], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: over the last hour, while on-call rotation changed. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9b5204cab2d65615_n", "kind": "noul", "options": ["false", "true"], "target": [0.37, 0.63], "state": "Node pgsql-14 flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: during the batch window, during a scheduled maintenance window. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3f1ba5d6127f05e1_n", "kind": "noul", "options": ["false", "true"], "target": [0.71, 0.29], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: over the last hour, during the system migration. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f814e07b9e13b64a_n", "kind": "noul", "options": ["false", "true"], "target": [0.47, 0.53], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, with a new vendor onboarded. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ff7506f888122260_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, while legacy systems are still active. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b0310969d677d5b2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.6, 0.37, 0.0, 0.03], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: in production only, immediately after go-live. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7e5f931b938925e4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.07, 0.86, 0.07], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: during the batch window, under an active deadline. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3383044f30987e33_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during a scheduled maintenance window. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a33cd9a8d60f3115_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.27, 0.71, 0.01], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: in production only, with a new vendor onboarded. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6b5407b8a233c55b_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally matches last Tuesday's incident signature. Context: over the last hour, with a new vendor onboarded. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_18fda9a7e70ed3b2_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: in production only, while on-call rotation changed. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0c997215de6741f8_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.92, 0.0, 0.0, 0.08], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during the holiday freeze. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_10f6ba45bc3f7a9a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.24, 0.72, 0.03], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during the holiday freeze. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bf1d34869654cbbf_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.35, 0.64, 0.01], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: across all regions, at the end of the fiscal period. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c723ab66964f0420_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.32, 0.55, 0.09, 0.0], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: in production only, mid-incident. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f3ccfadce8fe470a_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The log shipper flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: in production only, as part of a compliance sweep. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a2498889afa24083_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.22, 0.09, 0.07, 0.62], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: in production only, immediately after go-live. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2670c947e9e3c315_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.46, 0.51, 0.01], "state": "The log shipper matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: during the batch window, mid-incident. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_98a33d5a00a81ead_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.38, 0.24, 0.05, 0.33], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the holiday freeze. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d39019ef922da8d3_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.54, 0.41, 0.04, 0.01], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: across all regions, during the system migration. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_166ecf06764ef351_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.25, 0.74, 0.01], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during the system migration. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_539d16d0ced0c1d7_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_151f039ab5db2c82_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: in production only, under reduced staffing. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_35cd9c5560429633_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.83, 0.13, 0.02, 0.02], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: over the last hour, shortly after a software update. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9a3a2daba1880fa2_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: in production only, mid-incident. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1e989f2d86f5bad6_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.09, 0.25, 0.62], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: across all regions, at the end of the fiscal period. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_681e0bca6ec34e87_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.12, 0.7, 0.15, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: during the batch window, as part of a compliance sweep. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b1534353421146be_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.14, 0.79, 0.06, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: in production only, under reduced staffing. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7ab84fd2ae8f6b8a_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: over the last hour, with a new vendor onboarded. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_90f8f512ad2150a1_n", "kind": "noul", "options": ["false", "true"], "target": [0.4, 0.6], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: over the last hour, as part of a compliance sweep. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b5c37c44cf8ce1ca_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0303, 0.5657, 0.3333, 0.0707, 0.0], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_206be403f749e738_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.46, 0.39, 0.13, 0.0], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: across all regions, with staffing at reduced levels. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_059431d566345957_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d0548f550cd06916_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.47, 0.33, 0.18, 0.01], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during peak load. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6f7469e5d8b071cb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.09, 0.87, 0.04], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: during the batch window, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1a4814e94cce0b1d_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The log shipper reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: across all regions, immediately after go-live. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d39e9991e68ccf11_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "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 holiday freeze. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_914c0743867989c6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.23, 0.7, 0.04, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: in production only, during the quarterly review. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c565dc0ad178473f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.03, 0.52, 0.43, 0.01], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: across all regions, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_25b6653b60b2bc3f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.28, 0.71, 0.01, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: in production only, during the quarterly review. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ad1368e5a5750bc_n", "kind": "noul", "options": ["false", "true"], "target": [0.5, 0.5], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: during the batch window, during peak load. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cf6e6eb7aa805c62_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.6, 0.4, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: across all regions, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ea0fc2273e239065_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.17, 0.64, 0.18], "state": "The log shipper matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: across all regions, during an external partner integration. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9a68d716cb05bb30_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.31, 0.61, 0.01, 0.07], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: across all regions, mid-incident. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5dac6b76785e32f7_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, under reduced staffing. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aa4d8d773423cce2_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.81, 0.19, 0.0, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: in production only, shortly after a software update. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_29408bc9bb283b5e_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Node pgsql-14 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.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e78804c7e8aa71c1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.31, 0.53, 0.15, 0.01], "state": "The log shipper shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: during the batch window, while legacy systems are still active. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d3681233b25a784b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.24, 0.75, 0.01], "state": "The log shipper reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: during the batch window, under reduced staffing. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_615553075730ea30_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, shortly after a software update. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9f4ef17bace861c4_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.77, 0.01, 0.21, 0.01], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: over the last hour, with a new vendor onboarded. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_91549f3bc93c3dc1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.68, 0.01, 0.27], "state": "The metrics pipeline flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: during the batch window, shortly after a software update. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8a4d54f75f485657_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.37, 0.61], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: in production only, during the morning shift. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_20ea0a82af75b82e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.5, 0.49, 0.0], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: over the last hour, with staffing at reduced levels. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_151f039ab5db2c82_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.56, 0.0, 0.07, 0.37], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: in production only, under reduced staffing. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_daf4a129c3d845c3_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: across all regions, during an external partner integration. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dfd85ae7205acc7b_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: across all regions, during the system migration. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c2ab008b554293c9_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: over the last hour, shortly after a software update. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_78b30afe085a4e3c_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally matches last Tuesday's incident signature. Context: across all regions, mid-incident. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a0528e186c5ef986_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.32, 0.64, 0.03], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: over the last hour, during the morning shift. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_74e48815b9763eb5_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.02, 0.47, 0.43, 0.08], "state": "The log shipper matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: over the last hour, at the end of the fiscal period. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e709f3d55bcce818_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.05, 0.53, 0.39, 0.01], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: over the last hour, as part of a compliance sweep. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0a638fbb87921849_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.51, 0.48, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: over the last hour, during the holiday freeze. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_02ea75e1250dbc31_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.37, 0.29, 0.33, 0.01], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during the system migration. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ac0593ef408a0576_n", "kind": "noul", "options": ["false", "true"], "target": [0.57, 0.43], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: across all regions, while on-call rotation changed. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_271cad5572ad01d4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.12, 0.84, 0.04], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, with staffing at reduced levels. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_992c93647f6ea09c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.54, 0.45, 0.0], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: over the last hour, while legacy systems are still active. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5125af1af577d1f0_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.63, 0.29, 0.05, 0.03], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: across all regions, during normal operations. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c8d3a88ec4e4ab77_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: during the batch window, during an external partner integration. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c1a96edb63a5a8de_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during the holiday freeze. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2551c0b08cab3e12_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.19, 0.73, 0.04, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: during the batch window, mid-incident. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_99f3d2731b2ce39a_n", "kind": "noul", "options": ["false", "true"], "target": [0.37, 0.63], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during normal operations. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_81bd92ca93f66a16_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: across all regions, during normal operations. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d5772b840b4ab866_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: over the last hour, while on-call rotation changed. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_25bcac4ec77a1283_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: in production only, with a new vendor onboarded. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_36923e671b026ebe_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: over the last hour, during peak load. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9eb51876d64dd7ff_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.2, 0.28, 0.28, 0.24], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: across all regions, during a scheduled maintenance window. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cf6cb184dff48a8e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.04, 0.75, 0.2, 0.01], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during normal operations. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9f0becfd17c7b108_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.45, 0.11, 0.01, 0.43], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during a scheduled maintenance window. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e464111270074045_n", "kind": "noul", "options": ["false", "true"], "target": [0.91, 0.09], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: across all regions, mid-incident. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7d2ae47cf67ccc60_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.0, 0.01, 0.97], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: in production only, mid-incident. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e151901d0a38d868_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.37, 0.63, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: in production only, while legacy systems are still active. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_29d8e6db5da11b07_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.22, 0.26, 0.34, 0.18], "state": "The log shipper shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: across all regions, while on-call rotation changed. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0401571343adeda6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.33, 0.64, 0.02], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: across all regions, during normal operations. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1e989f2d86f5bad6_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: across all regions, at the end of the fiscal period. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7b26e564228e0ff7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.63, 0.27, 0.04, 0.0], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: in production only, while legacy systems are still active. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f52cf80f03b2f473_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.97, 0.0, 0.0, 0.03], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: over the last hour, while on-call rotation changed. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0f5a1fab444e6257_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.26, 0.72], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: across all regions, while on-call rotation changed. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bce89431712dd5fb_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: across all regions, under an active deadline. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_07155236268c03f8_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.22, 0.31, 0.1, 0.37], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during the system migration. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_17e68c1d16b7a83e_n", "kind": "noul", "options": ["false", "true"], "target": [0.23, 0.77], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: across all regions, during the system migration. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4d773927ceb8ea33_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.17, 0.71, 0.11, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, immediately after go-live. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b55301be242f245c_n", "kind": "noul", "options": ["false", "true"], "target": [0.39, 0.61], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: during the batch window, during an external partner integration. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8a7fb46eb1c83e28_n", "kind": "noul", "options": ["false", "true"], "target": [0.65, 0.35], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: during the batch window, during peak load. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9ea1da6b72b93ddf_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.48, 0.51, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the holiday freeze. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6251472988c03c1a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.61, 0.04, 0.0, 0.35], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: over the last hour, mid-incident. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e59e0e38df36c629_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.45, 0.54, 0.0], "state": "The log shipper reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: over the last hour, during peak load. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b29a0c843627ccb2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.42, 0.56], "state": "The log shipper returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: across all regions, during normal operations. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_04bc125e78dcf00e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.41, 0.49, 0.05, 0.0], "state": "Service catalog-sync flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: over the last hour, mid-incident. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0a15b7e22dde6c69_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: over the last hour, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_898a558af9a0d38a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.27, 0.7, 0.02], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during the holiday freeze. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5b4ce7af387d2730_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the system migration. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_512a73e3b12d522d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.24, 0.74, 0.02], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during normal operations. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c1f63eda4321999c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.28, 0.45, 0.26, 0.01], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: across all regions, mid-incident. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_268890b8a75f59ff_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.33, 0.62, 0.01, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: during the batch window, under reduced staffing. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ee30c52a1ded9efc_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: over the last hour, at the end of the fiscal period. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e1dff98db0212cab_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.46, 0.54, 0.0], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: over the last hour, with a new vendor onboarded. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c54e3cef59095df1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.34, 0.65, 0.01], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: in production only, at the end of the fiscal period. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d9032299425a26a2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.06, 0.49, 0.14, 0.31], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: over the last hour, immediately after go-live. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_add6b868ab30f64a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.27, 0.07, 0.16, 0.5], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during the quarterly review. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fed5e0810b51ddc1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.21, 0.74, 0.04], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: in production only, during a scheduled maintenance window. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_237ffdae5de8e1b8_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.57, 0.37, 0.06, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: across all regions, under reduced staffing. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fb97f777761f5ea2_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The log shipper returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: across all regions, during an external partner integration. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8c5ea8f1fad4a22f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.51, 0.48, 0.01], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: during the batch window, at the end of the fiscal period. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bd4bc9d6d0960f40_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: across all regions, with staffing at reduced levels. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_07d520da86ff2650_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: over the last hour, under an active deadline. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d79633f8c7941787_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.94, 0.0, 0.0, 0.06], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, under an active deadline. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9fce8279a8f3a908_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during peak load. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fbecda3cf5eef00f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.71, 0.01, 0.16, 0.12], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: over the last hour, while on-call rotation changed. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fe6798482bfc6dea_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.54, 0.43, 0.03, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: during the batch window, at the end of the fiscal period. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_722cea58faba7f60_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.0, 0.68, 0.31], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: across all regions, at the end of the fiscal period. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca65bf31326b313d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.72, 0.21, 0.05, 0.02], "state": "The log shipper shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: over the last hour, while legacy systems are still active. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c08d0b0439f2bba3_n", "kind": "noul", "options": ["false", "true"], "target": [0.7, 0.3], "state": "Service catalog-sync flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: during the batch window, during the holiday freeze. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b7932b2beafa05ca_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.86, 0.13, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: in production only, during the quarterly review. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9792ab8840958b1e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.09, 0.68, 0.19, 0.0], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: during the batch window, during the system migration. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_914bf5b99076b96c_n", "kind": "noul", "options": ["false", "true"], "target": [0.5, 0.5], "state": "The log shipper reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: across all regions, during the morning shift. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_91c596a7efc2f706_n", "kind": "noul", "options": ["false", "true"], "target": [0.67, 0.33], "state": "The log shipper lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: over the last hour, while on-call rotation changed. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e3e3679d054cba97_n", "kind": "noul", "options": ["false", "true"], "target": [0.54, 0.46], "state": "The log shipper lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: across all regions, with a new vendor onboarded. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4107636d7031933a_n", "kind": "noul", "options": ["false", "true"], "target": [0.37, 0.63], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: across all regions, with a new vendor onboarded. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b6b4fa8b8e64abc7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.1717, 0.8182, 0.0101], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: during the batch window, immediately after go-live. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dec1b0bdd7cc54bf_n", "kind": "noul", "options": ["false", "true"], "target": [0.43, 0.57], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: across all regions, following a recent audit. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7cc38c6039be78ed_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The log shipper reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: in production only, during the holiday freeze. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0e88d6bc464c7ea2_n", "kind": "noul", "options": ["false", "true"], "target": [0.19, 0.81], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: in production only, during the quarterly review. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d00afddde3c90466_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: in production only, immediately after go-live. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2e726eb914bac300_n", "kind": "noul", "options": ["false", "true"], "target": [0.4, 0.6], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: during the batch window, mid-incident. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c586de37fdbd4980_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.3, 0.69, 0.01], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: across all regions, during peak load. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b6bae954cee8b3d_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The log shipper flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: during the batch window, while on-call rotation changed. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_43c9c97b906f0eb3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.11, 0.28, 0.57, 0.04, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, with staffing at reduced levels. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c2227aeade41dedc_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.27, 0.26, 0.23, 0.24], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: during the batch window, during an external partner integration. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c9f4f3cfde85f2b5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.65, 0.34, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: during the batch window, following a recent audit. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bad31f7da30df058_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: in production only, while on-call rotation changed. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9158e154d727eeb3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.48, 0.48, 0.01], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: in production only, during normal operations. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a5813840f23e3054_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.89, 0.08, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: in production only, shortly after a software update. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9d52780aed8ad930_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: in production only, during the system migration. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a649a716eddcc566_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: across all regions, under reduced staffing. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_041f72d06d7bda47_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.44, 0.55, 0.0], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: across all regions, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2a208ac07afc7b0f_n", "kind": "noul", "options": ["false", "true"], "target": [0.42, 0.58], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: in production only, as part of a compliance sweep. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f7d57590bd644635_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: across all regions, under an active deadline. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2251e74fea8f70c1_n", "kind": "noul", "options": ["false", "true"], "target": [0.22, 0.78], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, under an active deadline. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2308046dcdeaacee_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.02, 0.44, 0.49], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: during the batch window, during the system migration. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_51e5daf9cf251ae9_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: in production only, following a recent audit. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a767b3c09a149c00_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Service catalog-sync lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: in production only, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cad6163bd0701d43_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Service catalog-sync correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: in production only, as part of a compliance sweep. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dde53effbf8fe07b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.65, 0.25, 0.08, 0.02], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, while on-call rotation changed. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f1313939091f7e4c_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "Service catalog-sync correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: in production only, during the holiday freeze. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_33adf4a905c2775e_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "The log shipper lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: across all regions, during an external partner integration. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b198d34bc3990fb9_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: over the last hour, as part of a compliance sweep. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7cb48a73714989e5_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: over the last hour, immediately after go-live. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_603080b4e413b5b3_n", "kind": "noul", "options": ["false", "true"], "target": [0.52, 0.48], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: over the last hour, immediately after go-live. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cd0cd6709908bf4d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.11, 0.66, 0.22, 0.01, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: in production only, immediately after go-live. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_61479a0db281dce8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.12, 0.65, 0.22, 0.0], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: over the last hour, shortly after a software update. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d5f5748cc374dc99_n", "kind": "noul", "options": ["false", "true"], "target": [0.19, 0.81], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: during the batch window, following a recent audit. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7cdeca455a794b68_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: over the last hour, with a new vendor onboarded. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fa23cf9ae529de09_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.73, 0.03, 0.2], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: in production only, shortly after a software update. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_84a924b6600662ec_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "The log shipper shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: during the batch window, during a scheduled maintenance window. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_56a9c3acbff7a655_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "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 operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e82dbf70cbabfdee_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.92, 0.01, 0.0, 0.07], "state": "The log shipper matches last Tuesday's incident signature; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during peak load. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_198397f6e8c8771d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.48, 0.02, 0.22, 0.28], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ee31bb406560e2c8_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.95, 0.0, 0.0, 0.05], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: in production only, following a recent audit. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4cfa80aef832f05a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.21, 0.76, 0.03], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: over the last hour, under an active deadline. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8d17287b2f3d1eab_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.18, 0.8, 0.02], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, at the end of the fiscal period. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d5bb62c28ad9e0c3_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: over the last hour, during the holiday freeze. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6cf8107ef036082b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.31, 0.62, 0.04, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: over the last hour, with staffing at reduced levels. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6692ec315001119e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.32, 0.1, 0.11, 0.47], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during the quarterly review. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b93b35610674efd5_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: in production only, with a new vendor onboarded. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d7d47c83f6586b9a_n", "kind": "noul", "options": ["false", "true"], "target": [0.63, 0.37], "state": "The metrics pipeline shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: in production only, during an external partner integration. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9ea1da6b72b93ddf_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.6, 0.37, 0.01, 0.02], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the holiday freeze. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e5eaefe4a478309a_n", "kind": "noul", "options": ["false", "true"], "target": [0.39, 0.61], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4fb099f8520ab2dd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.58, 0.33, 0.06, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: over the last hour, at the end of the fiscal period. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c6ba71f63fc6f142_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.48, 0.51, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: during the batch window, under an active deadline. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_76588361c48cd90d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.08, 0.01, 0.49, 0.42], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: in production only, under reduced staffing. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b429f5acc715ca5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.22, 0.61, 0.12, 0.05, 0.0, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: over the last hour, during the system migration. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2c007464ba666846_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.78, 0.19, 0.0], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: across all regions, during the system migration. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d01f6b8a39b5a531_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.95, 0.02, 0.0, 0.03], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: over the last hour, immediately after go-live. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_446e1db3767a6605_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.35, 0.02, 0.32, 0.31], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: across all regions, during peak load. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_980f9f9f1ccd2df3_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.52, 0.42, 0.06, 0.0], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: during the batch window, during peak load. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cfcd325c837c3536_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.13, 0.31, 0.51, 0.05], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: during the batch window, under an active deadline. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f13755e097ab6e98_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.06, 0.16, 0.15, 0.63], "state": "The metrics pipeline flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: in production only, following a recent audit. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_90f8f512ad2150a1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.16, 0.52, 0.3, 0.02, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: over the last hour, as part of a compliance sweep. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8a4d54f75f485657_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: in production only, during the morning shift. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_12fd89e71c258770_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.69, 0.2, 0.1, 0.01], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: across all regions, during peak load. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b2e688e24a31e3d3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.44, 0.46, 0.05, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: during the batch window, under reduced staffing. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a151b1edfba19449_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: during the batch window, during the holiday freeze. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4228aaa2e56970be_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.1, 0.4, 0.49, 0.01], "state": "The log shipper correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during normal operations. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_320b1face70bdbab_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.09, 0.52, 0.33, 0.05, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: across all regions, as part of a compliance sweep. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_48ee605a64b55f7b_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "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.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_24527d2fbc5c5385_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, with staffing at reduced levels. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f43efce8babe58d6_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the morning shift. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8cbb1880d9d0f08d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.22, 0.76, 0.02], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, following a recent audit. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6a129659707217e9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.13, 0.01, 0.77, 0.09], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4542a142423301c6_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: over the last hour, following a recent audit. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2e01d35226147b45_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.17, 0.66, 0.16, 0.0], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: in production only, while on-call rotation changed. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_84264dcf7eb51ac4_n", "kind": "noul", "options": ["false", "true"], "target": [0.68, 0.32], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: during the batch window, following a recent audit. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ede64889bb55c0c4_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: over the last hour, during the quarterly review. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e626b6f2c18bb8e9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.13, 0.05, 0.14, 0.68], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: over the last hour, under reduced staffing. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9c49de523bb303a3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.07, 0.84, 0.09], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally flags a step-function change in error slope. Context: over the last hour, mid-incident. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8ca21b3ed75eccfe_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.54, 0.34, 0.06, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: over the last hour, immediately after go-live. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_013945f2e84c1fae_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "The log shipper correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: across all regions, immediately after go-live. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c6fa919258ccfb20_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.35, 0.55, 0.1, 0.0, 0.0], "state": "The log shipper flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during a scheduled maintenance window. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5dd7a15b977983e3_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.31, 0.16, 0.02, 0.51], "state": "The log shipper reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: during the batch window, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bd2d0cdc91497dc1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.28, 0.7, 0.02, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: in production only, with a new vendor onboarded. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4542a142423301c6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.38, 0.61, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: over the last hour, following a recent audit. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ce17ae92b76ef1f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.05, 0.74, 0.21, 0.0], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: over the last hour, during an external partner integration. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2f852bd8fcc44797_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.36, 0.04, 0.37, 0.23], "state": "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 an active deadline. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ba4e20eb6272cef5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.35, 0.64, 0.01], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, while on-call rotation changed. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_20574748795f05ef_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.58, 0.4, 0.01], "state": "The log shipper reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: over the last hour, while legacy systems are still active. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9e64bb0a32adacab_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.2, 0.54, 0.26, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: across all regions, at the end of the fiscal period. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_23647b7df91cd92e_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "The metrics pipeline correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: over the last hour, during the quarterly review. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_85f5bc5391744c82_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: in production only, while on-call rotation changed. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8a05b3d630b050ac_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: across all regions, while on-call rotation changed. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bf37d4ce777a4153_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.3, 0.58, 0.1, 0.02], "state": "The log shipper matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: across all regions, during the system migration. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_06424dc1a84fc63b_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: over the last hour, shortly after a software update. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_529b143127e6bfc9_n", "kind": "noul", "options": ["false", "true"], "target": [0.37, 0.63], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: during the batch window, following a recent audit. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c505c5e6add215ca_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: across all regions, during the holiday freeze. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c9c7edeab820f646_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.37, 0.61, 0.01], "state": "Node pgsql-14 flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: in production only, mid-incident. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a8e9686b9604d1b9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.18, 0.57, 0.24, 0.01, 0.0], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: across all regions, during the quarterly review. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f5df45a6c61efc82_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: across all regions, at the end of the fiscal period. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a86692e2e4667077_n", "kind": "noul", "options": ["false", "true"], "target": [0.56, 0.44], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: across all regions, during the system migration. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8ce647d9c7167076_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.25, 0.59, 0.15, 0.01, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; 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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_35ae5057b3ed2f56_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.34, 0.64], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: in production only, with a new vendor onboarded. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6d6ab3436bdebeef_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: in production only, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0002d4406a0aa5ec_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: in production only, under an active deadline. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8fea6aec19972988_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.59, 0.35, 0.04, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, while on-call rotation changed. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f2c15a53a287c548_n", "kind": "noul", "options": ["false", "true"], "target": [0.65, 0.35], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: during the batch window, during the system migration. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0267bec9439c319a_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "The log shipper flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: in production only, at the end of the fiscal period. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d39019ef922da8d3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.5, 0.48, 0.01], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: across all regions, during the system migration. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2688bef52a52abd1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.34, 0.64, 0.01], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: across all regions, at the end of the fiscal period. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_75e75101abce3e10_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "Service catalog-sync lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: during the batch window, while on-call rotation changed. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ac3b2f0fee6e63db_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.06, 0.29, 0.64, 0.01], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: over the last hour, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_85a6c91be08caada_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.3, 0.69, 0.01], "state": "Node pgsql-14 flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the holiday freeze. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2895fc99867f50d5_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, with a new vendor onboarded. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_22f8e532376a35cb_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: over the last hour, while legacy systems are still active. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_26276d48f610b8d0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.11, 0.81, 0.08], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: over the last hour, mid-incident. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a29cef5f871c5827_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, as part of a compliance sweep. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f5df45a6c61efc82_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.37, 0.57, 0.01, 0.05], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: across all regions, at the end of the fiscal period. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2b9544613cc677d7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.41, 0.56, 0.01], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, as part of a compliance sweep. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bbd0487aab7f6f49_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: during the batch window, during the system migration. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aa9bb44e6712d5be_n", "kind": "noul", "options": ["false", "true"], "target": [0.4, 0.6], "state": "The metrics pipeline flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: over the last hour, during peak load. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6a5029580a679384_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.03, 0.36, 0.58, 0.02], "state": "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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8427d38227d31588_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: in production only, with staffing at reduced levels. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_adb7bff20102cc07_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.64, 0.32, 0.02, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, following a recent audit. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dff7c6f6e7e4c812_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.66, 0.32, 0.0], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: during the batch window, with a new vendor onboarded. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1fef59a7e048d966_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.57, 0.42, 0.0], "state": "The metrics pipeline shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: in production only, during the holiday freeze. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3549bc9fbde0f77c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.03, 0.81, 0.16], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: over the last hour, under an active deadline. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c5e7178510278fdf_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.04, 0.36, 0.59, 0.01], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during the system migration. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7dbb694e257a12c2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.26, 0.64, 0.1, 0.0, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, under reduced staffing. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0f8f375aa4cdcd9c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.05, 0.53, 0.4, 0.01], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: in production only, under an active deadline. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0e60701a2768e58a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.12, 0.68, 0.18, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, under an active deadline. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0817c4b41659386a_n", "kind": "noul", "options": ["false", "true"], "target": [0.65, 0.35], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: during the batch window, during the morning shift. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0be0b7c06c040470_n", "kind": "noul", "options": ["false", "true"], "target": [0.66, 0.34], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: during the batch window, during the morning shift. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_38d1bb546dca96c7_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "The metrics pipeline lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: in production only, at the end of the fiscal period. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_363ab3914ab76edc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.14, 0.69, 0.16, 0.0], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: in production only, during the morning shift. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_da983fdb8edd947b_n", "kind": "noul", "options": ["false", "true"], "target": [0.22, 0.78], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, while legacy systems are still active. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4d8e06e7e260f8c0_n", "kind": "noul", "options": ["false", "true"], "target": [0.47, 0.53], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: over the last hour, during peak load. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_04c24b382d8c57df_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.16, 0.31, 0.49, 0.04], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: across all regions, under reduced staffing. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0dbed6a05e4c07b6_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.61, 0.04, 0.05, 0.3], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during peak load. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2aee5cd9ba8a0aa7_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.49, 0.36, 0.14, 0.01], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: over the last hour, during the quarterly review. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_de55e33435b76019_n", "kind": "noul", "options": ["false", "true"], "target": [0.92, 0.08], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: in production only, under an active deadline. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ecf4bac04640e56_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: in production only, with a new vendor onboarded. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d84f132e39b60a5f_n", "kind": "noul", "options": ["false", "true"], "target": [0.62, 0.38], "state": "The log shipper lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: in production only, during an external partner integration. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7e978c76f3b72f57_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.12, 0.77, 0.1, 0.01], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally matches last Tuesday's incident signature. Context: during the batch window, with staffing at reduced levels. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6632272cee29b1c5_n", "kind": "noul", "options": ["false", "true"], "target": [0.66, 0.34], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the holiday freeze. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6305c52dab9e7b2c_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: in production only, during an external partner integration. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6c3c8312a7b7ee96_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.53, 0.01, 0.04, 0.42], "state": "Node pgsql-14 returned to baseline after 11 minutes; 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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_de0afa4ae7ab87ff_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.71, 0.24, 0.01, 0.04], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: during the batch window, under reduced staffing. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e78804c7e8aa71c1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.64, 0.33, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: during the batch window, while legacy systems are still active. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b6b4fa8b8e64abc7_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: during the batch window, immediately after go-live. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_41ba49f42d60bbdd_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during a scheduled maintenance window. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a27228c01cabea6f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.54, 0.45, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: across all regions, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6dff0b779ba4a8cd_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: across all regions, under reduced staffing. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_61479a0db281dce8_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.38, 0.39, 0.01, 0.22], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: over the last hour, shortly after a software update. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_98a85714059cc87d_n", "kind": "noul", "options": ["false", "true"], "target": [0.5, 0.5], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: in production only, during normal operations. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d3b5c90e93d85e69_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.32, 0.67, 0.01], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: over the last hour, while legacy systems are still active. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_95e3d80e01e422c9_n", "kind": "noul", "options": ["false", "true"], "target": [0.9, 0.1], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: during the batch window, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f1d6a67f50c86bea_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.84, 0.14, 0.02], "state": "The metrics pipeline flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: over the last hour, shortly after a software update. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c3b9992e6bd43d44_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.97, 0.0, 0.01, 0.02], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during normal operations. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_59d4af37f278b8ba_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.0, 0.02, 0.95], "state": "The log shipper lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: over the last hour, at the end of the fiscal period. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_253dbcccfc42da32_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.5, 0.42, 0.07, 0.01], "state": "The metrics pipeline lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: in production only, immediately after go-live. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_40c133552346988a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.39, 0.59, 0.01], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: over the last hour, during the morning shift. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7f6e48708ae5e353_n", "kind": "noul", "options": ["false", "true"], "target": [0.7, 0.3], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the morning shift. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cba6a0d1b0ab4c06_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.12, 0.75, 0.11], "state": "Dashboard checkout-funnel 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 automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6850e20435d3c491_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.48, 0.38, 0.12, 0.0], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: across all regions, under reduced staffing. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a9945a26ed7de519_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.05, 0.83, 0.12], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, at the end of the fiscal period. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f8a81fe24c93b602_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, immediately after go-live. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5e2d1d3c5adeb520_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.22, 0.66, 0.04, 0.08], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_66504073835d2c6e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.01, 0.8, 0.19], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: during the batch window, during the quarterly review. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ae205c79667ec1e1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.2, 0.75, 0.05], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: during the batch window, during the quarterly review. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d7fafbba230995aa_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.08, 0.81, 0.1, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: across all regions, during the holiday freeze. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c52e59a9ad46c8c9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.18, 0.44, 0.01, 0.37], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, immediately after go-live. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_58f0cba1a01d3beb_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.73, 0.22, 0.01, 0.04], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: in production only, under reduced staffing. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6d72a21966b68a17_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "The metrics pipeline lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: in production only, under reduced staffing. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ee82c9b5033842cc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.71, 0.28, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: over the last hour, under an active deadline. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d2b3ff16e194be62_n", "kind": "noul", "options": ["false", "true"], "target": [0.9, 0.1], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: in production only, mid-incident. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_85a6c91be08caada_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.64, 0.13, 0.02, 0.21], "state": "Node pgsql-14 flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the holiday freeze. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2e04a3979da02b02_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.36, 0.58, 0.02, 0.0], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: over the last hour, under reduced staffing. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_89f30119524ce2dd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.02, 0.85, 0.13], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: in production only, shortly after a software update. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e55bc18fb598a779_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.29, 0.63, 0.02, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during the quarterly review. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_26361aac64b070b9_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.13, 0.71, 0.15, 0.01], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: in production only, with a new vendor onboarded. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_96d04de87344f636_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.6, 0.33, 0.06, 0.01], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_064917e5efe65c5c_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: across all regions, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e1dff98db0212cab_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.71, 0.26, 0.02, 0.01], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: over the last hour, with a new vendor onboarded. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ce62d55fd3ddfcff_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: over the last hour, shortly after a software update. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ac0c9e827cfa0342_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.27, 0.71, 0.02], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: in production only, while legacy systems are still active. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8d17287b2f3d1eab_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.5, 0.02, 0.22, 0.26], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, at the end of the fiscal period. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e5b06df5adcbf8f7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.71, 0.26, 0.03, 0.0, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during a scheduled maintenance window. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_75ea0aabd79305be_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.2, 0.54, 0.25, 0.01], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during peak load. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_037c1fd004394ee6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.04, 0.81, 0.15], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, under an active deadline. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e82dbf70cbabfdee_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "The log shipper matches last Tuesday's incident signature; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during peak load. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_66072434eceeaf09_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.14, 0.73, 0.13, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, while on-call rotation changed. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fdcff6beec7cfcfe_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.08, 0.32, 0.59], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: in production only, during the system migration. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_11244bfc18f198c0_n", "kind": "noul", "options": ["false", "true"], "target": [0.65, 0.35], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: during the batch window, while on-call rotation changed. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f850a4e079dac855_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.99, 0.01, 0.0, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, under an active deadline. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9b43c7032ec1dc83_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_db23f7f2e0290efc_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, immediately after go-live. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c9995ce3b68dba4c_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, shortly after a software update. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ab9782399cec05f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.8182, 0.0303, 0.0101, 0.1414], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: during the batch window, during peak load. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fee80017f05005a9_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: across all regions, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6c3c8312a7b7ee96_n", "kind": "noul", "options": ["false", "true"], "target": [0.38, 0.62], "state": "Node pgsql-14 returned to baseline after 11 minutes; 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.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d11d178801815eb9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.59, 0.39], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: over the last hour, with a new vendor onboarded. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e7c18444cda0eae9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.56, 0.42], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: during the batch window, as part of a compliance sweep. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_477dac9879b5628b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.64, 0.28, 0.07, 0.01], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: during the batch window, while legacy systems are still active. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_99676f46df41db7d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.4, 0.58, 0.01], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during an external partner integration. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_af1a1e5d663d8e93_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.05, 0.77, 0.17, 0.0], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: across all regions, during normal operations. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b1304c1ae11f1899_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.87, 0.13, 0.0, 0.0], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: in production only, during peak load. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aebf9812fc5d1d09_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.73, 0.25, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: in production only, during peak load. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5a205d87791964fd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.19, 0.59, 0.18, 0.04, 0.0, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, as part of a compliance sweep. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ec196e3e40b9bf23_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.6, 0.33, 0.01, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: over the last hour, following a recent audit. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_20edde1efbee14ce_n", "kind": "noul", "options": ["false", "true"], "target": [0.67, 0.33], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: during the batch window, under an active deadline. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_79f82059fe1650c5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.77, 0.2, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: in production only, following a recent audit. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3ef81b5d239fce3c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.17, 0.79, 0.04], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, mid-incident. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9aa9fc0a73ad009f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.28, 0.71, 0.01], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: across all regions, during the morning shift. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7c7fc28576c8a52e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.11, 0.57, 0.3, 0.01], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: across all regions, with a new vendor onboarded. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8483dec0a643d044_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.66, 0.34, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: over the last hour, with staffing at reduced levels. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ea8e29d7c98ac6fd_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: in production only, as part of a compliance sweep. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c54e3cef59095df1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.64, 0.33, 0.03, 0.0], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: in production only, at the end of the fiscal period. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9d2cc02020d814ff_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.49, 0.47, 0.03, 0.01], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, as part of a compliance sweep. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_71d8e406f440ac30_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The metrics pipeline shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: during the batch window, during the morning shift. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_26cea952d7f01ba4_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.86, 0.13, 0.01, 0.0], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: across all regions, with staffing at reduced levels. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b3536e6c95425187_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.08, 0.36, 0.54, 0.02, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: over the last hour, while legacy systems are still active. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6f0eb02cbf85fb98_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: in production only, under an active deadline. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f199f6c665ae999d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.22, 0.51, 0.05, 0.22], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: in production only, immediately after go-live. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4333b632dc8104dd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.25, 0.56, 0.17, 0.0], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: in production only, during the quarterly review. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b46629538f55c1e8_n", "kind": "noul", "options": ["false", "true"], "target": [0.66, 0.34], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: over the last hour, as part of a compliance sweep. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8b710a9ef2d60041_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: in production only, during the holiday freeze. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ba8f014ff71356c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.87, 0.11, 0.01, 0.01], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, under reduced staffing. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cc121195183773d4_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: in production only, under an active deadline. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6148f5c63aeb1104_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.92, 0.06, 0.01, 0.01], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during peak load. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_437e194e75af8fd7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.02, 0.24, 0.38, 0.3, 0.05, 0.01], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during the system migration. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_feaf5d052abfc4f4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.11, 0.73, 0.13, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: over the last hour, during an external partner integration. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_da37e7bdeec730f0_n", "kind": "noul", "options": ["false", "true"], "target": [0.59, 0.41], "state": "The log shipper flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: across all regions, during normal operations. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_03d92c4362a0bfd0_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.74, 0.24, 0.01, 0.01], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the holiday freeze. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a9ca016904e3c961_n", "kind": "noul", "options": ["false", "true"], "target": [0.53, 0.47], "state": "The metrics pipeline lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: during the batch window, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5b4ce7af387d2730_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.76, 0.22, 0.01, 0.01], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the system migration. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aac75f4672829e71_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.54, 0.42, 0.03], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally matches last Tuesday's incident signature. Context: across all regions, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7e7c81c30e21ace5_n", "kind": "noul", "options": ["false", "true"], "target": [0.65, 0.35], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during a scheduled maintenance window. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c4ccfb6b0d5ce71c_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: over the last hour, at the end of the fiscal period. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1aebe92b3bf1cbda_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The metrics pipeline shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: in production only, during a scheduled maintenance window. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_785dfa5b87bec041_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.96, 0.02, 0.0, 0.02], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, under an active deadline. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f0087aa3d312df23_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.16, 0.02, 0.16, 0.66], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: across all regions, during the system migration. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cfea0e44ac3dbae2_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.95, 0.04, 0.0, 0.01], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: in production only, under an active deadline. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3dc0a10afb49324b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.3, 0.05, 0.27, 0.38], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during the holiday freeze. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d24d4c971fe6f247_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.3, 0.68, 0.02], "state": "Node pgsql-14 flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: during the batch window, mid-incident. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ff0a5fcde85919e4_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "The log shipper reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: over the last hour, during peak load. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2c4b1e7693cb8450_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.07, 0.28, 0.58, 0.07, 0.0], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: during the batch window, under an active deadline. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8d282d5e07b87b39_n", "kind": "noul", "options": ["false", "true"], "target": [0.46, 0.54], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, following a recent audit. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fe965ce8a13930fe_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.43, 0.48, 0.03, 0.0], "state": "Service catalog-sync flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: in production only, while legacy systems are still active. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_48f606f4c92bc39f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.06, 0.7, 0.23, 0.0], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: during the batch window, during an external partner integration. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dad03a35041a0fdb_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.86, 0.13, 0.01], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: across all regions, shortly after a software update. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_115d67f8d0032042_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.29, 0.67, 0.03], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9e32191cad420082_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: during the batch window, under an active deadline. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b76bed787bae2704_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.03, 0.57, 0.37], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: across all regions, with staffing at reduced levels. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8db6b2cca5f9bd42_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.47, 0.5, 0.01], "state": "The log shipper flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: in production only, as part of a compliance sweep. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c8d3a88ec4e4ab77_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.33, 0.65, 0.01], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: during the batch window, during an external partner integration. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e677b2e9f6a4e03c_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: across all regions, during peak load. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_12d411cbc3e2e6df_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.16, 0.8, 0.04], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: in production only, during an external partner integration. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6b7688f70b233edf_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.46, 0.51, 0.01], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d105d2157f67a8ec_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.0, 0.39, 0.6], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: over the last hour, at the end of the fiscal period. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9e01b76ac1d2fe41_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "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.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_88a74779fae07bf6_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: during the batch window, following a recent audit. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e6c3845770cae3d1_n", "kind": "noul", "options": ["false", "true"], "target": [0.63, 0.37], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: during the batch window, shortly after a software update. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_baee2cba13535c6f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.02, 0.35, 0.41, 0.2, 0.01], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, while on-call rotation changed. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_41824fec2c70eead_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Node pgsql-14 flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: during the batch window, during normal operations. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6a129659707217e9_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7552b7490170f092_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.58, 0.41, 0.0], "state": "Service catalog-sync correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: across all regions, while on-call rotation changed. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b8a122aa42e09f1c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.47, 0.53, 0.0], "state": "The metrics pipeline shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: over the last hour, under an active deadline. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_997648e0ee6b8ec5_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.06, 0.68, 0.26], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: across all regions, during an external partner integration. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6b5f524f399edc48_n", "kind": "noul", "options": ["false", "true"], "target": [0.51, 0.49], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during a scheduled maintenance window. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_65356be287049889_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.05, 0.84, 0.11], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: during the batch window, under an active deadline. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c94d07b1f6a847c3_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.58, 0.4], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: during the batch window, during a scheduled maintenance window. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_11244bfc18f198c0_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.7, 0.28, 0.02, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: during the batch window, while on-call rotation changed. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ba3abcf5132b506_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: over the last hour, as part of a compliance sweep. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7838ddb82d0abc63_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: in production only, during an external partner integration. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c24672b83c43d101_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.05, 0.83, 0.11, 0.0], "state": "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 a scheduled maintenance window. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2a31c9e043025ddf_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.33, 0.48, 0.17, 0.02], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: in production only, during normal operations. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ff0a5fcde85919e4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.28, 0.69, 0.02], "state": "The log shipper reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: over the last hour, during peak load. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_71813b934378a2fc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.1, 0.81, 0.09], "state": "The metrics pipeline correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: across all regions, immediately after go-live. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_10fffb62f8792019_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.22, 0.75, 0.03], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: across all regions, under an active deadline. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ef70e3343e54b02c_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally matches last Tuesday's incident signature. Context: in production only, while legacy systems are still active. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ffcb17bc316f4df1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.61, 0.23, 0.13, 0.03], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during a scheduled maintenance window. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e817fa8db15da2d9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.07, 0.29, 0.55, 0.08, 0.0], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: during the batch window, during the morning shift. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_975da4fa25118d20_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.35, 0.51, 0.08, 0.0], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: in production only, with staffing at reduced levels. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a3fd12b97610374f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.63, 0.27, 0.02, 0.08], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: across all regions, mid-incident. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_17a28e940c3858ab_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.67, 0.25, 0.07, 0.01], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during normal operations. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1912f80da9967b97_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: in production only, during the system migration. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f13755e097ab6e98_n", "kind": "noul", "options": ["false", "true"], "target": [0.42, 0.58], "state": "The metrics pipeline flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: in production only, following a recent audit. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e8735976824db8bc_n", "kind": "noul", "options": ["false", "true"], "target": [0.46, 0.54], "state": "The log shipper shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: across all regions, as part of a compliance sweep. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8884f7eabea204de_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.0, 0.4, 0.6], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: across all regions, during normal operations. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e244504935e5dee2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.5, 0.37, 0.11, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during the quarterly review. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e786f58ccb822066_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: across all regions, while on-call rotation changed. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_38b4d16ac56fec8f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.35, 0.64, 0.01], "state": "Node pgsql-14 flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: across all regions, shortly after a software update. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3afeab695af83995_n", "kind": "noul", "options": ["false", "true"], "target": [0.45, 0.55], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: across all regions, during normal operations. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0962e2f707185d80_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.44, 0.43, 0.12, 0.0, 0.0], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: during the batch window, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_592c75c437d5b4d7_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "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, shortly after a software update. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_08e6516a719b2cc4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.26, 0.72, 0.02], "state": "The log shipper shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: over the last hour, immediately after go-live. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9f2b2b697e34f733_n", "kind": "noul", "options": ["false", "true"], "target": [0.47, 0.53], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: across all regions, following a recent audit. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_57a5c8d70a36cbf7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.02, 0.12, 0.43, 0.38, 0.05, 0.0], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: in production only, while legacy systems are still active. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d21329268b5c61fe_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The log shipper correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during the quarterly review. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8a1c7d06e85bf1fb_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.71, 0.22, 0.05, 0.02], "state": "The log shipper shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: in production only, during the holiday freeze. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7ea28937e847a888_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: across all regions, during the quarterly review. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7cb4e7a980f6d8e0_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.29, 0.69, 0.01], "state": "Service catalog-sync shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: across all regions, at the end of the fiscal period. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f4aa0aa6a3f7e670_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.24, 0.73, 0.02], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: over the last hour, under an active deadline. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_52b2650c3ba43b93_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.03, 0.74, 0.23], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, immediately after go-live. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_88c12e1079c6885d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.95, 0.02, 0.01, 0.02], "state": "Service catalog-sync shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: in production only, mid-incident. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8644b952d3ebaac0_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.0, 0.02, 0.97], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: during the batch window, while on-call rotation changed. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f7e7855fd93498dc_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.29, 0.25, 0.03, 0.43], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: across all regions, while legacy systems are still active. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cb7a1f2564ba7d2e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.12, 0.81, 0.07], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, immediately after go-live. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_400a08a44495bcf1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.09, 0.82, 0.09], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, mid-incident. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a6698dc29da472d1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.01, 0.53, 0.44], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: over the last hour, at the end of the fiscal period. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c505c5e6add215ca_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.71, 0.28, 0.01, 0.0], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: across all regions, during the holiday freeze. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_55b8102604cb0612_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.3, 0.68, 0.01], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: across all regions, during the morning shift. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9abb9af0195b8608_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.65, 0.3, 0.0, 0.05], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during the quarterly review. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cd4dbd8bb1645b31_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: in production only, during the system migration. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_06ffe40dc1ecfdde_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.24, 0.42, 0.3, 0.04], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during a scheduled maintenance window. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_558898bab8511fd8_n", "kind": "noul", "options": ["false", "true"], "target": [0.37, 0.63], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: during the batch window, with staffing at reduced levels. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_71c948f698498ece_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.71, 0.26, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: over the last hour, while legacy systems are still active. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3e0b261085d79448_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.11, 0.85, 0.04], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: during the batch window, under reduced staffing. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c9c7edeab820f646_n", "kind": "noul", "options": ["false", "true"], "target": [0.41, 0.59], "state": "Node pgsql-14 flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: in production only, mid-incident. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_62ccc306f912a489_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.17, 0.75, 0.01, 0.07], "state": "Service catalog-sync shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: during the batch window, as part of a compliance sweep. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_92e1384e08d3986d_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: across all regions, during the system migration. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_71813b934378a2fc_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "The metrics pipeline correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: across all regions, immediately after go-live. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_efc353f7676bf1b2_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "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.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_44a715877fcd8676_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.34, 0.62, 0.03], "state": "The metrics pipeline flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: in production only, mid-incident. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8e3cc5c08a03272b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.55, 0.41, 0.03, 0.01], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: across all regions, at the end of the fiscal period. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bdf27e54313a0029_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "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.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cb186b02bc6c26c6_n", "kind": "noul", "options": ["false", "true"], "target": [0.54, 0.46], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, immediately after go-live. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b6687f174cc9f185_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.41, 0.56, 0.01], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: over the last hour, mid-incident. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7241262bc15b1a69_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.66, 0.31, 0.02, 0.01], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during an external partner integration. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_786fd6c9b705d052_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.26, 0.11, 0.02, 0.61], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: during the batch window, as part of a compliance sweep. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1daa4561fd5f4cb0_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.27, 0.02, 0.34, 0.37], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: during the batch window, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_98a85714059cc87d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.12, 0.17, 0.02, 0.69], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: in production only, during normal operations. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_61c0a617ebc96d83_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.09, 0.11, 0.7, 0.1, 0.0], "state": "The metrics pipeline flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: across all regions, during a scheduled maintenance window. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_984688f750256d98_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.22, 0.64, 0.12, 0.0], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f9bde606977d991d_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during normal operations. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d2b3ff16e194be62_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.12, 0.78, 0.1], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: in production only, mid-incident. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ae143df6f62db002_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: over the last hour, during an external partner integration. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_635abbcdf94d8d19_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.2, 0.73, 0.03, 0.04], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: across all regions, during the system migration. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e59e0e38df36c629_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.89, 0.08, 0.02, 0.01], "state": "The log shipper reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: over the last hour, during peak load. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b76a51f421438db6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.62, 0.36, 0.0], "state": "The log shipper reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: during the batch window, during an external partner integration. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_be2032e6fb885b88_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.69, 0.3, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during normal operations. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3e08344f71faeefd_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ebb9dd2fb6281821_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during the system migration. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_abc699cd8c2bd7c5_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: across all regions, following a recent audit. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_83dbfe07a39d825b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.65, 0.33, 0.02, 0.0], "state": "The log shipper flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: in production only, during an external partner integration. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4667fbaf100c17ee_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.88, 0.11, 0.01, 0.0], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: during the batch window, under an active deadline. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4bba3cc77a32e022_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0101, 0.2828, 0.6768, 0.0303], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: during the batch window, during the quarterly review. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_388a4f2353f5407c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.01, 0.28, 0.69], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the system migration. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aefe78865d7f777c_n", "kind": "noul", "options": ["false", "true"], "target": [0.7, 0.3], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: across all regions, following a recent audit. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1902c7f37ac21995_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.73, 0.23, 0.04, 0.0], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: in production only, with a new vendor onboarded. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7d75b0710d84c256_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.65, 0.33, 0.0], "state": "The log shipper reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: during the batch window, with a new vendor onboarded. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b34b61806288b565_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: during the batch window, during peak load. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9597cca3e1904f43_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.05, 0.62, 0.32, 0.0], "state": "The log shipper correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: in production only, during peak load. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_47a22788d012fdad_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.13, 0.3, 0.02, 0.55], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: across all regions, while on-call rotation changed. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_137bc5b4eaa7f808_n", "kind": "noul", "options": ["false", "true"], "target": [0.18, 0.82], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: over the last hour, under reduced staffing. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fa9325ae329daf1e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.32, 0.61, 0.07, 0.0, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: over the last hour, while legacy systems are still active. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_119e9cdd197fe522_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.6, 0.31, 0.08, 0.01], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, at the end of the fiscal period. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b1db99c51aeee8a0_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: across all regions, immediately after go-live. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_27e7547f7e9b05fb_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.32, 0.12, 0.19, 0.37], "state": "The log shipper shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: during the batch window, while legacy systems are still active. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_57b9030626dc3630_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.02, 0.5, 0.46, 0.01], "state": "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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_62750f00a5a3d36e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.92, 0.06, 0.01, 0.01], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: over the last hour, immediately after go-live. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_784e2f3580225024_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.79, 0.14, 0.06, 0.01], "state": "The log shipper shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: during the batch window, mid-incident. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_42691896f323a491_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.27, 0.54, 0.19, 0.0, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: in production only, during a scheduled maintenance window. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_19d01b965d9c85b5_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.52, 0.43, 0.04, 0.01], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: across all regions, with a new vendor onboarded. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_32b54e582bdefe39_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.11, 0.62, 0.25, 0.0], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: during the batch window, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aac77c7dde1aa473_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: in production only, during an external partner integration. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_59a947f70c5fc15d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.03, 0.26, 0.67, 0.04], "state": "Service catalog-sync correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: in production only, during a scheduled maintenance window. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_72f32cc98b1f4832_n", "kind": "noul", "options": ["false", "true"], "target": [0.39, 0.61], "state": "Service catalog-sync shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: across all regions, during an external partner integration. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_684b24d53e58d3c0_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: in production only, while on-call rotation changed. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f907d8363d30bfd7_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: during the batch window, while on-call rotation changed. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6bd0df3ad1ebab1c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.24, 0.68, 0.04, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: in production only, during an external partner integration. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8a32fe9806674f79_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.85, 0.0, 0.01, 0.14], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, following a recent audit. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b294d1dde75285c6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.15, 0.82, 0.03], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: during the batch window, following a recent audit. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_92abc61435214c2d_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: in production only, following a recent audit. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_62ab8c74ee22b33a_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: during the batch window, under reduced staffing. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0d997d51fdd8923d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.12, 0.59, 0.26, 0.01], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: in production only, with a new vendor onboarded. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9a4445224650c1fe_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.78, 0.21, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: in production only, at the end of the fiscal period. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a4b5e63a9bb5d733_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.23, 0.73, 0.03], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: across all regions, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bdfcb254d9376760_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: across all regions, as part of a compliance sweep. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0bb7bd9d8a3b5adb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.11, 0.74, 0.14, 0.0], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_71e5cfa81743c981_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "Node pgsql-14 flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: during the batch window, while on-call rotation changed. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_67e63af1cf794458_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "The log shipper lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, with staffing at reduced levels. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6febbf9e643d1b73_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "The log shipper reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, while on-call rotation changed. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eefbb4f87f80a9d4_n", "kind": "noul", "options": ["false", "true"], "target": [0.68, 0.32], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: in production only, during a scheduled maintenance window. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9ffb5b5d6c4ace52_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.35, 0.56, 0.06, 0.0], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: in production only, during the holiday freeze. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_914bf5b99076b96c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.28, 0.63, 0.05, 0.0], "state": "The log shipper reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: across all regions, during the morning shift. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_12e4781122b634e7_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.3, 0.29, 0.4, 0.01], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: across all regions, mid-incident. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1b9d809ba005a2d4_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: in production only, during the system migration. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_236179a567f39fc9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.06, 0.64, 0.25], "state": "The log shipper flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: across all regions, during a scheduled maintenance window. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_597f037047e1ee8a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.26, 0.73, 0.01], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aa5dbb280d093479_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.02, 0.6, 0.35, 0.03], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: over the last hour, as part of a compliance sweep. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c4cad63dec516304_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.17, 0.75, 0.06, 0.02], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: across all regions, following a recent audit. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bf5572c29b0ec1c1_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: during the batch window, following a recent audit. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9003bd7796e32e34_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: over the last hour, as part of a compliance sweep. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_13469f2dbd5a6ea2_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.57, 0.3, 0.12, 0.01], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the holiday freeze. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_39adb0862e1684ba_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.09, 0.35, 0.55, 0.01], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: during the batch window, during the system migration. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d130979aee19c171_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.51, 0.44, 0.01, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: over the last hour, with staffing at reduced levels. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_01733d259d7619b1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.98, 0.02, 0.0, 0.0], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: in production only, under an active deadline. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_48e823d794ce89fd_n", "kind": "noul", "options": ["false", "true"], "target": [0.2, 0.8], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, under reduced staffing. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_083572132303d418_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "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.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4f207dc26fda8cd1_n", "kind": "noul", "options": ["false", "true"], "target": [0.43, 0.57], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during normal operations. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1f024b689f270178_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.6, 0.39, 0.0], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: across all regions, shortly after a software update. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_725e9aaf55d22216_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.79, 0.01, 0.19], "state": "The log shipper lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: in production only, shortly after a software update. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9917f62ce2c7095a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.38, 0.07, 0.03, 0.52], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: across all regions, at the end of the fiscal period. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8a7810bd7055a8b1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.44, 0.37, 0.15, 0.04], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, at the end of the fiscal period. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0c997215de6741f8_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during the holiday freeze. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_07d520da86ff2650_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.55, 0.42, 0.01], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: over the last hour, under an active deadline. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0d07ac46d6dc45e9_n", "kind": "noul", "options": ["false", "true"], "target": [0.71, 0.29], "state": "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.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d426d5cd2cbd06e9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.53, 0.36, 0.08, 0.0], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the quarterly review. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_73a30f32ebe7d993_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.13, 0.01, 0.08, 0.78], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: in production only, as part of a compliance sweep. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a9ca016904e3c961_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.05, 0.7, 0.25, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: during the batch window, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_853d89db29a14380_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "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.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5ea705954bb70a25_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.47, 0.14, 0.03, 0.36], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: across all regions, during the quarterly review. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c61f8ad7a3f3729e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.45, 0.4, 0.14, 0.0], "state": "The log shipper flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: across all regions, under an active deadline. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cbd0ea7a4a3caa80_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.28, 0.7, 0.01], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: in production only, under reduced staffing. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_60f434efdfef0d13_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.22, 0.75, 0.03], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during the holiday freeze. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_62f5e555326f4c81_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.25, 0.73], "state": "The metrics pipeline flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: across all regions, during the system migration. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5dfc58659e326391_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.83, 0.16, 0.01, 0.0], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: in production only, while on-call rotation changed. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a3fd12b97610374f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.48, 0.51, 0.0], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: across all regions, mid-incident. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f6298bd5448856d8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.59, 0.36, 0.03, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: in production only, following a recent audit. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5264c43db0d2c701_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.84, 0.15, 0.0, 0.01], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: in production only, as part of a compliance sweep. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5fce97ef2be15620_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.21, 0.75, 0.03], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: in production only, while legacy systems are still active. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8fd9ab28d9118180_n", "kind": "noul", "options": ["false", "true"], "target": [0.68, 0.32], "state": "The metrics pipeline correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: in production only, during the holiday freeze. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8aacede6799cccd2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.52, 0.42, 0.01], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: over the last hour, as part of a compliance sweep. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_de1b40b51882af99_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.04, 0.75, 0.2, 0.01], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: over the last hour, shortly after a software update. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_114c7cbce3b76295_n", "kind": "noul", "options": ["false", "true"], "target": [0.56, 0.44], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: in production only, during the system migration. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_64deb0aff0f283f2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.1, 0.85, 0.05], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during the quarterly review. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b34b61806288b565_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.36, 0.61, 0.01], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: during the batch window, during peak load. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4b3f263ef6573907_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.02, 0.32, 0.56, 0.1, 0.0, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: across all regions, during normal operations. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_21545266b9a28ef2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.8, 0.01, 0.14, 0.05], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: in production only, under an active deadline. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fca572de5a213c93_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "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.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b00f916d4a2665b4_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "The metrics pipeline returned to baseline after 11 minutes; 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.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_de3f278596b1d4cd_n", "kind": "noul", "options": ["false", "true"], "target": [0.56, 0.44], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: across all regions, under reduced staffing. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_371f9b65d076919c_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "Service catalog-sync lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: in production only, under an active deadline. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e1dff98db0212cab_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: over the last hour, with a new vendor onboarded. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b823c5d2c4c506a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.08, 0.51, 0.02, 0.39], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: in production only, immediately after go-live. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7116a9645b1a1ab7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.36, 0.63, 0.01], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: across all regions, immediately after go-live. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_74b1284e36c182d3_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, immediately after go-live. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d28825504e2c6ded_n", "kind": "noul", "options": ["false", "true"], "target": [0.69, 0.31], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, mid-incident. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1ce4fbb648628d94_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.6, 0.34, 0.05, 0.01], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: in production only, with staffing at reduced levels. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b4aaf3f418057758_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.25, 0.73, 0.02], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during the holiday freeze. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c09ae2db19be2204_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.2, 0.53, 0.22, 0.05], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: over the last hour, during the holiday freeze. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_704b27b53243450b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.35, 0.63, 0.01], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during a scheduled maintenance window. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_628da98585f96231_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.06, 0.88, 0.06], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: in production only, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f5ef7d7c90540f2e_n", "kind": "noul", "options": ["false", "true"], "target": [0.38, 0.62], "state": "The log shipper flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: during the batch window, following a recent audit. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8e70add2b7ab95a2_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.77, 0.21, 0.02, 0.0], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during the quarterly review. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4de3bf7802faa79a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.25, 0.65, 0.1, 0.0, 0.0], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: across all regions, at the end of the fiscal period. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3abcf796d0ebfba8_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.6, 0.38], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: over the last hour, during an external partner integration. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0e6ab303437251b8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.7, 0.25, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: across all regions, following a recent audit. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8254f30160749ee9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.27, 0.53, 0.2, 0.0, 0.0], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: during the batch window, with a new vendor onboarded. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a2bba9af7f901d7f_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: in production only, during the morning shift. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_82885b53cb60c002_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.38, 0.61, 0.01], "state": "The log shipper shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, while legacy systems are still active. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_124c471e8040ac78_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.49, 0.49], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: across all regions, during the system migration. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6fbc8c0a75976305_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.41, 0.57], "state": "Service catalog-sync flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: during the batch window, while on-call rotation changed. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2086f85dbeeda4f0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.31, 0.67, 0.01], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: in production only, with a new vendor onboarded. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f8bf498c61543029_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: over the last hour, as part of a compliance sweep. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f42d2e2f3c2fad01_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the system migration. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ba6246cfc8df2c60_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.78, 0.14, 0.07, 0.01], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: over the last hour, while on-call rotation changed. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ad728eb195d5ba7d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.19, 0.74, 0.03], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: in production only, with a new vendor onboarded. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ab02b7345f8a9345_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.3, 0.07, 0.08, 0.55], "state": "The log shipper shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: during the batch window, under an active deadline. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b705d568cb7c4052_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.65, 0.26, 0.01, 0.08], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: during the batch window, during peak load. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bf1d34869654cbbf_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.73, 0.01, 0.11, 0.15], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: across all regions, at the end of the fiscal period. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c00de03c779bd135_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: in production only, as part of a compliance sweep. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5611ccd8488a35e0_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.06, 0.13, 0.04, 0.77], "state": "The log shipper shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: in production only, while on-call rotation changed. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8744e6e1270a2594_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.5657, 0.3939, 0.0303, 0.0101], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the morning shift. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1469da638a7fa7a5_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: in production only, during the holiday freeze. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5510412336f7641d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.0, 0.88, 0.11], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, as part of a compliance sweep. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a048eae1fe84eb0b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.26, 0.73, 0.01], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, following a recent audit. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_960173adc879629f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.51, 0.48, 0.0], "state": "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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9cbbd1680620315d_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "The log shipper shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, with a new vendor onboarded. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ffcb17bc316f4df1_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during a scheduled maintenance window. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0a8fd9e5cb6a9b71_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.56, 0.31, 0.12, 0.01], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: over the last hour, during the system migration. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a47ca30599e35210_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.03, 0.7, 0.26], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the morning shift. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b2bec84b80c0202e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.41, 0.47, 0.1, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, as part of a compliance sweep. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b731e1d576c176a3_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.01, 0.6, 0.37], "state": "The log shipper shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: during the batch window, during normal operations. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d5077479eefccca7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.82, 0.17, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: over the last hour, during an external partner integration. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8784c75aba971562_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.05, 0.88, 0.07], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: in production only, with a new vendor onboarded. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aa72a0886afb4d0c_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: across all regions, with staffing at reduced levels. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dc793a2423dbf41e_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: over the last hour, while legacy systems are still active. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca00c583e378ef59_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.11, 0.83, 0.06], "state": "The log shipper correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during peak load. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e1fb4e0d7b6d7b40_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, at the end of the fiscal period. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_987e55620e201bdb_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, under an active deadline. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2e89f4d1ee0c5f57_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: in production only, as part of a compliance sweep. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f600703ac21f8796_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.53, 0.47, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during an external partner integration. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dd22ad86eccd76de_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.23, 0.76, 0.01], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: across all regions, under reduced staffing. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fa9325ae329daf1e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.03, 0.65, 0.31, 0.01], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: over the last hour, while legacy systems are still active. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c4d9aeb8a7b0b45a_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: during the batch window, during an external partner integration. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f50c34ff5582d036_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.05, 0.54, 0.38, 0.03], "state": "The log shipper reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: during the batch window, during peak load. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ec734d72ffc801ad_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.26, 0.57, 0.15, 0.02], "state": "Service catalog-sync correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: over the last hour, as part of a compliance sweep. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8ddf9fec21f9c822_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.13, 0.5, 0.33, 0.03, 0.0], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: in production only, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e817fa8db15da2d9_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: during the batch window, during the morning shift. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c182c441d16581a5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.1212, 0.2727, 0.5556, 0.0505], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, under an active deadline. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d84f132e39b60a5f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.06, 0.86, 0.08, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: in production only, during an external partner integration. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_11e964bfae4d2d86_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "The metrics pipeline correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: in production only, at the end of the fiscal period. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b88c5ea1bf363cd5_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.87, 0.12, 0.01, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: in production only, under reduced staffing. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2267eea9d102d78d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.09, 0.41, 0.02, 0.48], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: over the last hour, following a recent audit. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_de2255cbce7c0320_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.44, 0.54, 0.01], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: across all regions, with staffing at reduced levels. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7c0f1199481a3cb2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.78, 0.04, 0.03, 0.15], "state": "Service catalog-sync flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: during the batch window, with staffing at reduced levels. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eefbb4f87f80a9d4_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.25, 0.43, 0.31, 0.01], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: in production only, during a scheduled maintenance window. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0c134def800aa1c9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.1, 0.78, 0.1, 0.0], "state": "The log shipper matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: during the batch window, shortly after a software update. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9cf1c0aef69ec2f9_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.76, 0.23, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: over the last hour, during the quarterly review. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4964069808d6059f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.18, 0.78, 0.04], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: over the last hour, during the holiday freeze. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3f377361ce9ed677_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.07, 0.12, 0.25, 0.56], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: during the batch window, during a scheduled maintenance window. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d5bebe1b0247211c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.57, 0.38, 0.02, 0.03], "state": "Service catalog-sync lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: during the batch window, during peak load. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_520da00a44ac5fe6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.19, 0.64, 0.17, 0.0, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: across all regions, with a new vendor onboarded. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_56b5cde3bac64c44_n", "kind": "noul", "options": ["false", "true"], "target": [0.42, 0.58], "state": "The log shipper shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_087f18c219b31896_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.76, 0.22, 0.01, 0.01], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally flags a step-function change in error slope. Context: across all regions, as part of a compliance sweep. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_67646f50f7d6a63c_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: during the batch window, under an active deadline. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ac3b2f0fee6e63db_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.39, 0.52, 0.09, 0.0, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: over the last hour, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3c9a9ac252417e4c_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: across all regions, as part of a compliance sweep. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_345914eaa621135a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.58, 0.15, 0.13, 0.14], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: in production only, under an active deadline. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_149c47203de6a4a4_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.94, 0.04, 0.01, 0.01], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: over the last hour, immediately after go-live. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_79e2542a894980f9_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: across all regions, during the morning shift. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_23e1c2a1840c2833_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.27, 0.48, 0.24, 0.0], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during peak load. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0707d6980385b9ab_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.58, 0.36, 0.03, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: during the batch window, while legacy systems are still active. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0895d7417727ba40_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.17, 0.81], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: during the batch window, as part of a compliance sweep. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2bf45a3e160d846e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.34, 0.6, 0.05], "state": "The metrics pipeline lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: over the last hour, during the holiday freeze. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_53f914db37d4a5de_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.96, 0.04, 0.0, 0.0], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_49a4eafbc88ad433_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5c76866e57ad1579_n", "kind": "noul", "options": ["false", "true"], "target": [0.23, 0.77], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally flags a step-function change in error slope. Context: across all regions, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d92f11306bff162f_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: over the last hour, while on-call rotation changed. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_387c4b551ce1141d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.03, 0.79, 0.18], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: in production only, mid-incident. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_94bc196e655a8a64_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.05, 0.49, 0.45, 0.01], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during normal operations. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4c691a13d8b242d3_n", "kind": "noul", "options": ["false", "true"], "target": [0.47, 0.53], "state": "The log shipper reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the holiday freeze. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_33c7a3d42f27139b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.67, 0.3, 0.02, 0.01], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: in production only, with a new vendor onboarded. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_13304d52bb2d1fae_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.85, 0.12, 0.01, 0.02], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: over the last hour, immediately after go-live. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a33cd9a8d60f3115_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.01, 0.24, 0.73], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: in production only, with a new vendor onboarded. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_18b7126b266b8b88_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.29, 0.02, 0.13, 0.56], "state": "The log shipper shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: in production only, during normal operations. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7796777046413d21_n", "kind": "noul", "options": ["false", "true"], "target": [0.43, 0.57], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: in production only, during a scheduled maintenance window. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_451153f4c5128750_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: over the last hour, during the system migration. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b54d93b3f6d29f4b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.72, 0.22, 0.05, 0.01], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: over the last hour, at the end of the fiscal period. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_77a43e0b963196a8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0202, 0.8081, 0.1717, 0.0], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: in production only, during normal operations. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f8f438425cb40297_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.85, 0.01, 0.05, 0.09], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during peak load. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ebb9bb4ea7be31bc_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: in production only, immediately after go-live. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_62157486128e418b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.79, 0.19, 0.01, 0.01], "state": "Service catalog-sync shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: in production only, during peak load. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8182e66bd543e93d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.92, 0.07, 0.0, 0.01], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally flags a step-function change in error slope. Context: over the last hour, during the morning shift. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c19c21d2a608da19_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.31, 0.67, 0.01], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: across all regions, while on-call rotation changed. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_82aad936141ec329_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.04, 0.67, 0.29, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally matches last Tuesday's incident signature. Context: during the batch window, during the holiday freeze. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d2a7c0ecfca93e8e_n", "kind": "noul", "options": ["false", "true"], "target": [0.55, 0.45], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: over the last hour, during the holiday freeze. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2d922080832a57a6_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.54, 0.05, 0.01, 0.4], "state": "The log shipper reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: over the last hour, mid-incident. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5e6c6f3e2379d60f_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "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.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e0a3d17369be7208_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.04, 0.83, 0.12], "state": "Service catalog-sync correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: over the last hour, while on-call rotation changed. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_61f22e5ef6632689_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.85, 0.13, 0.02, 0.0], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, while legacy systems are still active. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4209233e4843f18f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.83, 0.15, 0.02, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during normal operations. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cd44d6d05ff598c1_n", "kind": "noul", "options": ["false", "true"], "target": [0.69, 0.31], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: across all regions, with staffing at reduced levels. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1216e41e760ddc18_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, while legacy systems are still active. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f5516e642cdae6be_n", "kind": "noul", "options": ["false", "true"], "target": [0.7, 0.3], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: in production only, during the morning shift. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7552b7490170f092_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Service catalog-sync correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: across all regions, while on-call rotation changed. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f2b56130a5395fdf_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during the system migration. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_27cc53b027e09ca5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.04, 0.64, 0.32, 0.0], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: during the batch window, following a recent audit. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b2434e9ed31854d1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.09, 0.85, 0.06], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: in production only, during peak load. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4089d938fba218e2_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: across all regions, during the quarterly review. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_99ef288c2e93ce38_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.06, 0.73, 0.21, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: in production only, during the holiday freeze. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_702d4cd147cc545d_n", "kind": "noul", "options": ["false", "true"], "target": [0.43, 0.57], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: in production only, as part of a compliance sweep. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_702f3250ea0e0cea_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.21, 0.74, 0.05], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: in production only, under an active deadline. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8f46112e7084c475_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.1, 0.75, 0.14, 0.01], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: across all regions, following a recent audit. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d321c0674c4ef632_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.83, 0.0, 0.01, 0.16], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during the morning shift. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7997112f6790fb6e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.57, 0.41, 0.0], "state": "The log shipper flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: in production only, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_603080b4e413b5b3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.31, 0.54, 0.15, 0.0, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: over the last hour, immediately after go-live. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c4fe45ed4aba8c30_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.11, 0.79, 0.09, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: during the batch window, following a recent audit. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a1ebc50d954ea3b0_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.27, 0.6, 0.02, 0.11], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: across all regions, during the holiday freeze. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d31da26f5f7e79e9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.96, 0.0, 0.0, 0.04], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_13304d52bb2d1fae_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: over the last hour, immediately after go-live. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c28ba3093f1ef556_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.18, 0.36, 0.45, 0.01, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: during the batch window, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_670f4fdeadf62e9b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.64, 0.33, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: over the last hour, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_98df6761f6cafb95_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.63, 0.36, 0.0], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: in production only, during the holiday freeze. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_88e59bf617b7f237_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.22, 0.77, 0.01], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during the quarterly review. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6b6c375dbbd121a1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.09, 0.83, 0.08], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during the system migration. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3b4437b87cdbe174_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.57, 0.43, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the morning shift. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_92c19f9a4b528733_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: in production only, during the morning shift. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7451fbee72d05a60_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.18, 0.39, 0.41], "state": "The metrics pipeline 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 operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b566758345efc9ff_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.55, 0.36, 0.06, 0.0], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, with staffing at reduced levels. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4dd6e467a3aca27d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.3, 0.68, 0.02], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: over the last hour, with staffing at reduced levels. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_836ddacbcbbc164a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.35, 0.43, 0.21, 0.01], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, under reduced staffing. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b2a7a3827320d39d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.43, 0.52, 0.02, 0.0], "state": "The log shipper flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: during the batch window, at the end of the fiscal period. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_275a17c984928081_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.52, 0.48, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: during the batch window, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8632beb8b67996da_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.18, 0.77, 0.03, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: across all regions, during an external partner integration. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_237a191771e57089_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.35, 0.55, 0.08, 0.02], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, under reduced staffing. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a4be6fe8811ae7c1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.87, 0.12, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: over the last hour, while on-call rotation changed. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e94ddde0794017bf_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.19, 0.47, 0.32, 0.01], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, immediately after go-live. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b6e57017b17b04be_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, while legacy systems are still active. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d24d4c971fe6f247_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.92, 0.05, 0.02, 0.01], "state": "Node pgsql-14 flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: during the batch window, mid-incident. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8ad646342a5d2f25_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: over the last hour, during peak load. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8905bf85cd6dfd0a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.09, 0.54, 0.36, 0.01, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: in production only, with staffing at reduced levels. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b6e57017b17b04be_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.38, 0.41, 0.19, 0.01], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, while legacy systems are still active. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c2af400c0ab39ff3_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5c76866e57ad1579_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.87, 0.12, 0.0, 0.01], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally flags a step-function change in error slope. Context: across all regions, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_053484595eda5c3c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.92, 0.0, 0.07, 0.01], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8ecfc8dce5a2c073_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.59, 0.38, 0.02, 0.01], "state": "The metrics pipeline correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: in production only, during normal operations. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_15638b9b736bde40_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.66, 0.32, 0.01, 0.01], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: in production only, with a new vendor onboarded. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_64c1d92a14f97bad_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.14, 0.83, 0.03], "state": "The log shipper correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during the morning shift. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0cd87bd885fc91fe_n", "kind": "noul", "options": ["false", "true"], "target": [0.7, 0.3], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: in production only, at the end of the fiscal period. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4089d938fba218e2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.21, 0.26, 0.01, 0.52], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: across all regions, during the quarterly review. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_517fa3126e74beeb_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.73, 0.23, 0.03, 0.01], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, shortly after a software update. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d4d0a1a65fd39dec_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.77, 0.22, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: over the last hour, following a recent audit. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c2e8529d0771b780_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: during the batch window, under reduced staffing. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2b9544613cc677d7_n", "kind": "noul", "options": ["false", "true"], "target": [0.4, 0.6], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, as part of a compliance sweep. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_03408b5a97e22ddd_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.16, 0.09, 0.73, 0.02], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f3f5c519718d4c37_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.7, 0.25, 0.02, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: across all regions, following a recent audit. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1e7dc03ca6a50b91_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.09, 0.03, 0.03, 0.85], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, as part of a compliance sweep. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_42eb8be7859b0fa4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.06, 0.74, 0.19, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: during the batch window, shortly after a software update. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_93c306d96afebdb6_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.0, 0.54, 0.45], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: over the last hour, while on-call rotation changed. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_400a08a44495bcf1_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, mid-incident. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7cdeca455a794b68_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.74, 0.24, 0.01], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: over the last hour, with a new vendor onboarded. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_be180c9265dd3448_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.18, 0.67, 0.13, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d643c372e2ea1da9_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.41, 0.56, 0.01, 0.02], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: during the batch window, with a new vendor onboarded. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fee80017f05005a9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.16, 0.8, 0.04], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: across all regions, with staffing at reduced levels. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_153b1156f6cd3dd7_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: across all regions, mid-incident. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f88f92947aa0bcea_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.11, 0.73, 0.1, 0.0], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: across all regions, during a scheduled maintenance window. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_800d6f67edc05fbe_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.9, 0.09, 0.0, 0.01], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: during the batch window, under an active deadline. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e73c2d000dbc2e33_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.02, 0.46, 0.5], "state": "The log shipper shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: during the batch window, under an active deadline. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_99f3d2731b2ce39a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.21, 0.69, 0.1, 0.0, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during normal operations. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7116a9645b1a1ab7_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.84, 0.15, 0.0, 0.01], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: across all regions, immediately after go-live. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bf64f3f1964fba67_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.72, 0.03, 0.21], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: in production only, during the quarterly review. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a767b3c09a149c00_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.29, 0.52, 0.15, 0.04], "state": "Service catalog-sync lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: in production only, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_62157486128e418b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.62, 0.37, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: in production only, during peak load. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_28c32a9a0fe43d99_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.22, 0.32, 0.45, 0.01], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: in production only, while on-call rotation changed. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4fbd4f19a33531ca_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.02, 0.53, 0.45, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, at the end of the fiscal period. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8ebbcd63edc857f5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.56, 0.43, 0.0], "state": "The log shipper reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during normal operations. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_72f32cc98b1f4832_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.2, 0.7, 0.06], "state": "Service catalog-sync shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: across all regions, during an external partner integration. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a178c13dd2244be2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.44, 0.44, 0.12, 0.0, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: over the last hour, during a scheduled maintenance window. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2f476a7b8bb3fa8c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.34, 0.64, 0.01], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: over the last hour, mid-incident. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_204af7bbcf2b5e94_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: during the batch window, as part of a compliance sweep. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_90cdcea7d09d9275_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.59, 0.4, 0.0], "state": "The log shipper flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: during the batch window, during an external partner integration. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_63b024f8c9661472_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.08, 0.43, 0.01, 0.48], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: in production only, during the morning shift. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_975da4fa25118d20_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.3, 0.43, 0.27, 0.0], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: in production only, with staffing at reduced levels. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_48bc46359d18ce30_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.99, 0.0, 0.0, 0.01], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during the morning shift. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_51d4266f49a57570_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.6, 0.05, 0.01, 0.34], "state": "The metrics pipeline flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: over the last hour, during peak load. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6939c85b4a787f13_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.47, 0.51, 0.01, 0.01], "state": "The log shipper correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: across all regions, while legacy systems are still active. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9121c05c7f9cfe07_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.02, 0.38, 0.58], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, mid-incident. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dadf724772a36d6d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.57, 0.42, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: in production only, during an external partner integration. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b8671d192b8b5dec_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: across all regions, while legacy systems are still active. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_48bba1ea6b87b3a1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.36, 0.48, 0.12, 0.04], "state": "The log shipper reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: across all regions, during the system migration. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d01f6b8a39b5a531_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: over the last hour, immediately after go-live. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a968e8086ac57b95_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Service catalog-sync flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: across all regions, during a scheduled maintenance window. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_18e2129dba1ee58d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.06, 0.13, 0.57, 0.22, 0.01], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0be0dd120daa6d13_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "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.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3f1ba5d6127f05e1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.03, 0.73, 0.23, 0.0], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: over the last hour, during the system migration. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9f674b53a5265be5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.08, 0.4, 0.44, 0.07, 0.0], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, following a recent audit. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7f7f4d11d4dc8bee_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.81, 0.14, 0.04, 0.01], "state": "The log shipper reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: during the batch window, under an active deadline. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_43a1cc2f96063ea9_n", "kind": "noul", "options": ["false", "true"], "target": [0.49, 0.51], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, as part of a compliance sweep. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e9d3efd3420b6b92_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.68, 0.27, 0.03, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: over the last hour, while legacy systems are still active. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_03408b5a97e22ddd_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8c03a06c2b689322_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.02, 0.09, 0.64, 0.24, 0.0], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: in production only, following a recent audit. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_23754b46a24529a9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.15, 0.48, 0.36, 0.01, 0.0], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: across all regions, during the quarterly review. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2bb3641a1eb7a94a_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during an external partner integration. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_907bedbc70095f1b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.08, 0.16, 0.65, 0.1, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally matches last Tuesday's incident signature. Context: in production only, during a scheduled maintenance window. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_09e03f67b8d6e374_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.28, 0.71, 0.01], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: during the batch window, immediately after go-live. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_10bf3efab86ff6a0_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.3939, 0.5556, 0.0505, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: during the batch window, with staffing at reduced levels. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bfdd70984d0564b2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.71, 0.19, 0.06, 0.0], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during the quarterly review. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a74a5846c0d519b2_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.57, 0.41, 0.02, 0.0], "state": "The metrics pipeline flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: during the batch window, during the quarterly review. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cc996809a5a87881_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.05, 0.53, 0.41, 0.0], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: during the batch window, during a scheduled maintenance window. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7f2cc0b58144cbed_n", "kind": "noul", "options": ["false", "true"], "target": [0.66, 0.34], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, under reduced staffing. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_07f97b8fb0268895_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: in production only, following a recent audit. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d7be60fd2231db9a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.81, 0.19, 0.0, 0.0], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: across all regions, with a new vendor onboarded. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7885f1677fba5cb2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.43, 0.2, 0.01, 0.36], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: across all regions, during the quarterly review. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_894f65ab8abff315_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.2, 0.27, 0.44, 0.09], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_53f92526701613b6_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.4, 0.54, 0.05, 0.01], "state": "The log shipper reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: in production only, with staffing at reduced levels. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c380b0d2befb5070_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: across all regions, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f37762b79a186be5_n", "kind": "noul", "options": ["false", "true"], "target": [0.55, 0.45], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: in production only, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6f0eb02cbf85fb98_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.42, 0.55, 0.01], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: in production only, under an active deadline. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_848048a71f969129_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: over the last hour, immediately after go-live. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e8e31882d7461093_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: over the last hour, immediately after go-live. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fed5e0810b51ddc1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.75, 0.16, 0.05, 0.04], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: in production only, during a scheduled maintenance window. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a1a5e9d86e2c463f_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "The metrics pipeline shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: across all regions, immediately after go-live. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_da0f99f458880cd2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.87, 0.0, 0.0, 0.13], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, under an active deadline. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_def972e268d20ccb_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.19, 0.46, 0.34, 0.01], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: in production only, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5de635d89ae898b3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.66, 0.33, 0.0], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: in production only, at the end of the fiscal period. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_93ec4830fbf491e1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.72, 0.21, 0.05, 0.02], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, under an active deadline. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_890bb9cb8a63379f_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during the system migration. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d95a591b3f79cbb1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.27, 0.54, 0.14, 0.0], "state": "The log shipper matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, under reduced staffing. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_83f38134ff999234_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.3, 0.58, 0.08, 0.0], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: across all regions, during the system migration. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_52faf49e5db7130b_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "Service catalog-sync shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: over the last hour, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a2a493ecb5a37652_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.55, 0.44, 0.0], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: across all regions, while legacy systems are still active. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_44a72213db6e07c8_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.96, 0.03, 0.0, 0.01], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: across all regions, shortly after a software update. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8bc827cdd986f5de_n", "kind": "noul", "options": ["false", "true"], "target": [0.66, 0.34], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: in production only, during the quarterly review. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e40a73688c998852_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during an external partner integration. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f47fa71025a1ebd7_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.83, 0.05, 0.01, 0.11], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: over the last hour, under reduced staffing. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_529b143127e6bfc9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.08, 0.39, 0.49, 0.04, 0.0], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: during the batch window, following a recent audit. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1596da3f8c3755b7_n", "kind": "noul", "options": ["false", "true"], "target": [0.48, 0.52], "state": "The log shipper returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the morning shift. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2a31c9e043025ddf_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.2, 0.55, 0.2, 0.01], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: in production only, during normal operations. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c8c4fc083424ebda_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.54, 0.38, 0.07, 0.01], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: in production only, shortly after a software update. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5106d0b9782340ac_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: across all regions, during normal operations. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5f10d7085b230712_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.34, 0.01, 0.36, 0.29], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the system migration. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_582d13bda168e8e9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.25, 0.0, 0.63, 0.12], "state": "The metrics pipeline correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: during the batch window, during peak load. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_18c36210a27910f6_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.01, 0.48, 0.47], "state": "The log shipper reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: in production only, under reduced staffing. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_91da20bdfaadc1ea_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.67, 0.3, 0.03, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: during the batch window, during the quarterly review. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0cc1c97c951a8113_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.48, 0.5, 0.02, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: across all regions, as part of a compliance sweep. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_83dbfe07a39d825b_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "The log shipper flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: in production only, during an external partner integration. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c83a62c743bf4e55_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.28, 0.07, 0.07, 0.58], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: during the batch window, following a recent audit. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_49cb1d19fa66a9a1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.33, 0.67, 0.0], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: over the last hour, during an external partner integration. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_245db2010c6eae9a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.92, 0.02, 0.03, 0.03], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, with staffing at reduced levels. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bee02318a3c9a9f8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.19, 0.78, 0.03], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: across all regions, shortly after a software update. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_beb05f659f3c2cd6_n", "kind": "noul", "options": ["false", "true"], "target": [0.38, 0.62], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: across all regions, following a recent audit. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_585afcaa3f6fd825_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.12, 0.14, 0.03, 0.71], "state": "Service catalog-sync flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: in production only, following a recent audit. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_44d8ba99e74061f9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.96, 0.0, 0.0, 0.04], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: in production only, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_53d1c4a3a969f2d1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.35, 0.64, 0.01], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during peak load. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_119e9cdd197fe522_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, at the end of the fiscal period. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9c36bfd60aca0063_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during the system migration. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4333b632dc8104dd_n", "kind": "noul", "options": ["false", "true"], "target": [0.48, 0.52], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: in production only, during the quarterly review. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4f6f81272d9c789c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.13, 0.28, 0.5, 0.08, 0.0], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: in production only, during a scheduled maintenance window. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ac552ffd8f24efe_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.28, 0.71, 0.01], "state": "The log shipper flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: in production only, under reduced staffing. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_121e836575d8c3d4_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The log shipper correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: across all regions, at the end of the fiscal period. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_35809d69147bb034_n", "kind": "noul", "options": ["false", "true"], "target": [0.62, 0.38], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: over the last hour, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8fc8d29a6ad476ea_n", "kind": "noul", "options": ["false", "true"], "target": [0.41, 0.59], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: across all regions, immediately after go-live. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0cd87bd885fc91fe_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.62, 0.01, 0.01, 0.36], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: in production only, at the end of the fiscal period. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_43517daf835f7502_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.09, 0.04, 0.86], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, as part of a compliance sweep. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_46c37dc041e128d7_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.05, 0.78, 0.16, 0.01], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, following a recent audit. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a8ac7e4a18959862_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.64, 0.28, 0.07, 0.01], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: in production only, during the system migration. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ef5a129d99ba731b_n", "kind": "noul", "options": ["false", "true"], "target": [0.18, 0.82], "state": "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.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9731f57ad8294fc5_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.92, 0.06, 0.01, 0.01], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, mid-incident. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9f856652dd67bde0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.22, 0.67, 0.07, 0.04, 0.0, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: during the batch window, during the holiday freeze. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e2d08655d2028dec_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: in production only, mid-incident. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c3a2ada5d16a2084_n", "kind": "noul", "options": ["false", "true"], "target": [0.44, 0.56], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: over the last hour, during the morning shift. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f8b5603a91f7e25f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.17, 0.73, 0.07, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, following a recent audit. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_290699e716823253_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.85, 0.07, 0.07], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: in production only, shortly after a software update. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fb0dd12ba7d6d1a4_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.74, 0.23, 0.02, 0.01], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the morning shift. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c5e7178510278fdf_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.37, 0.54, 0.09, 0.0, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during the system migration. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1583f50fa2d0bdd3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.34, 0.52, 0.13, 0.01, 0.0], "state": "The log shipper lost 4 minutes of trace data; 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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_51af7aa51dae33a3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.24, 0.71, 0.03, 0.0], "state": "The metrics pipeline flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: over the last hour, under reduced staffing. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c44bf3123b7c5a41_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.35, 0.63, 0.01], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: in production only, mid-incident. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8384da0f35839714_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.31, 0.67, 0.01], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: during the batch window, during the holiday freeze. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d7616fff436ca2fb_n", "kind": "noul", "options": ["false", "true"], "target": [0.56, 0.44], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during the quarterly review. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_546cbcb774596f37_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.0, 0.9, 0.07], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: over the last hour, during normal operations. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f0510f5114fb2d5e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.52, 0.38, 0.1, 0.0], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: across all regions, with a new vendor onboarded. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d9c469bca95a91f8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.79, 0.2, 0.0], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: in production only, while legacy systems are still active. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c408e7af0ba3b01f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.08, 0.19, 0.62, 0.11, 0.0], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: during the batch window, shortly after a software update. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0e5893ed2aba1568_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.16, 0.48, 0.33, 0.02, 0.0], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: over the last hour, during an external partner integration. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_46b7cda5a15425ce_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.12, 0.79, 0.09, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: during the batch window, while on-call rotation changed. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0e7dcc3a4ef51be4_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "The log shipper lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: in production only, under an active deadline. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_21837cf7ba18fb90_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.1, 0.23, 0.55, 0.12], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_69cb1976f77780b2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.08, 0.0, 0.82, 0.1], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: across all regions, during peak load. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c60c33f721de1244_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.0, 0.08, 0.88, 0.04], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, with a new vendor onboarded. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b4aaf3f418057758_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during the holiday freeze. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c9f3695f5fd555d6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.3, 0.46, 0.22, 0.01], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6405e58deabe4c14_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The metrics pipeline correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: during the batch window, mid-incident. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5d47ce3af524486f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.62, 0.19, 0.05, 0.14], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: during the batch window, while on-call rotation changed. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_51d4266f49a57570_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.49, 0.5, 0.0], "state": "The metrics pipeline flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: over the last hour, during peak load. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_37cf5fda142ee2d9_n", "kind": "noul", "options": ["false", "true"], "target": [0.64, 0.36], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during the holiday freeze. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_89926e2d3926f815_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: across all regions, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1bde45a30bbfa4db_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.76, 0.0, 0.23], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: in production only, shortly after a software update. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c85f5a2157fccc40_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: over the last hour, mid-incident. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bd2d0cdc91497dc1_n", "kind": "noul", "options": ["false", "true"], "target": [0.59, 0.41], "state": "The log shipper shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: in production only, with a new vendor onboarded. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_35d35ecad4874601_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: over the last hour, under an active deadline. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3d0c3a2c90a90d29_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: in production only, under an active deadline. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0c5b0e5fa71ece38_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.34, 0.65, 0.01], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: in production only, during normal operations. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f1cd3e6c603143d2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.43, 0.54, 0.01], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: across all regions, mid-incident. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ea20420b7e883739_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: over the last hour, during a scheduled maintenance window. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_504d32baf68334f2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.58, 0.37, 0.01, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: over the last hour, shortly after a software update. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_44872c5979084e16_n", "kind": "noul", "options": ["false", "true"], "target": [0.43, 0.57], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during an external partner integration. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_214cf9eb8da30da8_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: during the batch window, during the morning shift. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_978885345c00db55_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.52, 0.46, 0.01], "state": "The log shipper flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: over the last hour, during the quarterly review. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8f77efe77d58fdec_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.57, 0.42, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: in production only, shortly after a software update. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2f14d116ce3faf91_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: in production only, during the system migration. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2c3418ea1663c143_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.96, 0.04, 0.0, 0.0], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: in production only, under reduced staffing. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8df7816c5c79884c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.12, 0.18, 0.57, 0.11, 0.01], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: over the last hour, shortly after a software update. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9c2970010102bbee_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.42, 0.54, 0.03, 0.01], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: during the batch window, during an external partner integration. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a9986de765179e80_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.21, 0.78, 0.01], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: over the last hour, during an external partner integration. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_676e54d127c715db_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.67, 0.32, 0.0], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: over the last hour, during normal operations. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_298edecf69f7d6c6_n", "kind": "noul", "options": ["false", "true"], "target": [0.57, 0.43], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: across all regions, shortly after a software update. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f199f6c665ae999d_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: in production only, immediately after go-live. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_97f4ad10da01e9d3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.17, 0.77, 0.06], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: over the last hour, following a recent audit. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_28f7f287b7ad5c59_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.06, 0.55, 0.38, 0.0], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: in production only, immediately after go-live. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_54719746d29696c5_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.02, 0.27, 0.71, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the quarterly review. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f3fbfe3f13be8618_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.17, 0.72, 0.08, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, shortly after a software update. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5cbedb575cb6174b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.13, 0.85, 0.02], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during peak load. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_78b4ef98d6b25c50_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: over the last hour, during the system migration. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2af8710379a6f6bb_n", "kind": "noul", "options": ["false", "true"], "target": [0.49, 0.51], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: across all regions, while legacy systems are still active. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eb112ee6526c5937_n", "kind": "noul", "options": ["false", "true"], "target": [0.22, 0.78], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: over the last hour, while legacy systems are still active. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0cc1c97c951a8113_n", "kind": "noul", "options": ["false", "true"], "target": [0.68, 0.32], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: across all regions, as part of a compliance sweep. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_312b43ff6569d76b_n", "kind": "noul", "options": ["false", "true"], "target": [0.9, 0.1], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during the system migration. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_268d94dd53f57fe3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.49, 0.5, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: across all regions, following a recent audit. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a051f3dbede6022f_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "The log shipper correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: across all regions, during an external partner integration. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_928dce781c980e91_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.1, 0.06, 0.03, 0.81], "state": "The log shipper lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: during the batch window, during the holiday freeze. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3f71b728b03afc43_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.68, 0.02, 0.28], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: in production only, shortly after a software update. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_785dfa5b87bec041_n", "kind": "noul", "options": ["false", "true"], "target": [0.91, 0.09], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, under an active deadline. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cf2527fbacc2c34a_n", "kind": "noul", "options": ["false", "true"], "target": [0.58, 0.42], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: during the batch window, during a scheduled maintenance window. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c423434da9e809a6_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: over the last hour, during an external partner integration. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_88ea141de90fa34b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.6, 0.28, 0.1, 0.02], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, immediately after go-live. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_36723f448ba45f01_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: across all regions, during the holiday freeze. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_95a7c8a1230d242c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.69, 0.29, 0.0], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_212bbe79f6c1935b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.88, 0.11, 0.01, 0.0], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_473d1ec7670fe3a5_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "The metrics pipeline lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: in production only, under reduced staffing. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4de3bf7802faa79a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.01, 0.15, 0.82], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: across all regions, at the end of the fiscal period. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4a939a33ff19ebc4_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: in production only, under reduced staffing. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fde66e0fe94ff3bd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.71, 0.28, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: during the batch window, shortly after a software update. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_639ff2a14f558dcf_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: over the last hour, mid-incident. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2b06737ffdd3d9ae_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.83, 0.03, 0.05, 0.09], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, under reduced staffing. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_83f38134ff999234_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.02, 0.33, 0.61, 0.04], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: across all regions, during the system migration. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_924b0bcead71b0e7_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.27, 0.23, 0.02, 0.48], "state": "The log shipper shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during normal operations. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dcfa721e339ad37e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.61, 0.36, 0.02, 0.01], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: during the batch window, during the quarterly review. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_db578b9fcef917f2_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: over the last hour, while on-call rotation changed. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_41bfbba83f83017a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.73, 0.18, 0.07, 0.02], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally flags a step-function change in error slope. Context: in production only, during a scheduled maintenance window. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8d66c145f5cfa212_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.45, 0.53, 0.01], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c83bfa4f23bdafa6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.25, 0.49, 0.26, 0.0, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: during the batch window, during the morning shift. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d969e5d48e90c358_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.24, 0.75, 0.01], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during the morning shift. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4dcef18f0c1f2438_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.0, 0.22, 0.77, 0.01], "state": "Service catalog-sync shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: during the batch window, while legacy systems are still active. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2688bef52a52abd1_n", "kind": "noul", "options": ["false", "true"], "target": [0.7, 0.3], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: across all regions, at the end of the fiscal period. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8b076748302085c8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.2, 0.79, 0.01], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: in production only, while legacy systems are still active. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f5a84925684d56a1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.96, 0.0, 0.01, 0.03], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during the morning shift. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_79f82059fe1650c5_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.29, 0.67, 0.04, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: in production only, following a recent audit. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b76a51f421438db6_n", "kind": "noul", "options": ["false", "true"], "target": [0.69, 0.31], "state": "The log shipper reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: during the batch window, during an external partner integration. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_92e1384e08d3986d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.52, 0.46, 0.01], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: across all regions, during the system migration. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_13a6d05023596613_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.17, 0.69, 0.12, 0.02], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_723c1a63c27ae04d_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: across all regions, under reduced staffing. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bdfcb254d9376760_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.6, 0.34, 0.01], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: across all regions, as part of a compliance sweep. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_936ee6f5862098e6_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.02, 0.89, 0.09, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: over the last hour, during an external partner integration. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_abade13fa03ae66a_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: in production only, during the morning shift. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a095274d6b0484e5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.36, 0.59, 0.03], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: over the last hour, during the system migration. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7275e3a614ff1615_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.54, 0.45, 0.0], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: during the batch window, during peak load. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e930831482b59e58_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.93, 0.04, 0.0, 0.03], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: in production only, under an active deadline. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_084ff4ce18527269_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.1, 0.27, 0.49, 0.14], "state": "Node pgsql-14 flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: across all regions, while legacy systems are still active. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1fb4b566884b701a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.14, 0.52, 0.27, 0.01], "state": "The metrics pipeline 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 operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca506297b3ad9fb6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.66, 0.33, 0.0], "state": "Service catalog-sync flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: during the batch window, shortly after a software update. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c6b805d255ae34b3_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: in production only, under an active deadline. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_020d5bb9d171472c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.46, 0.51, 0.01], "state": "The log shipper shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: during the batch window, during the system migration. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0dbb5c90e33dd3d5_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during the holiday freeze. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_833dc0d74faeac74_n", "kind": "noul", "options": ["false", "true"], "target": [0.56, 0.44], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: across all regions, during a scheduled maintenance window. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_75dea4ef284873bb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.34, 0.64, 0.01], "state": "Service catalog-sync 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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8b813f3c190927ad_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: across all regions, under an active deadline. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e670cd89105aaf80_n", "kind": "noul", "options": ["false", "true"], "target": [0.67, 0.33], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: during the batch window, during the morning shift. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ff697dca850bf64c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.11, 0.71, 0.02, 0.16], "state": "The log shipper flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: over the last hour, following a recent audit. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7467c6f62e8a76e8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.02, 0.81, 0.17], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: across all regions, under an active deadline. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1e632400d4131ecf_n", "kind": "noul", "options": ["false", "true"], "target": [0.51, 0.49], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: over the last hour, during the system migration. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fb0dd12ba7d6d1a4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.32, 0.66, 0.01], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the morning shift. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7e1e862e853db28f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.02, 0.45, 0.5], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: across all regions, during the quarterly review. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_642ba8e159385f66_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.06, 0.0, 0.16, 0.78], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_21e7ba63ecda4e23_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.35, 0.01, 0.37, 0.27], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during a scheduled maintenance window. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_90e3a7e12df5e349_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: across all regions, shortly after a software update. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_70d49e49e5f42c45_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.26, 0.33, 0.02, 0.39], "state": "The metrics pipeline shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: over the last hour, with staffing at reduced levels. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b4a163a140949f74_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.09, 0.82, 0.09, 0.0, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during normal operations. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6b6c375dbbd121a1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.57, 0.06, 0.01, 0.36], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during the system migration. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_85862de7230ae993_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.98, 0.01, 0.0, 0.01], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, immediately after go-live. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_37c3f5ed1c53d327_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: in production only, during peak load. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cb0d4d3da55cb5c4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.07, 0.66, 0.27, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: over the last hour, under an active deadline. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d98a984eaed56a47_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.11, 0.81, 0.08], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_620918a8930534d4_n", "kind": "noul", "options": ["false", "true"], "target": [0.7, 0.3], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: in production only, while on-call rotation changed. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_280735b7c9e3176f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.41, 0.52, 0.02], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during the holiday freeze. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_275a17c984928081_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.83, 0.16, 0.01, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: during the batch window, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6fbc8c0a75976305_n", "kind": "noul", "options": ["false", "true"], "target": [0.63, 0.37], "state": "Service catalog-sync flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: during the batch window, while on-call rotation changed. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bbcb92db03191654_n", "kind": "noul", "options": ["false", "true"], "target": [0.67, 0.33], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: in production only, during a scheduled maintenance window. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_468b3cac759689bb_n", "kind": "noul", "options": ["false", "true"], "target": [0.4, 0.6], "state": "Service catalog-sync flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: in production only, during normal operations. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_da1cce04235ca6f4_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The log shipper correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: in production only, shortly after a software update. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ef82a64766ff1b8b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.69, 0.29, 0.02, 0.0], "state": "The log shipper flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: across all regions, during the holiday freeze. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e32ef1e1fed78397_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0101, 0.0505, 0.0909, 0.6768, 0.1717, 0.0], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: in production only, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7025d60160a8628e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.18, 0.8, 0.02], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: during the batch window, under an active deadline. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0d568a1e2db91f59_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.07, 0.47, 0.37, 0.09, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: in production only, mid-incident. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e43d4740833e8d5b_n", "kind": "noul", "options": ["false", "true"], "target": [0.44, 0.56], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: across all regions, under reduced staffing. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cf899c2c42d90245_n", "kind": "noul", "options": ["false", "true"], "target": [0.49, 0.51], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during the morning shift. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_781e354bbbdaa175_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.51, 0.48, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: over the last hour, while legacy systems are still active. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c09ae2db19be2204_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0707, 0.5657, 0.3434, 0.0202, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: over the last hour, during the holiday freeze. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_637fc0288a3bf1c0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.15, 0.83, 0.02], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during the morning shift. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a262d3fd496342a2_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: during the batch window, during the quarterly review. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f388432d9def5579_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: across all regions, as part of a compliance sweep. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f51bdb8c25ef04ab_n", "kind": "noul", "options": ["false", "true"], "target": [0.71, 0.29], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: over the last hour, while on-call rotation changed. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_14fd7fd348ed406c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.76, 0.24, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: during the batch window, while on-call rotation changed. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e232cdcc94d54785_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.05, 0.55, 0.39, 0.01], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: across all regions, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_835fa6c3c98f92a5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.35, 0.62, 0.02], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: during the batch window, immediately after go-live. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eccf4d2cc0213b5f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.13, 0.79, 0.07, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during a scheduled maintenance window. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_69c45c3caf7d632b_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The log shipper reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: over the last hour, during normal operations. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_901674df022a7e68_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.52, 0.0, 0.46, 0.02], "state": "Service catalog-sync correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: across all regions, during peak load. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_da3a579b97150681_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.03, 0.26, 0.69, 0.02], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: in production only, during normal operations. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c8089628aeaff1a5_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: in production only, during the morning shift. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ab02b7345f8a9345_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "The log shipper shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: during the batch window, under an active deadline. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_93961702b07ef9c1_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, under reduced staffing. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c122da7d0e940ed8_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: across all regions, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f5c5f643919c1fa0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0404, 0.5354, 0.404, 0.0202, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: across all regions, during the system migration. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_05662335e3e69f50_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: in production only, during an external partner integration. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2fb97583af14319e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.22, 0.71, 0.06, 0.01], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, following a recent audit. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d08ec3c762c7ae95_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.15, 0.79, 0.06], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: over the last hour, during normal operations. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f75ded48dc776781_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.59, 0.4, 0.01, 0.0], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: across all regions, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4510d41fe66c2650_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.36, 0.48, 0.15, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during the morning shift. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ad61efb97e1f4ef9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.07, 0.28, 0.62, 0.03, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: across all regions, following a recent audit. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4fa9c64ff2b94b10_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "The log shipper shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: over the last hour, during an external partner integration. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a5ebac9ada98850f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.53, 0.47, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: over the last hour, with staffing at reduced levels. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_069b055d1fda653b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.34, 0.25, 0.01, 0.4], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1a29f885c3d05831_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.43, 0.55, 0.01], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: in production only, shortly after a software update. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_642ba8e159385f66_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.22, 0.43, 0.35, 0.0, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_513e29d2a5d94b3a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.07, 0.01, 0.46, 0.46], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: in production only, while legacy systems are still active. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ae322b5b8bb607cc_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during the morning shift. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1eee00fd316ed8cf_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, under an active deadline. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3c48d3a073d3a744_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.3, 0.29, 0.02, 0.39], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: during the batch window, during the morning shift. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_347886fdf4b055a7_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during normal operations. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f6ba756a5a0b8c71_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.93, 0.06, 0.0, 0.01], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: across all regions, under an active deadline. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1b8eaa85db6cb04f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.86, 0.04, 0.02, 0.08], "state": "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 supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6d3b3129ce2d6da5_n", "kind": "noul", "options": ["false", "true"], "target": [0.9, 0.1], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during the quarterly review. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_35d35ecad4874601_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.31, 0.66, 0.02], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: over the last hour, under an active deadline. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4a2eed05ea3d2edb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.08, 0.84, 0.08], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: in production only, during the holiday freeze. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ed91a614e1108c87_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.4, 0.02, 0.06, 0.52], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: over the last hour, with staffing at reduced levels. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_59cf98ce906ed507_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.73, 0.01, 0.0, 0.26], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: in production only, following a recent audit. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ade0fbc0c3a1a2c5_n", "kind": "noul", "options": ["false", "true"], "target": [0.47, 0.53], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: in production only, as part of a compliance sweep. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d5586cc048399312_n", "kind": "noul", "options": ["false", "true"], "target": [0.65, 0.35], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: over the last hour, following a recent audit. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2865a50ef29772c6_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: over the last hour, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_39406ae45de15130_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.07, 0.73, 0.19, 0.0], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: during the batch window, as part of a compliance sweep. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2277e31551ca9e53_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.98, 0.02, 0.0, 0.0], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: across all regions, under an active deadline. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a426fc7a77b786b1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.79, 0.0, 0.05, 0.16], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: in production only, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2bb3641a1eb7a94a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.25, 0.0, 0.73, 0.02], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during an external partner integration. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_67dabcbe7f0b42bf_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.03, 0.42, 0.51, 0.02], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: over the last hour, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dc0f96a446849eb1_n", "kind": "noul", "options": ["false", "true"], "target": [0.65, 0.35], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: over the last hour, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4f6f3bd7b7c5ab70_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "The log shipper flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: in production only, following a recent audit. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4e4a57a4719829bc_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.23, 0.69, 0.07], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: across all regions, during normal operations. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0e18bd2801ffdb37_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.31, 0.56, 0.1, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: during the batch window, during the holiday freeze. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e88d3046f8791d91_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "The log shipper lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: over the last hour, under reduced staffing. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2b5e426e13e4097f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.57, 0.33, 0.08, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during peak load. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dde1c5d822c29931_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.48, 0.51, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: across all regions, following a recent audit. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c9c7edeab820f646_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.21, 0.19, 0.01, 0.59], "state": "Node pgsql-14 flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: in production only, mid-incident. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f03d9859a36bf9c7_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.06, 0.4, 0.53], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: over the last hour, as part of a compliance sweep. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_319f9cf43356acd3_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: over the last hour, shortly after a software update. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7d090c18c10f1c54_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.15, 0.83, 0.02], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: in production only, following a recent audit. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_534519c6a9e9a124_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.77, 0.21, 0.01, 0.01], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, while on-call rotation changed. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f0a83b00a2361202_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: in production only, shortly after a software update. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8f169565ba6b09a5_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.48, 0.02, 0.27, 0.23], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, at the end of the fiscal period. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b030858a4608ba2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.01, 0.08, 0.86], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: during the batch window, mid-incident. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_99f6d46720facfa5_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.12, 0.8, 0.06, 0.02], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, following a recent audit. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3f942772df45ce87_n", "kind": "noul", "options": ["false", "true"], "target": [0.53, 0.47], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: across all regions, with a new vendor onboarded. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6824c699ce579415_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.26, 0.69, 0.05, 0.0], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: across all regions, at the end of the fiscal period. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_166ed5cd125df9d1_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: in production only, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_35664a9df45215ea_n", "kind": "noul", "options": ["false", "true"], "target": [0.58, 0.42], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during peak load. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_06424dc1a84fc63b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.96, 0.0, 0.04], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: over the last hour, shortly after a software update. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6583018f16aa9359_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: over the last hour, with staffing at reduced levels. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_961c4e5381856f9e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.06, 0.03, 0.9], "state": "The log shipper matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: in production only, while on-call rotation changed. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b160c7b04d538eb5_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.01, 0.44, 0.52], "state": "The log shipper shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: over the last hour, during the holiday freeze. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e7c18444cda0eae9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.15, 0.63, 0.16, 0.0], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: during the batch window, as part of a compliance sweep. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b1621a960a29320e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.01, 0.61, 0.36], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: in production only, under an active deadline. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_53d1c4a3a969f2d1_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during peak load. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c13fe4bb72684187_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.22, 0.64, 0.14, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: over the last hour, while legacy systems are still active. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_967b0b75cee0e199_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: over the last hour, during the holiday freeze. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e40a73688c998852_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.83, 0.12, 0.03, 0.02], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during an external partner integration. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_71f5c4b8f6778c01_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.42, 0.46, 0.1, 0.0], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during the holiday freeze. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c97be4dbb893c35a_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "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 an external partner integration. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2acdfd4e4a77c6c9_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: during the batch window, under reduced staffing. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bf64f3f1964fba67_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: in production only, during the quarterly review. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_12b1ca0108f9d3dc_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.4, 0.55, 0.04, 0.01], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: across all regions, as part of a compliance sweep. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_329c2b47632bf512_n", "kind": "noul", "options": ["false", "true"], "target": [0.23, 0.77], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during the holiday freeze. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1110ef5f9271cdd1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.36, 0.48, 0.14, 0.01, 0.0], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eb5e389c3df44f62_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.16, 0.67, 0.17, 0.0], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a257fcfa0baa6053_n", "kind": "noul", "options": ["false", "true"], "target": [0.61, 0.39], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: over the last hour, shortly after a software update. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3d4dd6d3b06567ec_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.2, 0.75, 0.05], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: across all regions, mid-incident. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4789c62be23dc7ce_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.12, 0.48, 0.04, 0.36], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: during the batch window, during the quarterly review. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ddd53badb1354305_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during the holiday freeze. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9f0becfd17c7b108_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.13, 0.8, 0.07], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during a scheduled maintenance window. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ba23a0abeef89bac_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.06, 0.87, 0.07], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, under reduced staffing. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_94c410685d9dcb51_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.32, 0.65, 0.02], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: across all regions, with staffing at reduced levels. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_47740b1e2abd1e22_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.03, 0.11, 0.56, 0.28, 0.01], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: in production only, under reduced staffing. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_745f9e31eea67a99_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.23, 0.75, 0.02], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: during the batch window, while legacy systems are still active. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eae2faba9ae45163_n", "kind": "noul", "options": ["false", "true"], "target": [0.5, 0.5], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: in production only, during a scheduled maintenance window. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2255f8529bc56d28_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: across all regions, during the morning shift. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_33f6c3fb7ce0cd38_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.83, 0.15, 0.01, 0.01], "state": "The log shipper flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: across all regions, during the holiday freeze. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_478e92f3536ea767_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.08, 0.43, 0.46, 0.03, 0.0], "state": "The log shipper reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: during the batch window, mid-incident. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2a3ea9df5a1bc6e4_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.0, 0.97, 0.02], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: during the batch window, following a recent audit. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6e842d6be5fa07d2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.13, 0.42, 0.44, 0.01, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: over the last hour, with a new vendor onboarded. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_62ab8c74ee22b33a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.02, 0.7, 0.27, 0.01], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: during the batch window, under reduced staffing. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c1f63eda4321999c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.08, 0.58, 0.32, 0.01], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: across all regions, mid-incident. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_25772914d7ca27d1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.8, 0.16, 0.01, 0.03], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: in production only, during normal operations. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6f35375bb2aeb954_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.14, 0.83, 0.03], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during normal operations. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6ece76fb8913b976_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.06, 0.88, 0.05, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: across all regions, during the quarterly review. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e2a3e3e62ba5de23_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.72, 0.27, 0.01, 0.0], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: across all regions, during the system migration. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_13304d52bb2d1fae_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.28, 0.7, 0.02], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: over the last hour, immediately after go-live. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_01360f5c6c52459a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.01, 0.55, 0.39], "state": "The log shipper shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: across all regions, during the holiday freeze. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_af7fa10f09678d47_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: during the batch window, shortly after a software update. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1cf9f0d3cfca3e8a_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during the quarterly review. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c182ce7efb082c0e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.18, 0.8, 0.02], "state": "Service catalog-sync 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 on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d99970ae3f1a446d_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during peak load. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7e1e862e853db28f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.09, 0.4, 0.48, 0.03, 0.0], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: across all regions, during the quarterly review. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8a5c4babefb361ca_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.86, 0.1, 0.02, 0.02], "state": "The metrics pipeline flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during the holiday freeze. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_606798a0f69dfd68_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.9394, 0.0202, 0.0101, 0.0303], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, as part of a compliance sweep. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_76bdd9f766d045c3_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "The log shipper reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: during the batch window, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7b5966e621aeef56_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.1, 0.83, 0.07], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: over the last hour, during the holiday freeze. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_865bb4d160eec35f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.34, 0.55, 0.1, 0.01], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: during the batch window, while legacy systems are still active. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_28b87ce873ad21ba_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.3, 0.69, 0.01], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: during the batch window, during peak load. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b8903fa1b9b72984_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.16, 0.82, 0.02], "state": "The log shipper correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: over the last hour, during peak load. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bf64382602706fab_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during an external partner integration. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9a4c6c8f98b76f55_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "Node pgsql-14 flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: across all regions, during an external partner integration. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_321983923609e9b6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.21, 0.71, 0.07, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, as part of a compliance sweep. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4a2eed05ea3d2edb_n", "kind": "noul", "options": ["false", "true"], "target": [0.18, 0.82], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: in production only, during the holiday freeze. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b6ec7181a44acfe3_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: over the last hour, immediately after go-live. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f28d8c77725efe8b_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: over the last hour, under an active deadline. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_64323ef9c51a5279_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.15, 0.05, 0.76], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: over the last hour, following a recent audit. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_262c83ad778ebde9_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: across all regions, during the holiday freeze. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0f169180279b0e05_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.56, 0.41, 0.01], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: in production only, during an external partner integration. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f1d6a67f50c86bea_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.51, 0.49, 0.0], "state": "The metrics pipeline flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: over the last hour, shortly after a software update. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_99f2ee62848e722f_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "The metrics pipeline 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 review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f24379de7d51da06_n", "kind": "noul", "options": ["false", "true"], "target": [0.62, 0.38], "state": "The log shipper shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: across all regions, during the holiday freeze. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c892194b64a23f3a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.26, 0.73, 0.01], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: during the batch window, with a new vendor onboarded. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c50e3c902ea23020_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.2, 0.17, 0.15, 0.48], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: in production only, during the holiday freeze. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c52e59a9ad46c8c9_n", "kind": "noul", "options": ["false", "true"], "target": [0.71, 0.29], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, immediately after go-live. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d2750fa8381dd3c2_n", "kind": "noul", "options": ["false", "true"], "target": [0.61, 0.39], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: during the batch window, as part of a compliance sweep. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c72c0c108d60f47c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.09, 0.66, 0.23, 0.02, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: in production only, during an external partner integration. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e6860f2cdec64992_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.04, 0.78, 0.18, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: across all regions, during the system migration. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e10bb6384fe1548f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.05, 0.65, 0.28, 0.01], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: over the last hour, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5a074d11ac3e5840_n", "kind": "noul", "options": ["false", "true"], "target": [0.71, 0.29], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: across all regions, during the system migration. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3c8054a56a7360ee_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.55, 0.45, 0.0], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: in production only, during an external partner integration. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dc3f2f13f5e5698e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.14, 0.67, 0.19, 0.0, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: in production only, during normal operations. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d254c5640cb44c16_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: over the last hour, during normal operations. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7edf279828e4417e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.27, 0.65, 0.07, 0.01], "state": "The log shipper shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: in production only, with a new vendor onboarded. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5529705762f31a4d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.12, 0.7, 0.04, 0.14], "state": "The metrics pipeline 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 operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_44a353ca23a860f5_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: during the batch window, during the quarterly review. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_033149b8bcd98fc1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.69, 0.0, 0.09, 0.22], "state": "The log shipper returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during an external partner integration. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e41c8641faf49f24_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: in production only, with a new vendor onboarded. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_440d56252ff6d322_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.01, 0.37, 0.57], "state": "The log shipper reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: across all regions, under reduced staffing. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_027c9763cef774d4_n", "kind": "noul", "options": ["false", "true"], "target": [0.23, 0.77], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: in production only, with staffing at reduced levels. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_61942adc56474cdf_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.5, 0.44, 0.01], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: across all regions, following a recent audit. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a178c13dd2244be2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.06, 0.01, 0.27, 0.66], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: over the last hour, during a scheduled maintenance window. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d793baadbb4826d3_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.56, 0.41, 0.03, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: across all regions, under reduced staffing. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a0528e186c5ef986_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: over the last hour, during the morning shift. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b23250c791b5e544_n", "kind": "noul", "options": ["false", "true"], "target": [0.68, 0.32], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: in production only, during the morning shift. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_96a63b219bc5c215_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.38, 0.15, 0.03, 0.44], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: in production only, while on-call rotation changed. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1b57621f08128cb1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.3, 0.68, 0.01], "state": "The log shipper reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: over the last hour, under reduced staffing. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_27ff8cfde95ffcc9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.07, 0.2, 0.41, 0.32], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the system migration. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_15403d7b1d1f70cd_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: in production only, during the system migration. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2d8d9da10247eb1b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.09, 0.58, 0.32, 0.01], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: during the batch window, while on-call rotation changed. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2670c947e9e3c315_n", "kind": "noul", "options": ["false", "true"], "target": [0.7, 0.3], "state": "The log shipper matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: during the batch window, mid-incident. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5c76866e57ad1579_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.11, 0.83, 0.06], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally flags a step-function change in error slope. Context: across all regions, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_98eeb572a6a387ed_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.27, 0.72, 0.01], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f3900f85aac5a6bc_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.98, 0.0, 0.0, 0.02], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: in production only, under reduced staffing. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_055e1a0cf92a7d2b_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: in production only, with staffing at reduced levels. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e638212cd6faff73_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.24, 0.71, 0.04, 0.01], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: across all regions, as part of a compliance sweep. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ede2d168903bcca5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.75, 0.23, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during normal operations. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c059b5cb4e6adea1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.45, 0.53, 0.01], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: over the last hour, while legacy systems are still active. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e06a3ff86270f6af_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.5, 0.48], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: over the last hour, with a new vendor onboarded. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_06cdae4e93e4966a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.27, 0.49, 0.22, 0.01], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, while on-call rotation changed. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fd6d27eae7c8c374_n", "kind": "noul", "options": ["false", "true"], "target": [0.7, 0.3], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: in production only, as part of a compliance sweep. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7cde686750879b14_n", "kind": "noul", "options": ["false", "true"], "target": [0.7, 0.3], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during peak load. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_988e5797e485e4c0_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: during the batch window, during the morning shift. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_296a5aaaa21f5cf1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.61, 0.34, 0.03, 0.02], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: during the batch window, under reduced staffing. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0d329ba81bc3a874_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "The log shipper reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: over the last hour, during the quarterly review. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c848524b4459a509_n", "kind": "noul", "options": ["false", "true"], "target": [0.43, 0.57], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the morning shift. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_15cf87675cd63644_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: across all regions, during the morning shift. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0050c0907da73be7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.34, 0.65, 0.01], "state": "The log shipper reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: during the batch window, shortly after a software update. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e786f58ccb822066_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.27, 0.28, 0.02, 0.43], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: across all regions, while on-call rotation changed. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_269ed858d810daff_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.05, 0.51, 0.32, 0.12], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: in production only, during normal operations. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8727bbe0322250d7_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.99, 0.01, 0.0, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: across all regions, under an active deadline. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_da6384c63ed0e1db_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.0, 0.21, 0.78], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: in production only, during a scheduled maintenance window. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c3389c61e89d727a_n", "kind": "noul", "options": ["false", "true"], "target": [0.61, 0.39], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during the holiday freeze. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5bdf8b5533b72222_n", "kind": "noul", "options": ["false", "true"], "target": [0.18, 0.82], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a09944e314d7ad09_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.11, 0.84, 0.05], "state": "The log shipper reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: across all regions, following a recent audit. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_00bf28b49e3b9b78_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.4, 0.44, 0.13, 0.03], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, mid-incident. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_10e8a1b1d307d5f8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.27, 0.73, 0.0], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: across all regions, during the morning shift. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c628e485afbd8145_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.75, 0.22, 0.02, 0.01], "state": "The log shipper matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: in production only, shortly after a software update. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1e783e44639ee69f_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, following a recent audit. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3a42dfa097784dad_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: over the last hour, during normal operations. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b6afaf1df11e5af1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.18, 0.26, 0.44, 0.12], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: in production only, while legacy systems are still active. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_62bcb6b28c7f1ffa_n", "kind": "noul", "options": ["false", "true"], "target": [0.38, 0.62], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during the quarterly review. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3b854371d3e92f2d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.27, 0.72, 0.01], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, following a recent audit. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e2a3e3e62ba5de23_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: across all regions, during the system migration. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_afb3603dd1abfd50_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.16, 0.51, 0.25, 0.06, 0.01], "state": "Service catalog-sync 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 supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0114da06b3ea90fe_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.05, 0.8, 0.15], "state": "Service catalog-sync correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: across all regions, while legacy systems are still active. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_466b6e9a7228ff54_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.9, 0.09, 0.01, 0.0], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, while on-call rotation changed. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4d43d3bf973f0738_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.96, 0.03, 0.0, 0.01], "state": "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, immediately after go-live. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5a074d11ac3e5840_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.57, 0.41, 0.0], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: across all regions, during the system migration. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cfea0e44ac3dbae2_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: in production only, under an active deadline. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ccc5bf228c13a1d7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.6, 0.39, 0.0], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: across all regions, during the system migration. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_39406ae45de15130_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: during the batch window, as part of a compliance sweep. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9580b5c3a6e00a21_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.77, 0.18, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: over the last hour, with staffing at reduced levels. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_672aef205a121ddc_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.01, 0.04, 0.95], "state": "Service catalog-sync lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: in production only, during the system migration. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5c8c03f883a7b3d0_n", "kind": "noul", "options": ["false", "true"], "target": [0.39, 0.61], "state": "The metrics pipeline correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9c57d1b9e77a1d06_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.89, 0.02, 0.01, 0.08], "state": "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, under reduced staffing. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f3ead914998e1fee_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.97, 0.0, 0.0, 0.03], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: over the last hour, with staffing at reduced levels. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d5dfa6bb5816849b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.11, 0.85, 0.04], "state": "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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c4b0beaae4f8368e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.06, 0.01, 0.11, 0.82], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: during the batch window, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e1e1bcfd7eca4832_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.33, 0.62, 0.04, 0.0], "state": "The log shipper flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: during the batch window, during the quarterly review. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bbc960615e52174f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.01, 0.39, 0.58], "state": "The log shipper correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_21e7ba63ecda4e23_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.37, 0.62, 0.01], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during a scheduled maintenance window. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_63b024f8c9661472_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.06, 0.86, 0.07, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: in production only, during the morning shift. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_079d55122ae93293_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.25, 0.27, 0.01, 0.47], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: during the batch window, during the quarterly review. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_18f7bf8ac018bee5_n", "kind": "noul", "options": ["false", "true"], "target": [0.7, 0.3], "state": "The metrics pipeline correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: during the batch window, at the end of the fiscal period. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b38845dbdb9bb370_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.18, 0.8, 0.02], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during normal operations. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_83417674c61ac02e_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, following a recent audit. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bb260f4044ff9ebb_n", "kind": "noul", "options": ["false", "true"], "target": [0.9, 0.1], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: across all regions, during an external partner integration. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4f6f3bd7b7c5ab70_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.87, 0.13, 0.0, 0.0], "state": "The log shipper flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: in production only, following a recent audit. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_be2032e6fb885b88_n", "kind": "noul", "options": ["false", "true"], "target": [0.63, 0.37], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during normal operations. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c54e3cef59095df1_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: in production only, at the end of the fiscal period. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_84a924b6600662ec_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.56, 0.42], "state": "The log shipper shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: during the batch window, during a scheduled maintenance window. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_166acde8bedd4350_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.16, 0.68, 0.16, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: in production only, during a scheduled maintenance window. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9e9308d8a2dc38e8_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.96, 0.03, 0.01, 0.0], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during normal operations. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_01cc837a77c9a5e4_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.05, 0.77, 0.17, 0.01], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: during the batch window, as part of a compliance sweep. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ffe07fc5c83e212c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.9, 0.09, 0.01, 0.0], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: in production only, with staffing at reduced levels. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_49bec1a0a15e0f83_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.22, 0.37, 0.4, 0.01], "state": "Node pgsql-14 flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: in production only, during a scheduled maintenance window. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fb97f777761f5ea2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.14, 0.73, 0.11, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: across all regions, during an external partner integration. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_32d548996da2a524_n", "kind": "noul", "options": ["false", "true"], "target": [0.38, 0.62], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during the quarterly review. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6be6ecf80d315a7d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.92, 0.05, 0.03, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: in production only, under an active deadline. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d7c31087b955fa59_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: across all regions, during the system migration. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7c7fc28576c8a52e_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: across all regions, with a new vendor onboarded. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c64436abad062a67_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.61, 0.38, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: across all regions, during an external partner integration. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_02b5e2018ace817e_n", "kind": "noul", "options": ["false", "true"], "target": [0.38, 0.62], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the quarterly review. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d98a984eaed56a47_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d7d47c83f6586b9a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.08, 0.53, 0.35], "state": "The metrics pipeline shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: in production only, during an external partner integration. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_56ec38af968872e3_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.46, 0.3, 0.23, 0.01], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: over the last hour, during the holiday freeze. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_64deb0aff0f283f2_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during the quarterly review. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e332ef97e5a1eace_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.58, 0.42, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during the morning shift. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9792ab8840958b1e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.01, 0.8, 0.19], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: during the batch window, during the system migration. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b1bde925828e7967_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.04, 0.52, 0.43], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: during the batch window, mid-incident. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_437e194e75af8fd7_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.01, 0.48, 0.46], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during the system migration. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7153fd5fcc5c1049_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during the morning shift. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fe22a988c32c2f82_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: during the batch window, during the holiday freeze. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ff5975111ff4320_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "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.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8365c8575c91c116_n", "kind": "noul", "options": ["false", "true"], "target": [0.44, 0.56], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, as part of a compliance sweep. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5b76cb8697cff7ab_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.08, 0.03, 0.1, 0.79], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: in production only, during the system migration. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c00de03c779bd135_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.09, 0.18, 0.57, 0.16], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: in production only, as part of a compliance sweep. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b7f13b46141fe527_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "The log shipper correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, as part of a compliance sweep. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2979a26c36e1934b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.19, 0.66, 0.11, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, following a recent audit. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d54909cdd49e31c0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.09, 0.83, 0.08], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during the quarterly review. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fd10d3a5ff659962_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.2, 0.67, 0.12, 0.01], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: during the batch window, during peak load. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fbd200a761682e17_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.01, 0.41, 0.55], "state": "The log shipper reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: during the batch window, during normal operations. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4510d41fe66c2650_n", "kind": "noul", "options": ["false", "true"], "target": [0.63, 0.37], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during the morning shift. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4b3f9b34813daa14_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, at the end of the fiscal period. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_17a28e940c3858ab_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during normal operations. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3796f609358d6057_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.0, 0.38, 0.57], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: during the batch window, at the end of the fiscal period. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0c978cd45b6cb01e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.32, 0.66, 0.01], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: during the batch window, shortly after a software update. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e295f7bde693147f_n", "kind": "noul", "options": ["false", "true"], "target": [0.9, 0.1], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: over the last hour, while legacy systems are still active. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8495245eb1c1e365_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.19, 0.05, 0.51, 0.25], "state": "The metrics pipeline correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during the holiday freeze. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8facfb2d805b6094_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.07, 0.12, 0.61, 0.2, 0.0], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f814e07b9e13b64a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.34, 0.65, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, with a new vendor onboarded. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_61e49f518d313d51_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.0, 0.33, 0.63], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: in production only, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4cfa80aef832f05a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.96, 0.04, 0.0, 0.0], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: over the last hour, under an active deadline. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8c2981c3aeff9011_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.02, 0.63, 0.35], "state": "The metrics pipeline 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 supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1d8a644ecdddf039_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.43, 0.55, 0.01, 0.01], "state": "The log shipper reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: during the batch window, as part of a compliance sweep. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8d7b1a12446e5cdd_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.48, 0.44, 0.04, 0.04], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: over the last hour, following a recent audit. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6c0f41ed469d74ee_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: in production only, during the quarterly review. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_12403c7f07468569_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "The log shipper returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: across all regions, shortly after a software update. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e332ef97e5a1eace_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.52, 0.43, 0.03, 0.02], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during the morning shift. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1280069eac0fbae6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.18, 0.53, 0.27, 0.01, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, with a new vendor onboarded. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d7970b88840122a1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.4, 0.43, 0.15, 0.0], "state": "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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ee4f99e3a9815a9d_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: across all regions, during a scheduled maintenance window. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c9de22acbee7c4dc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.29, 0.7, 0.01], "state": "Node pgsql-14 flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: in production only, immediately after go-live. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f9ac22395ae0610b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.22, 0.07, 0.46, 0.25], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during a scheduled maintenance window. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_45a67cad1ce04c85_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.32, 0.68, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during the morning shift. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_670f4fdeadf62e9b_n", "kind": "noul", "options": ["false", "true"], "target": [0.23, 0.77], "state": "The metrics pipeline lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: over the last hour, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_936ee6f5862098e6_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: over the last hour, during an external partner integration. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b37c42f380f7793a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.63, 0.36, 0.0], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: during the batch window, during the system migration. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6dbd3b7f659a3008_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: across all regions, during the holiday freeze. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1a55c7879e72cfc6_n", "kind": "noul", "options": ["false", "true"], "target": [0.22, 0.78], "state": "The log shipper correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: in production only, mid-incident. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_57e3a1384f9b1f95_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.59, 0.39], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: over the last hour, with staffing at reduced levels. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_615553075730ea30_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.64, 0.34, 0.01, 0.01], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, shortly after a software update. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d129e39265375f82_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.26, 0.13, 0.05, 0.56], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: across all regions, with staffing at reduced levels. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_947c78c18a199170_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.09, 0.19, 0.53, 0.19, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: across all regions, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6b6ba21fa496b324_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Service catalog-sync flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: in production only, during the quarterly review. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_48881da220e866d7_n", "kind": "noul", "options": ["false", "true"], "target": [0.39, 0.61], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during the quarterly review. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_76a1bf515f99e04b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.24, 0.61, 0.12, 0.0], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: during the batch window, at the end of the fiscal period. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_db4bb4b7ff883eb8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.62, 0.34, 0.03, 0.0], "state": "The log shipper flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: in production only, during the morning shift. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3022b2cba57e00f9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.4, 0.46, 0.08, 0.0], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the system migration. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3c8b4b16e98eed67_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: during the batch window, with a new vendor onboarded. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_865bb4d160eec35f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.74, 0.23, 0.0], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: during the batch window, while legacy systems are still active. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_06e97b9a5af907c6_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: during the batch window, immediately after go-live. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f13755e097ab6e98_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.34, 0.57, 0.04, 0.0], "state": "The metrics pipeline flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: in production only, following a recent audit. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b658697efc02e29c_n", "kind": "noul", "options": ["false", "true"], "target": [0.53, 0.47], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: across all regions, shortly after a software update. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_739b3abc81682118_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.98, 0.0, 0.0, 0.02], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, mid-incident. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_82885b53cb60c002_n", "kind": "noul", "options": ["false", "true"], "target": [0.9, 0.1], "state": "The log shipper shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, while legacy systems are still active. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_35dc5d4135893953_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.1, 0.05, 0.8], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: in production only, while legacy systems are still active. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d49495b23fb3f83a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.83, 0.11, 0.05, 0.01], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: in production only, immediately after go-live. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2a8eb2da414f463e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.66, 0.31, 0.01, 0.02], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fb0dd12ba7d6d1a4_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the morning shift. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7b26e564228e0ff7_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.34, 0.63, 0.03, 0.0], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: in production only, while legacy systems are still active. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_45e77208345803b0_n", "kind": "noul", "options": ["false", "true"], "target": [0.43, 0.57], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during the morning shift. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ed3b510e1cf44a1f_n", "kind": "noul", "options": ["false", "true"], "target": [0.41, 0.59], "state": "The metrics pipeline shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: across all regions, while on-call rotation changed. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a2bba9af7f901d7f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.45, 0.33, 0.2, 0.01], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: in production only, during the morning shift. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8c84adcada7333c4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.03, 0.54, 0.4, 0.01], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: in production only, during a scheduled maintenance window. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7d30c93dec6b73cb_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.15, 0.48, 0.35, 0.02], "state": "The log shipper returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: over the last hour, mid-incident. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b00f916d4a2665b4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.16, 0.7, 0.13, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; 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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_67f37a804e7c7403_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during the holiday freeze. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_643ee87e852015ef_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.61, 0.39, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: over the last hour, with a new vendor onboarded. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e88d3046f8791d91_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.57, 0.03, 0.02, 0.38], "state": "The log shipper lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: over the last hour, under reduced staffing. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0c5b0e5fa71ece38_n", "kind": "noul", "options": ["false", "true"], "target": [0.2, 0.8], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: in production only, during normal operations. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_71627c66668d1994_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.98, 0.01, 0.0, 0.01], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, under an active deadline. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fb1ae7baec9a0c5a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.35, 0.01, 0.6], "state": "The metrics pipeline flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: in production only, immediately after go-live. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b90be77501694dc_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during an external partner integration. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dadf724772a36d6d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.46, 0.51, 0.03, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: in production only, during an external partner integration. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ef60429fd299ea53_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.17, 0.05, 0.11, 0.67], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: over the last hour, with staffing at reduced levels. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_20edde1efbee14ce_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.28, 0.64, 0.04, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: during the batch window, under an active deadline. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cb4796f58d149b75_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: in production only, during the system migration. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f5a51e4b5b1a51ae_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.36, 0.64, 0.0], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: in production only, while on-call rotation changed. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f3900f85aac5a6bc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.33, 0.4, 0.26, 0.01], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: in production only, under reduced staffing. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9f2b2b697e34f733_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.02, 0.11, 0.24, 0.52, 0.11, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: across all regions, following a recent audit. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_06feebd8ee7a4263_n", "kind": "noul", "options": ["false", "true"], "target": [0.53, 0.47], "state": "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, during a scheduled maintenance window. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1b98c22b19ae758b_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "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, with a new vendor onboarded. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_14fd7fd348ed406c_n", "kind": "noul", "options": ["false", "true"], "target": [0.65, 0.35], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: during the batch window, while on-call rotation changed. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ea344ff006c239a2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.14, 0.84, 0.02], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: across all regions, shortly after a software update. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2e5b071fecbe1572_n", "kind": "noul", "options": ["false", "true"], "target": [0.61, 0.39], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: over the last hour, during a scheduled maintenance window. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f343b871297b5240_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.96, 0.02, 0.0, 0.02], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: during the batch window, during peak load. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_320b1face70bdbab_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: across all regions, as part of a compliance sweep. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a257fcfa0baa6053_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.12, 0.72, 0.14, 0.02], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: over the last hour, shortly after a software update. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_89926e2d3926f815_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.3, 0.28, 0.34, 0.08], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: across all regions, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_56282e68afd98729_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: across all regions, during an external partner integration. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0e18bd2801ffdb37_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0202, 0.0202, 0.3939, 0.5657], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: during the batch window, during the holiday freeze. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bd53fda28e41ed01_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.89, 0.06, 0.05, 0.0], "state": "The log shipper flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, under an active deadline. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_036e389c7e256b6b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.1, 0.66, 0.19, 0.0], "state": "The log shipper matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: during the batch window, as part of a compliance sweep. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f34747d1bc1a436f_n", "kind": "noul", "options": ["false", "true"], "target": [0.47, 0.53], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: during the batch window, during an external partner integration. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8fea6aec19972988_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.78, 0.18, 0.04, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, while on-call rotation changed. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9aa9fc0a73ad009f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.06, 0.77, 0.05, 0.12], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: across all regions, during the morning shift. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c5dc4663b70cf323_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.41, 0.51, 0.05, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: during the batch window, shortly after a software update. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2b1162807cb82ecf_n", "kind": "noul", "options": ["false", "true"], "target": [0.43, 0.57], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during the holiday freeze. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_40f648521fead275_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.42, 0.53, 0.02, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: in production only, during the morning shift. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3672ae046d55d2ff_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.04, 0.93, 0.03, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: during the batch window, during normal operations. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_48ed8e6a3c640e11_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.72, 0.27, 0.0], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during an external partner integration. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_54c4ffe2c06b221f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.23, 0.51, 0.01, 0.25], "state": "The log shipper matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: in production only, during normal operations. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c3562ebd5b0d7dca_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.58, 0.02, 0.07, 0.33], "state": "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, as part of a compliance sweep. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f89a4dda105c63a9_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "Service catalog-sync correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: during the batch window, under an active deadline. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b9993a106179523c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.01, 0.03, 0.41, 0.52, 0.02], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: across all regions, during normal operations. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_38cf6a8fdc7d74e2_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.57, 0.39, 0.04, 0.0], "state": "Service catalog-sync flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: during the batch window, while on-call rotation changed. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_abade13fa03ae66a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.27, 0.72, 0.01], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: in production only, during the morning shift. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_473d1ec7670fe3a5_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.94, 0.06, 0.0, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: in production only, under reduced staffing. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7d5ddbd44240fa6f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.01, 0.44, 0.52], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9ba4b77ecfb3b0e3_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: in production only, immediately after go-live. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a2cb29f7d44604dc_n", "kind": "noul", "options": ["false", "true"], "target": [0.55, 0.45], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during a scheduled maintenance window. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_abb2bb19d1559b45_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.59, 0.4, 0.0], "state": "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 an external partner integration. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0a3bf112b019e62a_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "The log shipper lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: across all regions, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e01504564441af8b_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: during the batch window, during peak load. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fe965ce8a13930fe_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Service catalog-sync flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: in production only, while legacy systems are still active. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bfdd70984d0564b2_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.08, 0.79, 0.12, 0.01], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during the quarterly review. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9dd6b6cb29b08253_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.28, 0.68, 0.03, 0.01], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: across all regions, under reduced staffing. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_15d41388f85a1729_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.85, 0.08, 0.06, 0.01], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: over the last hour, under an active deadline. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4b901bd4111c39a6_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: during the batch window, at the end of the fiscal period. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e8e31882d7461093_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.04, 0.54, 0.42, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: over the last hour, immediately after go-live. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ebe8321726c860a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.11, 0.53, 0.35, 0.01], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: in production only, at the end of the fiscal period. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e9d3e82390401326_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.86, 0.1, 0.02, 0.02], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: in production only, under an active deadline. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d769e299e40de70a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.02, 0.1, 0.13, 0.56, 0.18, 0.01], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: in production only, shortly after a software update. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_27e558ccf20c20ac_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.92, 0.06, 0.01, 0.01], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: in production only, during peak load. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_80094e3d5dddb5c0_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.53, 0.22, 0.01, 0.24], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_95692f55dad78102_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during an external partner integration. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_da983fdb8edd947b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.43, 0.56, 0.01], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, while legacy systems are still active. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_97001f04aa21e0f7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.03, 0.44, 0.4, 0.13, 0.0, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, immediately after go-live. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_414491a38dcc8e82_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.11, 0.85, 0.04], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: across all regions, mid-incident. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0962e2f707185d80_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.09, 0.0, 0.19, 0.72], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: during the batch window, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2aab6e54b27b1a57_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.41, 0.57, 0.01], "state": "The log shipper correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, under reduced staffing. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f388432d9def5579_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.01, 0.04, 0.49, 0.43, 0.02], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: across all regions, as part of a compliance sweep. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2d922080832a57a6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.31, 0.66, 0.02], "state": "The log shipper reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: over the last hour, mid-incident. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9e85c3b0ccf82813_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.55, 0.36, 0.04, 0.0], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, under reduced staffing. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3dc5bdb51f48200a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.82, 0.17, 0.01, 0.0], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: in production only, while on-call rotation changed. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_db578b9fcef917f2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.42, 0.58, 0.0], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: over the last hour, while on-call rotation changed. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e417c87ce8250017_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during normal operations. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eb97c04614140738_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.23, 0.67, 0.08, 0.02], "state": "The log shipper correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: during the batch window, as part of a compliance sweep. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d1dfcd4b3972e086_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.07, 0.44, 0.48, 0.01, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: in production only, with staffing at reduced levels. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7d19172e06b9e542_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: in production only, mid-incident. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1d28f4f0f7c7f819_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.12, 0.08, 0.12, 0.68], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: across all regions, while on-call rotation changed. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4d382faaa3ba5900_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during normal operations. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cc7a5a80bb6cb130_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.24, 0.08, 0.63], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: over the last hour, while on-call rotation changed. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a29cef5f871c5827_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.62, 0.32, 0.04, 0.02], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, as part of a compliance sweep. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c1b1c811075a8f55_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.39, 0.59, 0.01], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: during the batch window, at the end of the fiscal period. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4bfa6531259dad1b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.37, 0.61, 0.01], "state": "The log shipper correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: in production only, during peak load. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bd80b5eee25864f1_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "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, while on-call rotation changed. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f695fd40f46117d0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.35, 0.62, 0.02], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: across all regions, mid-incident. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_250d831c47edb2ac_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: during the batch window, with a new vendor onboarded. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fb591d0b8976cb74_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.58, 0.41, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: over the last hour, with a new vendor onboarded. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1855d0d3b8c06bef_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: during the batch window, during peak load. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2019fc4fdfc5baaa_n", "kind": "noul", "options": ["false", "true"], "target": [0.37, 0.63], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: in production only, during an external partner integration. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bd0eba2064548ae1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.09, 0.04, 0.75, 0.12], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: in production only, under reduced staffing. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_15a92085135dac36_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: over the last hour, during an external partner integration. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_63b024f8c9661472_n", "kind": "noul", "options": ["false", "true"], "target": [0.58, 0.42], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: in production only, during the morning shift. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5125af1af577d1f0_n", "kind": "noul", "options": ["false", "true"], "target": [0.69, 0.31], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: across all regions, during normal operations. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b206ce9324c63cc_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during the quarterly review. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fc98218fa5c722aa_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: in production only, during normal operations. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ef60e75566756c76_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.96, 0.04, 0.0, 0.0], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: in production only, with staffing at reduced levels. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fb04856443154bd8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.22, 0.76, 0.02], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: during the batch window, with a new vendor onboarded. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3c3dce01b583d115_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.37, 0.61, 0.01], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, as part of a compliance sweep. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3e08344f71faeefd_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.68, 0.18, 0.14, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5186af0fc495ef1f_n", "kind": "noul", "options": ["false", "true"], "target": [0.17, 0.83], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: in production only, during normal operations. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_79206a5fcf142ed7_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: across all regions, with staffing at reduced levels. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e32d41b698f78d64_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.12, 0.82, 0.06], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: in production only, under an active deadline. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5123410baa410380_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.58, 0.4, 0.0], "state": "The log shipper reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: over the last hour, during the morning shift. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b8457396d6c277df_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.18, 0.81, 0.01], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: in production only, shortly after a software update. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_60d0ae0935021130_n", "kind": "noul", "options": ["false", "true"], "target": [0.68, 0.32], "state": "The log shipper matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: in production only, during normal operations. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9a2dd2384612bc89_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.11, 0.85, 0.04], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: across all regions, during the holiday freeze. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f2b56130a5395fdf_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.19, 0.79, 0.02], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during the system migration. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0a6133bc92d2db48_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: in production only, during an external partner integration. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eac204ed8d795d76_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.46, 0.5, 0.01], "state": "The log shipper reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: across all regions, during normal operations. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7744676a7b52bd13_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.86, 0.11, 0.02, 0.01], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: over the last hour, under an active deadline. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_badd27f64c12a035_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.8, 0.19, 0.01, 0.0], "state": "The log shipper correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: over the last hour, under reduced staffing. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b2bec84b80c0202e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.91, 0.0, 0.0, 0.09], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, as part of a compliance sweep. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_67646f50f7d6a63c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.2, 0.79, 0.01], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: during the batch window, under an active deadline. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_df0841f7f2f41879_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7c0f1199481a3cb2_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Service catalog-sync flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: during the batch window, with staffing at reduced levels. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d2750fa8381dd3c2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.02, 0.38, 0.57], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: during the batch window, as part of a compliance sweep. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_49a28c17b6d89e43_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.47, 0.06, 0.02, 0.45], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_702f3250ea0e0cea_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: in production only, under an active deadline. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b6e603096ce8f68a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.42, 0.41, 0.16, 0.01], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: over the last hour, immediately after go-live. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9731f57ad8294fc5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.07, 0.8, 0.13], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, mid-incident. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_979f44756945490a_n", "kind": "noul", "options": ["false", "true"], "target": [0.37, 0.63], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during a scheduled maintenance window. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2598e1a8666ae0f4_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: over the last hour, immediately after go-live. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_889b6628ae5f64e2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.15, 0.82, 0.03], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: in production only, under reduced staffing. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bd460e0f02ddfb5b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.26, 0.61, 0.09, 0.0], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: across all regions, while on-call rotation changed. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eda7644c1f10379a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.02, 0.16, 0.75, 0.07], "state": "Service catalog-sync flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: across all regions, during the holiday freeze. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_05662335e3e69f50_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.06, 0.08, 0.81, 0.05], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: in production only, during an external partner integration. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_539feeb361eb70c1_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during normal operations. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_91a289f380986db0_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.0, 0.22, 0.75], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: in production only, during normal operations. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d9032299425a26a2_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: over the last hour, immediately after go-live. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e75fa280bcf0327b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.95, 0.0, 0.0, 0.05], "state": "The log shipper lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during the holiday freeze. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2662cef7d4cee8be_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.4, 0.58], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: in production only, during the system migration. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_38048b85d9b2e064_n", "kind": "noul", "options": ["false", "true"], "target": [0.2, 0.8], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: in production only, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_153b1156f6cd3dd7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.24, 0.71, 0.04], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: across all regions, mid-incident. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_17776cc8ed98e594_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: across all regions, while on-call rotation changed. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_944bcee49c70c2c0_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.08, 0.09, 0.22, 0.61], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: over the last hour, during a scheduled maintenance window. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9ee4337e34322b9b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.16, 0.06, 0.19, 0.59], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, with a new vendor onboarded. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_76cc7fbd28affc4e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.03, 0.36, 0.58, 0.03], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: in production only, during the morning shift. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9d24cfbcc94b5141_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.2, 0.51, 0.28, 0.01], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: in production only, under reduced staffing. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bb2d55b3a9f5ed0b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.22, 0.68, 0.04, 0.06], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: across all regions, while on-call rotation changed. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8384da0f35839714_n", "kind": "noul", "options": ["false", "true"], "target": [0.59, 0.41], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: during the batch window, during the holiday freeze. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5f0dae60abf4458c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.31, 0.67, 0.01], "state": "Service catalog-sync lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: during the batch window, during an external partner integration. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_40cae5df014e14e3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.37, 0.62, 0.01], "state": "The log shipper matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: across all regions, at the end of the fiscal period. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_42eb8be7859b0fa4_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.54, 0.11, 0.35], "state": "Service catalog-sync lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: during the batch window, shortly after a software update. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_88118af93c4bb4af_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.5, 0.49, 0.0], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the system migration. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0eb8dc03a6d9403e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.77, 0.0, 0.01, 0.22], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, while on-call rotation changed. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_21e6a43cded08e7e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.62, 0.36], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: in production only, during an external partner integration. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c8885f4f1a4ad011_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.24, 0.71, 0.02, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: during the batch window, during the morning shift. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8bf5e929e40df477_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.6, 0.39, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the morning shift. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eaf5ad7e8245df2e_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, with a new vendor onboarded. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_878f63570c9ca2cd_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.11, 0.45, 0.38, 0.06], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: in production only, during an external partner integration. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2f5540b961126783_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: during the batch window, at the end of the fiscal period. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_835fa6c3c98f92a5_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.18, 0.2, 0.2, 0.42], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: during the batch window, immediately after go-live. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3421a7950fef8905_n", "kind": "noul", "options": ["false", "true"], "target": [0.44, 0.56], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: in production only, while on-call rotation changed. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5c0b8d813b1524e8_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.44, 0.03, 0.21, 0.32], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: during the batch window, with staffing at reduced levels. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_77e60a417a4a2d0a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.2727, 0.6869, 0.0404, 0.0], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: in production only, during normal operations. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6ae34dee4512a1fb_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: over the last hour, during the system migration. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bd4bc9d6d0960f40_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.3, 0.69, 0.01], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: across all regions, with staffing at reduced levels. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_437e194e75af8fd7_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during the system migration. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d97af7d578684446_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.46, 0.53, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: over the last hour, during the quarterly review. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_47f29fe1b3231021_n", "kind": "noul", "options": ["false", "true"], "target": [0.45, 0.55], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: across all regions, during the morning shift. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ffcb17bc316f4df1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.34, 0.63, 0.02], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during a scheduled maintenance window. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dec713caa4567308_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: in production only, under an active deadline. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6c0f41ed469d74ee_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.78, 0.21, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: in production only, during the quarterly review. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9f674b53a5265be5_n", "kind": "noul", "options": ["false", "true"], "target": [0.52, 0.48], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, following a recent audit. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ff0a5fcde85919e4_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.74, 0.22, 0.03, 0.01], "state": "The log shipper reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: over the last hour, during peak load. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e4190c0eafcc34e7_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.36, 0.58, 0.03, 0.03], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, mid-incident. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5643c936177f0ea7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.02, 0.28, 0.13, 0.42, 0.12, 0.03], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: across all regions, during a scheduled maintenance window. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fa169560f9c54f95_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.29, 0.7, 0.01], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: during the batch window, during an external partner integration. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_56f6fe7f6e74332a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.07, 0.51, 0.41, 0.01, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: in production only, during the quarterly review. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_535dc7fd36cac5fa_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.7, 0.27, 0.02, 0.01], "state": "The metrics pipeline shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during peak load. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d648098aad507d59_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, while on-call rotation changed. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2a428105b2080529_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.84, 0.07, 0.08], "state": "The log shipper reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: across all regions, shortly after a software update. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_85982566fbdd6976_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.76, 0.19, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: across all regions, immediately after go-live. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a58cd5c438d924c0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.35, 0.65, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the morning shift. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b682a359127d9ec4_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.33, 0.65, 0.01], "state": "Service catalog-sync shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: during the batch window, while on-call rotation changed. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1da04e52cc450f8f_n", "kind": "noul", "options": ["false", "true"], "target": [0.65, 0.35], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: over the last hour, following a recent audit. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_79c85077e9a3722a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.37, 0.53, 0.08, 0.02], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during peak load. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cc47c4e7cecf99a8_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.68, 0.29, 0.02, 0.01], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: in production only, with staffing at reduced levels. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_afd87f8fdf55b851_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.75, 0.21, 0.01, 0.03], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: during the batch window, shortly after a software update. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8c0cdfa317141def_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: during the batch window, shortly after a software update. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bc956fa83e9fd6d5_n", "kind": "noul", "options": ["false", "true"], "target": [0.49, 0.51], "state": "The log shipper reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: in production only, as part of a compliance sweep. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_75d74d57db0a99c5_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.68, 0.32, 0.0, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: during the batch window, following a recent audit. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3c48d3a073d3a744_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.46, 0.54, 0.0], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: during the batch window, during the morning shift. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8cbb1880d9d0f08d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.76, 0.16, 0.0, 0.08], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, following a recent audit. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_01ca1a3891187f21_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.31, 0.6, 0.06, 0.0], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: during the batch window, while on-call rotation changed. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_988e171846ddba47_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.28, 0.02, 0.3, 0.4], "state": "The log shipper shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: across all regions, during peak load. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_79f01c0f89c28453_n", "kind": "noul", "options": ["false", "true"], "target": [0.51, 0.49], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, immediately after go-live. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ecc16c2561349445_n", "kind": "noul", "options": ["false", "true"], "target": [0.63, 0.37], "state": "The log shipper correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: during the batch window, with a new vendor onboarded. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_66d80698bd02fe75_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.24, 0.74, 0.02], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: in production only, with a new vendor onboarded. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d42d19389b606fc1_n", "kind": "noul", "options": ["false", "true"], "target": [0.61, 0.39], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: in production only, while on-call rotation changed. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_463189e2ceebff58_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: in production only, at the end of the fiscal period. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c8a4136b63829911_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.5, 0.47, 0.01], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: over the last hour, following a recent audit. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_59418a57a146b061_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.41, 0.59, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: during the batch window, mid-incident. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6cc342b089e81b8f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.02, 0.3, 0.67, 0.01], "state": "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, during the holiday freeze. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cbba21f642bcedaa_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.14, 0.34, 0.5, 0.02, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: in production only, during a scheduled maintenance window. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_43a1cc2f96063ea9_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.0, 0.1, 0.9, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, as part of a compliance sweep. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4fcc40cbf1d9ca28_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: during the batch window, during an external partner integration. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1d23983c7359b5f1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.65, 0.08, 0.02, 0.25], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, with staffing at reduced levels. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1b92df4264a99dcf_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, as part of a compliance sweep. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ed936eb5fe70a25b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.17, 0.81, 0.02], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during the quarterly review. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3db124ff31bab8ad_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.94, 0.0, 0.01, 0.05], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during a scheduled maintenance window. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_607bc689a68c3686_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "The log shipper returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: across all regions, with a new vendor onboarded. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aeaae2abc7c01adb_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.38, 0.2, 0.05, 0.37], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: over the last hour, during peak load. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e9f19f49c216e469_n", "kind": "noul", "options": ["false", "true"], "target": [0.22, 0.78], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, immediately after go-live. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2bfc7efc31d78a61_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.32, 0.67, 0.01, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: in production only, as part of a compliance sweep. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b1c916cf4691d848_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.29, 0.51, 0.2, 0.0, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: across all regions, under reduced staffing. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_be2dfe3232ca0925_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.92, 0.06, 0.02, 0.0], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: in production only, mid-incident. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fae03c436424c16f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.9, 0.0, 0.1], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: in production only, shortly after a software update. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f8119d431f51d5a4_n", "kind": "noul", "options": ["false", "true"], "target": [0.21, 0.79], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during normal operations. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6c973df422aec2b4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.23, 0.63, 0.08, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: across all regions, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aeaae2abc7c01adb_n", "kind": "noul", "options": ["false", "true"], "target": [0.44, 0.56], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: over the last hour, during peak load. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f9046674ef545000_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.63, 0.01, 0.12, 0.24], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, under reduced staffing. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4dde4a2ef14c7dd4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.05, 0.86, 0.09], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, under reduced staffing. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fe22a988c32c2f82_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.64, 0.32, 0.03, 0.01], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: during the batch window, during the holiday freeze. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c83a62c743bf4e55_n", "kind": "noul", "options": ["false", "true"], "target": [0.51, 0.49], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: during the batch window, following a recent audit. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f814e07b9e13b64a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.25, 0.48, 0.25, 0.01, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, with a new vendor onboarded. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c91c50225ad9611d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.21, 0.66, 0.12, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: in production only, shortly after a software update. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ffe07fc5c83e212c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.16, 0.83, 0.01], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: in production only, with staffing at reduced levels. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_37187f705c5e6ef5_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.02, 0.3, 0.67], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: during the batch window, during a scheduled maintenance window. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d28825504e2c6ded_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.01, 0.17, 0.78], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, mid-incident. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2f6ff01413ae0a8c_n", "kind": "noul", "options": ["false", "true"], "target": [0.49, 0.51], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: during the batch window, as part of a compliance sweep. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_31a72894c028bd0d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.33, 0.66, 0.01], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: in production only, during normal operations. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7961c1ea1ee2e8e8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.15, 0.79, 0.04, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the morning shift. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c43105c2477b140d_n", "kind": "noul", "options": ["false", "true"], "target": [0.7, 0.3], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during a scheduled maintenance window. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5b9cb0e480136646_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The metrics pipeline shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: over the last hour, at the end of the fiscal period. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9fac15c07e33765e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.16, 0.49, 0.34, 0.01], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during peak load. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9018d507e426d4df_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.24, 0.71, 0.04], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: across all regions, mid-incident. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b1fcc16f8deb2040_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.17, 0.39, 0.41, 0.03, 0.0], "state": "The log shipper reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: during the batch window, as part of a compliance sweep. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_48e823d794ce89fd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.18, 0.79, 0.03], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, under reduced staffing. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8d078dbfd2394745_n", "kind": "noul", "options": ["false", "true"], "target": [0.21, 0.79], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: across all regions, with a new vendor onboarded. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aa5dbb280d093479_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.1, 0.37, 0.52, 0.01, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: over the last hour, as part of a compliance sweep. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_57b179edc1fdbf9a_n", "kind": "noul", "options": ["false", "true"], "target": [0.64, 0.36], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: in production only, following a recent audit. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_de2255cbce7c0320_n", "kind": "noul", "options": ["false", "true"], "target": [0.66, 0.34], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: across all regions, with staffing at reduced levels. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_853d89db29a14380_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.11, 0.82, 0.07], "state": "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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4dcef18f0c1f2438_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.18, 0.59, 0.23, 0.0, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: during the batch window, while legacy systems are still active. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_60a31bf32c9102ad_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "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 system migration. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_409b8061e2bd0a7b_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: during the batch window, following a recent audit. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c8a4136b63829911_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.64, 0.34, 0.01, 0.01], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: over the last hour, following a recent audit. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e191545f5efd4adc_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.66, 0.32, 0.01, 0.01], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: in production only, at the end of the fiscal period. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3ce4acf51d346757_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.41, 0.58, 0.0], "state": "The log shipper reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: during the batch window, during the system migration. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_db6d5eb40c692ee6_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.08, 0.5, 0.41], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: in production only, while legacy systems are still active. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_60afcd5960d0a748_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.55, 0.32, 0.13, 0.0], "state": "The metrics pipeline correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: across all regions, during normal operations. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_01c3e7bc20a468cc_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.21, 0.67, 0.1, 0.02], "state": "The log shipper returned to baseline after 11 minutes; additionally matches last Tuesday's incident signature. Context: during the batch window, under an active deadline. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_047055b1f2df0124_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.96, 0.0, 0.0, 0.04], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: during the batch window, mid-incident. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d7c31087b955fa59_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.64, 0.33, 0.02, 0.01], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: across all regions, during the system migration. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a35ae03469d0f602_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.24, 0.74, 0.02], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: during the batch window, while on-call rotation changed. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4fbd4f19a33531ca_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "The log shipper shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, at the end of the fiscal period. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8de6bb003c3d2b1b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.06, 0.84, 0.1], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, mid-incident. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eea110eb87dd5a7f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.1, 0.12, 0.43, 0.35], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: in production only, during an external partner integration. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_36e2ce5740948990_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.32, 0.66, 0.02], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7f2ed8eb80037306_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: in production only, at the end of the fiscal period. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_db6ae811deaae4ef_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.78, 0.04, 0.08, 0.1], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, with staffing at reduced levels. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a6ece2c054abb7f5_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "The metrics pipeline shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: across all regions, under an active deadline. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fae03c436424c16f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.46, 0.46, 0.07, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: in production only, shortly after a software update. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_116e5b31ccbf4cb1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.37, 0.08, 0.03, 0.52], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: across all regions, during normal operations. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4bcf900df94ce124_n", "kind": "noul", "options": ["false", "true"], "target": [0.23, 0.77], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: across all regions, shortly after a software update. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ea2bf855f59e3f4_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.35, 0.61, 0.0, 0.04], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: across all regions, under reduced staffing. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d6d83ea1c2e44ed4_n", "kind": "noul", "options": ["false", "true"], "target": [0.67, 0.33], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: over the last hour, under reduced staffing. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ee6e702f9629d850_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.58, 0.35, 0.06, 0.01], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: in production only, during the system migration. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_565edaa049f70cd9_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.28, 0.3, 0.41, 0.01], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8c84adcada7333c4_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.56, 0.3, 0.13, 0.01], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: in production only, during a scheduled maintenance window. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f2cf80535a3d3c07_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.73, 0.24, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: over the last hour, following a recent audit. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2f1d3cafc152e493_n", "kind": "noul", "options": ["false", "true"], "target": [0.52, 0.48], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: in production only, while legacy systems are still active. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5a491e04822d7dce_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.18, 0.8, 0.02], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: over the last hour, under reduced staffing. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a7b29fdb6ed24a87_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.27, 0.12, 0.58], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: over the last hour, immediately after go-live. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_db999562405ac966_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.25, 0.05, 0.21, 0.49], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: during the batch window, while legacy systems are still active. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_898a558af9a0d38a_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during the holiday freeze. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e59e0e38df36c629_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "The log shipper reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: over the last hour, during peak load. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_76b9aa21e53b6b67_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.48, 0.51, 0.0], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: over the last hour, with a new vendor onboarded. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_37ae90525cfdba8c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.51, 0.01, 0.03, 0.45], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0f5af912a31989af_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, while legacy systems are still active. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_448a13b1040cc306_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.0, 0.76, 0.19], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: in production only, during peak load. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a8a54bac2816a1a8_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Service catalog-sync flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: across all regions, during the morning shift. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_36723f448ba45f01_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.98, 0.0, 0.0, 0.02], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: across all regions, during the holiday freeze. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_17e68c1d16b7a83e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.16, 0.75, 0.07, 0.02, 0.0, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: across all regions, during the system migration. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_12403c7f07468569_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.13, 0.73, 0.11, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: across all regions, shortly after a software update. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d573cb528042634d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.0, 0.64, 0.35], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: over the last hour, during a scheduled maintenance window. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_606798a0f69dfd68_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.56, 0.43, 0.0], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, as part of a compliance sweep. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5b2deedde26fa3f5_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.02, 0.72, 0.25], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: in production only, with a new vendor onboarded. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c9b7dfe4a12581b6_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.82, 0.15, 0.03, 0.0], "state": "The log shipper correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: in production only, with staffing at reduced levels. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b815a82884a901ca_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.65, 0.33, 0.0], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, as part of a compliance sweep. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2bf45a3e160d846e_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "The metrics pipeline lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: over the last hour, during the holiday freeze. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dc0f96a446849eb1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.45, 0.38, 0.14, 0.03], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: over the last hour, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5693c7d309454c00_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.19, 0.04, 0.02, 0.75], "state": "The log shipper returned to baseline after 11 minutes; additionally matches last Tuesday's incident signature. Context: across all regions, during the morning shift. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a755e8a7eee0a84b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.12, 0.8, 0.04, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during normal operations. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_88e99b3c5fa28cb6_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.38, 0.38, 0.23, 0.01], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: over the last hour, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_da3a579b97150681_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.2, 0.58, 0.22, 0.0, 0.0], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: in production only, during normal operations. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_456350603fa2e7af_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.17, 0.01, 0.08, 0.74], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5cb2e9fc974bc9f2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.07, 0.02, 0.42, 0.49], "state": "The log shipper matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: in production only, with staffing at reduced levels. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4bcf900df94ce124_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.87, 0.11, 0.0, 0.02], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: across all regions, shortly after a software update. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0002d4406a0aa5ec_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.08, 0.82, 0.1], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: in production only, under an active deadline. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d547e7bf600bc73e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.0, 0.0, 0.98], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: in production only, with staffing at reduced levels. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7467c6f62e8a76e8_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.39, 0.07, 0.42, 0.12], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: across all regions, under an active deadline. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_caccf33282d85630_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.57, 0.38, 0.03, 0.02], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: across all regions, during an external partner integration. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1ce4fbb648628d94_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.3, 0.67, 0.02], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: in production only, with staffing at reduced levels. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_40f648521fead275_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.24, 0.36, 0.06, 0.34], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: in production only, during the morning shift. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a945668295e4f718_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.19, 0.78, 0.02, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: during the batch window, while on-call rotation changed. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9ea9f6459fd775af_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.53, 0.46, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during a scheduled maintenance window. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a151b1edfba19449_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.28, 0.71, 0.01], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: during the batch window, during the holiday freeze. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_59c2a47c4ac0dacc_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Service catalog-sync 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 review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ac67f1040237794f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.28, 0.64, 0.07, 0.01], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: in production only, during the quarterly review. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b920d987cb55e4c3_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.5, 0.42, 0.08, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: during the batch window, while legacy systems are still active. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_64ee4969bf48651c_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Service catalog-sync shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: across all regions, with a new vendor onboarded. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f22b696c8ad01f8d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.26, 0.71, 0.03], "state": "Service catalog-sync correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: over the last hour, mid-incident. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fe786f31cdc86e52_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.1, 0.55, 0.29, 0.06, 0.0, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during an external partner integration. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0c0f42eaaec20497_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.15, 0.78, 0.06], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: during the batch window, during an external partner integration. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f3f5c519718d4c37_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: across all regions, following a recent audit. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_71e5cfa81743c981_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.44, 0.08, 0.06, 0.42], "state": "Node pgsql-14 flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: during the batch window, while on-call rotation changed. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_228e78771b4734ae_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "The log shipper lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: during the batch window, immediately after go-live. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_54719746d29696c5_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the quarterly review. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d0937a022615166d_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, under an active deadline. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_90a8c0776af1ee46_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.08, 0.49, 0.42], "state": "Service catalog-sync flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: across all regions, immediately after go-live. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_556fea0b65fd6993_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.66, 0.3, 0.04, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: across all regions, during normal operations. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ec2d1f99856a8865_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.79, 0.19, 0.01, 0.01], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: over the last hour, while on-call rotation changed. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7cb48a73714989e5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.1414, 0.8182, 0.0404], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: over the last hour, immediately after go-live. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f4d553a4e7c1708d_n", "kind": "noul", "options": ["false", "true"], "target": [0.69, 0.31], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: over the last hour, as part of a compliance sweep. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8db6b2cca5f9bd42_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.04, 0.69, 0.25], "state": "The log shipper flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: in production only, as part of a compliance sweep. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f196ae510768623a_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The metrics pipeline shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: in production only, following a recent audit. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_960f2ef33f6ac65f_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: during the batch window, mid-incident. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_067232aae04c8d55_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.73, 0.26, 0.01, 0.0], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: in production only, while on-call rotation changed. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5895d69a43055346_n", "kind": "noul", "options": ["false", "true"], "target": [0.63, 0.37], "state": "The log shipper shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: during the batch window, shortly after a software update. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ed402eb293d8430c_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The log shipper shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: during the batch window, under an active deadline. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fee80017f05005a9_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.89, 0.1, 0.01, 0.0], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: across all regions, with staffing at reduced levels. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d17f1c21eb063ef2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.18, 0.78, 0.04], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, mid-incident. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_41bfbba83f83017a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.21, 0.72, 0.06], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally flags a step-function change in error slope. Context: in production only, during a scheduled maintenance window. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1cece41bb8882a49_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.01, 0.77, 0.2], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: over the last hour, during the quarterly review. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_97a558b660ebe2c9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.63, 0.35, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: across all regions, during an external partner integration. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_858e4da56f7a910f_n", "kind": "noul", "options": ["false", "true"], "target": [0.44, 0.56], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: during the batch window, while on-call rotation changed. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8de6bb003c3d2b1b_n", "kind": "noul", "options": ["false", "true"], "target": [0.2, 0.8], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, mid-incident. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5dfccb36cbc1710f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.18, 0.1, 0.26, 0.46], "state": "The log shipper correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: across all regions, during the morning shift. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f69c2ae15bbceb50_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.74, 0.0, 0.05, 0.21], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: across all regions, with staffing at reduced levels. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a7b29fdb6ed24a87_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.57, 0.43, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: over the last hour, immediately after go-live. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3f2a5c0bdb9bd726_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.56, 0.23, 0.18, 0.03], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during a scheduled maintenance window. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_05662335e3e69f50_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.14, 0.82, 0.04], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: in production only, during an external partner integration. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a09944e314d7ad09_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.2, 0.19, 0.02, 0.59], "state": "The log shipper reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: across all regions, following a recent audit. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b815a82884a901ca_n", "kind": "noul", "options": ["false", "true"], "target": [0.57, 0.43], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, as part of a compliance sweep. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8eccb6032d1e8dad_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.08, 0.74, 0.17, 0.01], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: across all regions, while legacy systems are still active. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e41c06d8279b9423_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: over the last hour, following a recent audit. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_842eb6c144fc5785_n", "kind": "noul", "options": ["false", "true"], "target": [0.45, 0.55], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: during the batch window, during the system migration. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f20c931e3b0c4eff_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.53, 0.45, 0.01, 0.01], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, shortly after a software update. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8849fd2195514c3e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.43, 0.51, 0.01], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: over the last hour, during the system migration. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0da7a7904cda1e12_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.4, 0.12, 0.46, 0.02], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, mid-incident. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a0a4ee9647f914bd_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.93, 0.0, 0.0, 0.07], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: across all regions, while on-call rotation changed. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_16979c66622f2388_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.21, 0.77, 0.02], "state": "The log shipper reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, following a recent audit. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c8208014ec0d2544_n", "kind": "noul", "options": ["false", "true"], "target": [0.67, 0.33], "state": "The log shipper returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during normal operations. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b76a51f421438db6_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.66, 0.32], "state": "The log shipper reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: during the batch window, during an external partner integration. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_11e67c763449ec23_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.8, 0.15, 0.01, 0.04], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: during the batch window, with staffing at reduced levels. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_47e144991d782291_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.84, 0.11, 0.05, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, while legacy systems are still active. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a6d4811b61d9839e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.02, 0.86, 0.12], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: across all regions, with staffing at reduced levels. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3c6fa5b454b1960f_n", "kind": "noul", "options": ["false", "true"], "target": [0.4, 0.6], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the quarterly review. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3d0c3a2c90a90d29_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.88, 0.1, 0.01, 0.01], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: in production only, under an active deadline. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eb6ea5606f235807_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.75, 0.14, 0.09, 0.02], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: over the last hour, mid-incident. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8727bbe0322250d7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.07, 0.86, 0.07], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: across all regions, under an active deadline. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_483e39930950ec13_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: during the batch window, during peak load. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_37187f705c5e6ef5_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: during the batch window, during a scheduled maintenance window. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fb04856443154bd8_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.62, 0.35, 0.02, 0.01], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: during the batch window, with a new vendor onboarded. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3c5ceb7be4fa63e7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.17, 0.7, 0.1, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: over the last hour, during the quarterly review. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_969e4605fb313e7d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.46, 0.2, 0.25, 0.09], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: during the batch window, mid-incident. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d9a3e2a7985ac952_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.35, 0.42, 0.18, 0.01], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: across all regions, as part of a compliance sweep. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5129834c2be66d95_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.11, 0.81, 0.08], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: across all regions, with a new vendor onboarded. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0a7bc4d0e4d42da2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.0, 0.47, 0.51], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: in production only, at the end of the fiscal period. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_28c32a9a0fe43d99_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: in production only, while on-call rotation changed. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9121c05c7f9cfe07_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.04, 0.52, 0.32, 0.12, 0.0, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, mid-incident. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_611781dbf5d6f870_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "The log shipper lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, following a recent audit. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c6b805d255ae34b3_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.13, 0.13, 0.02, 0.72], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: in production only, under an active deadline. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ef30cd0d3607ee62_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "The log shipper reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: in production only, during the system migration. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5e2d1d3c5adeb520_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.36, 0.64, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_44e2ae38c60736df_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.3, 0.48, 0.17, 0.05], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: in production only, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c42f2a3b387b7f49_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "The log shipper reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: in production only, while legacy systems are still active. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_25bcac4ec77a1283_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.06, 0.9, 0.04], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: in production only, with a new vendor onboarded. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6a6a0535e93a2fc7_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.37, 0.59, 0.02, 0.02], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: during the batch window, following a recent audit. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_391da02debb82c27_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.8, 0.18, 0.0], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: in production only, following a recent audit. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2e57b06362c34ff0_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: over the last hour, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a7c6dc939f337830_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.38, 0.61, 0.01], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: during the batch window, while legacy systems are still active. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b93cccd8137900bd_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.32, 0.54, 0.12, 0.02], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7a443e158d554e34_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "The log shipper lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the morning shift. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_18d7c93f64d3dcc1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.95, 0.03, 0.02, 0.0], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, immediately after go-live. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_76320323facabee7_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.09, 0.06, 0.17, 0.68], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: across all regions, during the system migration. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b0ae4d79a7556ce6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.27, 0.54, 0.16, 0.02, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: in production only, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a8ac7e4a18959862_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.66, 0.34, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: in production only, during the system migration. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_296a5aaaa21f5cf1_n", "kind": "noul", "options": ["false", "true"], "target": [0.54, 0.46], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: during the batch window, under reduced staffing. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_597f43800d3b3d80_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.36, 0.62, 0.01], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: in production only, shortly after a software update. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3c6fa5b454b1960f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.44, 0.48, 0.01, 0.07], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the quarterly review. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_10fffb62f8792019_n", "kind": "noul", "options": ["false", "true"], "target": [0.61, 0.39], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: across all regions, under an active deadline. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d611c31c987a6641_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during a scheduled maintenance window. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2c91e806795c3fd8_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "The metrics pipeline flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: across all regions, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_53407943d6fc4d96_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "The log shipper lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: during the batch window, during the holiday freeze. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d79633f8c7941787_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, under an active deadline. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6fa5fda86d36b09f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.0, 0.26, 0.73], "state": "The log shipper lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: across all regions, during normal operations. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_679eea852bb4c45c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.0, 0.38, 0.6], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: during the batch window, during the morning shift. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0e13e61579c0028e_n", "kind": "noul", "options": ["false", "true"], "target": [0.37, 0.63], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: across all regions, under reduced staffing. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5f6d2c2cc249978b_n", "kind": "noul", "options": ["false", "true"], "target": [0.7, 0.3], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: over the last hour, following a recent audit. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c85f5a2157fccc40_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.01, 0.38, 0.59], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: over the last hour, mid-incident. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cd0cd6709908bf4d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.31, 0.45, 0.02, 0.22], "state": "The log shipper shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: in production only, immediately after go-live. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_643b0f6292bc9ded_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.44, 0.56, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: across all regions, mid-incident. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f64ea47ebec1b909_n", "kind": "noul", "options": ["false", "true"], "target": [0.7, 0.3], "state": "Node pgsql-14 flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: during the batch window, under reduced staffing. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_73c6a7add3479ecd_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.0, 0.0, 0.99], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2255f8529bc56d28_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.08, 0.16, 0.15, 0.61], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: across all regions, during the morning shift. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_90f1bbe49bb23f91_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.45, 0.52, 0.01], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: in production only, during the system migration. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5ea33814cbb065e7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.19, 0.79, 0.02], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: over the last hour, under an active deadline. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_af8d46ec951ebf38_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.28, 0.15, 0.05, 0.52], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: in production only, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a45690d299e1f2a6_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.91, 0.07, 0.01, 0.01], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: in production only, mid-incident. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0c859824557cfda2_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "Service catalog-sync flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: during the batch window, during the system migration. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ad0e854f5e3d1299_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.8182, 0.0, 0.101, 0.0808], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: during the batch window, during the quarterly review. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3b002d0b93ad4f84_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "The log shipper shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: during the batch window, during the quarterly review. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_347886fdf4b055a7_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.76, 0.23, 0.0, 0.01], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during normal operations. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8cd00edfb61aa790_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "Service catalog-sync correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: in production only, during the holiday freeze. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_15b7ae0a35f3c290_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.25, 0.72, 0.02], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: during the batch window, under an active deadline. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_34863c051a2d4ba6_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.7, 0.21, 0.0, 0.09], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, mid-incident. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2b1af16afab09fac_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, while on-call rotation changed. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f1f8a47f530c9642_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.8182, 0.1616, 0.0101, 0.0101], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: in production only, with staffing at reduced levels. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aa42fc42c8404956_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.08, 0.82, 0.1], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: in production only, under an active deadline. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_61942adc56474cdf_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: across all regions, following a recent audit. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6a63d3469ffb55aa_n", "kind": "noul", "options": ["false", "true"], "target": [0.41, 0.59], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: in production only, during a scheduled maintenance window. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_36e4399890860f43_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "The log shipper matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: in production only, at the end of the fiscal period. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c8885f4f1a4ad011_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: during the batch window, during the morning shift. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_46b71bb4a1dd72ab_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.46, 0.51, 0.03, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: across all regions, while legacy systems are still active. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_637fa3b187aa6c15_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.15, 0.76, 0.08, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, shortly after a software update. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_17776cc8ed98e594_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.08, 0.8, 0.12, 0.0, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: across all regions, while on-call rotation changed. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_48e03a68bc1d9ba6_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.15, 0.59, 0.24, 0.02], "state": "The metrics pipeline lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: in production only, immediately after go-live. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c43a00a9b6e3d3c3_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: in production only, at the end of the fiscal period. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cb27d2b12a4d0655_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.25, 0.23, 0.42, 0.1], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: in production only, during the system migration. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_06cdae4e93e4966a_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, while on-call rotation changed. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a3bea62925139cf9_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, while on-call rotation changed. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_010714ba5c9c9b84_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.45, 0.53, 0.02, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: across all regions, shortly after a software update. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ef60429fd299ea53_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: over the last hour, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_70614cc21ef4a4ed_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: during the batch window, with staffing at reduced levels. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_65ae3fcde11f63fc_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.06, 0.87, 0.01, 0.06], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: in production only, immediately after go-live. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_af1a1e5d663d8e93_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.35, 0.63], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: across all regions, during normal operations. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1e7dc03ca6a50b91_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.45, 0.52, 0.01], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, as part of a compliance sweep. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8cbb1880d9d0f08d_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, following a recent audit. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6e842d6be5fa07d2_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.02, 0.63, 0.34, 0.01], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: over the last hour, with a new vendor onboarded. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9e1bd1d0b7ac74b9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.09, 0.86, 0.05], "state": "The log shipper flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: in production only, immediately after go-live. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_960173adc879629f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.25, 0.73, 0.02, 0.0], "state": "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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c51953862a36f52a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.02, 0.73, 0.2], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: during the batch window, during the system migration. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4d327cc1eb0401de_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: over the last hour, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7b83ff3ff41a6095_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.05, 0.85, 0.1], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: during the batch window, under an active deadline. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2267eea9d102d78d_n", "kind": "noul", "options": ["false", "true"], "target": [0.61, 0.39], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: over the last hour, following a recent audit. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_de565b1e99ef021a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.44, 0.54, 0.01], "state": "The log shipper reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: during the batch window, under an active deadline. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_abc699cd8c2bd7c5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.31, 0.62, 0.07, 0.0, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: across all regions, following a recent audit. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_90f8f512ad2150a1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.27, 0.71], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: over the last hour, as part of a compliance sweep. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ef79b4f0829010d1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.15, 0.84, 0.01], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: in production only, with a new vendor onboarded. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b7932b2beafa05ca_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: in production only, during the quarterly review. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ea0fc2273e239065_n", "kind": "noul", "options": ["false", "true"], "target": [0.71, 0.29], "state": "The log shipper matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: across all regions, during an external partner integration. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a27228c01cabea6f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.87, 0.12, 0.01, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: across all regions, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e295f7bde693147f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.84, 0.13, 0.01, 0.02], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: over the last hour, while legacy systems are still active. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e451d3fef511fe19_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.65, 0.34, 0.0], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: during the batch window, while on-call rotation changed. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cb0d4d3da55cb5c4_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.0, 0.54, 0.45], "state": "The metrics pipeline lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: over the last hour, under an active deadline. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_62180e0ed67f55af_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: across all regions, while on-call rotation changed. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_189f4549a0c9d2e2_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.28, 0.47, 0.22, 0.03], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: during the batch window, during the system migration. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1b76625ca98d7956_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0404, 0.6768, 0.2727, 0.0101, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during the holiday freeze. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9d767bf30b014062_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.04, 0.42, 0.53, 0.01], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: during the batch window, following a recent audit. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_878f63570c9ca2cd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.28, 0.72, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: in production only, during an external partner integration. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dec7802417e327dd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.29, 0.7, 0.01], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: across all regions, with staffing at reduced levels. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5125af1af577d1f0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.58, 0.41, 0.0], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: across all regions, during normal operations. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_269ed858d810daff_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.06, 0.21, 0.6, 0.12, 0.0], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: in production only, during normal operations. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7cbbc4e97cb3cde0_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.95, 0.01, 0.02], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: during the batch window, shortly after a software update. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cb209b96c2f7ac33_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: over the last hour, shortly after a software update. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7b7d956d04e1d809_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.15, 0.83, 0.02], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, with staffing at reduced levels. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a3dc59b5d6b06448_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.0, 0.21, 0.78], "state": "The log shipper lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: across all regions, as part of a compliance sweep. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f0d4bc694780a65d_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during an external partner integration. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_54f722affb882e3b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.72, 0.25, 0.02, 0.01], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, at the end of the fiscal period. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5129834c2be66d95_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: across all regions, with a new vendor onboarded. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1d17a2265fb7622d_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "The log shipper lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: in production only, during an external partner integration. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6e163621aee8d149_n", "kind": "noul", "options": ["false", "true"], "target": [0.22, 0.78], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during peak load. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1469da638a7fa7a5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.25, 0.71, 0.03], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: in production only, during the holiday freeze. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3abd2ad4f9802b2c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.28, 0.71, 0.01], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: over the last hour, during an external partner integration. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_51af7aa51dae33a3_n", "kind": "noul", "options": ["false", "true"], "target": [0.43, 0.57], "state": "The metrics pipeline flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: over the last hour, under reduced staffing. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_043f4d0be564ac57_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: in production only, during the quarterly review. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3f0f5aee4c1d740c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.08, 0.88, 0.04], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during peak load. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4fee1d651251efd4_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.9, 0.09, 0.0, 0.01], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: across all regions, shortly after a software update. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_18f7bf8ac018bee5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0101, 0.404, 0.5657, 0.0202], "state": "The metrics pipeline correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: during the batch window, at the end of the fiscal period. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fa9c53349b78f486_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.6, 0.39, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: over the last hour, under an active deadline. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_74c16b94646863db_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.13, 0.1, 0.46, 0.31], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: across all regions, during the quarterly review. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_05266732ea7c0c47_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.0, 0.85, 0.15], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during normal operations. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0383cc86b4f6dda9_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: during the batch window, while legacy systems are still active. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7be8826494ddc38d_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b6ca9a63aae78ed9_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "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, shortly after a software update. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a6ece2c054abb7f5_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.2, 0.17, 0.21, 0.42], "state": "The metrics pipeline shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: across all regions, under an active deadline. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3da45301c58c42fa_n", "kind": "noul", "options": ["false", "true"], "target": [0.71, 0.29], "state": "The metrics pipeline correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: over the last hour, under reduced staffing. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fc380c2b10933de2_n", "kind": "noul", "options": ["false", "true"], "target": [0.57, 0.43], "state": "The log shipper correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: across all regions, as part of a compliance sweep. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1fee3cd78cf64772_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.4, 0.58, 0.01], "state": "The metrics pipeline 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 on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ea7a2594578937a9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.32, 0.67, 0.01], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, shortly after a software update. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c432f5788f6952ab_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: across all regions, with staffing at reduced levels. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1461b9acb39f212d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.33, 0.65, 0.02], "state": "Node pgsql-14 flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: during the batch window, during the quarterly review. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_26cea952d7f01ba4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.26, 0.73, 0.01], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: across all regions, with staffing at reduced levels. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_095a09003f8d7b71_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.38, 0.62, 0.0], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: in production only, with staffing at reduced levels. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b316082ed17d9b70_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.18, 0.02, 0.01, 0.79], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: in production only, during the morning shift. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_28392deab2b429a4_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.91, 0.08, 0.0, 0.01], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: in production only, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e76253d035ee181b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.97, 0.0, 0.03], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: in production only, shortly after a software update. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c059b5cb4e6adea1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.76, 0.19, 0.04, 0.01], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: over the last hour, while legacy systems are still active. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c2e8529d0771b780_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.88, 0.04, 0.02, 0.06], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: during the batch window, under reduced staffing. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9ba4b77ecfb3b0e3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.37, 0.6, 0.01], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: in production only, immediately after go-live. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ec61f330e1a97f3_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "The metrics pipeline correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: in production only, with a new vendor onboarded. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_71e45e9d99f4ac48_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: during the batch window, during the system migration. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1dc46f6f845e35c5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.39, 0.58, 0.01], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: across all regions, shortly after a software update. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9dd6b6cb29b08253_n", "kind": "noul", "options": ["false", "true"], "target": [0.52, 0.48], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: across all regions, under reduced staffing. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e68b5989e2bc26ae_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.48, 0.46, 0.03, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: across all regions, during an external partner integration. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8cde76217ac60a7b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.27, 0.72, 0.01], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: in production only, shortly after a software update. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4964069808d6059f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.72, 0.21, 0.04, 0.03], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: over the last hour, during the holiday freeze. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_22595ea42966dc81_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: in production only, while on-call rotation changed. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d0e948c4d7c2d973_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.59, 0.38, 0.0], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the system migration. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8700788eb164467b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.93, 0.0, 0.04, 0.03], "state": "The log shipper correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during a scheduled maintenance window. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_59a947f70c5fc15d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.18, 0.16, 0.51, 0.13, 0.01], "state": "Service catalog-sync correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: in production only, during a scheduled maintenance window. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9bbf7a56da71d304_n", "kind": "noul", "options": ["false", "true"], "target": [0.45, 0.55], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: in production only, during the morning shift. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1e3e5ce32a74a23c_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during the quarterly review. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1209640699cdf9a3_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during peak load. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a4b5e63a9bb5d733_n", "kind": "noul", "options": ["false", "true"], "target": [0.64, 0.36], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: across all regions, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_479bc5901d292b5f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.79, 0.19, 0.0], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: in production only, during a scheduled maintenance window. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4dc26a73df75a210_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.66, 0.29, 0.04, 0.01], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: over the last hour, during the quarterly review. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_76a1bf515f99e04b_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: during the batch window, at the end of the fiscal period. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2aee5cd9ba8a0aa7_n", "kind": "noul", "options": ["false", "true"], "target": [0.5, 0.5], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: over the last hour, during the quarterly review. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6d99814a6e888011_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.44, 0.48, 0.08, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: in production only, during peak load. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_33adf4a905c2775e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.85, 0.14, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: across all regions, during an external partner integration. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ff71206b0fcbdf2f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.46, 0.07, 0.02, 0.45], "state": "Service catalog-sync flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: in production only, during peak load. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_592c75c437d5b4d7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.13, 0.76, 0.1], "state": "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, shortly after a software update. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_beaf10adbf84782a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.54, 0.42, 0.02, 0.02], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: across all regions, during the morning shift. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2f476a7b8bb3fa8c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.49, 0.24, 0.27, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: over the last hour, mid-incident. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3d0c3a2c90a90d29_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.11, 0.83, 0.06], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: in production only, under an active deadline. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b77c3ff272871e88_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.02, 0.25, 0.72], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: across all regions, at the end of the fiscal period. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_76c8886f02ccf218_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.29, 0.48, 0.21, 0.01, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: during the batch window, as part of a compliance sweep. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3b17ac5a265499ad_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.16, 0.59, 0.25, 0.0, 0.0], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: during the batch window, under reduced staffing. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4fd0409603d0714d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.22, 0.48, 0.3, 0.0, 0.0], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: across all regions, during the system migration. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_33adf4a905c2775e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.3, 0.64, 0.05, 0.01], "state": "The log shipper lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: across all regions, during an external partner integration. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_094b5bacc52a549b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.76, 0.23, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: in production only, with a new vendor onboarded. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bc68020d58b91c74_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.53, 0.06, 0.03, 0.38], "state": "The log shipper shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during the holiday freeze. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9b3dc593e72a6352_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.33, 0.06, 0.04, 0.57], "state": "The log shipper shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: in production only, mid-incident. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_84a924b6600662ec_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.1, 0.78, 0.09, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: during the batch window, during a scheduled maintenance window. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e5eaa499f3edc6be_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during normal operations. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_da6384c63ed0e1db_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.06, 0.78, 0.15, 0.0], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: in production only, during a scheduled maintenance window. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8ddf9fec21f9c822_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: in production only, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f3b71d43160443f9_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: in production only, mid-incident. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1cd6e2261f731d88_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.29, 0.03, 0.29, 0.39], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, with a new vendor onboarded. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_657782ff04a1376c_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: in production only, shortly after a software update. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b1be6df2ebc315ab_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.05, 0.52, 0.38, 0.05], "state": "The log shipper reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: over the last hour, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e04fdb4044a6fd94_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.01, 0.12, 0.84], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_498c5de0fcaefcc9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.06, 0.37, 0.56], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: in production only, during the quarterly review. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2bcb2c106496e532_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.68, 0.15, 0.12, 0.05], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: in production only, mid-incident. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_76a8b4df68809f82_n", "kind": "noul", "options": ["false", "true"], "target": [0.67, 0.33], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: in production only, while legacy systems are still active. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_85ecefcdbef9fb21_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, with staffing at reduced levels. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_198189809cde8bd4_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0505, 0.1717, 0.2222, 0.5556], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: across all regions, during the quarterly review. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_216953f6972b360a_n", "kind": "noul", "options": ["false", "true"], "target": [0.59, 0.41], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: over the last hour, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ddadfca7416d7644_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "The log shipper reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: during the batch window, following a recent audit. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_47dd1685305608f5_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: in production only, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_41bf928ec411bf61_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.84, 0.14, 0.01, 0.01], "state": "The log shipper matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: during the batch window, mid-incident. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a581eb07fe826a0a_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: across all regions, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_38781e2e071af25f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.05, 0.01, 0.93], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: in production only, following a recent audit. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_350b71dbffba259a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.26, 0.72, 0.01], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: in production only, following a recent audit. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a47ca30599e35210_n", "kind": "noul", "options": ["false", "true"], "target": [0.57, 0.43], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the morning shift. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d958ef3f41f3e2bb_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: across all regions, during an external partner integration. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7edf279828e4417e_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The log shipper shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: in production only, with a new vendor onboarded. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_574e439a4ef2018c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.26, 0.01, 0.24, 0.49], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: across all regions, during the system migration. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a4be6fe8811ae7c1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.66, 0.24, 0.1, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: over the last hour, while on-call rotation changed. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_32b54e582bdefe39_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.84, 0.02, 0.06, 0.08], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: during the batch window, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8c492d4adb43361a_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "The log shipper correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: during the batch window, mid-incident. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4f52de9c02c184ee_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: in production only, under reduced staffing. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0f8f8be3858de579_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.42, 0.14, 0.14, 0.3], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during peak load. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f695fd40f46117d0_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: across all regions, mid-incident. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_62c9a27c8b40eeef_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.72, 0.27, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: across all regions, during the holiday freeze. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d43487580c637577_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.03, 0.27, 0.32, 0.35, 0.03, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: across all regions, as part of a compliance sweep. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6cb82c4e034f1d18_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during the quarterly review. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_404c2ec7405c0220_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.76, 0.21, 0.02, 0.01], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: across all regions, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9b85b736d2fcdf20_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.05, 0.8, 0.14, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: during the batch window, during the system migration. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3632e8c50902eb91_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.11, 0.82, 0.07], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: over the last hour, following a recent audit. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_74f9f38627addd2c_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: in production only, while on-call rotation changed. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7132abf43f1ec5eb_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.91, 0.06, 0.03, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: over the last hour, during an external partner integration. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1d9d7ec7d9b7f95e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.45, 0.55, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: during the batch window, at the end of the fiscal period. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ddd53badb1354305_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.15, 0.82, 0.03], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during the holiday freeze. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_50b80b47106921e4_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: over the last hour, while on-call rotation changed. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_657b4dd659333261_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.1, 0.79, 0.11], "state": "The metrics pipeline flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: during the batch window, mid-incident. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e23afe5fa28a8ed8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.22, 0.76, 0.02], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: over the last hour, during the quarterly review. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_44d8ba99e74061f9_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: in production only, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f850a4e079dac855_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.0505, 0.8081, 0.1414], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, under an active deadline. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8affdcef31adcce8_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.79, 0.19, 0.02, 0.0], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7076f27201707ff7_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4ad997a34ce9a3c9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.67, 0.32, 0.0], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during the morning shift. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fa5b6971800fa393_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.26, 0.32, 0.38, 0.03], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: in production only, under an active deadline. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d4df17ac883772e5_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.47, 0.45, 0.08, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: over the last hour, during peak load. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9ce93d49d2f29bc8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.13, 0.68, 0.18, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: in production only, during peak load. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_47c916f501463dd4_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.47, 0.43, 0.09, 0.01], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: over the last hour, while legacy systems are still active. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b52866d0c098e6d9_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "The log shipper flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: over the last hour, under an active deadline. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fc380c2b10933de2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.16, 0.62, 0.16, 0.0], "state": "The log shipper correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: across all regions, as part of a compliance sweep. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5a205d87791964fd_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.0, 0.05, 0.92, 0.03], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, as part of a compliance sweep. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e404b58732f62eef_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.83, 0.14, 0.02, 0.01], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during an external partner integration. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ff7506f888122260_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.46, 0.39, 0.13, 0.0], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, while legacy systems are still active. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_073b90b4c85288ae_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during an external partner integration. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c6ba71f63fc6f142_n", "kind": "noul", "options": ["false", "true"], "target": [0.38, 0.62], "state": "The log shipper shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: during the batch window, under an active deadline. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3f778fe2ba4b3d77_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.07, 0.69, 0.22, 0.02], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during a scheduled maintenance window. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_367d46be9cf7e0cd_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The metrics pipeline flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: in production only, as part of a compliance sweep. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bd2d0cdc91497dc1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0101, 0.8182, 0.1717, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: in production only, with a new vendor onboarded. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7cbf78f145eb9479_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.88, 0.11, 0.01, 0.0], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: in production only, while on-call rotation changed. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b7ab1229ac0e1c4_n", "kind": "noul", "options": ["false", "true"], "target": [0.47, 0.53], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: during the batch window, during peak load. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_abbb664d3015ac68_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.18, 0.1, 0.08, 0.64], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: across all regions, during the system migration. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a66f0bc423fce0ec_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.34, 0.63, 0.02], "state": "The log shipper shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: across all regions, during the system migration. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_245db2010c6eae9a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.43, 0.56, 0.0], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, with staffing at reduced levels. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f71aecac8178fd49_n", "kind": "noul", "options": ["false", "true"], "target": [0.45, 0.55], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during a scheduled maintenance window. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a33cd9a8d60f3115_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: in production only, with a new vendor onboarded. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f51bdb8c25ef04ab_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.57, 0.42, 0.0], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: over the last hour, while on-call rotation changed. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f6ba756a5a0b8c71_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.29, 0.7, 0.01], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: across all regions, under an active deadline. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d37ec17544ee6504_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.67, 0.32, 0.0], "state": "The log shipper shows a slow leak in heap growth; 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 automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0de7bfa8739d0f18_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.75, 0.21, 0.04, 0.0], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: over the last hour, during the morning shift. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_75ea0aabd79305be_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.11, 0.66, 0.22, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during peak load. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ff5975111ff4320_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.2, 0.14, 0.36, 0.3], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cfd18f1f91bb687a_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "The log shipper reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: in production only, as part of a compliance sweep. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2cf9127aec9bb01c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.12, 0.84, 0.04], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: over the last hour, with staffing at reduced levels. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cfd18f1f91bb687a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.52, 0.41, 0.06, 0.01], "state": "The log shipper reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: in production only, as part of a compliance sweep. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6d32e300bdb5723f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.71, 0.24, 0.0, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: during the batch window, during the morning shift. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f19f77177f7bd9a7_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.94, 0.05, 0.0, 0.01], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: during the batch window, mid-incident. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_831ed8c8932bcf7c_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: in production only, during an external partner integration. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d99b757add51b1e3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.05, 0.89, 0.06, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: over the last hour, under reduced staffing. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_83f38134ff999234_n", "kind": "noul", "options": ["false", "true"], "target": [0.39, 0.61], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: across all regions, during the system migration. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2fb97583af14319e_n", "kind": "noul", "options": ["false", "true"], "target": [0.43, 0.57], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, following a recent audit. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f46b7b7f7117dbe3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.2, 0.68, 0.1, 0.0], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: in production only, during peak load. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_083572132303d418_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.66, 0.34, 0.0], "state": "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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1f63d2502608b95b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.1, 0.05, 0.11, 0.74], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: across all regions, following a recent audit. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9d07c7c3ca39f49a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.15, 0.63, 0.22, 0.0], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, shortly after a software update. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e075f121146bac62_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: during the batch window, during normal operations. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b32cb2fd2ae1c20a_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: during the batch window, shortly after a software update. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e94ddde0794017bf_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, immediately after go-live. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_40a63bb8846bf86a_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, immediately after go-live. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_18c36210a27910f6_n", "kind": "noul", "options": ["false", "true"], "target": [0.47, 0.53], "state": "The log shipper reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: in production only, under reduced staffing. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_153b1156f6cd3dd7_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.87, 0.11, 0.01, 0.01], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: across all regions, mid-incident. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dbf66c332f74855c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.11, 0.59, 0.29, 0.01], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: in production only, at the end of the fiscal period. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_695532197963ace8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.1, 0.86, 0.04], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, shortly after a software update. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4823de6a955f1d2b_n", "kind": "noul", "options": ["false", "true"], "target": [0.54, 0.46], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: during the batch window, during the quarterly review. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d85562652e7126d1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.11, 0.45, 0.39, 0.05, 0.0], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: in production only, at the end of the fiscal period. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f601f758371c811b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.24, 0.34, 0.35, 0.05], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: across all regions, mid-incident. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2aa5fbee764fdf57_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.21, 0.77, 0.02], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during the system migration. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7cb48a73714989e5_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.91, 0.07, 0.0, 0.02], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: over the last hour, immediately after go-live. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_47cbadcb91c14c54_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.53, 0.45, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: in production only, under reduced staffing. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_42301bef49629f68_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.18, 0.74, 0.06, 0.02, 0.0, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: in production only, during the quarterly review. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_039fa142e996e655_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.06, 0.75, 0.19, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, with staffing at reduced levels. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ad445fd6c49f2c88_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.32, 0.42, 0.01, 0.25], "state": "Service catalog-sync shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: in production only, during the quarterly review. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fd6d27eae7c8c374_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.01, 0.04, 0.52, 0.41, 0.01], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: in production only, as part of a compliance sweep. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ed19a5f53c241b52_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.52, 0.45, 0.01], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: during the batch window, mid-incident. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ebbd793f2d5b5fc3_n", "kind": "noul", "options": ["false", "true"], "target": [0.57, 0.43], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: during the batch window, during a scheduled maintenance window. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_97d5a11e89a3bdc4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.14, 0.77, 0.07, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: in production only, following a recent audit. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_583a9d9300dbcfca_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.05, 0.87, 0.08, 0.0], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: across all regions, during the quarterly review. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ad0e854f5e3d1299_n", "kind": "noul", "options": ["false", "true"], "target": [0.22, 0.78], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: during the batch window, during the quarterly review. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e7173d97184683b8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.12, 0.42, 0.42, 0.04, 0.0], "state": "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, during the morning shift. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_780c994c600c207e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.66, 0.27, 0.05, 0.02], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during peak load. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9af65b32402d2397_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.61, 0.31, 0.08, 0.0, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: during the batch window, during a scheduled maintenance window. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3632e8c50902eb91_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.86, 0.01, 0.1, 0.03], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: over the last hour, following a recent audit. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a53ae687e89e5ae9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.41, 0.3, 0.01, 0.28], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0e8d9c60ae634ed8_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.7, 0.28, 0.01], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: during the batch window, shortly after a software update. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_09534f74484f4af8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.08, 0.53, 0.37, 0.01], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: across all regions, mid-incident. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cdb8f9b457ecbb19_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.14, 0.74, 0.02, 0.1], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: during the batch window, as part of a compliance sweep. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5936a91c770c9731_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.02, 0.74, 0.24], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally flags a step-function change in error slope. Context: over the last hour, under an active deadline. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a2cb29f7d44604dc_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.31, 0.01, 0.03, 0.65], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during a scheduled maintenance window. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4d8e06e7e260f8c0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.28, 0.58, 0.12, 0.0], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: over the last hour, during peak load. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_abdfc795f51f9d49_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.01, 0.44, 0.55], "state": "Service catalog-sync lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: over the last hour, while on-call rotation changed. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eaf5ad7e8245df2e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.22, 0.76, 0.02], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, with a new vendor onboarded. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_67f37a804e7c7403_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.2727, 0.6667, 0.0505, 0.0101], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during the holiday freeze. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_308c4b2d2048ba61_n", "kind": "noul", "options": ["false", "true"], "target": [0.58, 0.42], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: over the last hour, at the end of the fiscal period. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_23ee7b85cb1292aa_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.07, 0.75, 0.17, 0.01], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: during the batch window, during an external partner integration. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_496c99ee79da5311_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: during the batch window, immediately after go-live. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ed6266a6519926a5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.73, 0.26, 0.0], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: across all regions, during normal operations. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c8fbd17a379cbad0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.63, 0.37, 0.0], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: during the batch window, with a new vendor onboarded. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2c4c219826f98fd4_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.04, 0.52, 0.42], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: during the batch window, with a new vendor onboarded. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e5b06df5adcbf8f7_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during a scheduled maintenance window. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a0a4ee9647f914bd_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: across all regions, while on-call rotation changed. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2255f8529bc56d28_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.68, 0.31, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: across all regions, during the morning shift. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8d7ca293241c40aa_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.96, 0.03, 0.0, 0.01], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally reports empty scrape targets after the network change. Context: over the last hour, immediately after go-live. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_85f5bc5391744c82_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.9, 0.09, 0.01, 0.0], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: in production only, while on-call rotation changed. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f922140e1ab37020_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: in production only, immediately after go-live. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_29b1c08efa168ca1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.12, 0.15, 0.08, 0.65], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: over the last hour, as part of a compliance sweep. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_56ec38af968872e3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.12, 0.22, 0.55, 0.1, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: over the last hour, during the holiday freeze. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_da37e7bdeec730f0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.21, 0.61, 0.18, 0.0, 0.0], "state": "The log shipper flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: across all regions, during normal operations. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4966f68948aa1edd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.17, 0.37, 0.42, 0.03, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, at the end of the fiscal period. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_38cf6a8fdc7d74e2_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "Service catalog-sync flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: during the batch window, while on-call rotation changed. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9f700a50fbba0486_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.06, 0.06, 0.55, 0.31, 0.01], "state": "The log shipper matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: during the batch window, as part of a compliance sweep. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2dc6b620fa20ca5d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.12, 0.84, 0.04], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: in production only, immediately after go-live. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_905c2d544341369c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.72, 0.27, 0.01, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: in production only, during the system migration. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_823c2ef859dc5c5c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.37, 0.57, 0.05, 0.01], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: in production only, as part of a compliance sweep. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ae7fc9aa95d5ab94_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.26, 0.71, 0.02], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, immediately after go-live. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_637fc0288a3bf1c0_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.38, 0.01, 0.4, 0.21], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during the morning shift. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e5746e898c88847b_n", "kind": "noul", "options": ["false", "true"], "target": [0.7, 0.3], "state": "The log shipper shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: in production only, during an external partner integration. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aba3520249b2f616_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: in production only, immediately after go-live. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0be0b7c06c040470_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.51, 0.48, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: during the batch window, during the morning shift. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_290699e716823253_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: in production only, shortly after a software update. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0c0f42eaaec20497_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: during the batch window, during an external partner integration. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d467ac77213602b6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.09, 0.39, 0.48, 0.04, 0.0], "state": "The metrics pipeline flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: across all regions, as part of a compliance sweep. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cf725733135cc99a_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "The log shipper lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during the holiday freeze. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5bdf8b5533b72222_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.06, 0.79, 0.15, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b0310969d677d5b2_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: in production only, immediately after go-live. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_33f6c3fb7ce0cd38_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.34, 0.65, 0.01], "state": "The log shipper flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: across all regions, during the holiday freeze. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fdd67927938aa961_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.76, 0.2, 0.04, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, while on-call rotation changed. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2f852bd8fcc44797_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "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 an active deadline. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fc714cc230b209b8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.34, 0.6, 0.06, 0.0, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7aff109a3e8c36e2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.13, 0.84, 0.03], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: over the last hour, immediately after go-live. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_52d88160702ee1e8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.25, 0.74, 0.01], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: over the last hour, under reduced staffing. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_71a34ce33fa3288a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.1, 0.21, 0.6, 0.08, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: during the batch window, during the system migration. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e75fa280bcf0327b_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "The log shipper lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during the holiday freeze. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2865a50ef29772c6_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.7, 0.25, 0.05, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: over the last hour, with staffing at reduced levels. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9f576097d3c2da5e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.36, 0.62, 0.02, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: across all regions, at the end of the fiscal period. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cbc0c992dcb4a7f6_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.81, 0.17, 0.02], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: during the batch window, shortly after a software update. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_99f247f513528d3a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.1, 0.86, 0.04], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: during the batch window, following a recent audit. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_15a92085135dac36_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.02, 0.17, 0.26, 0.51, 0.04, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: over the last hour, during an external partner integration. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_60ebf4e98066460e_n", "kind": "noul", "options": ["false", "true"], "target": [0.6, 0.4], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: during the batch window, under an active deadline. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_643b0f6292bc9ded_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.15, 0.09, 0.34, 0.42], "state": "Service catalog-sync shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: across all regions, mid-incident. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_434119ea1bca8f26_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.1, 0.01, 0.56, 0.33], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: during the batch window, at the end of the fiscal period. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_80250e528411ed5c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.13, 0.64, 0.19, 0.04, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: across all regions, under an active deadline. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ef782d9abc028e10_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: across all regions, shortly after a software update. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_926277f27352de01_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: in production only, during normal operations. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_25c05aee2960a6bd_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.74, 0.25, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: during the batch window, at the end of the fiscal period. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fa4b475e98f9119a_n", "kind": "noul", "options": ["false", "true"], "target": [0.49, 0.51], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dae5f96b7576b97a_n", "kind": "noul", "options": ["false", "true"], "target": [0.5, 0.5], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: in production only, during the morning shift. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d080312d52c4565a_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during an external partner integration. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0f5af912a31989af_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.59, 0.4, 0.0], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, while legacy systems are still active. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b6afaf1df11e5af1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.56, 0.43, 0.0], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: in production only, while legacy systems are still active. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d40d7ccd24f10882_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, at the end of the fiscal period. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7d2ae47cf67ccc60_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: in production only, mid-incident. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a1309467849eac7b_n", "kind": "noul", "options": ["false", "true"], "target": [0.61, 0.39], "state": "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.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1fee3cd78cf64772_n", "kind": "noul", "options": ["false", "true"], "target": [0.43, 0.57], "state": "The metrics pipeline 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 on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_47d8e2c3d0a7cd34_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.33, 0.21, 0.01, 0.45], "state": "Service catalog-sync shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: over the last hour, at the end of the fiscal period. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_db824cfa84c7161b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.48, 0.5], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: during the batch window, during an external partner integration. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_54c4ffe2c06b221f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.8, 0.17, 0.0], "state": "The log shipper matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: in production only, during normal operations. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ee4f99e3a9815a9d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.23, 0.21, 0.03, 0.53], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: across all regions, during a scheduled maintenance window. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cc62ecec6e2d026e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.35, 0.02, 0.19, 0.44], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: in production only, with staffing at reduced levels. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ed06191f323926de_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.11, 0.14, 0.6, 0.14, 0.01], "state": "The log shipper correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: over the last hour, during a scheduled maintenance window. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dca80036fc27653c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.21, 0.37, 0.35, 0.07], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: over the last hour, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ba4ac7a5ef0c9344_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5d2ddc53f9f631cb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.75, 0.24, 0.0], "state": "The metrics pipeline shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: in production only, during the system migration. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2b1ca094d49a6fda_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during peak load. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bc84ff902854fa73_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.09, 0.56, 0.33, 0.01], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_76cc7fbd28affc4e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.15, 0.52, 0.32, 0.01, 0.0], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: in production only, during the morning shift. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f9448e26ddb2fe9b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.43, 0.44, 0.11, 0.0], "state": "The log shipper reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: in production only, shortly after a software update. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4bab92aa72110e07_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.94, 0.06, 0.0, 0.0], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: in production only, with staffing at reduced levels. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_929cdb50e988d398_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.08, 0.88, 0.04], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: during the batch window, shortly after a software update. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_13469f2dbd5a6ea2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.46, 0.53, 0.0], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the holiday freeze. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ce97227bb0007987_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.46, 0.51, 0.01], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: across all regions, during the quarterly review. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_16bc14f2836ed622_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.11, 0.84, 0.05], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: in production only, during peak load. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b82820cab21b5aee_n", "kind": "noul", "options": ["false", "true"], "target": [0.4, 0.6], "state": "The log shipper returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: across all regions, during the system migration. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5219773b91ab11e3_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.44, 0.53, 0.03, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: during the batch window, while on-call rotation changed. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_38781e2e071af25f_n", "kind": "noul", "options": ["false", "true"], "target": [0.69, 0.31], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: in production only, following a recent audit. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_52d88160702ee1e8_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.34, 0.63, 0.01, 0.02], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: over the last hour, under reduced staffing. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_087f18c219b31896_n", "kind": "noul", "options": ["false", "true"], "target": [0.71, 0.29], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally flags a step-function change in error slope. Context: across all regions, as part of a compliance sweep. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_503689448e21ac83_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.64, 0.02, 0.01, 0.33], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: in production only, under reduced staffing. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_10d200dfe972c644_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.53, 0.46, 0.0], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during the morning shift. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e8c6231769567f90_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.24, 0.6, 0.12, 0.0], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: in production only, during the holiday freeze. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7087b7c9b084b4b0_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.35, 0.41, 0.03, 0.21], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: in production only, with staffing at reduced levels. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5fb88450f8bbbf1e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.45, 0.52, 0.02, 0.01], "state": "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, following a recent audit. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b8298e43e1e5e5e7_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: across all regions, while on-call rotation changed. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_caccf33282d85630_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: across all regions, during an external partner integration. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6e163621aee8d149_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.05, 0.88, 0.07], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during peak load. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_38048b85d9b2e064_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.95, 0.02, 0.0, 0.03], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: in production only, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_861f6fe81bd81dce_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: across all regions, during a scheduled maintenance window. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eaf5ad7e8245df2e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.72, 0.26, 0.01, 0.01], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, with a new vendor onboarded. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_93db406618a09300_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.42, 0.56, 0.01], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: over the last hour, during peak load. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e60673a904e76c15_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: in production only, under an active deadline. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dae5f96b7576b97a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.01, 0.49, 0.45], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: in production only, during the morning shift. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_10bf3efab86ff6a0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.06, 0.84, 0.09, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: during the batch window, with staffing at reduced levels. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d611c31c987a6641_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.14, 0.61, 0.19, 0.0], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during a scheduled maintenance window. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_99f4926a28da3e72_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.79, 0.16, 0.05], "state": "The log shipper flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: in production only, shortly after a software update. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_64bdcffa6827d158_n", "kind": "noul", "options": ["false", "true"], "target": [0.62, 0.38], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: across all regions, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_db4bba3f01b6fc7f_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The metrics pipeline flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: across all regions, at the end of the fiscal period. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_582d13bda168e8e9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.11, 0.61, 0.23, 0.01], "state": "The metrics pipeline correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: during the batch window, during peak load. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_78a8c1086f17a9a1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.58, 0.41, 0.0], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: over the last hour, as part of a compliance sweep. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ee3e059761003426_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.69, 0.29, 0.0], "state": "The metrics pipeline flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: during the batch window, during the holiday freeze. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2cf9127aec9bb01c_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: over the last hour, with staffing at reduced levels. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_07e74f2692ddc9f0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.47, 0.51, 0.01], "state": "The log shipper shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: across all regions, shortly after a software update. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b39a58650d0a51f1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.92, 0.06, 0.02, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during the morning shift. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_20dc48a108093394_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.15, 0.8, 0.05], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: during the batch window, as part of a compliance sweep. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2d922080832a57a6_n", "kind": "noul", "options": ["false", "true"], "target": [0.23, 0.77], "state": "The log shipper reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: over the last hour, mid-incident. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e9e90b5e08ad951e_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: across all regions, following a recent audit. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a476ff22e4b40a3d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.29, 0.04, 0.23, 0.44], "state": "The log shipper shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: across all regions, under an active deadline. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_90c6b54ce17e6cbc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.09, 0.76, 0.14, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: during the batch window, following a recent audit. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_823ace2b5495f647_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.41, 0.58, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: during the batch window, while on-call rotation changed. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2662cef7d4cee8be_n", "kind": "noul", "options": ["false", "true"], "target": [0.67, 0.33], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: in production only, during the system migration. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_907bedbc70095f1b_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally matches last Tuesday's incident signature. Context: in production only, during a scheduled maintenance window. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7153fd5fcc5c1049_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.35, 0.65, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, during the morning shift. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7d6816a68c2b92c1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.45, 0.5, 0.03, 0.0], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: across all regions, with a new vendor onboarded. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cf0b53949a90140f_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, while legacy systems are still active. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5fe199c2f77c4167_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: in production only, while on-call rotation changed. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_431a66b17ed96ca5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.1414, 0.8182, 0.0404], "state": "The log shipper reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: during the batch window, during the system migration. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_627fc1d0bb79ef39_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.18, 0.01, 0.12, 0.69], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: in production only, with staffing at reduced levels. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d91b841ae912b902_n", "kind": "noul", "options": ["false", "true"], "target": [0.63, 0.37], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: in production only, as part of a compliance sweep. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5123410baa410380_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.44, 0.42, 0.13, 0.01], "state": "The log shipper reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: over the last hour, during the morning shift. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b087eafd33e8f843_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.07, 0.51, 0.26, 0.14, 0.01], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, mid-incident. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_baf4d6220323e5a5_n", "kind": "noul", "options": ["false", "true"], "target": [0.23, 0.77], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during peak load. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_00bdfdf29e75ccae_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.58, 0.42, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: during the batch window, with a new vendor onboarded. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d43b58a53f957b11_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.15, 0.81, 0.03, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: during the batch window, during peak load. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ed91f24332039d71_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.21, 0.1, 0.65, 0.04], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: in production only, immediately after go-live. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e32ef1e1fed78397_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.25, 0.01, 0.11, 0.63], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: in production only, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_88e59bf617b7f237_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.5, 0.45, 0.04, 0.01], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during the quarterly review. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f37762b79a186be5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.04, 0.64, 0.32, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: in production only, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ff0a156c64e53236_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.21, 0.77, 0.02], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bd460e0f02ddfb5b_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: across all regions, while on-call rotation changed. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fec0994ead8e5df1_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Node pgsql-14 correlates with the vendor status page incident; 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 review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_07e74f2692ddc9f0_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.63, 0.35, 0.01, 0.01], "state": "The log shipper shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: across all regions, shortly after a software update. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c8203d3a2fe8d894_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.04, 0.81, 0.15, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally matches last Tuesday's incident signature. Context: across all regions, while on-call rotation changed. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_02e70d71386df51f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.36, 0.45, 0.15, 0.04], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: during the batch window, as part of a compliance sweep. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8182e66bd543e93d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.2, 0.77, 0.03], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally flags a step-function change in error slope. Context: over the last hour, during the morning shift. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_660bb640fe1e5921_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "The log shipper lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: in production only, as part of a compliance sweep. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_409b8061e2bd0a7b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.35, 0.43, 0.09, 0.13], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: during the batch window, following a recent audit. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6ebf8468cfa344aa_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.68, 0.07, 0.01, 0.24], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: in production only, during peak load. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3d8d0b2a52741e1d_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: across all regions, immediately after go-live. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_657ddbe0fe7a038b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.07, 0.88, 0.05], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during the morning shift. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aec8610f6543fe11_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.31, 0.67], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: during the batch window, under an active deadline. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cb19060120bffb30_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: in production only, with staffing at reduced levels. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fe09c177a65ed5d6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.3, 0.41, 0.27, 0.01, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: over the last hour, during the quarterly review. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b23250c791b5e544_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.24, 0.13, 0.33, 0.3], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: in production only, during the morning shift. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_efc678416d230d59_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "The metrics pipeline shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: in production only, immediately after go-live. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_183f3f116dbd9a55_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.2828, 0.1414, 0.0303, 0.5455], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: over the last hour, following a recent audit. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4052f5d37f117db3_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.99, 0.0, 0.0, 0.01], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: during the batch window, during peak load. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_90e3a7e12df5e349_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.57, 0.4, 0.01], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: across all regions, shortly after a software update. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9a3d44ae6c26dc29_n", "kind": "noul", "options": ["false", "true"], "target": [0.41, 0.59], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: over the last hour, during peak load. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b331cc75576b83ca_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: during the batch window, with staffing at reduced levels. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_780c994c600c207e_n", "kind": "noul", "options": ["false", "true"], "target": [0.71, 0.29], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during peak load. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aa5d18ec98978de7_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: over the last hour, under an active deadline. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b811c3508c7b6a71_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.58, 0.4, 0.0], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: across all regions, during the holiday freeze. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e7a139f815283fb8_n", "kind": "noul", "options": ["false", "true"], "target": [0.23, 0.77], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, immediately after go-live. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_913b4247c0a78821_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: during the batch window, with a new vendor onboarded. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_705ec9a7d02ee5ab_n", "kind": "noul", "options": ["false", "true"], "target": [0.39, 0.61], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: during the batch window, during a scheduled maintenance window. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_be2dfe3232ca0925_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: in production only, mid-incident. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c24e74df9fbf66d1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.73, 0.05, 0.01, 0.21], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally lost 4 minutes of trace data. Context: during the batch window, at the end of the fiscal period. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_45b5b5d537acd377_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.51, 0.49, 0.0], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: during the batch window, with staffing at reduced levels. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4c00123562ef3c4e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.27, 0.64, 0.08, 0.01], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: in production only, shortly after a software update. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_88f7ed5f46ac527a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.44, 0.08, 0.0, 0.48], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during peak load. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a1ebc50d954ea3b0_n", "kind": "noul", "options": ["false", "true"], "target": [0.52, 0.48], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: across all regions, during the holiday freeze. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f3b71d43160443f9_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.98, 0.01, 0.0, 0.01], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: in production only, mid-incident. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_52be48b8f2caf7dc_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: over the last hour, following a recent audit. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_43368c76580c1474_n", "kind": "noul", "options": ["false", "true"], "target": [0.2, 0.8], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, with a new vendor onboarded. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f217d4867c010acc_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.51, 0.47], "state": "The metrics pipeline correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: across all regions, while legacy systems are still active. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3524ff425564bc53_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during the holiday freeze. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3421a7950fef8905_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.21, 0.59, 0.14, 0.0], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: in production only, while on-call rotation changed. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_589bd0bdedb33318_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.1919, 0.5657, 0.0101, 0.2323], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: across all regions, under an active deadline. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e464111270074045_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.25, 0.41, 0.32, 0.01], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: across all regions, mid-incident. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0c912fb531a9a1c0_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "The log shipper lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: across all regions, under an active deadline. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d3a2eb231bb2c4b5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.48, 0.44, 0.07, 0.01, 0.0, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: across all regions, at the end of the fiscal period. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5df8e2890c108205_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.5, 0.49, 0.0], "state": "The log shipper flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: in production only, during a scheduled maintenance window. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e784c803e5cb8bb7_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.92, 0.02, 0.0, 0.06], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: during the batch window, under an active deadline. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c72c0c108d60f47c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.44, 0.54], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: in production only, during an external partner integration. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7076f27201707ff7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.09, 0.8, 0.11], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0e77bc02de5b7405_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: over the last hour, during the holiday freeze. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1902c7f37ac21995_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.34, 0.63, 0.02], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: in production only, with a new vendor onboarded. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c62d202fc8b58c56_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.74, 0.24, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: during the batch window, with staffing at reduced levels. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7f42867b99d812f1_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: across all regions, under an active deadline. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4f396ccf243b9cf9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.35, 0.63, 0.01], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: over the last hour, during the holiday freeze. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7e5f931b938925e4_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.96, 0.04, 0.0, 0.0], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: during the batch window, under an active deadline. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f8ae9f172b3fe2cf_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: in production only, while legacy systems are still active. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1563756c8a653554_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.53, 0.4, 0.06, 0.01], "state": "The log shipper matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: over the last hour, during the holiday freeze. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d769e299e40de70a_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: in production only, shortly after a software update. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_67b9298660fe6f7b_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: over the last hour, following a recent audit. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eb97c04614140738_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.07, 0.68, 0.22, 0.01], "state": "The log shipper correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: during the batch window, as part of a compliance sweep. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8d07db9868f04269_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.79, 0.17, 0.04, 0.0], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: over the last hour, during an external partner integration. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e5eaa499f3edc6be_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.35, 0.62, 0.03, 0.0, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during normal operations. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c3b9992e6bd43d44_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during normal operations. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_22555bf02c5aeb9a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.86, 0.12, 0.0, 0.02], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: during the batch window, during the holiday freeze. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1c1d90041d10626c_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: in production only, under an active deadline. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ce79b3d0b1bba8db_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the quarterly review. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_11296670f77e65ee_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.31, 0.67, 0.01], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: across all regions, while on-call rotation changed. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2ccd329f675b9c66_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: across all regions, during the holiday freeze. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2942076c054edae5_n", "kind": "noul", "options": ["false", "true"], "target": [0.46, 0.54], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: during the batch window, under reduced staffing. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f7d22efbe2331a2e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.65, 0.34, 0.01, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, with a new vendor onboarded. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6861f37adea39929_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.21, 0.77, 0.02], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: in production only, while on-call rotation changed. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_606e9a20dcf9f48e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.0, 0.01, 0.99], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: in production only, as part of a compliance sweep. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_41bf9e113bd3a250_n", "kind": "noul", "options": ["false", "true"], "target": [0.42, 0.58], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: in production only, with a new vendor onboarded. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3c01e06ec51286ab_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.56, 0.3, 0.11, 0.0], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the quarterly review. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_766c5de04e34fd1c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.37, 0.61, 0.01], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: in production only, at the end of the fiscal period. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2b1162807cb82ecf_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.16, 0.49, 0.3, 0.04, 0.0], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during the holiday freeze. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_44c05e04063a447b_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "The log shipper flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, with staffing at reduced levels. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e6617da963f1d26f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.42, 0.57, 0.01], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during normal operations. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2662cef7d4cee8be_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.02, 0.09, 0.6, 0.28, 0.0], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: in production only, during the system migration. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_104854ae7a68ea0b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.07, 0.3, 0.61, 0.02, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: during the batch window, while legacy systems are still active. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6283304cdd46b91f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.92, 0.02, 0.01, 0.05], "state": "Node pgsql-14 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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a580bbedec231618_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.22, 0.54, 0.22, 0.02, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: across all regions, under an active deadline. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_52faf49e5db7130b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.79, 0.18, 0.02, 0.01], "state": "Service catalog-sync shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: over the last hour, with staffing at reduced levels. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3641702b2d37aa09_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Service catalog-sync shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: over the last hour, during peak load. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d856343fe4430ac2_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: over the last hour, following a recent audit. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_870e806889159e99_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The log shipper lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: during the batch window, while legacy systems are still active. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ba4e20eb6272cef5_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, while on-call rotation changed. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_66072434eceeaf09_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.9, 0.02, 0.01, 0.07], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, while on-call rotation changed. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e4bf362afb6c1a52_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.12, 0.57, 0.25, 0.06, 0.0], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, as part of a compliance sweep. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6de561fa5caf14c8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.07, 0.78, 0.14, 0.0], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: over the last hour, while on-call rotation changed. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d3680106218d9f24_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.07, 0.86, 0.07], "state": "The metrics pipeline shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: during the batch window, under an active deadline. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e8897e368b85ec9d_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: during the batch window, during the morning shift. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d8e8cc48cc1147cf_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.03, 0.83, 0.14], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: during the batch window, with a new vendor onboarded. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1c30f122c6ddbb0f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.56, 0.31, 0.09, 0.01], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fffe09cb251fe5f8_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.67, 0.27, 0.05, 0.01], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, with staffing at reduced levels. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d84f132e39b60a5f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.2, 0.68, 0.1, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: in production only, during an external partner integration. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cb9e4d37d9f78573_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.63, 0.31, 0.05, 0.01], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally reports empty scrape targets after the network change. Context: during the batch window, under reduced staffing. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d5586cc048399312_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.19, 0.72, 0.09, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: over the last hour, following a recent audit. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_998a6f7e1468bd11_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.0, 0.11, 0.87, 0.02], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: during the batch window, during the system migration. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_907bedbc70095f1b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.01, 0.54, 0.42, 0.03], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally matches last Tuesday's incident signature. Context: in production only, during a scheduled maintenance window. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_072f8c770e3b902e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.19, 0.53, 0.27, 0.0], "state": "Service catalog-sync flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: in production only, mid-incident. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_397746334308f6d5_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.03, 0.06, 0.9], "state": "The log shipper matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: during the batch window, during the system migration. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7415478494cc2803_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.24, 0.29, 0.35, 0.12], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: in production only, mid-incident. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2f9b56e7ef8f3e7c_n", "kind": "noul", "options": ["false", "true"], "target": [0.63, 0.37], "state": "The metrics pipeline shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: in production only, shortly after a software update. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_58bc0c178f0a9b47_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.07, 0.19, 0.67, 0.07, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: across all regions, during a scheduled maintenance window. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ad445fd6c49f2c88_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.83, 0.15, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: in production only, during the quarterly review. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b25717431c67c519_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.01, 0.02, 0.29, 0.64, 0.03], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: in production only, during the quarterly review. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_df1a1ada49983578_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.04, 0.49, 0.44, 0.01], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during the quarterly review. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7aff109a3e8c36e2_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.95, 0.02, 0.01, 0.02], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: over the last hour, immediately after go-live. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3c8054a56a7360ee_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: in production only, during an external partner integration. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_04e2d4344a078530_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.74, 0.21, 0.04, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during the morning shift. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a4956eee38c9eae1_n", "kind": "noul", "options": ["false", "true"], "target": [0.91, 0.09], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: in production only, during the system migration. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_baa7474bfe001b61_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.24, 0.75, 0.01], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: in production only, during the holiday freeze. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ac67f1040237794f_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: in production only, during the quarterly review. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f16c1a355b29b809_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, with a new vendor onboarded. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b93cccd8137900bd_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, with staffing at reduced levels. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a5a31f49d9e9f9e3_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.92, 0.07, 0.01, 0.0], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during normal operations. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4667fbaf100c17ee_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: during the batch window, under an active deadline. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d80df85652d31fc7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.43, 0.51, 0.01], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally correlates with the vendor status page incident. Context: over the last hour, as part of a compliance sweep. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c43105c2477b140d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.1, 0.18, 0.61, 0.11, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during a scheduled maintenance window. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dcba489931d6439d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.11, 0.54, 0.32, 0.01], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: in production only, while on-call rotation changed. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b8c1e1782716be55_n", "kind": "noul", "options": ["false", "true"], "target": [0.92, 0.08], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during an external partner integration. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4f396ccf243b9cf9_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.62, 0.33, 0.04, 0.01], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: over the last hour, during the holiday freeze. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e61ce4baa570a6ae_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.7, 0.29, 0.0, 0.01], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: in production only, following a recent audit. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2def5e77f6641a87_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.71, 0.25, 0.02, 0.02], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during peak load. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_329c2b47632bf512_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.22, 0.75, 0.03], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during the holiday freeze. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3d71a0710ce451e2_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Service catalog-sync lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: during the batch window, following a recent audit. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3f5db9c342ca4315_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.8, 0.19, 0.01, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: in production only, shortly after a software update. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f8ae9f172b3fe2cf_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.24, 0.71, 0.02, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: in production only, while legacy systems are still active. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_02e70d71386df51f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.06, 0.76, 0.17, 0.0], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows clock skew of 800ms across replicas. Context: during the batch window, as part of a compliance sweep. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9003bd7796e32e34_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.08, 0.02, 0.01, 0.89], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: over the last hour, as part of a compliance sweep. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_53532c3c65dabec7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.11, 0.84, 0.05], "state": "The log shipper reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: across all regions, at the end of the fiscal period. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_367d46be9cf7e0cd_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.03, 0.87, 0.09], "state": "The metrics pipeline flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: in production only, as part of a compliance sweep. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_111d67ddf223d927_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: across all regions, under an active deadline. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c3b9992e6bd43d44_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.44, 0.55, 0.01], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during normal operations. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a9945a26ed7de519_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, at the end of the fiscal period. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_23778d87b6993de8_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally lost 4 minutes of trace data. Context: across all regions, with staffing at reduced levels. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4b726c3ecf66c27d_n", "kind": "noul", "options": ["false", "true"], "target": [0.45, 0.55], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during peak load. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ec0d5e1348186e49_n", "kind": "noul", "options": ["false", "true"], "target": [0.43, 0.57], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: over the last hour, during a scheduled maintenance window. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a40b864642d07031_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.56, 0.36, 0.08, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: in production only, during peak load. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cf5625720254f9b9_n", "kind": "noul", "options": ["false", "true"], "target": [0.41, 0.59], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, following a recent audit. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2a5bb884bc0316f5_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "The metrics pipeline correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: over the last hour, following a recent audit. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_693dcb1497790085_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: in production only, during the morning shift. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_08456920e5af2956_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.55, 0.44, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows clock skew of 800ms across replicas. Context: across all regions, immediately after go-live. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6873d2081505ef72_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.59, 0.34, 0.06, 0.01], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during normal operations. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_def972e268d20ccb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.12, 0.18, 0.57, 0.13, 0.0], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: in production only, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_35809d69147bb034_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.6, 0.39, 0.0], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: over the last hour, with staffing at reduced levels. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ba7378867f32f758_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.15, 0.8, 0.02, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the quarterly review. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5b5f7f02e116823c_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: across all regions, following a recent audit. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_01ca1a3891187f21_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.07, 0.42, 0.48, 0.03], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: during the batch window, while on-call rotation changed. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_76b9aa21e53b6b67_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: over the last hour, with a new vendor onboarded. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_37b77ed14c3ac6cc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.67, 0.32, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: across all regions, while on-call rotation changed. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_705ec9a7d02ee5ab_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.12, 0.5, 0.37, 0.01, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: during the batch window, during a scheduled maintenance window. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c4f2d21e5c9a9086_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.03, 0.14, 0.62, 0.2, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: in production only, shortly after a software update. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_54fa6598301360c7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.07, 0.12, 0.45, 0.34, 0.02], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally matches last Tuesday's incident signature. Context: over the last hour, during a scheduled maintenance window. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fe786f31cdc86e52_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.86, 0.12], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during an external partner integration. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7f7f4d11d4dc8bee_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.27, 0.71, 0.01], "state": "The log shipper reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: during the batch window, under an active deadline. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_baee2cba13535c6f_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, while on-call rotation changed. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_55b8102604cb0612_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.21, 0.01, 0.18, 0.6], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: across all regions, during the morning shift. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0f6b7cca0e439c2c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.53, 0.44, 0.02, 0.01], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: across all regions, during the quarterly review. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e5537aeb17739c05_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.42, 0.56, 0.01], "state": "The metrics pipeline flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: in production only, at the end of the fiscal period. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7bde691cefeedcf1_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "The log shipper shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: across all regions, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9d6fda594fc58b03_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.64, 0.15, 0.03, 0.18], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_88c3e6db5bc225ed_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: in production only, as part of a compliance sweep. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a9f04fc7714a9d75_n", "kind": "noul", "options": ["false", "true"], "target": [0.58, 0.42], "state": "The log shipper correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: across all regions, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_16e736628ba9a108_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.98, 0.0, 0.0, 0.02], "state": "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.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_589bd0bdedb33318_n", "kind": "noul", "options": ["false", "true"], "target": [0.9, 0.1], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: across all regions, under an active deadline. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9ee4337e34322b9b_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, with a new vendor onboarded. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_082781777b5ddd99_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.18, 0.79, 0.02, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: over the last hour, during peak load. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d5455356765de767_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.12, 0.16, 0.69, 0.03], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: during the batch window, mid-incident. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1be9baac9f657dc9_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.31, 0.62, 0.06, 0.01], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: during the batch window, following a recent audit. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b5b3d7710aa6ad81_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.46, 0.48, 0.04, 0.02], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: across all regions, during normal operations. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6cf4229cc0ad81df_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.11, 0.84, 0.05], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: across all regions, during the system migration. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a41c11967d7e7ce0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.37, 0.61, 0.01], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: over the last hour, while legacy systems are still active. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3053364cf37a1a7b_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: during the batch window, immediately after go-live. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ff697dca850bf64c_n", "kind": "noul", "options": ["false", "true"], "target": [0.37, 0.63], "state": "The log shipper flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: over the last hour, following a recent audit. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7ee79485d64c1165_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.6, 0.39, 0.0], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: over the last hour, shortly after a software update. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eb6f53ddae7e4004_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.08, 0.81, 0.11, 0.0], "state": "The metrics pipeline 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 supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_674a06c2ce038dac_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during a scheduled maintenance window. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a6d4811b61d9839e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.95, 0.04, 0.0, 0.01], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: across all regions, with staffing at reduced levels. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_64ee4969bf48651c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.21, 0.54, 0.25, 0.0, 0.0], "state": "Service catalog-sync shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: across all regions, with a new vendor onboarded. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_572ce95f6864df8b_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "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, while legacy systems are still active. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3c01467228a86e07_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: over the last hour, while on-call rotation changed. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d9612a4b0af2378d_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "The metrics pipeline shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: in production only, with staffing at reduced levels. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2aebe535c0d5bae6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.12, 0.75, 0.12, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: over the last hour, during peak load. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_21a91fd7feb502ee_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.39, 0.51, 0.09, 0.01], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: during the batch window, during the morning shift. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a9f04fc7714a9d75_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.21, 0.67, 0.08, 0.0], "state": "The log shipper correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: across all regions, with staffing at reduced levels. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b0ee988fdcd0dd9e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.9, 0.07, 0.01, 0.02], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, mid-incident. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6fb51091ba7bbdc0_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.95, 0.03, 0.01, 0.01], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, while legacy systems are still active. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cb19060120bffb30_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.39, 0.23, 0.01, 0.37], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: in production only, with staffing at reduced levels. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4d382faaa3ba5900_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.96, 0.0, 0.0, 0.04], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during normal operations. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_18851c15000e8a45_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.94, 0.05, 0.0, 0.01], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: in production only, during the morning shift. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_23ee7b85cb1292aa_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.11, 0.79, 0.09, 0.0], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: during the batch window, during an external partner integration. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fb04c10f03d2a9e2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.25, 0.74, 0.01], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, while legacy systems are still active. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5b9cb0e480136646_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.35, 0.22, 0.01, 0.42], "state": "The metrics pipeline shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: over the last hour, at the end of the fiscal period. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c9de22acbee7c4dc_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.14, 0.36, 0.02, 0.48], "state": "Node pgsql-14 flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: in production only, immediately after go-live. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_02cb1be8aac19263_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.5, 0.33, 0.15, 0.0], "state": "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, during the holiday freeze. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ebb9bb4ea7be31bc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.3, 0.67, 0.02], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: in production only, immediately after go-live. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5e946035baf33d20_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.9, 0.06, 0.01, 0.03], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the holiday freeze. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8744e6e1270a2594_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the morning shift. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bbd0487aab7f6f49_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.59, 0.41, 0.0], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: during the batch window, during the system migration. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_64ce0de3a1e55b5b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.16, 0.56, 0.25, 0.02, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a0b04ca34efa6bd0_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "The log shipper returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: over the last hour, during the morning shift. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4c3189838fc327dc_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The metrics pipeline flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: in production only, during a scheduled maintenance window. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bc92d0c302846595_n", "kind": "noul", "options": ["false", "true"], "target": [0.44, 0.56], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: in production only, while legacy systems are still active. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4117b7e7a759d4a8_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.2, 0.5, 0.29, 0.01], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows clock skew of 800ms across replicas. Context: across all regions, under reduced staffing. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5219773b91ab11e3_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "The metrics pipeline lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: during the batch window, while on-call rotation changed. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_df16f73c93476cf2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.6, 0.4, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: in production only, with staffing at reduced levels. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_95a7c8a1230d242c_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "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.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca158537feeb0a85_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.56, 0.43, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: in production only, shortly after a software update. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_073b90b4c85288ae_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.88, 0.0, 0.11, 0.01], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during an external partner integration. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b6646de0624ade50_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: during the batch window, under an active deadline. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9341eab3032753f3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.73, 0.26, 0.0], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: during the batch window, during the morning shift. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2f6747ae1b83b3ed_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: during the batch window, mid-incident. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f37762b79a186be5_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.24, 0.03, 0.02, 0.71], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: in production only, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b6e603096ce8f68a_n", "kind": "noul", "options": ["false", "true"], "target": [0.72, 0.28], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: over the last hour, immediately after go-live. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d573cb528042634d_n", "kind": "noul", "options": ["false", "true"], "target": [0.39, 0.61], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: over the last hour, during a scheduled maintenance window. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_90bd84cb4688ba13_n", "kind": "noul", "options": ["false", "true"], "target": [0.68, 0.32], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: in production only, immediately after go-live. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2a63604f303b271f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.09, 0.47, 0.41, 0.01], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: in production only, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f0472f6f927b23db_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.64, 0.28, 0.07, 0.01], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: in production only, during the quarterly review. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b4e2c416f547c80e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.12, 0.82, 0.06], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: across all regions, mid-incident. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e3e3679d054cba97_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.0, 0.17, 0.83], "state": "The log shipper lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: across all regions, with a new vendor onboarded. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7e978c76f3b72f57_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.09, 0.8, 0.1, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally matches last Tuesday's incident signature. Context: during the batch window, with staffing at reduced levels. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_602824eff2608b92_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.34, 0.38, 0.27, 0.01], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, with staffing at reduced levels. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_52e912d5342d4c2d_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: over the last hour, during a scheduled maintenance window. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3da45301c58c42fa_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.5, 0.43, 0.07, 0.0], "state": "The metrics pipeline correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: over the last hour, under reduced staffing. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_02b09493066ade2d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.03, 0.37, 0.52, 0.08], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: across all regions, shortly after a software update. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9cf9e625a0af11a4_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "The log shipper shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: during the batch window, during the morning shift. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e7eabd7ebe0b1c6c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.41, 0.28, 0.29, 0.02], "state": "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, under an active deadline. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_79f82059fe1650c5_n", "kind": "noul", "options": ["false", "true"], "target": [0.89, 0.11], "state": "The log shipper shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: in production only, following a recent audit. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fae7c98b7af23f3f_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: across all regions, during the morning shift. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6421fa2479e9fe3a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.78, 0.19, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: across all regions, during an external partner integration. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_928dce781c980e91_n", "kind": "noul", "options": ["false", "true"], "target": [0.48, 0.52], "state": "The log shipper lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: during the batch window, during the holiday freeze. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_924f19e9c3bb8928_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.12, 0.86, 0.02], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during peak load. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_414491a38dcc8e82_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: across all regions, mid-incident. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dde1c5d822c29931_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "Service catalog-sync shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: across all regions, following a recent audit. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b755661e9924a290_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.13, 0.02, 0.14, 0.71], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: over the last hour, during the system migration. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_15ef3693a09d8090_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.03, 0.82, 0.15], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, under reduced staffing. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c480412abf78579a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.82, 0.17, 0.01, 0.0], "state": "The log shipper flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: across all regions, under reduced staffing. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_35e102fa1fc1cc2d_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "The log shipper shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: across all regions, shortly after a software update. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_574e439a4ef2018c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.1, 0.46, 0.42, 0.02, 0.0], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: across all regions, during the system migration. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a556272ae0245ef6_n", "kind": "noul", "options": ["false", "true"], "target": [0.39, 0.61], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: in production only, at the end of the fiscal period. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b66270a8773a47b_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "Node pgsql-14 flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: over the last hour, during the morning shift. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_68663830b170d3e6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.53, 0.43, 0.01], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: across all regions, mid-incident. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ec0f74236b5241f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.23, 0.7, 0.06, 0.01], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: over the last hour, following a recent audit. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_111d67ddf223d927_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.12, 0.35, 0.11, 0.42], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: across all regions, under an active deadline. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2b06737ffdd3d9ae_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, under reduced staffing. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0267bec9439c319a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.63, 0.35, 0.02, 0.0], "state": "The log shipper flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: in production only, at the end of the fiscal period. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bb268e16aa8345f6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.55, 0.44, 0.0], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: across all regions, as part of a compliance sweep. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e7c35e9ecc539b64_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.39, 0.42, 0.16, 0.01], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: across all regions, mid-incident. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6abdd07f3694153e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.48, 0.46, 0.03, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally shows a slow leak in heap growth. Context: across all regions, under an active deadline. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ade3aa4a1933fd0c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.23, 0.6, 0.12], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally shows a slow leak in heap growth. Context: during the batch window, under an active deadline. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_041f72d06d7bda47_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.23, 0.1, 0.1, 0.57], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: across all regions, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_08e6516a719b2cc4_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The log shipper shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: over the last hour, immediately after go-live. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1461b9acb39f212d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.38, 0.57, 0.05, 0.0], "state": "Node pgsql-14 flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: during the batch window, during the quarterly review. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_53d9e41d178b5151_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: over the last hour, following a recent audit. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f42c74d501ac94a9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.64, 0.32, 0.01, 0.03], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: across all regions, with staffing at reduced levels. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3dcfc9c612e22cea_n", "kind": "noul", "options": ["false", "true"], "target": [0.73, 0.27], "state": "The log shipper correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: across all regions, during normal operations. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_495296d44a858770_n", "kind": "noul", "options": ["false", "true"], "target": [0.61, 0.39], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: across all regions, immediately after go-live. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5954213ea658489c_n", "kind": "noul", "options": ["false", "true"], "target": [0.64, 0.36], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: across all regions, at the end of the fiscal period. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5037335403753775_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.05, 0.5, 0.44, 0.01, 0.0], "state": "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, with a new vendor onboarded. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4fee1d651251efd4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.14, 0.83, 0.03], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: across all regions, shortly after a software update. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ec196e3e40b9bf23_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.31, 0.47, 0.22, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: over the last hour, following a recent audit. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cce6e77b0ca1ddc9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.14, 0.8, 0.06], "state": "The log shipper reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: across all regions, immediately after go-live. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6791f4264ae7a939_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.27, 0.71, 0.02], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: across all regions, during the morning shift. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0df54c65d26d8aad_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.97, 0.01, 0.01, 0.01], "state": "The log shipper reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: over the last hour, under an active deadline. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_57a5c8d70a36cbf7_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.17, 0.14, 0.64], "state": "Node pgsql-14 matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: in production only, while legacy systems are still active. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7e7c81c30e21ace5_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.26, 0.01, 0.28, 0.45], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, during a scheduled maintenance window. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_caccf33282d85630_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.67, 0.3, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: across all regions, during an external partner integration. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bee02318a3c9a9f8_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.36, 0.02, 0.62], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: across all regions, shortly after a software update. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3257a5e958713b08_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.25, 0.74, 0.01], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, shortly after a software update. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3b6f5fbda4e73f15_n", "kind": "noul", "options": ["false", "true"], "target": [0.64, 0.36], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: during the batch window, during the morning shift. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d5586cc048399312_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.07, 0.65, 0.27, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: over the last hour, following a recent audit. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_726f03a40aadff78_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.06, 0.01, 0.09, 0.84], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: in production only, as part of a compliance sweep. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_91a83a210b68feaa_n", "kind": "noul", "options": ["false", "true"], "target": [0.91, 0.09], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, under an active deadline. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_20757a8833b86768_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.03, 0.36, 0.57, 0.03], "state": "The log shipper matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: across all regions, immediately after go-live. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_98763e2d62de8ffb_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.03, 0.49, 0.45], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: over the last hour, under reduced staffing. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_572ce95f6864df8b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.76, 0.24, 0.0], "state": "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, while legacy systems are still active. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6e7dcb7056a6809b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.74, 0.05, 0.01, 0.2], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: during the batch window, during peak load. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cd8ea6a5eb6c1279_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.2, 0.76, 0.04], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally flags a step-function change in error slope. Context: during the batch window, during normal operations. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a9986de765179e80_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: over the last hour, during an external partner integration. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2359a7003883c3ea_n", "kind": "noul", "options": ["false", "true"], "target": [0.43, 0.57], "state": "The log shipper matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: across all regions, following a recent audit. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_964ba3537197a273_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.45, 0.49, 0.05, 0.01], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, with a new vendor onboarded. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e075f121146bac62_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.02, 0.43, 0.52], "state": "The metrics pipeline lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: during the batch window, during normal operations. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_07812d4509d1fe25_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.21, 0.74, 0.05, 0.0], "state": "The log shipper shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: in production only, following a recent audit. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4cce35ce6e2fcbf5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.24, 0.74, 0.02], "state": "The log shipper correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, following a recent audit. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7e4faeaec0b8f83f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.62, 0.36, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: across all regions, following a recent audit. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e321896e5ce0ac32_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.29, 0.6, 0.1, 0.01], "state": "The metrics pipeline correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: over the last hour, during the quarterly review. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c8089628aeaff1a5_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.62, 0.11, 0.08, 0.19], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: in production only, during the morning shift. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ed53c2762bec0dcd_n", "kind": "noul", "options": ["false", "true"], "target": [0.74, 0.26], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: during the batch window, with a new vendor onboarded. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b2538a9e84cc9461_n", "kind": "noul", "options": ["false", "true"], "target": [0.71, 0.29], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: during the batch window, at the end of the fiscal period. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ee8b35a2aee97538_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.57, 0.43, 0.0], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: over the last hour, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cc62ecec6e2d026e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.08, 0.79, 0.12, 0.0], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: in production only, with staffing at reduced levels. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a29cef5f871c5827_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.25, 0.73, 0.02], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, as part of a compliance sweep. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b62c7d585a3696fc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.32, 0.67, 0.01], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, under reduced staffing. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ab601c1ac485840d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.67, 0.32, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the holiday freeze. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_72b9442266e34810_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The metrics pipeline flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: in production only, during the system migration. Reported by the operator.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aeff9321fa6647f9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.05, 0.55, 0.4, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: over the last hour, under an active deadline. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1d23983c7359b5f1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.52, 0.36, 0.08, 0.0], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, with staffing at reduced levels. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3257a5e958713b08_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "Node pgsql-14 flags a step-function change in error slope; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, shortly after a software update. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e8aafe32aa2fbbc0_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: over the last hour, during a scheduled maintenance window. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_25ef2a266529d4d1_n", "kind": "noul", "options": ["false", "true"], "target": [0.65, 0.35], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows a slow leak in heap growth. Context: over the last hour, during the system migration. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2390665307c1e28e_n", "kind": "noul", "options": ["false", "true"], "target": [0.38, 0.62], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: in production only, during the quarterly review. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e638212cd6faff73_n", "kind": "noul", "options": ["false", "true"], "target": [0.43, 0.57], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: across all regions, as part of a compliance sweep. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_77acdec4c70fcacd_n", "kind": "noul", "options": ["false", "true"], "target": [0.49, 0.51], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: in production only, at the end of the fiscal period. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_76cc7fbd28affc4e_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: in production only, during the morning shift. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4a939a33ff19ebc4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.03, 0.36, 0.59, 0.01], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally matches last Tuesday's incident signature. Context: in production only, under reduced staffing. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_41bf928ec411bf61_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.18, 0.79, 0.03], "state": "The log shipper matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: during the batch window, mid-incident. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3b4437b87cdbe174_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "The log shipper shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the morning shift. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_64deb0aff0f283f2_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.84, 0.0, 0.13, 0.03], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during the quarterly review. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b3f19600df86d460_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, following a recent audit. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0045a4bca93cf802_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.15, 0.62, 0.06, 0.17], "state": "The metrics pipeline flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: in production only, mid-incident. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aa09988c9f95d0d6_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.7, 0.21, 0.01, 0.08], "state": "The log shipper shows a slow leak in heap growth; additionally shows a 22% drop in request rate with no deploys. Context: in production only, with staffing at reduced levels. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3acf5baf3e23037b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.33, 0.66, 0.01], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: in production only, while on-call rotation changed. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9cfb4f84f058c79b_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.15, 0.14, 0.47, 0.24], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during an external partner integration. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2aeea829b43dd105_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The log shipper returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: across all regions, with staffing at reduced levels. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1a29f885c3d05831_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: in production only, shortly after a software update. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_638e7fdb5248749f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.02, 0.32, 0.65], "state": "The log shipper reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: over the last hour, mid-incident. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0692e887285ef586_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.94, 0.0, 0.06, 0.0], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: in production only, during an external partner integration. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_330f5c4ba29fab8b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.25, 0.64, 0.1, 0.01], "state": "The log shipper shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: over the last hour, during the morning shift. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8affdcef31adcce8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.15, 0.83, 0.02], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: in production only, during the quarterly review. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8d07db9868f04269_n", "kind": "noul", "options": ["false", "true"], "target": [0.36, 0.64], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: over the last hour, during an external partner integration. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_020d5bb9d171472c_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "The log shipper shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: during the batch window, during the system migration. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d25dd9b6cd657aaa_n", "kind": "noul", "options": ["false", "true"], "target": [0.41, 0.59], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: across all regions, during the holiday freeze. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eb6f53ddae7e4004_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.68, 0.28, 0.01, 0.0], "state": "The metrics pipeline 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 supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a6e103bb450f7d5d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.25, 0.61, 0.08, 0.0], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: across all regions, under reduced staffing. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ee30c52a1ded9efc_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.05, 0.7, 0.25, 0.0], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally shows a slow leak in heap growth. Context: over the last hour, at the end of the fiscal period. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a744cd6437e7c82f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.09, 0.01, 0.04, 0.86], "state": "The log shipper shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: during the batch window, while on-call rotation changed. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fd6d27eae7c8c374_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.28, 0.06, 0.03, 0.63], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: in production only, as part of a compliance sweep. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_de3856d8a7d7af71_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.46, 0.53, 0.0], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: in production only, under reduced staffing. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b1bde925828e7967_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.32, 0.65, 0.02], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally reports empty scrape targets after the network change. Context: during the batch window, mid-incident. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f174c7163b0a91f6_n", "kind": "noul", "options": ["false", "true"], "target": [0.53, 0.47], "state": "The log shipper reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: over the last hour, during the morning shift. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5ab9935e50701bc1_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.07, 0.45, 0.47, 0.01], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: over the last hour, with a new vendor onboarded. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fb802cf7dc288858_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.0, 0.18, 0.81], "state": "The log shipper lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: across all regions, during the system migration. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8efea7cd78da752b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.47, 0.51, 0.01], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the morning shift. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_94eb784ba3ff68d0_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.45, 0.53, 0.01], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: over the last hour, under an active deadline. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5b76cb8697cff7ab_n", "kind": "noul", "options": ["false", "true"], "target": [0.4, 0.6], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: in production only, during the system migration. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8d17287b2f3d1eab_n", "kind": "noul", "options": ["false", "true"], "target": [0.77, 0.23], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, at the end of the fiscal period. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c96e41496d30b863_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.45, 0.5, 0.04, 0.01], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: in production only, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_63428c3ec7f0e31c_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: across all regions, during peak load. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_702f3250ea0e0cea_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.98, 0.01, 0.0, 0.01], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: in production only, under an active deadline. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8d0ab85e9cbcb251_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.14, 0.78, 0.08], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: across all regions, immediately after go-live. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9578e242693a8cce_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.01, 0.42, 0.56], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: in production only, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9bfee9027cafea34_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: across all regions, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0d070a256e0006ae_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: during the batch window, during the holiday freeze. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ae8204ec1186e041_n", "kind": "noul", "options": ["false", "true"], "target": [0.48, 0.52], "state": "The log shipper matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: over the last hour, during the morning shift. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e7c35e9ecc539b64_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.27, 0.11, 0.01, 0.61], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: across all regions, mid-incident. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1cf12e67961973be_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.68, 0.3, 0.01, 0.01], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: across all regions, with staffing at reduced levels. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9592d32f8fccfaa8_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.39, 0.5, 0.1, 0.01], "state": "Service catalog-sync 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 automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3d71a0710ce451e2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.04, 0.71, 0.25, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: during the batch window, following a recent audit. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d94eb0cdc616e78b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.27, 0.7, 0.03], "state": "Service catalog-sync flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: across all regions, mid-incident. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3188e8874bce1a97_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: across all regions, under an active deadline. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e7cd76bf37d59c5b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.04, 0.54, 0.39, 0.01], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: across all regions, as part of a compliance sweep. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_59df05b7ff77a1e8_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "The log shipper reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: in production only, during a scheduled maintenance window. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d4c7ed56f730f470_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.4, 0.29, 0.13, 0.18], "state": "Node pgsql-14 flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: during the batch window, during a scheduled maintenance window. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_60503f528a15925f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.0, 0.02, 0.45, 0.51, 0.01], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: during the batch window, following a recent audit. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fa9c53349b78f486_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.91, 0.04, 0.04, 0.01], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: over the last hour, under an active deadline. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9f76bbbc933d1976_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.97, 0.0, 0.03], "state": "The log shipper matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: over the last hour, shortly after a software update. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7552b7490170f092_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.45, 0.5, 0.05, 0.0], "state": "Service catalog-sync correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: across all regions, while on-call rotation changed. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_59c2a47c4ac0dacc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.19, 0.53, 0.24, 0.01], "state": "Service catalog-sync 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 review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b370d7b306469c20_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.68, 0.0, 0.1, 0.22], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: in production only, during an external partner integration. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d0eaff04e4823fc8_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.03, 0.85, 0.1], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally correlates with the vendor status page incident. Context: over the last hour, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_44c05e04063a447b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.26, 0.73, 0.01], "state": "The log shipper flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, with staffing at reduced levels. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5e69a82c6a192a1a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.12, 0.58, 0.3, 0.0, 0.0], "state": "The metrics pipeline flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: over the last hour, while legacy systems are still active. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8254f30160749ee9_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: during the batch window, with a new vendor onboarded. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_23251dca2b44da43_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.05, 0.73, 0.21, 0.0], "state": "The log shipper matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: in production only, as part of a compliance sweep. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d130979aee19c171_n", "kind": "noul", "options": ["false", "true"], "target": [0.52, 0.48], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: over the last hour, with staffing at reduced levels. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_726f03a40aadff78_n", "kind": "noul", "options": ["false", "true"], "target": [0.43, 0.57], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: in production only, as part of a compliance sweep. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d9e74ceba11e7d0c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.59, 0.4, 0.0], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: across all regions, during the quarterly review. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_89145242e68e8fb6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.2222, 0.5657, 0.1616, 0.0505, 0.0, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, while on-call rotation changed. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_812c5d6a46b04e31_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.32, 0.66, 0.01], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally flags a step-function change in error slope. Context: during the batch window, under an active deadline. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ef5a129d99ba731b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.13, 0.82, 0.05], "state": "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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e69b00e4c5dec16a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.37, 0.08, 0.03, 0.52], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: during the batch window, as part of a compliance sweep. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_af70750de597baa3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.05, 0.89, 0.06, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: during the batch window, while on-call rotation changed. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0267bec9439c319a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.36, 0.63, 0.01], "state": "The log shipper flags a step-function change in error slope; additionally lost 4 minutes of trace data. Context: in production only, at the end of the fiscal period. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a57cfce0db3b0427_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.09, 0.61, 0.29, 0.01], "state": "Node pgsql-14 returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: in production only, during an external partner integration. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e0157b39cf4a9495_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: across all regions, under reduced staffing. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2989f48a4e8b00a4_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally reports empty scrape targets after the network change. Context: during the batch window, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_522576dc9328401c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.67, 0.32, 0.01, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: over the last hour, while on-call rotation changed. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b00f916d4a2665b4_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.13, 0.62, 0.24, 0.01], "state": "The metrics pipeline returned to baseline after 11 minutes; 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.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f199f6c665ae999d_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.11, 0.57, 0.31, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: in production only, immediately after go-live. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a8e9686b9604d1b9_n", "kind": "noul", "options": ["false", "true"], "target": [0.55, 0.45], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally returned to baseline after 11 minutes. Context: across all regions, during the quarterly review. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3be979b46f40c800_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.49, 0.5, 0.0], "state": "The log shipper reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: over the last hour, with staffing at reduced levels. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d9b1b40b971901ab_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The log shipper shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: in production only, mid-incident. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_382ea4987732ecb7_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "The metrics pipeline correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: across all regions, during an external partner integration. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b676f78d523d53d7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.02, 0.13, 0.1, 0.56, 0.18, 0.01], "state": "The log shipper matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: during the batch window, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b4aaf3f418057758_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.95, 0.03, 0.0, 0.02], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during the holiday freeze. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fcbfde8cc9d3ed1e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.79, 0.18, 0.02, 0.01], "state": "The log shipper correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, while on-call rotation changed. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4c364664222fa489_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.48, 0.51, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: across all regions, with a new vendor onboarded. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_222f73525a210641_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.66, 0.29, 0.03, 0.02], "state": "The log shipper lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: over the last hour, mid-incident. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b08fc882d4e3a646_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.06, 0.67, 0.25, 0.02, 0.0], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, while legacy systems are still active. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8884f7eabea204de_n", "kind": "noul", "options": ["false", "true"], "target": [0.57, 0.43], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: across all regions, during normal operations. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_75e75101abce3e10_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.07, 0.8, 0.13, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: during the batch window, while on-call rotation changed. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ca1c9712099a15f0_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.04, 0.52, 0.41, 0.03], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: during the batch window, shortly after a software update. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cb4f7665497fea7f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.13, 0.75, 0.11], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, as part of a compliance sweep. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_43a1cc2f96063ea9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.02, 0.41, 0.37, 0.19, 0.01, 0.0], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, as part of a compliance sweep. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0ec61f330e1a97f3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.29, 0.7, 0.01], "state": "The metrics pipeline correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: in production only, with a new vendor onboarded. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eaef7a4eac24b05b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.37, 0.62, 0.01], "state": "The log shipper correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: in production only, during peak load. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_12e4781122b634e7_n", "kind": "noul", "options": ["false", "true"], "target": [0.22, 0.78], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: across all regions, mid-incident. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_97f7e13f477c367e_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "The metrics pipeline flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: across all regions, shortly after a software update. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4a46b6016deb8b3b_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "The log shipper returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: during the batch window, at the end of the fiscal period. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9fd01f76ec84cf3c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.1, 0.63, 0.21, 0.06, 0.0], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, as part of a compliance sweep. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3f942772df45ce87_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.08, 0.76, 0.14, 0.02], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: across all regions, with a new vendor onboarded. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a945a11450ca4edf_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.4, 0.56, 0.02], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: over the last hour, during normal operations. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cb0d4d3da55cb5c4_n", "kind": "noul", "options": ["false", "true"], "target": [0.24, 0.76], "state": "The metrics pipeline lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: over the last hour, under an active deadline. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dd41e431a4723440_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.35, 0.01, 0.25, 0.39], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the system migration. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9fb4c447d2786c27_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.37, 0.59, 0.01, 0.0], "state": "The metrics pipeline shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: over the last hour, shortly after a software update. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c0a45cdb89379103_n", "kind": "noul", "options": ["false", "true"], "target": [0.83, 0.17], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: across all regions, while on-call rotation changed. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_055e1a0cf92a7d2b_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.93, 0.07, 0.0, 0.0], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: in production only, with staffing at reduced levels. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5ffe803a29767ed2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.39, 0.51, 0.1, 0.0, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: over the last hour, during normal operations. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9fd01f76ec84cf3c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.19, 0.55, 0.24, 0.02], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, as part of a compliance sweep. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f20c931e3b0c4eff_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.12, 0.85, 0.03], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, shortly after a software update. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_58b4747db20229df_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.06, 0.12, 0.54, 0.26, 0.01], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: in production only, during the system migration. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4fcc40cbf1d9ca28_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.17, 0.79, 0.03, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: during the batch window, during an external partner integration. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c2227aeade41dedc_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.52, 0.48, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: during the batch window, during an external partner integration. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_602824eff2608b92_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, with staffing at reduced levels. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_512814574df99005_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.11, 0.86, 0.03], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: across all regions, with staffing at reduced levels. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9b3dc593e72a6352_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.26, 0.7, 0.04], "state": "The log shipper shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: in production only, mid-incident. Reported by the on-call engineer.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_66e5292b9f0c123a_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "The log shipper lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: across all regions, with a new vendor onboarded. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f37927b79739b925_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.31, 0.0, 0.09, 0.6], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: during the batch window, with staffing at reduced levels. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a9945a26ed7de519_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.81, 0.17, 0.01, 0.01], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, at the end of the fiscal period. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e9d3efd3420b6b92_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: over the last hour, while legacy systems are still active. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_de90092fcc6136a3_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: in production only, during peak load. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_246297b575a73e5b_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "The metrics pipeline shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during the system migration. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aec98a3a9e3f1f1f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.25, 0.71, 0.03], "state": "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.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7d30c93dec6b73cb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.07, 0.28, 0.61, 0.04, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally shows clock skew of 800ms across replicas. Context: over the last hour, mid-incident. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0383cc86b4f6dda9_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.06, 0.01, 0.64, 0.29], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows clock skew of 800ms across replicas. Context: during the batch window, while legacy systems are still active. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6efbe7753cc413fc_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.36, 0.5, 0.14, 0.0], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, while legacy systems are still active. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d5772b840b4ab866_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.11, 0.86, 0.03], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: over the last hour, while on-call rotation changed. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8fa997048398aa91_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.63, 0.35, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: across all regions, during the holiday freeze. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_85b4a7de55c6bae8_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.7, 0.27, 0.0], "state": "Service catalog-sync correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: over the last hour, under reduced staffing. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1e3e5ce32a74a23c_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.85, 0.1, 0.02, 0.03], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during the quarterly review. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aad0eb13de87d49a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.65, 0.3, 0.0], "state": "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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_12bc36631f4bb638_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.7, 0.22, 0.07, 0.01], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: over the last hour, shortly after a software update. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_af70750de597baa3_n", "kind": "noul", "options": ["false", "true"], "target": [0.39, 0.61], "state": "The log shipper lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: during the batch window, while on-call rotation changed. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_04b9059eddd942ca_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, under an active deadline. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a6e103bb450f7d5d_n", "kind": "noul", "options": ["false", "true"], "target": [0.43, 0.57], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: across all regions, under reduced staffing. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_77e60a417a4a2d0a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.56, 0.38, 0.01], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: in production only, during normal operations. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_71a34ce33fa3288a_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.2323, 0.5556, 0.202, 0.0101], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: during the batch window, during the system migration. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fd028d56fb7f09dd_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "The log shipper matches last Tuesday's incident signature; additionally reports cardinality explosion in the metrics store. Context: across all regions, under reduced staffing. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e41ece981bb0294d_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.58, 0.28, 0.13, 0.01], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: over the last hour, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_495764ea71f54e80_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: over the last hour, immediately after go-live. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b77c3ff272871e88_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.78, 0.19, 0.0], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: across all regions, at the end of the fiscal period. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_20969bf86f8537fc_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.37, 0.53, 0.1, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: during the batch window, during an external partner integration. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fb802cf7dc288858_n", "kind": "noul", "options": ["false", "true"], "target": [0.54, 0.46], "state": "The log shipper lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: across all regions, during the system migration. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7b817a7b2b5b43bc_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.34, 0.02, 0.15, 0.49], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: over the last hour, with staffing at reduced levels. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_cb09c555c844d984_n", "kind": "noul", "options": ["false", "true"], "target": [0.31, 0.69], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, immediately after go-live. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ad5a7826a9ad5645_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.82, 0.16, 0.01, 0.01], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: over the last hour, with staffing at reduced levels. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fcf51493fa10bfbb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.54, 0.44, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: during the batch window, while legacy systems are still active. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_74e48815b9763eb5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.08, 0.75, 0.16, 0.0], "state": "The log shipper matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: over the last hour, at the end of the fiscal period. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6cf4229cc0ad81df_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: across all regions, during the system migration. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d06c94469d5ef1e8_n", "kind": "noul", "options": ["false", "true"], "target": [0.58, 0.42], "state": "The log shipper returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during peak load. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3c01467228a86e07_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.09, 0.38, 0.21, 0.32], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: over the last hour, while on-call rotation changed. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_13144f828cc41e78_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.65, 0.34, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during peak load. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_53e99d6b0d57041f_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: in production only, following a recent audit. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_704f4a5275720b2f_n", "kind": "noul", "options": ["false", "true"], "target": [0.2, 0.8], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally matches last Tuesday's incident signature. Context: in production only, while legacy systems are still active. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_569cecf3eb6d7fd1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.0, 0.43, 0.56], "state": "The log shipper correlates with the vendor status page incident; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during the quarterly review. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_155a9a01e72a50b9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.03, 0.44, 0.52, 0.01], "state": "The log shipper matches last Tuesday's incident signature; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during a scheduled maintenance window. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f1d87591c1b90962_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally flags a step-function change in error slope. Context: across all regions, during the system migration. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1b76625ca98d7956_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.4, 0.46, 0.02, 0.12], "state": "Service catalog-sync shows a slow leak in heap growth; additionally shows cache hit rate steady at 99.2%. Context: over the last hour, during the holiday freeze. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_164eea183b0fbbef_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during the morning shift. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1cb8e128731420f4_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.93, 0.05, 0.02, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: over the last hour, with staffing at reduced levels. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7663c6bf41f0d559_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.22, 0.76, 0.02], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally matches last Tuesday's incident signature. Context: during the batch window, during the system migration. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0cebf13cfcf4e49d_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "Service catalog-sync correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: across all regions, during the morning shift. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_739b3abc81682118_n", "kind": "noul", "options": ["false", "true"], "target": [0.88, 0.12], "state": "The metrics pipeline shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, mid-incident. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5a491e04822d7dce_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.97, 0.0, 0.0, 0.03], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally lost 4 minutes of trace data. Context: over the last hour, under reduced staffing. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_73e8f2c7f6e13828_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.14, 0.81, 0.05], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: across all regions, mid-incident. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7bb8e1fcdca1c354_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.26, 0.56, 0.15, 0.03], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: in production only, during a scheduled maintenance window. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_da464cff8aa41c4a_n", "kind": "noul", "options": ["false", "true"], "target": [0.69, 0.31], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: across all regions, with a new vendor onboarded. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f42d2e2f3c2fad01_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.73, 0.22, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the system migration. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ade11d20613f9f34_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.35, 0.64, 0.01], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, while legacy systems are still active. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a068a3e8abd279b5_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.3, 0.32, 0.34, 0.04], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally correlates with the vendor status page incident. Context: over the last hour, under reduced staffing. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_23754b46a24529a9_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: across all regions, during the quarterly review. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9c49de523bb303a3_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.98, 0.02, 0.0, 0.0], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally flags a step-function change in error slope. Context: over the last hour, mid-incident. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ec2d33037ec03cdf_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.09, 0.86, 0.05], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, immediately after go-live. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c83bfa4f23bdafa6_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "The log shipper shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: during the batch window, during the morning shift. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fae7c98b7af23f3f_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.5, 0.48, 0.01, 0.01], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: across all regions, during the morning shift. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_eb150f1628564ea9_n", "kind": "noul", "options": ["false", "true"], "target": [0.59, 0.41], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: across all regions, while on-call rotation changed. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_948026183c6b5ba3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.7, 0.28, 0.0], "state": "Service catalog-sync lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: across all regions, with a new vendor onboarded. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f1042f6841ea4699_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.06, 0.83, 0.11], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally matches last Tuesday's incident signature. Context: over the last hour, during peak load. Reported by the operator.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c4ccfb6b0d5ce71c_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.04, 0.0, 0.31, 0.65], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally reports empty scrape targets after the network change. Context: over the last hour, at the end of the fiscal period. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0c859824557cfda2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.46, 0.52, 0.01], "state": "Service catalog-sync flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: during the batch window, during the system migration. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5ad9ba3b567d3a5f_n", "kind": "noul", "options": ["false", "true"], "target": [0.61, 0.39], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: during the batch window, at the end of the fiscal period. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_66072434eceeaf09_n", "kind": "noul", "options": ["false", "true"], "target": [0.62, 0.38], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, while on-call rotation changed. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_76c8886f02ccf218_n", "kind": "noul", "options": ["false", "true"], "target": [0.42, 0.58], "state": "The log shipper lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: during the batch window, as part of a compliance sweep. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2b137f3aa877f9ff_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.64, 0.34, 0.02, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: in production only, during an external partner integration. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b54d93b3f6d29f4b_n", "kind": "noul", "options": ["false", "true"], "target": [0.71, 0.29], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: over the last hour, at the end of the fiscal period. Reported by the operator.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5106d0b9782340ac_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.1, 0.66, 0.18, 0.06], "state": "Service catalog-sync lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: across all regions, during normal operations. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_585afcaa3f6fd825_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.38, 0.6, 0.01], "state": "Service catalog-sync flags a step-function change in error slope; additionally reports cardinality explosion in the metrics store. Context: in production only, following a recent audit. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1d94de517452a4a3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.02, 0.12, 0.32, 0.49, 0.05, 0.0], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally matches last Tuesday's incident signature. Context: over the last hour, during normal operations. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8eabafb20ab993ac_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.09, 0.49, 0.37, 0.05, 0.0], "state": "Service catalog-sync flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: in production only, mid-incident. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ad82484389d26794_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.02, 0.38, 0.59], "state": "The log shipper reports empty scrape targets after the network change; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, while on-call rotation changed. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3df20839b079da87_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.42, 0.55, 0.02, 0.01], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally lost 4 minutes of trace data. Context: across all regions, during the quarterly review. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_038ae8f8c83a3da7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.49, 0.37, 0.13, 0.0], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: in production only, while legacy systems are still active. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_842eb6c144fc5785_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.52, 0.43, 0.02, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: during the batch window, during the system migration. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4191f7719a18a041_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.01, 0.78, 0.21], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: over the last hour, while on-call rotation changed. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_db4bb4b7ff883eb8_n", "kind": "noul", "options": ["false", "true"], "target": [0.43, 0.57], "state": "The log shipper flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: in production only, during the morning shift. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d08ec3c762c7ae95_n", "kind": "noul", "options": ["false", "true"], "target": [0.91, 0.09], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally correlates with the vendor status page incident. Context: over the last hour, during normal operations. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b4c095a048c4a176_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.0, 0.03, 0.94, 0.03], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: during the batch window, while on-call rotation changed. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ee496d54df12764a_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The metrics pipeline correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: in production only, during the system migration. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9854ace1f6a77c20_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during the quarterly review. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2f5540b961126783_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.6, 0.4, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: during the batch window, at the end of the fiscal period. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f6c88f9551f0205b_n", "kind": "noul", "options": ["false", "true"], "target": [0.3, 0.7], "state": "The log shipper lost 4 minutes of trace data; additionally reports empty scrape targets after the network change. Context: during the batch window, during the holiday freeze. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d105d2157f67a8ec_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.54, 0.44, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: over the last hour, at the end of the fiscal period. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_48e03a68bc1d9ba6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.11, 0.49, 0.37, 0.03, 0.0], "state": "The metrics pipeline lost 4 minutes of trace data; additionally returned to baseline after 11 minutes. Context: in production only, immediately after go-live. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_16da5341d8244d31_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: during the batch window, under an active deadline. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2320f5aecd351132_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.29, 0.01, 0.36, 0.34], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally shows a 22% drop in request rate with no deploys. Context: in production only, with a new vendor onboarded. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8744e6e1270a2594_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.5, 0.48, 0.01], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during the morning shift. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fe22a988c32c2f82_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.02, 0.6, 0.38, 0.0], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally shows a slow leak in heap growth. Context: during the batch window, during the holiday freeze. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0d070a256e0006ae_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.72, 0.27, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: during the batch window, during the holiday freeze. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e95ec390dfc96a85_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.18, 0.1, 0.06, 0.66], "state": "The log shipper shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: in production only, mid-incident. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_36232c7517c2d7a7_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally flags a step-function change in error slope. Context: over the last hour, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e79885baf80439d4_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.16, 0.72, 0.1, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: in production only, during the morning shift. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_025f00cdf95d94c1_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.18, 0.68, 0.13, 0.0], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, during the system migration. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4b901bd4111c39a6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.73, 0.26, 0.0], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: during the batch window, at the end of the fiscal period. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0cd957283bca381a_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.0, 0.02, 0.93, 0.05], "state": "Dashboard checkout-funnel returned to baseline after 11 minutes; additionally correlates with the vendor status page incident. Context: in production only, following a recent audit. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b0310969d677d5b2_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.06, 0.85, 0.09], "state": "Dashboard checkout-funnel shows disk at 91% and climbing 1%/hour; additionally shows a slow leak in heap growth. Context: in production only, immediately after go-live. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_aaaf68cecbab1d7f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.05, 0.47, 0.45, 0.02], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally correlates with the vendor status page incident. Context: across all regions, as part of a compliance sweep. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_db6ae811deaae4ef_n", "kind": "noul", "options": ["false", "true"], "target": [0.27, 0.73], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, with staffing at reduced levels. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_16979c66622f2388_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.9, 0.08, 0.01, 0.01], "state": "The log shipper reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, following a recent audit. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_23647b7df91cd92e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.03, 0.12, 0.73, 0.12], "state": "The metrics pipeline correlates with the vendor status page incident; additionally flags a step-function change in error slope. Context: over the last hour, during the quarterly review. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c2af400c0ab39ff3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.19, 0.67, 0.1, 0.0], "state": "The log shipper returned to baseline after 11 minutes; additionally shows a 22% drop in request rate with no deploys. Context: across all regions, with staffing at reduced levels. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6eb9dba9ab856ff6_n", "kind": "noul", "options": ["false", "true"], "target": [0.45, 0.55], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally flags a step-function change in error slope. Context: across all regions, during an external partner integration. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a107add0ac8184a2_n", "kind": "noul", "options": ["false", "true"], "target": [0.81, 0.19], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally flags a step-function change in error slope. Context: in production only, immediately after go-live. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_54f722affb882e3b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.21, 0.78, 0.01], "state": "Node pgsql-14 reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, at the end of the fiscal period. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f8bf498c61543029_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.64, 0.31, 0.04, 0.01], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally reports empty scrape targets after the network change. Context: over the last hour, as part of a compliance sweep. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a4bf61beafe39a67_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.71, 0.27, 0.01, 0.01], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, during peak load. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3d6e20396755e444_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.06, 0.86, 0.07, 0.0], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: during the batch window, while on-call rotation changed. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c44bf3123b7c5a41_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: in production only, mid-incident. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_2dc8704e2a26c3de_n", "kind": "noul", "options": ["false", "true"], "target": [0.75, 0.25], "state": "The metrics pipeline matches last Tuesday's incident signature; additionally lost 4 minutes of trace data. Context: across all regions, shortly after a software update. Reported by the on-call engineer.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d12cea274bfd49a9_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.08, 0.64, 0.25, 0.02, 0.0], "state": "Dashboard checkout-funnel shows cache hit rate steady at 99.2%; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the morning shift. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6522af16a7f4eb1d_n", "kind": "noul", "options": ["false", "true"], "target": [0.45, 0.55], "state": "Service catalog-sync reports empty scrape targets after the network change; additionally returned to baseline after 11 minutes. Context: over the last hour, immediately after go-live. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_216093cc0efc502f_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: in production only, following a recent audit. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_654786f006ac574a_n", "kind": "noul", "options": ["false", "true"], "target": [0.29, 0.71], "state": "Service catalog-sync shows a slow leak in heap growth; additionally lost 4 minutes of trace data. Context: across all regions, with staffing at reduced levels. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_29ee6e62a09b9992_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.76, 0.2, 0.03, 0.01], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during an external partner integration. Reported by the supervisor.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f93301907c97a5a7_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.03, 0.93, 0.02], "state": "The metrics pipeline flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: across all regions, under an active deadline. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_de55e33435b76019_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.02, 0.71, 0.27], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally correlates with the vendor status page incident. Context: in production only, under an active deadline. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0d070a256e0006ae_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.27, 0.58, 0.14, 0.01], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally shows a slow leak in heap growth. Context: during the batch window, during the holiday freeze. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9331bece1dc7261e_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: during the batch window, under reduced staffing. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f92522f6fe598b8e_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.07, 0.83, 0.09, 0.0], "state": "Service catalog-sync shows clock skew of 800ms across replicas; additionally flags a step-function change in error slope. Context: over the last hour, as part of a compliance sweep. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5e6c6f3e2379d60f_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.39, 0.59, 0.01], "state": "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.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ae143df6f62db002_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.46, 0.48, 0.05, 0.01], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: over the last hour, during an external partner integration. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3421a7950fef8905_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.54, 0.05, 0.02, 0.39], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: in production only, while on-call rotation changed. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_81950e3214baac62_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "Node pgsql-14 shows clock skew of 800ms across replicas; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, under an active deadline. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f50c34ff5582d036_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.22, 0.63, 0.13, 0.0], "state": "The log shipper reports cardinality explosion in the metrics store; additionally returned to baseline after 11 minutes. Context: during the batch window, during peak load. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_60cd925c448012ee_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.37, 0.61, 0.01], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: during the batch window, during the holiday freeze. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_efc8b82559ea5806_n", "kind": "noul", "options": ["false", "true"], "target": [0.28, 0.72], "state": "The log shipper shows disk at 91% and climbing 1%/hour; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during the system migration. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1411322a8f5a0b55_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: across all regions, mid-incident. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c39afb7c8182f63c_n", "kind": "noul", "options": ["false", "true"], "target": [0.34, 0.66], "state": "Node pgsql-14 lost 4 minutes of trace data; additionally reports cardinality explosion in the metrics store. Context: across all regions, during peak load. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e6f70824e113871d_n", "kind": "noul", "options": ["false", "true"], "target": [0.42, 0.58], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: across all regions, with a new vendor onboarded. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0e13e61579c0028e_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.71, 0.01, 0.02, 0.26], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows cache hit rate steady at 99.2%. Context: across all regions, under reduced staffing. Reported by the operator.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9ff804b41f5d7fa7_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.72, 0.24, 0.02, 0.02], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during an external partner integration. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8ec79f61de5e4b47_n", "kind": "noul", "options": ["false", "true"], "target": [0.68, 0.32], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: during the batch window, shortly after a software update. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_af946a1127ccc143_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.05, 0.86, 0.09, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during peak load. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d121442ff2aac3fc_n", "kind": "noul", "options": ["false", "true"], "target": [0.76, 0.24], "state": "Service catalog-sync correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: across all regions, during the system migration. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e9bef21b6ca42f7c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.37, 0.61, 0.01], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: during the batch window, shortly after a software update. Reported by the automated check.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a2d7c5bbdcaf2edb_n", "kind": "noul", "options": ["false", "true"], "target": [0.79, 0.21], "state": "Service catalog-sync reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: during the batch window, during an external partner integration. Reported by the supervisor.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bc0e7b44963e1ff1_n", "kind": "noul", "options": ["false", "true"], "target": [0.64, 0.36], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally flags a step-function change in error slope. Context: across all regions, while on-call rotation changed. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4ba14d8db16d29ae_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.86, 0.12, 0.01, 0.01], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally shows clock skew of 800ms across replicas. Context: across all regions, shortly after a software update. Reported by the review queue.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5e4cb06dbd8a7956_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.92, 0.0, 0.01, 0.07], "state": "Dashboard checkout-funnel shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, while on-call rotation changed. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f987cd45cab45131_n", "kind": "noul", "options": ["false", "true"], "target": [0.21, 0.79], "state": "The log shipper lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during a scheduled maintenance window. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_49bec1a0a15e0f83_n", "kind": "noul", "options": ["false", "true"], "target": [0.86, 0.14], "state": "Node pgsql-14 flags a step-function change in error slope; additionally correlates with the vendor status page incident. Context: in production only, during a scheduled maintenance window. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_41e667b383ea89bd_n", "kind": "noul", "options": ["false", "true"], "target": [0.5, 0.5], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: over the last hour, during a scheduled maintenance window. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6c73f330ad126ed5_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.5, 0.38, 0.11, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows cache hit rate steady at 99.2%. Context: in production only, during the holiday freeze. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f142b65e793e590b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.51, 0.48, 0.0], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows a slow leak in heap growth. Context: across all regions, during the quarterly review. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_149c47203de6a4a4_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally correlates with the vendor status page incident. Context: over the last hour, immediately after go-live. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_116e5b31ccbf4cb1_n", "kind": "noul", "options": ["false", "true"], "target": [0.39, 0.61], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally reports cardinality explosion in the metrics store. Context: across all regions, during normal operations. Reported by the review queue.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8d9e6df9300bb760_n", "kind": "noul", "options": ["false", "true"], "target": [0.32, 0.68], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: during the batch window, mid-incident. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e2d08655d2028dec_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.08, 0.01, 0.02, 0.89], "state": "The log shipper shows a 22% drop in request rate with no deploys; additionally lost 4 minutes of trace data. Context: in production only, mid-incident. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3efcf68eec5da020_n", "kind": "noul", "options": ["false", "true"], "target": [0.7, 0.3], "state": "The log shipper shows a slow leak in heap growth; additionally matches last Tuesday's incident signature. Context: across all regions, during peak load. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_79206a5fcf142ed7_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.01, 0.15, 0.26, 0.51, 0.07, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally correlates with the vendor status page incident. Context: across all regions, with staffing at reduced levels. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_88e99b3c5fa28cb6_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.67, 0.28, 0.0], "state": "Service catalog-sync shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: over the last hour, as part of a compliance sweep. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bbe480e6e4fb9f6f_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.82, 0.03, 0.04, 0.11], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally returned to baseline after 11 minutes. Context: over the last hour, during peak load. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3f77c507e7c6a664_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.16, 0.75, 0.07, 0.02, 0.0, 0.0], "state": "Node pgsql-14 shows cache hit rate steady at 99.2%; additionally returned to baseline after 11 minutes. Context: during the batch window, while legacy systems are still active. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_08ef56c0f80ef673_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.37, 0.62, 0.01], "state": "Node pgsql-14 reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: during the batch window, under reduced staffing. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f0ce468748a2527f_n", "kind": "noul", "options": ["false", "true"], "target": [0.2, 0.8], "state": "The metrics pipeline correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: during the batch window, mid-incident. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c480412abf78579a_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.18, 0.81, 0.01], "state": "The log shipper flags a step-function change in error slope; additionally matches last Tuesday's incident signature. Context: across all regions, under reduced staffing. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_6647ce193f53feda_n", "kind": "noul", "options": ["false", "true"], "target": [0.8, 0.2], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally returned to baseline after 11 minutes. Context: during the batch window, following a recent audit. Reported by the review queue.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_704b27b53243450b_n", "kind": "noul", "options": ["false", "true"], "target": [0.78, 0.22], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during a scheduled maintenance window. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_912be7e605d79c22_n", "kind": "noul", "options": ["false", "true"], "target": [0.85, 0.15], "state": "Node pgsql-14 shows disk at 91% and climbing 1%/hour; additionally returned to baseline after 11 minutes. Context: over the last hour, during an external partner integration. Reported by the automated check.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5eb6585f11572cda_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.01, 0.42, 0.52], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: across all regions, during the morning shift. Reported by the automated check.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_31930b4c6eb826fe_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.46, 0.53, 0.0], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally reports cardinality explosion in the metrics store. Context: in production only, with a new vendor onboarded. Reported by the automated check.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4ec76076b7e24645_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.03, 0.16, 0.55, 0.24, 0.02, 0.0], "state": "Service catalog-sync matches last Tuesday's incident signature; additionally shows cache hit rate steady at 99.2%. Context: across all regions, during normal operations. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_c26fd5e560a04499_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.01, 0.06, 0.29, 0.64], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally lost 4 minutes of trace data. Context: in production only, immediately after go-live. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b593e43e14c7af84_n", "kind": "noul", "options": ["false", "true"], "target": [0.33, 0.67], "state": "Dashboard checkout-funnel reports cardinality explosion in the metrics store; additionally matches last Tuesday's incident signature. Context: across all regions, during the system migration. Reported by the automated check.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3def9c518bb7fdc1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.46, 0.16, 0.03, 0.35], "state": "Dashboard checkout-funnel shows a slow leak in heap growth; additionally shows clock skew of 800ms across replicas. Context: across all regions, during the holiday freeze. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_224fa9977b916206_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.52, 0.15, 0.02, 0.31], "state": "The metrics pipeline reports cardinality explosion in the metrics store; additionally shows cache hit rate steady at 99.2%. Context: during the batch window, during a scheduled maintenance window. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3200b294ae89a7ba_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.33, 0.54, 0.13, 0.0, 0.0], "state": "The log shipper shows clock skew of 800ms across replicas; additionally returned to baseline after 11 minutes. Context: during the batch window, during normal operations. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_a3c2c989350e98be_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.82, 0.16, 0.01, 0.01], "state": "The metrics pipeline correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: during the batch window, under reduced staffing. Reported by the operator.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d98a984eaed56a47_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.67, 0.24, 0.07, 0.02], "state": "Service catalog-sync correlates with the vendor status page incident; additionally reports cardinality explosion in the metrics store. Context: across all regions, mid-incident. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_ea7a2594578937a9_n", "kind": "noul", "options": ["false", "true"], "target": [0.25, 0.75], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, shortly after a software update. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_9d75fd8975599d47_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.98, 0.02, 0.0, 0.0], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, shortly after a software update. Reported by the automated check.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f8ae9f172b3fe2cf_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.12, 0.21, 0.28, 0.39], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally flags a step-function change in error slope. Context: in production only, while legacy systems are still active. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bd8faeadb33166f2_n", "kind": "noul", "options": ["false", "true"], "target": [0.6, 0.4], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally reports cardinality explosion in the metrics store. Context: across all regions, with staffing at reduced levels. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7e4b4ec7e0bf102b_n", "kind": "noul", "options": ["false", "true"], "target": [0.87, 0.13], "state": "Dashboard checkout-funnel flags a step-function change in error slope; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during peak load. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0c619429577bda08_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.95, 0.0, 0.01, 0.04], "state": "Service catalog-sync shows disk at 91% and climbing 1%/hour; additionally shows clock skew of 800ms across replicas. Context: over the last hour, at the end of the fiscal period. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5db51a5cbb5c60fb_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.33, 0.64, 0.02], "state": "Dashboard checkout-funnel matches last Tuesday's incident signature; additionally shows clock skew of 800ms across replicas. Context: during the batch window, with a new vendor onboarded. Reported by the on-call engineer.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_fdcff6beec7cfcfe_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.04, 0.45, 0.49, 0.01], "state": "The metrics pipeline reports empty scrape targets after the network change; additionally matches last Tuesday's incident signature. Context: in production only, during the system migration. Reported by the review queue.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_4f17ce2244fabb97_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.32, 0.04, 0.02, 0.62], "state": "The log shipper reports cardinality explosion in the metrics store; additionally shows clock skew of 800ms across replicas. Context: over the last hour, at the end of the fiscal period. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_49cb1d19fa66a9a1_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.08, 0.03, 0.88, 0.01], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally shows a slow leak in heap growth. Context: over the last hour, during an external partner integration. Reported by the review queue.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_03d92c4362a0bfd0_n", "kind": "noul", "options": ["false", "true"], "target": [0.35, 0.65], "state": "Dashboard checkout-funnel shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: during the batch window, during the holiday freeze. Reported by the monitoring system.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_7d1add9a463ea921_n", "kind": "noul", "options": ["false", "true"], "target": [0.23, 0.77], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, under reduced staffing. Reported by the supervisor.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0968341171ac8bb3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.38, 0.61, 0.01], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, during the morning shift. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d21329268b5c61fe_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.15, 0.82, 0.03], "state": "The log shipper correlates with the vendor status page incident; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, during the quarterly review. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8a4d54f75f485657_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.43, 0.55, 0.01], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: in production only, during the morning shift. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_253dbcccfc42da32_n", "kind": "noul", "options": ["false", "true"], "target": [0.71, 0.29], "state": "The metrics pipeline lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: in production only, immediately after go-live. Reported by the automated check.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0b90be77501694dc_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.77, 0.0, 0.05, 0.18], "state": "Dashboard checkout-funnel lost 4 minutes of trace data; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, during an external partner integration. Reported by the monitoring system.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_26361aac64b070b9_n", "kind": "noul", "options": ["false", "true"], "target": [0.45, 0.55], "state": "The metrics pipeline shows clock skew of 800ms across replicas; additionally shows cache hit rate steady at 99.2%. Context: in production only, with a new vendor onboarded. Reported by the review queue.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_e73c2d000dbc2e33_n", "kind": "noul", "options": ["false", "true"], "target": [0.23, 0.77], "state": "The log shipper shows clock skew of 800ms across replicas; additionally reports empty scrape targets after the network change. Context: during the batch window, under an active deadline. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_37024efe4bc0be10_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.24, 0.58, 0.14, 0.0], "state": "The metrics pipeline correlates with the vendor status page incident; additionally returned to baseline after 11 minutes. Context: in production only, immediately after go-live. Reported by the monitoring system.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_3a175b815d50ffa3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.01, 0.08, 0.71, 0.2, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally correlates with the vendor status page incident. Context: in production only, at the end of the fiscal period. Reported by the supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_861f6fe81bd81dce_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.03, 0.1, 0.76, 0.11, 0.0], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: across all regions, during a scheduled maintenance window. Reported by the review queue.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_542d64ee8fc2efa3_n", "kind": "noul", "options": ["false", "true"], "target": [0.23, 0.77], "state": "Service catalog-sync returned to baseline after 11 minutes; additionally lost 4 minutes of trace data. Context: in production only, during the holiday freeze. Reported by the on-call engineer.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_1798fa40e847b9e8_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.8, 0.19, 0.01, 0.0], "state": "Dashboard checkout-funnel reports empty scrape targets after the network change; additionally shows disk at 91% and climbing 1%/hour. Context: in production only, while legacy systems are still active. Reported by the monitoring system.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_bf38b3e21bbd4c13_n", "kind": "noul", "options": ["false", "true"], "target": [0.69, 0.31], "state": "Service catalog-sync shows cache hit rate steady at 99.2%; additionally shows disk at 91% and climbing 1%/hour. Context: over the last hour, shortly after a software update. Reported by the monitoring system.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_db711bf7b1a5387d_n", "kind": "noul", "options": ["false", "true"], "target": [0.84, 0.16], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally shows a 22% drop in request rate with no deploys. Context: during the batch window, while legacy systems are still active. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_23f612548dbcc878_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.32, 0.65, 0.02], "state": "The log shipper 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 supervisor.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8c0cdfa317141def_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.02, 0.96, 0.0, 0.02], "state": "Service catalog-sync flags a step-function change in error slope; additionally shows a slow leak in heap growth. Context: during the batch window, shortly after a software update. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_0e18bd2801ffdb37_n", "kind": "noul", "options": ["false", "true"], "target": [0.82, 0.18], "state": "The log shipper shows cache hit rate steady at 99.2%; additionally reports empty scrape targets after the network change. Context: during the batch window, during the holiday freeze. Reported by the monitoring system.", "question": "Is this scenario one where: the dashboard itself is broken?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_5347d9814bee19d3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.01, 0.55, 0.44, 0.0], "state": "Service catalog-sync correlates with the vendor status page incident; additionally shows a slow leak in heap growth. Context: across all regions, during an external partner integration. Reported by the monitoring system.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8528a9e45dccf30e_c", "kind": "choice", "options": ["page_on_call", "open_ticket", "watch", "auto_remediate"], "target": [0.85, 0.13, 0.01, 0.01], "state": "Dashboard checkout-funnel correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: during the batch window, during peak load. Reported by the on-call engineer.", "question": "Action for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_25c05aee2960a6bd_n", "kind": "noul", "options": ["false", "true"], "target": [0.62, 0.38], "state": "Node pgsql-14 shows a 22% drop in request rate with no deploys; additionally flags a step-function change in error slope. Context: during the batch window, at the end of the fiscal period. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_d57446422899d7d8_n", "kind": "noul", "options": ["false", "true"], "target": [0.67, 0.33], "state": "The log shipper correlates with the vendor status page incident; additionally lost 4 minutes of trace data. Context: across all regions, during the holiday freeze. Reported by the supervisor.", "question": "Is this scenario one where: this can wait until morning?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_8f0ef10d2a34443c_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.02, 0.13, 0.82, 0.03, 0.0], "state": "The log shipper lost 4 minutes of trace data; additionally shows clock skew of 800ms across replicas. Context: over the last hour, during the holiday freeze. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_f7d9a996dabbf780_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.97, 0.0, 0.0, 0.03], "state": "The log shipper shows clock skew of 800ms across replicas; additionally shows disk at 91% and climbing 1%/hour. Context: across all regions, with staffing at reduced levels. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_dd808d0547fa88ef_n", "kind": "noul", "options": ["false", "true"], "target": [0.26, 0.74], "state": "The log shipper reports empty scrape targets after the network change; additionally reports cardinality explosion in the metrics store. Context: over the last hour, during the morning shift. Reported by the operator.", "question": "Is this scenario one where: this is a real incident, not an artifact?", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_b6ec7181a44acfe3_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.0, 0.0, 0.28, 0.69, 0.03], "state": "Node pgsql-14 correlates with the vendor status page incident; additionally reports empty scrape targets after the network change. Context: over the last hour, immediately after go-live. Reported by the supervisor.", "question": "Rate user-visible impact for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_96f3b760ba6bbfd6_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.11, 0.01, 0.07, 0.81], "state": "The metrics pipeline shows a 22% drop in request rate with no deploys; additionally reports cardinality explosion in the metrics store. Context: in production only, during the holiday freeze. Reported by the on-call engineer.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_14b2d53ae1c71c7b_s", "kind": "score", "options": ["0", "1", "2", "3", "4", "5"], "target": [0.0, 0.04, 0.33, 0.58, 0.05, 0.0], "state": "Node pgsql-14 shows a slow leak in heap growth; additionally returned to baseline after 11 minutes. Context: in production only, immediately after go-live. Reported by the operator.", "question": "Rate anomaly confidence for this scenario on a 0-5 scale.", "domain": "observability", "family": "technical", "source": "yuri_v3"} {"id": "v3_01bc2814a90e6c0d_c", "kind": "choice", "options": ["capacity", "code_regression", "dependency", "telemetry_artifact"], "target": [0.05, 0.02, 0.45, 0.48], "state": "The metrics pipeline returned to baseline after 11 minutes; additionally reports empty scrape targets after the network change. Context: over the last hour, during the holiday freeze. Reported by the supervisor.", "question": "Diagnosis for this scenario.", "domain": "observability", "family": "technical", "source": "yuri_v3"}