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
We are using NewRelic for APM management. And we want to use our own distributed tracing based on OT alongside with NewRelic. Doing this I came up on problem - NewRelic is not capturing details of SQL transactions when OT JDBC instrumentation is enabled.
Investigating the issue I found this commit: #277
It seems like at some moment dynamic proxies where introduced instead of plain wrappers.
Is there some specific reason for using dynamic proxies over plain wrappers? Can we roll back to wrappers or, at least, make this configurable? I am ready to offer the patch.
The text was updated successfully, but these errors were encountered:
We are using NewRelic for APM management. And we want to use our own distributed tracing based on OT alongside with NewRelic. Doing this I came up on problem - NewRelic is not capturing details of SQL transactions when OT JDBC instrumentation is enabled.
Investigating the issue I found this commit: #277
It seems like at some moment dynamic proxies where introduced instead of plain wrappers.
Is there some specific reason for using dynamic proxies over plain wrappers? Can we roll back to wrappers or, at least, make this configurable? I am ready to offer the patch.
The text was updated successfully, but these errors were encountered: