-
Notifications
You must be signed in to change notification settings - Fork 142
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
unparented segment/subsegment resolution #67
Comments
Hi, sorry for the late response. I saw the Here are several options:
Please let me know in an ideal case how you expect your tracing data to be structured so I can provide further help. |
late? that was really fast :)
I think it's worth discussing what the ideal solution would be, I have no firm proposal. |
Hi, Please let me know if solution2 works for you. In that case I would imagine your service graph is split into two parts. One represents the request flow starts from your main thread and the other one represents the background work. All background work subsegments will be aggregated to a single node with name like You can also do some more complicated logic on how to create the unparented segment so you categorize the workers into different logical nodes on the service graph to fit your need. Please let me know your findings and I can see a general enough |
ya solution 2 seems to be working for me. Right now I have them all in one unparented bucket, but I could imagine some people may want them categorized by thread or perhaps pool (which could include a name for more context). However I decided not to do that because the threads may be one-offs. |
I'm closing this issue now. Will put the |
I'm using aws-xray-sdk to trace an application which uses the google pubsub module. Unfortunately this module uses various threads which means that I get a lot of
SegmentNotFoundException
exceptions causing my application to fail.It's going to be impossible for me to track down all the locations where it creates threads and pass the trace entity and call
xray_recorder.set_trace_entity
.How about if this SDK provides support for a "root thread" which it will use to resolve the segment/subsegment if the current context does not have one?The text was updated successfully, but these errors were encountered: