-
Notifications
You must be signed in to change notification settings - Fork 737
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
Cannot start a span with specified traceId
#4671
Labels
question
User is asking a question not related to a new feature or bug
Comments
This is the incorrect line The trace id alone is insufficient to create a parent context, which requires a trace id and a span id. Interacting with context like this directly using keys is not recommended and is likely to cause issues like what you are experiencing here. Yes, you should be using a propagator for this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
Steps to Reproduce
I have a python service and a node service. they communciate via Redis pub/sub
Now its worth noting i have tired maybe 10 different variations here using all sorts of boilerplate like
context.with
startActiveSpan
etc. etc. and nothing worksExpected Result
All the logs should print the same traceId
Actual Result
1, 2 and 3 print the same traceId => therefore the spans are working on the python side, and I have correctly received the same traceId back
But 4 is printing a new traceId, so when I start a new span on the node service, it will not use the passed traceId in the context
Additional Details
I have been on and off with this for over 2 weeks and I cannot get my node service to work, the documentation for this is extremely confusing and I'm having to dig into ancient github issues to find any examples of this.
I realise most people use a Propagator, but I don't think that will work for redis pub/sub
OpenTelemetry Setup Code
No response
package.json
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: