-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Go panic in OLTP exporter #16499
Comments
Thanks for the report @barclayadam, this appears to be a dup of open-telemetry/opentelemetry-collector#6420, which has been fixed in v0.64.1. Can you test with that version and see if it solves your issue? |
@codeboten I have upgraded to Helm chart 0.40.2 which uses docker otel/opentelemetry-collector-contrib:0.66.0 and I still see the same issue (included again in case stack is different due to new version):
|
@codeboten this time the culprit seems to be a metrics component (before happened on traces). My guess base on the config is prometheus exporter (have not checked yet). |
Describe the bug
Go is periodically producing a panic log and restarting (with an exit code of 2) with one of 2 outputs:
Steps to reproduce
I've only noticed this in logs recently trying to understand why I'm seeing duplicate logs being published via OLTP end so I do not have reproduction or what part of my configuration could be causing this
What version did you use?
0.63.1
What config did you use?
Environment
Helm chart: 0.38.0
Azure Kubernetes Service: v1.22.11
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: