Closed stephenhong closed 1 year ago
Looks like another instance of https://github.com/open-telemetry/opentelemetry-collector/issues/6794.
@stephenhong did you have this issue before 0.82.0?
@mx-psi, @songy23, @mackjmr is it possible that datadog exporter got a mutable operation on the original metrics pdata recently?
This could be related to the Datadog exporter. My current guess is DataDog/opentelemetry-mapping-go/pull/101 that was enabled in the Collector on #23445. I'll confirm with @gbbr and open a PR to set MutatesData
to true.
@dmitryax I saw this issue in v0.80.0 as well during local testing. I was using an old version of the Otel Java agent and the collector was not using the Datadog exporter. The error didn't show up again after switching the collector version to 0.82.0 so I thought it was fixed. But then when I enabled the Datadog exporter, I saw this error come up again
Thanks for the report @stephenhong, it is expected that you would see this in v0.80.0 as well if the underlying cause is https://github.com/DataDog/opentelemetry-mapping-go/pull/101. This will be fixed on v0.83.0 by the PR that closed this issue.
Component(s)
No response
What happened?
Description
The collector is shutting down and restarting repeatedly due to the following error
Steps to Reproduce
Run Otel collector v0.82.0 with the below config.yaml There are multiple apps sending trace, metrics, and logs to this collector but not sure what exact data is causing this
Expected Result
No panic: runtime error
Actual Result
Got the above error
Collector version
v0.82.0
Environment information
Environment
OS: AmazonLinux2
OpenTelemetry Collector configuration
Log output
Additional context
No response