Mikołaj Świątek

Components in core which currently do this: - `exporterhelper` Components in contrib which currently do this: - `filelogreceiver` - `sqlqueryreceiver` - `ackextension` - `mongodbatlasreceiver` - `groupbytraceprocessor`

I think I'd rather solve this in a more generic way. That is, ensure that we don't set any env variables the user has set. You can run into the...

This was solved in a generic way by https://github.com/open-telemetry/opentelemetry-operator/pull/3964.

The title of your PRs indicates it's adding support for attribute labels as well resource ones, but the code only seems to implement resources. Are you planning on a follow-up?

@sigurdfalk it would help a lot if you could post your collector configuration. This is a problem that could conceivably be caused by any of the prometheus-related components.

Are you sure that's the right one? It doesn't have any prometheus components in it, and only seems to be shipping logs to Loki.

I *think* you're suffering from https://github.com/open-telemetry/opentelemetry-collector/issues/12458, but I'm not sure why, given that you're using the deprecated syntax for configuring the Prometheus endpoint. Can you post the output of the...

That output doesn't have any of the problems Mimir complains about. Are you sure you aren't introducing them in some intermediate processing step?

The confusing thing here is that, as far as I understand, @sigurdfalk is using plain Prometheus to scrape these metrics, and the dotted named don't actually show up in the...

Ah, that would explain it indeed. Thank you for the investigation and detailed explanation @zepellin! @sigurdfalk can you verify that this is indeed the case in your environment?