-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Description
Component(s)
exporter/awsxray
What happened?
Description
When using OTel Collector with X-Ray Receiver/Exporter, X-Ray Segment gets converted into OpenTelemetry Span (via X-Ray Receiver) and then later gets converted into X-Ray Segment (via X-Ray Exporter).
In X-Ray Receiver, we explicitly convert the in_progress Segment field attribute into the aws.xray.inprogress attribute.
In X-Ray Exporter, we don't convert the aws.xray.inprogress attribute back into the in_progress Segment field:
Therefore the in_progress functionality does not function as it was intended as it is now part of metadata instead of being a Segment field. The Segment doesn't have the ability to be updated later since it isn't correctly labeled as in_progress in X-Ray.
Steps to Reproduce
- Use X-Ray Receiver + X-Ray Exporter
- Send segment to OTel Collector's X-Ray Receier:
cat sample-trace.json | nc -u 127.0.0.1 2000
sample-trace.json:
{"format":"json","version":1}
{"type":"segment","trace_id":"1-64d8bfaf-fd72e26886b3fdd3a272224e","id":"6222467a3d841238","start_time":1759136781.313,"in_progress":true,"name":"testName","user":"213456","origin":"AWS::EC2::Instance","namespace":"aws","aws":{"account_id":"123456789012"}}
Expected Result
X-Ray Segment should have in_progress as a Segment field (exactly like in sample-trace.json).
Actual Result
X-Ray Segment has in_progress as metadata.
Collector version
v0.138.0
Environment information
Environment
Any
OpenTelemetry Collector configuration
extensions:
awsproxy:
local_mode: true
region: 'us-west-2'
receivers:
awsxray:
transport: udp
proxy_server:
tls:
insecure: false
server_name_override: ""
region: 'us-west-2'
role_arn: ""
aws_endpoint: ""
local_mode: true
otlp:
protocols:
grpc:
endpoint: 0.0.0.0:4315
http:
endpoint: 0.0.0.0:4316
exporters:
awsxray:
region: 'us-west-2'
index_all_attributes: true
service:
pipelines:
traces:
receivers: [awsxray, otlp]
exporters: [awsxray]
extensions: [awsproxy]
telemetry:
logs:
level: debugLog output
Additional context
No response
Tip
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.