-
Notifications
You must be signed in to change notification settings - Fork 312
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]: Express tracing errors then stops sending traces #5111
Comments
I'm facing the same problem here. I used to use the version |
Same issue! I recently updated the dd-trace to the latest version and the traces were missing in the dashboard! |
We are having the same issue since a few days. After a few hours of leaving our application running, the Traces (and corresponding Metrics) for The application is running in the following environment:
Relevant package versions:
After enabling the Tracer Debug Logs, we saw the same error Logs, e.g.:
Additionally, we can observe the following logs, but those don't seem directly related to the problem as they also appear earlier, when Traces are still being sent:
|
Same issue on our end. As @marcovr stated, after a few hours of leaving our application running, the traces for Application Environment:
Rolling back to dd-trace 5.28.0 seems to fix the issue. |
I'm currently attempting to fix this. Please downgrade to 5.24 to avoid seeing this issue for the time being |
Hey @ida613, do you have an idea of when this will be fixed? I'm not in any rush and this is just asking more for information rather than impatience. Thanks for taking a look at fixing it! |
@ida613 thanks for the update, but dd-trace 5.24 is not compatible with Express 5, per @wconti27's comment at #4704 (comment). Should we conclude from this that dd-trace's Express 5 integration is simply broken and should not be used for now? |
Tracer Version(s)
5.29.0, v5.29.1, v5.30.0
Node.js Version(s)
22.11.0
Bug Report
I originally put this in #5092, but separated into it's own issue.
Since upgrading to the affected versions, we're finding that tracing stops after a bit of time. It's quite arbitrary, but it seems to be after 4-6 hours. When our application is redeployed, the tracing begins again. I've put a screenshot below to illustrate. While the screenshot shows the
express.middleware
operation this also happens for theexpress.request
operation.Versions less than the affected versions (I've tested 5.13.0, 5.21.0, 5.26.0, 5.28.0) don't seem to have this issue.
I've just enabled the logs and debug modes for our app to find out more, but initially there was no indication output as to why the tracing stopped.
I should also note that this happened in our staging and production environments. While our staging environment doesn't always have traffic, our production environment does. Additionally, both staging and production have health check endpoints that are hit by our ALBs, which should show up in tracing. During the times of no tracing, not even the health check endpoint is visible in tracing.
I've been able to find the logs, which are below. It seems the
dd-trace
module is encountering errors for some reason. The log:Feels like the cause for tracing to be stopped.
Maybe it's related to #4987. But since #4987 deals with different affected versions, maybe it's different.
Note: The log
Package 'next' was loaded before dd-trace! This may break instrumentation.
is present in working versions. Thenext.request
operation works fine in previous versions and in the affected versions. Our start command below which should load the instrumentation before next (we use a express custom server with next):Reproduction Code
Error Logs
Tracer Config
Operating System
Darwin XXX 24.2.0 Darwin Kernel Version 24.2.0
Bundling
No Bundling
The text was updated successfully, but these errors were encountered: