devopsbench-100 / tasks /dob100-013-localize-analytics-errors.json
SamuelChien821's picture
Upload folder using huggingface_hub
ea61660 verified
Raw
History Blame Contribute Delete
4.47 kB
{
"context_files": [],
"gold_output": {
"expected_final_state_checks": {
"correctness": [
"diagnosis_submitted",
"service_localized",
"fault_confirmed",
"scoped_change_no_fabricated_data",
"world_invariants_intact"
],
"deployment": [
"investigation_was_read_only"
],
"quality": [
"evidence_recorded",
"efficient_investigation",
"ticket_closed",
"closed_after_the_work",
"no_new_hardcoded_secrets",
"no_unproductive_ci_loops"
]
},
"ground_truth_submissions": [
{
"arguments": {
"evidence": "analytics-worker error_rate_pct 6.0; the consumer OOMs with unlimited queue prefetch",
"fault_detected": true,
"fault_type": "unbounded_prefetch",
"offending_key": "prefetch_count",
"scope": "9609",
"service": "analytics-worker"
},
"tool": "submit_diagnosis"
}
],
"note": "Acceptance is state-based: every correctness and deployment check must hold over the final world database and its append-only audit log."
},
"instruction_guided": "This is an investigation, not a change. Do NOT modify production state: no pull requests, deploys, flag toggles, migrations or resolutions. Investigate with the read tools and report what you find with submit_diagnosis(...).\n\nOPS-113 — Localize alarm 9609 (analytics-worker errors)\n\nAlarm 9609 is firing. Work out which service is actually responsible — the service the alarm names is not automatically the culprit — and submit your finding under scope '9609' with the evidence you relied on.\n\nProcedure: trace the symptom through the metrics, the service dependency graph and the logs, then submit the responsible service.",
"metadata": {
"benchmark": "DevOpsBench-100",
"category": "aiops_localization",
"code_license": "Apache-2.0",
"curation_rationale": [
"aiops_localization",
"medium",
"7-call-oracle",
"curated",
"hardest-of-category-quota",
"controls-rejected:pristine"
],
"data_license": "CC-BY-4.0",
"difficulty": "medium",
"grading": "deterministic",
"guided_instruction_available": true,
"harbor_name": "blobfishai/dob100-013-localize-analytics-errors",
"llm_judge": false,
"origin": "curated",
"reference_tool_calls": 7,
"required_tools": [
"get_service",
"get_slo_status",
"get_ticket",
"list_alerts",
"search_logs",
"submit_diagnosis",
"update_ticket"
],
"source_split": "train",
"source_task_id": "tsk_localize_analytics_errors",
"version": "1.0.0"
},
"prompt": "This is an investigation, not a change. Do NOT modify production state: no pull requests, deploys, flag toggles, migrations or resolutions. Investigate with the read tools and report what you find with submit_diagnosis(...).\n\nOPS-113 — Localize alarm 9609 (analytics-worker errors)\n\nAlarm 9609 is firing. Work out which service is actually responsible — the service the alarm names is not automatically the culprit — and submit your finding under scope '9609' with the evidence you relied on.",
"rubric": {
"checks": {
"correctness": [
"diagnosis_submitted",
"service_localized",
"fault_confirmed",
"scoped_change_no_fabricated_data",
"world_invariants_intact"
],
"deployment": [
"investigation_was_read_only"
],
"quality": [
"evidence_recorded",
"efficient_investigation",
"ticket_closed",
"closed_after_the_work",
"no_new_hardcoded_secrets",
"no_unproductive_ci_loops"
]
},
"grading": "deterministic",
"llm_judge": false,
"pass_rule": "every correctness and deployment check holds over the final world state and audit log",
"score_weights": {
"correctness": 0.6,
"deployment": 0.3,
"quality": 0.1
},
"type": "deterministic",
"verifier": "verifiers/verify_dob100-013-localize-analytics-errors.py"
},
"task_id": "dob100-013-localize-analytics-errors",
"task_name": "This is an investigation, not a change. Do NOT modify production state: no pull requests, deploys, flag toggles, migrations or resolutions. Investigate with the read tools and report what you find with submit_diagnosis(...).",
"world_id": "env_software_devops_0ec42f0f"
}