-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Sentry span not keep traceId #14803
Comments
Hi @xiaoxiangmoe thanks for writing in! EDIT: It is probably not related after all |
@xiaoxiangmoe just to confirm: Are you calling |
@xiaoxiangmoe I set this up as a repo here: https://github.com/andreiborza/14803-continue-trace Are there any differences to what you have? Could you try running this and see if it runs as expected? I'm getting
|
@andreiborza change from import * as Sentry from '@sentry/node'; to import * as Sentry from '@sentry/core'; will make this error happen Okay, I found why it it not work. In my real world app, it exists both import * as Sentry from '@sentry/node';
Sentry.startSpan() and // for sharing code to both node and browser, we import @sentry/core here
import * as Sentry from '@sentry/core';
Sentry.startSpan() And |
#14819 may fix this |
@xiaoxiangmoe yep, that's likely it. Thanks for raising this tho. |
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/node
SDK Version
8.43.0
Framework Version
nodejs
Link to Sentry event
No response
Reproduction Example/SDK Setup
No response
Steps to Reproduce
Expected Result
Log same traceId
same as v8.42.0
Actual Result
different traceId
The text was updated successfully, but these errors were encountered: