-
Notifications
You must be signed in to change notification settings - Fork 599
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
A NoMethodError is raised with a segment callback set #2213
Comments
Hi @toncid, We're sorry to hear that the callback isn't working out as we'd hoped. There are at least 2 issues you've brought to our attention with this issue that we'll be looking into:
Once we roll out those 2 fixes, you should no longer see the agent attempt to call There may be an issue unexpected issue happening within the callback itself. If you can reproduce the problem with a callback that does not contain any sensitive values or business logic and feel comfortable sharing the callback code, we'll attempt to use it to reproduce and investigate the issue. If not, no worries, we can still proceed. |
@toncid the 2 fixes described in my previous comment will be delivered with #2218 via a new Feel free to test with that branch:
There's a new update: #2218 has been merged and the |
Hello @fallwith, this has helped! There was indeed a kind of I would suggest to always run the segment callback with a |
Thank you for the great support! |
Sure thing, @toncid! I'm glad to hear things are working for you. The new |
Description
When the experimental segment callback is set, an unhandled
NoMethodError
is raised by the agent when aNet::HTTP
call happens within a delayed job:As this is a local agent error, it does not appear in the New Relic dashboard.
Removing the callback fixes the problem.
Expected Behavior
The exception is prevented and normal execution continues.
Troubleshooting or NR Diag results
Provide any other relevant log data.
Stack trace:
Steps to Reproduce
NewRelic::Agent::Transaction::ExternalRequestSegment.set_segment_callback(...)
Net::HTTP
request from within a delayed job.Note: It is possible that the
delayed_job
part is irrelevant, but this is how I can repro within our project.Your Environment
Ruby v2.6, Rails v6.1.7.4
Additional context
Possibly related tickets: #1556 and #1923.
For Maintainers Only or Hero Triaging this bug
Suggested Priority (P1,P2,P3,P4,P5): N/A
Suggested T-Shirt size (S, M, L, XL, Unknown): N/A
The text was updated successfully, but these errors were encountered: