Elastic APM reporting seems to drop spans after a maximum per HTTP endpoint call #23885
Labels
~backend
Backend-related issue.
bug
Something isn't working as documented
~engineering-initiated
Engineering-initiated story, such as a bug, refactor, or contributor experience improvement.
#g-endpoint-ops
Endpoint ops product group
:release
Ready to write code. Scheduled in a release. See "Making changes" in handbook.
💥 Actual behavior
When looking at a trace for an HTTP call, Elastic APM is missing later spans in the trace when a trace has a bunch of spans (e.g. for N+1 DB calls in a list endpoint).
🧑💻 Steps to reproduce
🕯️ More info
As of creating this issue, I haven't confirmed whether OpenTelemetry has the same issue, so using OTel as a sink for traces rather than Elastic APM may be a near-term workaround for long traces.
The text was updated successfully, but these errors were encountered: