-
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
[receiver/awsxray] X-Ray Receiver appears to be dropping or rejecting segments from X-Ray #36128
Comments
Pinging code owners: See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Example (anonymised) trace attached. |
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. |
Component(s)
No response
What happened?
Description
We are forwarding X-Ray trace data (from batch-get-traces) to the awsxrayreceiver but after extensive debugging we've come to the conclusion that it is either not receiving all spans, or is rejecting some segments somehow. We get missing root spans in multiple services (tested Grafana, Honeycomb), and have verified through debug/file exporters that the OTel collector otlphttp exporter is not receiving many spans.
The fileexporter returns:
Which is missing a number of spans, including the root span (5f40bc419f287db1 which has no parent_id)
We run this with a batch processor, and have tested with no processors.
Our lambda sends xray trace data to the otel collector, has been extensively tested/debugged, and is verifiably sending the root span:
Note the 4th of 11 spans forwarded contains 5f40bc419f287db1, the root span. This span is not in the trace output above - somewhere in the collector of awsxrayreceiver -> otlphttp it's being lost/dropped/rejected.
And the relevant message being sent:
The message is, as far as we can tell, a valid trace message. There are no errors/warnings in the collector logs.
Example message:
Steps to Reproduce
Send large trace with nested subsegments to awsxrayreceiver
Fewer segments are exported via otlphttp than exist in the trace, including the all-important root span
Expected Result
Root span is not missing in whatever service the otel collector otlphttp exporter sends spans to. A span exists in our trace without a parent_id and this is the correct root span.
Actual Result
Root span is missing.
Collector version
0.112.0
Environment information
Environment
OS: amazonlinux:2023
Compiler(if manually compiled): golang:1.22-alpine, go.opentelemetry.io/collector/cmd/builder@v0.112.0
Binary:
OpenTelemetry Collector configuration
Log output
Nothing incorrect in the logs that do show, but there are missing log entries for the missing spans. Given that these are exporter debug logs, the only remaining outcome we see is that the awsxrayreceiver is at fault?
The text was updated successfully, but these errors were encountered: