Skip to content
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

ErrorCode: InvalidName #184

Open
jpresley23-tw opened this issue Jan 20, 2023 · 2 comments
Open

ErrorCode: InvalidName #184

jpresley23-tw opened this issue Jan 20, 2023 · 2 comments

Comments

@jpresley23-tw
Copy link

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
Copy link
Contributor

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
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants