-
Notifications
You must be signed in to change notification settings - Fork 400
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
capture_params doesn't work for error capture #127
Comments
Hey Scott, This is a bug, but it only kicks in if the error is raised after the transaction's name has been set, which happens at the end of the request. At the creation of the transaction, it gets the full URL, which will be used in most error cases. I agree there's a bug here, but just not stripping the parameters off the URL will lead to another, even more subtle bug. We should probably be capturing the raw URL and then setting |
@othiym23 I've been having trouble with this as well. I've tried:
In all three cases, when I hit
What gives? 😒 |
This is an amazing bug report. I'm looking at it now! |
Hi @dukedave, very sorry about this. We just did this part wrong. We're going to have to fix how Your test app was fantastic, and much appreciated. I will get fixing this into our queue, and let you know as soon as it's released. |
We have this issue as well. Can we get an update on the status? |
I believe we have fixed this in our latest release, version 1.7.2. Can people give that a spin and see if it resolves things? Thanks! |
Release v7.1.0
fixed discuss link in README
fixed discuss link in README
chore: update explorer hub link in readme
This strips the url of query strings and thus renders the capture_params argument useless, especially for Error Collecting.
https://github.com/newrelic/node-newrelic/blob/master/lib/transaction.js#L-103
I forked/hacked around this for personal deployment, but it'd be nice to have this in the main library
The text was updated successfully, but these errors were encountered: