Open slonka opened 6 months ago
Original author @bcollard
We can add debug exporter example:
metrics:
exporters:
- datadog
- debug
This will log all collected metrics, so we could find metrics on which datadog exporter fails, and create issue in OpenTelemetry collector. @bcollard could you look at it?
otel-exporter-2.log otel-exporter-1.log
Otel-collector keeps crashing with the debug exporter for metrics.
I see that I forgot about rest of the debug exporter config. @bcollard can you run this again with this config:
mode: deployment
config:
exporters:
debug:
verbosity: detailed
datadog:
api:
site: datadoghq.eu
key: <key>
service:
pipelines:
logs:
exporters:
- datadog
traces:
exporters:
- datadog
metrics:
exporters:
- datadog
- debug
This should properly log collected metrics co we can debug further
here attached otel-cluster1.log otel-cluster2.log
"kuma" appears a lot in the otel-cluster1.log
file, not in the other.
Logs look fine, but we could also verify if this is only datadog collector issue by pushing metrics to some other saas product like grafana and check if this issue is still there. There is an example on how to set this up in demo-scene repo. Cold out try this without datadog exporter @bcollard ?
Removing closed state labels due to the issue being reopened.
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
What happened?
Not sure if we are faulty or if it's the Datadog exporter/mapping for otel.
Repro / setup: