You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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
Reproduction Code
No response
Error Logs
No response
Tracer Config
Operating System
GNU/Linux
Bundling
No Bundling
The text was updated successfully, but these errors were encountered: