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
Coming out of a k8s operator discussion involving automated injection logic that would allow a customer to leverage New Relic APM functionality without altering their existing code base...
As per the docs, currently a customer wanting to define a custom method tracer must do so by adding a line of code for every method to be traced:
add_method_tracer:my_method_to_be_traced
It would be ideal if we could leverage a configuration parameter to permit method tracers to by added automatically when the agent starts.
Users could enjoy all of the custom functionality without any alterations being made to their .rb files.
For example, given this Ruby code:
moduleMyCompanyclassImagedefrender_png# code to render a PNGendendclassUserdefself.notify# code to notify usersendendend
We could support a configuration parameter called :custom_tracer_method_list like so in newrelic.yml:
Coming out of a k8s operator discussion involving automated injection logic that would allow a customer to leverage New Relic APM functionality without altering their existing code base...
As per the docs, currently a customer wanting to define a custom method tracer must do so by adding a line of code for every method to be traced:
It would be ideal if we could leverage a configuration parameter to permit method tracers to by added automatically when the agent starts.
Users could enjoy all of the custom functionality without any alterations being made to their .rb files.
For example, given this Ruby code:
We could support a configuration parameter called
:custom_tracer_method_list
like so innewrelic.yml
:Method tracers would then automatically be added for the 2 methods on the list.
The text was updated successfully, but these errors were encountered: