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
Originally posted by tanenbaum April 9, 2024
Hello!
I was looking at how I might get instrumentation out of the library, both traces and metrics. I noticed that the ch-go "low level" API instruments various code paths, like https://github.com/ClickHouse/ch-go/blob/main/query.go#L609. I did at first think this library used those code paths, but as far as I can tell it is only sharing the driver.Conn interface definition and not using the ch-go client.
Is there any plan to do the same sort of instrumentation in this library? Would you like contributions in this area?
The text was updated successfully, but these errors were encountered:
Discussed in #1267
Originally posted by tanenbaum April 9, 2024
Hello!
I was looking at how I might get instrumentation out of the library, both traces and metrics. I noticed that the ch-go "low level" API instruments various code paths, like https://github.com/ClickHouse/ch-go/blob/main/query.go#L609. I did at first think this library used those code paths, but as far as I can tell it is only sharing the
driver.Conn
interface definition and not using the ch-go client.Is there any plan to do the same sort of instrumentation in this library? Would you like contributions in this area?
The text was updated successfully, but these errors were encountered: