-
Notifications
You must be signed in to change notification settings - Fork 303
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
Give a way to handle gracefully errors from dd tracer #1564
Comments
We already catch errors from dd-trace and send them to the debug logs, so it should never happen that we throw. If it does happen then there is a bug. It's worth noting however that dd-trace might show up in many stack traces since we hook into a lot of things, so it's also possible that you are having an existing issue that looks like it comes from dd-trace because of the stack trace even if that's not the case. Can you share more information about these errors and stack traces that we could look at? |
@rochdev here you go:
|
For the first and the last one, they should be existing errors that dd-trace is only involved in because the scope manager is present in all asynchronous operations, and we instrument the For the second one it's a bit more complicated. It looks like it could be the way we parse the route, which is surprising because we use the same logic as Express. It's possible we do things in a different way than your specific version of Express though which could cause this issue. Are these errors something you are able to easily reproduce with a snippet you could share? |
I just experienced something similar and was in need of the same. I'd rather have the instrumentation/monitoring not to work than to crash a legitimate user-facing request as it happened.
|
@arturkasperek is this still an issue for you? |
We have a similar need because of a failure in dd-trace to parse our large json post bodies: #4594 |
I'm using
http
plugin for tracing things in my server application. I noticed that server is pretty often restarted due to dd-trace errors like:I'm using following settings (my dd-trace version is 0.33.2):
I don't like the current situation where the dd agent can cause the failure of my process. I think dd tracer should enable in some way catching the error.
I was thinking about 2 solutions:
First - error handler:
Second - use error class hierarchy:
I would be thankful for any solutions of my problem,
Thank you :-)
The text was updated successfully, but these errors were encountered: