Redis attributes not aligned with latest semantic conventions

[luke6Lh43]

What version of OpenTelemetry are you using?

"@opentelemetry/api": "^1.9.0"
"@opentelemetry/auto-instrumentations-node": "^0.50.0"
"@opentelemetry/exporter-trace-otlp-http": "^0.53.0"
"@opentelemetry/sdk-node": "^0.53.0"

What version of Node are you using?

Node.js 22.9.0, NPM 10.8.3

What did you do?

https://github.com/luke6Lh43/otel-redis-testing/blob/main/Readme.md#nodejs

Additional context

Hello,

I have recently been working on a project that required Redis instrumentation for two different languages. During this process, I noticed some discrepancies in the attributes being collected. To investigate further, I conducted testing to check the attributes collected for Redis instrumentation across six of the most popular languages. I have documented my testing in this GitHub repository:

[Link to GitHub Repo]

Findings for Node.js:

What We Capture Today ==> How It Should Look in Latest Semantic Conventions

db.system: redis ==> db.system: redis
net.peer.name: localhost ==> network.peer.name: localhost
net.peer.port: 6379 ==> network.peer.port: 6379
db.connection_string: redis://localhost:6379 ==> (Not needed)
(Not captured) ==> db.query.text: GET myKey
(Not captured) ==> db.namespace: 0

[dyladan]

Changing to a feature request because this isn't wrong it's just old.

According to https://github.com/open-telemetry/semantic-conventions/blob/main/docs/database/database-spans.md we shouldn't update database instrumentations until they're stabilized in semconv, so this is on hold.