Description
Component
OpenTelemetry.Instrumentation.StackExchangeRedis
Package Version
| Package Name | Version |
|---|---|
| OpenTelemetry.Api | 1.11.2 |
| OpenTelemetry | 1.11.2 |
| OpenTelemetry.Instrumentation.StackExchangeRedis | (v1.11.0-beta.2) |
| StackExchange.Redis | (v2.7.4) |
Runtime Version
net8.0
Description
We use OpenTelemetry.Instrumentation.StackExchangeRedis to trace Redis operations. After switching from standalone Redis to Redis Cluster mode, we noticed that spans for specific commands like SETEX no longer appear. Instead, we only see generic spans labeled as CLUSTER.
Expected behavior:
Spans for actual commands such as SETEX, GET, etc., should be recorded, even when using Redis in Cluster mode.
Actual behavior:
Only generic spans (e.g., CLUSTER, GET) appear.
No visibility into actual user commands like SETEX.
Attachments:
Included screenshots of trace data with and without Redis Cluster mode for comparison.
Steps to Reproduce
Create any app with redis teleemetry, use writes on redis on cluster mode
Expected Result
Spans for actual commands such as SETEX, GET, etc., should be recorded, even when using Redis in Cluster mode.
Actual Result
Only generic spans (e.g., CLUSTER, GET) appear.
No visibility into actual user commands like SETEX.
Additional Context
No response