Skip to content
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

[BUG]: Requests and APM metrics zero-ing out with just a dd-trace upgrade 5.24.0 -> 5.35.0 #5247

Open
TREFZ opened this issue Feb 11, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@TREFZ
Copy link

TREFZ commented Feb 11, 2025

Tracer Version(s)

5.35.0

Node.js Version(s)

22.11.0

Bug Report

For our Node application, we pin dd-trace just to the major version, specifically v5. As part of a routine package-lock.json regeneration, our dd-trace version was bumped from 5.24.0 to 5.35.0. Immediately after release, our Datadog monitors for low request rates went off, showing that requests and all APM metrics were zero-ing out. But by all other monitoring, the website powered by this application was fine. The application was clearly responding to requests, and all traffic was normal.

On closer inspection of the released pull requests, we noted the upgrade in dd-trace, and maybe more importantly a major version upgrade to dd-trace's dependency @datadog/native-metrics. We can't say for sure if that was the cause, but after rolling back these changes, all Datadog activity returned to normal. For now, we've pinned our dd-trace version exactly to 5.24.0.

Shown below is our requests, segmented by release:

light blue = dd-trace 5.24.0
dark blue = dd-trace 5.35.0 upgrade, requests fall off a cliff
purple = back to dd-trace 5.24.0, requests return to normal

Image

Reproduction Code

No response

Error Logs

No response

Tracer Config

tracer.init({
  logInjection: true,
  runtimeMetrics: true,
  version: <release version>
});

Operating System

GNU/Linux

Bundling

No Bundling

@TREFZ TREFZ added the bug Something isn't working label Feb 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant