OTEL_TRACES_INDEX_ID_PATTERN make customizable

[nicolas-fidel-wmx]

Is your feature request related to a problem? Please describe.
I'd like to be able to customize the OTEL_TRACES_INDEX_ID_PATTERN so that quickwit returns the traces of my custom indexes by default.

I'd like a jaeger instance to be able to use custom indexes to modify parameters.

Describe the solution you'd like
Add an env variables for this param or field in config

Additional context
By the way, the jaeger documentation is compatible only with V1, which will be in EOL at the end of the year. But the version 0.8.1 api works well with jaeger version 2.5 but not above because they've changed the grpc storage spec.

[fmassot]

Thanks @nicolas-fidel-wmx for the feedback.

I don't think we are going to make it customizable in the short term. I would rather refactor all this and support the new jaeger version.

Why can't you migrate your customer index to new index IDs so it matches the OTEL_TRACES_INDEX_ID_PATTERN?

[nicolas-fidel-wmx]

That's what I did, but currently with your helm chart it's not possible to create an index that matches the naming convention (OTEL_TRACES_INDEX_ID_PATTERN) because the helm chat takes the name of the index to create the bootstrap job, but you can't name a kubernetes job with a _.