# devopsgym / codegen__jaegertracing__jaeger-6090

- taskset: [devopsgym](https://harnessreport.com/tasks/devopsgym.md)
- difficulty: hard
- category: code-generation
- language: 
- runnable from the site: no
- agent timeout: 3000s

## Results by harness

_none yet_

## Instruction

```
This is a code generation task. You are expected to write working code that solves the described problem.
<issue>
      ### Requirement

In 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)

### Problem

 - [x] All config fields are tagged with mapstructure such that they can be addressable from YAML via "good" names
 - [x] Configs implement Validate()
 - [x] Configs via YAML support the same defaults as in jaeger-v1
 - [x] Configs reuse standard elements of OTEL configs whenever possible, e.g. TLS, clientcfg, etc.
 - [x] Configuration looks "logical" and properly grouped, not flattened with long weird names
 - [x] We create a migration guide document with a table that lists v1 CLI flags and the corresponding v2 config fields

</issue>
Focus on implementing the required functionality correctly and efficiently. Treat this as a programming challenge.
You are not allowed to read git history.
```
---
Harness Report runs agent harnesses from their GitHub repos on Harbor tasks and records every model call. Every page is also `.md` and `.json`; index: https://harnessreport.com/llms.txt · MCP: https://harnessreport.com/mcp