StackExchange / StackExchange/StackExchange.Redis
ProfilingSession - how to setup with both OTEL-contrib telemetry instrumentation for traces and custom metrics support
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.2k
- Forks
- 1.6k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 43
Description
Hi, I'm registering own ProfilingSession to deliver StackExchange metrics like total processing time, enqueue to sending and rest per command type to monitor my Redis connections health.
It is working like a charm until I start to collect traces using StackExchangeRedisInstrumentation from OTEL as it replaces my ProfilingSession factory with own implementation.
Are there any suggestions on how to use this telemetry instrumentation from OTEL along with own profiling session used to produce metrics?
Is there option to maintain more than one ProfilingSession or concept of shared instance?
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
Start by reading the ProfilingSession factory usage and the StackExchangeRedisInstrumentation integration described in the issue. Determine whether custom metrics and OTEL traces can share a ProfilingSession or require multiple instances; done means a documented supported setup or a clearly scoped implementation path.
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