-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[exporter/datadog] Datadog exporter panics while exporting metrics pushed from Kuma dataplane proxy #32103
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
@Automaat If it is easy to reproduce, would you be able to use the file exporter or the debug exporter to get some sample metrics? It sounds like the problematic metric is an OTLP Histogram, but I don't have enough data to reproduce just yet. |
@mx-psi we have logs from debug-exporter, here: kumahq/kuma#9336 (comment) If it is not enough I can collect more |
@Automaat These logs don't have any sample data, using one of the exporters mentioned on #32103 (comment) should allow us to see the actual payload. If you have not used them before, see https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/troubleshooting.md#local-exporters for a brief explanation |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
Component(s)
exporter/datadog
What happened?
Description
We've introduced support for pushing metrics to OpenTelemetry collector in Kuma service mesh, and we discovered an issue with datadog exporter. A couple of minutes after we start pushing metrics to collector, it panics. More information in Kuma issue, with logs from debug exporter: kumahq/kuma#9336
Steps to Reproduce
Install Kuma, guide
Install demo app
kumactl install demo | kubectl apply -f -
Otel collector with config:
Expected Result
exporter does not panic
Actual Result
exporter panics
Collector version
0.92.0
Environment information
Environment
OpenTelemetry Collector configuration
Log output
Additional context
No response
The text was updated successfully, but these errors were encountered: