Support separate tracing spans or retry metadata for go-redis retry attempts with otel

[Shahana-Hamza-Mamutty]

Hi,

I'm using go-redis/v9 with OpenTelemetry tracing enabled via redisotel.InstrumentTracing().

I've noticed that the current implementation of the ProcessHook wraps the redis.ProcessHookmethod, which includes internal retry logic. This means that all retry attempts are hidden inside a single span, making it difficult to trace retry behavior or visualize retry-related latency.

Is there any existing mechanism (or plan) to emit separate spans for each retry, or to at least expose retry-related metadata such as retry_count within the current span?