You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(Filing this for posterity and so others can chime in if they've noticed the behavior. We plan to address this issue and will link to PR when available. Please feel free to assign this issue to me 🙇 , cc @mx-psi )
The text was updated successfully, but these errors were encountered:
This PR is part of work to address Payload size errors reported here: #2676
Combined with batching of spans/traces, spans with very large attribute values such as stacktraces can cause payload sizes to become excessive. This PR adds a max tag (a datadog span attribute, basically), value helper function, and truncates tag values when they're too large, which brings this in line with Datadog-Agent limits: https://github.com/DataDog/datadog-agent/blob/140a4ee164261ef2245340c50371ba989fbeb038/pkg/trace/traceutil/truncate.go#L23
Additionally, worth noting that work being done to directly import and re-use portions of the datadog-agent codebase will make this sort of thing much easier, and work being done within datadog to permit shorter batching times should also help resolve the Payload size errors being seen. However for now this PR can help.
**Link to tracking Issue:** <Issue number if applicable>
#2676
Describe the bug
We've noticed that bc there is no truncation of span attributes (or datadog tags) at the collector-contrib datadogexporter, occasionally payloads get rejected for being excessively large. It would make sense to apply the same truncation logic/limits that occurs in the datadog-agent repository: https://github.com/DataDog/datadog-agent/blob/e081bed84866686eeab56a98da5ff9b4b9f03ded/pkg/trace/traceutil/truncate.go#L19-L26 to traces emitted by the opentelemtry-collector's datadogexporter.
Additional context
(Filing this for posterity and so others can chime in if they've noticed the behavior. We plan to address this issue and will link to PR when available. Please feel free to assign this issue to me 🙇 , cc @mx-psi )
The text was updated successfully, but these errors were encountered: