{"task": {"agent_timeout": 3000, "task": "codegen__jaegertracing__jaeger-6090", "verifier_timeout": 3000, "instruction": "This is a code generation task. You are expected to write working code that solves the described problem.\n<issue>\n      ### Requirement\n\nIn this issue, we want to align the configuration for elastic search and open search storage with OTEL (part of https://github.com/jaegertracing/jaeger/issues/5229)\n\n### Problem\n\n - [x] All config fields are tagged with mapstructure such that they can be addressable from YAML via \"good\" names\n - [x] Configs implement Validate()\n - [x] Configs via YAML support the same defaults as in jaeger-v1\n - [x] Configs reuse standard elements of OTEL configs whenever possible, e.g. TLS, clientcfg, etc.\n - [x] Configuration looks \"logical\" and properly grouped, not flattened with long weird names\n - [x] We create a migration guide document with a table that lists v1 CLI flags and the corresponding v2 config fields\n\n</issue>\nFocus on implementing the required functionality correctly and efficiently. Treat this as a programming challenge.\nYou are not allowed to read git history.\n", "memory": "8192m", "runnable": false, "difficulty": "hard", "language": "", "cpus": "", "instruction_truncated": false, "category": "code-generation", "compose": false, "has_solution": true, "oracle": null, "docker_image": "", "taskset": "devopsgym", "tags": ["code-generation", "devops-bench"]}, "runs": []}