Alex Boten

based on the output of the pprof shown here, this looks closely related to https://github.com/open-telemetry/opentelemetry-collector/issues/10858

A workaround for this is to update the config to parse correctly w/ v0.3.0 ``` - periodic: exporter: otlp: endpoint: https://${MY_BACKEND} headers: - name: key value: value protocol: http/protobuf temporality_preference:...

This bug will eventually go away once the config schema releases v1.0 and we can use feature-gates to deprecate old configuration support

@iblancasa sure go for it!

Discussion about headers field https://github.com/open-telemetry/opentelemetry-collector/issues/13930

thanks @iblancasa, i've assigned this to you

@arminru i should be able to, please assign it to me :)

Added @tylerbenson and @serkan-ozal to the CNCF account, please confirm you have access

Thanks for opening the issue @dentonk, i support adding this as well, as i introduced this PR https://github.com/open-telemetry/opentelemetry-collector/pull/13791 that missed adding `WithQueue`, can you submit a PR and i can...

> I've been able to reproduce in the collector helm chart using this simplified (core only components) values.yaml: Should this be transfered to the helm-charts/operator repo then @TylerHelmuth?