DB and HTTP semantic convention stability migration for Redis instrumentation#4370
Conversation
MikeGoldsmith
left a comment
There was a problem hiding this comment.
Looks good - thanks @tammy-baylis-swi.
Left some queries about some semconv keys and a couple of suggestions.
|
Please pardon my delay in addressing your feedback @emdneto and @MikeGoldsmith ! Please could you take another pass through this one for Redis instrumentation and semconv opt-in. Current CI/CD failures for |
Np. I realized I left a pending review since last month 😅 Looking into the rstcheck error |
|
If you can resolve the above discussions we can merge :) |
@lzchen done! |
Migrate the Valkey instrumentation (and the shared redis-valkey-base helpers) to support the new stable DB and HTTP semantic conventions via OTEL_SEMCONV_STABILITY_OPT_IN, mirroring what was done for Redis in open-telemetry#4370. - redis-valkey-base: switch helpers to use _semconv stability helpers (_set_db_system, _set_db_statement, _set_db_redis_database_index, _set_http_net_peer_name_client, _set_http_peer_port_client, _set_net_transport) and resolve schema_url via signal-type opt-in - valkey: drop hardcoded attribute keys from KVStoreConfig, mark package as semconv migration, switch tracer schema_url to the stability-aware helper - tests: cover default / database / database/dup / http / http/dup stability modes for db.system, db.statement and connection attrs
Description
Add Redis instrumentor support for when
OTEL_SEMCONV_STABILITY_OPT_INincludesEDIT: This uses now-merged updates from SQLAlchemy PR, no conflicts 🙂
This duplicates all_semconvhelper updates in #4110 at 02adc40Fixes #2930, #2885
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Does This PR Require a Core Repo Change?
Checklist:
See contributing.md for styleguide, changelog guidelines, and more.