Skip to content
This repository has been archived by the owner on Jun 15, 2023. It is now read-only.

Please clarify behavior of subsegment http.request.traced property, meaning of "broken" trace #61

Closed
jmm opened this issue Mar 29, 2022 · 1 comment
Labels

Comments

@jmm
Copy link

jmm commented Mar 29, 2022

Hello, the segment documents :: HTTP request data documentation says:

traced – (subsegments only) boolean indicating that the downstream call is to another traced service. If this field is set to true, X-Ray considers the trace to be broken until the downstream service uploads a segment with a parent_id that matches the id of the subsegment that contains this block.

  1. Can you please clarify what "broken" means? What affect does it have on behavior? How would it be observable in the console or raw trace data?

  2. What would be the effect of setting that on a subsegment for a request to a non-instrumented service that will never upload a segment?

See also:

aws/aws-xray-sdk-node#493

@joshbean
Copy link
Contributor

Closing this issue or pull request in advance of archiving this repo. For more information about the decision to archive this repo (and others in the 'awsdocs' org), see the announcement on the AWS News Blog.

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

No branches or pull requests

2 participants