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
Would it be reasonable to make it configurable whether or not the Ping() call is traced on the DB conn? In my case Ping() is used in a service-level health check with a high call frequency, and those traces are just noise.
The text was updated successfully, but these errors were encountered:
gbbr
changed the title
Excluding Ping from database tracing
database:sql: excluding Ping from database tracing
Feb 10, 2018
ah, great. I didn't know that was a feature. It would still be preferable to not send them to the agent at all, since they have such high frequency, but I think that ignore list will be acceptable.
Would it be reasonable to make it configurable whether or not the Ping() call is traced on the DB conn? In my case Ping() is used in a service-level health check with a high call frequency, and those traces are just noise.
The text was updated successfully, but these errors were encountered: