In the same way as seen on the OpenTelemetry instrumentation forgo-redis it would be extremely beneficial to create a similar package for redigo. Not only we can track the overhead of the client code, but we can also precisely trace errors/latency spikes/timeouts/etc...
Some further info:
Important Note: Semantic conventions to follow while preparing a package for manual instrumentation.
While this is not mandatory, we should aim for standardization across clients/languages/DBs. Here's the spec on DB semantic conventions:
https://github.com/open-telemetry/semantic-conventions/blob/main/docs/database/redis.md
PS: will gladly contribute to this matter.
In the same way as seen on the OpenTelemetry instrumentation for
go-redisit would be extremely beneficial to create a similar package for redigo. Not only we can track the overhead of the client code, but we can also precisely trace errors/latency spikes/timeouts/etc...Some further info:
Important Note: Semantic conventions to follow while preparing a package for manual instrumentation.
While this is not mandatory, we should aim for standardization across clients/languages/DBs. Here's the spec on DB semantic conventions:
https://github.com/open-telemetry/semantic-conventions/blob/main/docs/database/redis.md
PS: will gladly contribute to this matter.