Is it possible to make the jaeger collector use dynamic indexes? route based on some trace cable

[Kaua3045]

I would like to know if in V2, for example, it is possible to route traces to specific indexes in Elasticsearch based on some trace field, thus avoiding deploying 1 collector per app. If possible, where can I find information about this and how to migrate from V1 to V2? Thank you in advance.

[dosubot[bot]]

Jaeger V2 does not support routing traces to specific Elasticsearch indexes based on trace fields (like service name or custom tags). Index selection is managed by static prefixes, date/time patterns, and optionally by using read/write aliases or Index Lifecycle Management (ILM) policies. All traces are written to indexes determined by these static or temporal schemes, not by trace content or fields. There is no configuration or code path in V2 that enables dynamic index routing based on trace fields, so deploying one collector per app for this purpose is not necessary or supported reference reference.

For migration from V1 to V2, the main changes are in configuration style (YAML instead of environment variables) and storage API alignment with OpenTelemetry. The Elasticsearch storage backend in V2 is compatible with ES 7.x and 8.x, and you can enable features like ILM or rollover with options like --es.use-aliases=true. For more on migration and compatibility, see the Jaeger V2 Elasticsearch storage docs.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}