This repository has been archived by the owner on Oct 3, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 21
Trace ID not carried forward from parent #39
Comments
ryan-lang
changed the title
Publish interval results in broken traces
Trace ID not carried forward from parent
Mar 1, 2020
On further digging, it seems that The workaround is to provide an X-Ray-specific ID Generator like so:
And then wherever your trace is configured:
If I have the time, I'll clean this up into a pull request. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm experiencing an issue when publishing traces that run longer than the publish interval. The first batch of spans is properly sent to X-Ray, but subsequent spans are dropped.
This seems to be happening because a new AmazonTraceID is generated on every publish bundle, regardless of whether the span has a parent or not. Specifically,
convertToAmazonTraceID
injects a fresh timestamp each time, resulting in a new unique trace ID, even when we want to be carrying forward the existing trace ID.Included is a small program demonstrating the issue. I added some logging to opencensus-go-exporter-aws (not shown here) so we can see what's getting sent to AWS. The results show two different trace IDs.
The text was updated successfully, but these errors were encountered: