Multiple separate requests are associated with the same trace ID

[punkpeye]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/node - fastify

SDK Version

9.40.0

Framework Version

Fastify 5.4.0

Link to Sentry event

No response

Reproduction Example/SDK Setup

const app = fastify();

setupFastifyErrorHandler(app);

app.get('/test-trace', (request, reply) => {
  reply.send(`${getCurrentScope().getPropagationContext().traceId}`);
});

const address = await app.listen({
  host: '::',
  port: options.port,
});

Steps to Reproduce

1. Request /test-trace

Expected Result

Expecting to get a different trace ID for every rquest.

Actual Result

$ curl http://127.0.0.1:7410/test-trace
e4dbd740816d4cc98be4d8b901581dff%                                                                                                                                                                                                                                                                   $ curl http://127.0.0.1:7410/test-trace
e4dbd740816d4cc98be4d8b901581dff%

[linear]

JS-756 Sentry traces do not work in an extremely simple Node.js/Fastify application

[punkpeye]

My application is initialized with:

node --experimental-transform-types --import ./app/instrument.ts ./app/bin/start-server.ts

I also tried

tsx --import ./app/instrument.ts ./app/bin/start-server.ts

Makes no difference.

[punkpeye]

If I add SENTRY_DEBUG=1, I don't see anything related to Fastify. Even when I make requests, nothing is logged.

Sentry Logger [log]: Initializing Sentry: process: 16673, thread: main.
Sentry Logger [warn]: No DSN provided, client will not send events.
Sentry Logger [log]: Running in ESM mode.
Sentry Logger [log]: @opentelemetry/api: Registered a global for diag v1.9.0.
Sentry Logger [log]: @opentelemetry/api: Registered a global for trace v1.9.0.
Sentry Logger [log]: @opentelemetry/api: Registered a global for propagation v1.9.0.
Sentry Logger [log]: @opentelemetry/api: Registered a global for context v1.9.0.
[instrument] Sentry.init
app ready: http://[::]:7410

[mydea]

Hello, the trace ID is not on the current scope, and should not be accessed this way. Instead, you can do Sentry.getTraceData() to get trace data if you need it for some custom process, which will be unique in different requests.

Also, things may not work if no DSN is provided, as that disables the SDK.