opentelemetry-collector-contrib: [Datadog] Payload too large
Describe the bug We are hitting “Payload too large”
What did you see instead?
2021-01-02T19:46:41.072Z info datadogexporter/traces_exporter.go:155 failed to send traces {"component_kind": "exporter", "component_type": "datadog", "component_name": "datadog", "error": "failed to send trace payload to trace edge: Post \"https://trace.agent.datadoghq.eu/api/v0.2/traces\": write tcp 192.168.234.159:34974->35.241.39.98:443: write: broken pipe"}
2021-01-02T19:46:43.041Z info datadogexporter/traces_exporter.go:155 failed to send traces {"component_kind": "exporter", "component_type": "datadog", "component_name": "datadog", "error": "failed to send trace payload to trace edge: request to https://trace.agent.datadoghq.eu/api/v0.2/traces responded with 413 Payload too large"}
2021-01-02T19:46:45.027Z info datadogexporter/traces_exporter.go:155 failed to send traces {"component_kind": "exporter", "component_type": "datadog", "component_name": "datadog", "error": "failed to send trace payload to trace edge: request to https://trace.agent.datadoghq.eu/api/v0.2/traces responded with 413 Payload too large"}
2021-01-02T19:46:47.602Z info datadogexporter/traces_exporter.go:155 failed to send traces {"component_kind": "exporter", "component_type": "datadog", "component_name": "datadog", "error": "failed to send trace payload to trace edge: request to https://trace.agent.datadoghq.eu/api/v0.2/traces responded with 413 Payload too large"}
What version did you use? 0.17.0
We are hitting these errors. How can we configure it?
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 16 (10 by maintainers)
Commits related to this issue
- Temporarily skip test until it is fixed (#1925) This test is very unstable on windows. Issue for proper fix is filed: https://github.com/open-telemetry/opentelemetry-collector/issues/1923 — committed to dynatrace-oss-contrib/opentelemetry-collector-contrib by tigrannajaryan 4 years ago
- Bump github.com/golangci/golangci-lint in /internal/tools (#1925) Bumps [github.com/golangci/golangci-lint](https://github.com/golangci/golangci-lint) from 1.40.0 to 1.40.1. - [Release notes](https:... — committed to ljmsc/opentelemetry-collector-contrib by dependabot[bot] 3 years ago
Hello !
Could you display in the error the number of events/metrics that the plugin tried sending ? That makes things easier for fine tuning 😉
Thanks,
I think for this specific user the issue is solved but this will continue to pop up for future users until addressed, and the above mitigation is imprecise. let’s keep this open until the work for
is complete.
Hi, generally the same comments apply here https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/1909#issuecomment-755969384 Traces issues are (for the most part) handled by Eric