opentelemetry-instrumentation-redis: semantic convention stability migration

[tammy-baylis-swi]

What problem do you want to solve?

semantic convention stability migration for opentelemetry-instrumentation-redis

Describe the solution you'd like

Implement the semconv opt-in feature for Redis

Describe alternatives you've considered

No response

Additional Context

Part of this #2453

May duplicate #2885

Would you like to implement a fix?

None

[luke6Lh43]

Hello! I opened #2885, which is referenced here. I’m planning to start working on the semantic convention migration for Redis (I already discussed it with @pmcollins ). From what I understand, we need to implement new environment variable (OTEL_SEMCONV_STABILITY_OPT_IN) that will enable the new semantic convention scheme.

One thing I’d like to clarify: since we use "database" as a value (rather than something Redis-specific), does this mean we need to implement it for all databases before merging? For example, if an application uses both MySQL and Redis, and OTEL_SEMCONV_STABILITY_OPT_IN only is available only for Redis, MySQL instrumentation will ignore it and still be sending experimental sem conv. Would that be ok?

Thanks!