StackExchange / StackExchange/StackExchange.Redis
Connection Multiplexer OpenTelemetry based metrics
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.2k
- Forks
- 1.6k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names the Connection Multiplexer, connection usage, timeout exceptions, and existing log-based metrics, but no files, tests, or entry points. Start by locating those areas in the repository and reviewing how metrics are currently exposed. Done means the requested OpenTelemetry metrics and their client-versus-server diagnostic purpose are concretely scoped.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, redis
- Domain
- backend, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100