Default RED Metric names from otelcol spanmetricsconnector are chainging in v0.109.0

[frzifus]

RED Metrics generated by the spanmetricsconnector will be prefixed by default when using an OpenTelemetry Collector v0.109.0 or higher.

We currently configure jaeger-query to fallback to the old behaviour without any prefix. We might want to support an option to use both variants.

See:

• [connector/spanmetrics] Improve consistency between metrics generated by spanmetricsconnector open-telemetry/opentelemetry-collector-contrib#34485
• Remove the default metrics namespace/prefix for span RED metrics in Jaeger query #1072

[pavolloffay]

I wonder why @iblancasa didn't bring this to attention :)

[pavolloffay]

https://github.com/open-telemetry/opentelemetry-collector-contrib/releases/tag/v0.109.0

https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/connector/spanmetricsconnector#configurations there is namespace configuration option, does it work if we set it to an empty string?

[iblancasa]

I wonder why @iblancasa didn't bring this to attention :)

I mentioned the change in my internal status report and during one of our 1on1s.

https://github.com/open-telemetry/opentelemetry-collector-contrib/releases/tag/v0.109.0

https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/connector/spanmetricsconnector#configurations there is namespace configuration option, does it work if we set it to an empty string?

There is a feature flag. Doesn't it help?

[pavolloffay]

The FF does not help. IIRC we would need make code changes in the operator to enable it.

I think we have 2 options:

• set the namespace to empty in the collector config. @frzifus could you please test it?
• make the breaking change in 3.4 to use the default namespace and allow overriding the namespace in tempo CR.