[BUG]: Some traces disappear on Node 24.2.0

[tjsousa]

Tracer Version(s)

5.56.0

Node.js Version(s)

24.2.0

Bug Report

Since upgrading to Node 24 we ran into a weird situation where some traces suddenly disappear. We use BullMQ with ioredis for background jobs and even though some traces come in as normal, others completely disappeared even if logs continue to show everything working as normal.

We also use other Datadog products such as Errors, Profiler and Logs and all these continue to work.

Turning DD_TRACE_DEBUG=true does not show any error expect much less Encoding payload: messages, so assuming the issue happens before actually trying to send the spans to the agent.

Currently blocked by this to upgrade to Node 24, any recommendation on what we can try to further diagnose the issue?

Reproduction Code

No response

Error Logs

No response

Tracer Config

tracer.init({
  logInjection: !!process.env.DD_ENV, // Only instrument logs if DD_ENV is set
  samplingRules: [
    {
      sampleRate: 0.01,
      service: 'redis_staging',
    },
    {
      sampleRate: 0.05,
      service: 'redis_production',
    },
  ],
});

Operating System

Linux 6.6.72+ #1 SMP PREEMPT_DYNAMIC Sun Apr 27 08:53:34 UTC 2025 x86_64 Linux

Bundling

No Bundling

[BridgeAR]

We do not yet fully support Node.js 24. There was a major change around the way things are handling async context frames.

Can you please see if things are working as expected when using the --no-async-context-frame flag as outlined here https://github.com/DataDog/dd-trace-js#version-release-lines-and-maintenance?

That should likely resolve your issue for now. We are currently migrating all our instrumentations to the new way so that this is not an issue, it just takes some time since it applied to almost all our integrations and we have to rework them one by one.

[tjsousa]

Thanks @BridgeAR. I tested it with the flag and indeed the issue goes away, thanks for enlightening me. I was wondering if there's any estimate for when Node 24 full support will ship that you could share publicly, given that being a global flag we lose the supposed improvements to the async local storage across the board making the Node 24 upgrade a little less relevant for us at this point.

[BridgeAR]

It is difficult to give a concrete timeline right now. It will likely still take a couple of weeks to get everything migrated. It might be possible to use it earlier depending on what instrumentations you rely upon.
For further context see nodejs/node#58204.

[BridgeAR]

We opened a tracking bug for the overall progress: #6025

[BridgeAR]

I am closing this in favor of the mentioned tracking bug.