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
Currently, the SE.Redis SDK provides metrics through logs. I’m interested in knowing if there are any plans to expose these metrics as OpenTelemetry metrics.
Specifically, I’m looking for metrics related to the Connection Multiplexer and connection usage. This information would help me fine-tune the number of connections configured in my Redis client, allowing me to make optimal use of Redis pipelining while keeping end-to-end latency under control.
Another use case I'm looking for is when we run into issues like timeout exceptions, we should be able to tell whether it was due to some server side issue or some kind of blocking on the client side itself.
The text was updated successfully, but these errors were encountered:
Currently, the SE.Redis SDK provides metrics through logs. I’m interested in knowing if there are any plans to expose these metrics as OpenTelemetry metrics.
Specifically, I’m looking for metrics related to the Connection Multiplexer and connection usage. This information would help me fine-tune the number of connections configured in my Redis client, allowing me to make optimal use of Redis pipelining while keeping end-to-end latency under control.
Another use case I'm looking for is when we run into issues like timeout exceptions, we should be able to tell whether it was due to some server side issue or some kind of blocking on the client side itself.
The text was updated successfully, but these errors were encountered: