2개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
0
Just to follow up, I figured out what was missing, I wasn't explicitly requesting the AWSTraceHeader in my SQS ReceiveMessage command, upon requesting it the trace data is indeed present.
답변함 일 년 전
0
Is it possible that the upstream of EventBridge does not inject correct xray trace header? Could you print the http header X-Amzn-Trace-Id
of EventBridge request?
답변함 일 년 전
관련 콘텐츠
- AWS 공식업데이트됨 8달 전
No, as I tried adding a lambda target and the trace header is propagated correctly in the case of lambda targets. I'm using the nodejs xray wrapper on the upstream, I don't know how to print the header but I'm 100% sure that it's correct