search

aws / aws-xray-daemon

The AWS X-Ray daemon listens for traffic on UDP port 2000, gathers raw segment data, and relays it to the AWS X-Ray API.
Apache License 2.0
191 stars 69 forks source link

ErrorCode: InvalidName #184

Open jpresley23-tw opened 1 year ago

jpresley23-tw commented 1 year ago

I am getting the following error in the aws xray daemon. I couldn't find an answer in Google. We are using a spring boot application with reactive. We are using 'io.zipkin.aws:zipkin-reporter-xray-udp:0.23.4' library.

 aws-xray-daemon-77bff65c9f-528fm 2023-01-20T00:16:31Z [Error] Unprocessed trace 1-63c9dd57-4295cbfdfe320e9251232b6b, segment: {                                                       
 aws-xray-daemon-77bff65c9f-528fm   ErrorCode: "InvalidName",                                                                                                                          
 aws-xray-daemon-77bff65c9f-528fm   Id: "cbb6a6a3e8c41c46",                                                                                                                            
 aws-xray-daemon-77bff65c9f-528fm   Message: "Invalid subsegment. ErrorCode: InvalidName, Cause: null"                                                                                 
 aws-xray-daemon-77bff65c9f-528fm }
atshaw43 commented 1 year ago

Hello,

This error occurs when a segment/subsegment with an invalid name is sent to the XRay backend from the daemon. The XRay backend will send a message back to the daemon that the name is invalid and log an error.

Please check to see that you are only using valid characters for the name of the segments/subsegments and that the length of the name is at most 200 characters.

You can read more here. https://docs.aws.amazon.com/xray/latest/devguide/xray-api-segmentdocuments.html#api-segmentdocuments-fields

Best, Adam

jpresley23-tw commented 1 year ago

Thank you for the explanation. Would this error cause a lag in the reported duration for the transaction? Also will this error cause AWS X-Ray to not receive the segment? We notice that we still get trace even though we received this error.