Add Valkey Instrumentation

[sightseeker]

Description

This PR introduces a new Valkey instrumentation plugin for the OpenTelemetry Python Contrib library.
users can now automatically capture and export Valkey trace data alongside existing OpenTelemetry spans. This fills the gap for applications leveraging Valkey’s Client library, enabling end-to-end distributed tracing without manual span management.

Notes:

• Since the valkey-search module is not yet GA, related tests are intentionally omitted in this PR.

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

• Added unit tests under instrumentation/opentelemetry-instrumentation-valkey/tests/ covering:
  • automatic span creation on Valkey client calls
  • context propagation across async boundaries
  • correct attribute mapping (e.g. db.statement, db.valkey.args_length, db.valkey.database_index, net.peer.name)
• Manual end-to-end test with example app instrumented via opentelemetry-instrumentation-valkey, verified spans in Jaeger backend
• Test configuration:
  • tox -e py38-test-instrumentation-valkey
  • tox -e py39-test-instrumentation-valkey
  • tox -e py310-test-instrumentation-valkey
  • tox -e py311-test-instrumentation-valkey
  • tox -e py312-test-instrumentation-valkey
  • tox -e py313-test-instrumentation-valkey
  • tox -e pypy3-test-instrumentation-valkey
• Lint configuration:
  • tox -e lint-instrumentation-valkey

Does This PR Require a Core Repo Change?

• Yes. – Link to PR:
• No.

Checklist:

• Followed the style guidelines of this project
• Changelogs have been updated (CHANGELOG.md entry under “New Features”)
• Unit tests have been added
• Documentation has been updated (README and Sphinx docs)

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: sightseeker / name: Kohei Saito (6a1c5ef, baf8d66, b5789a8, ea73a0e, 4bbc332, 87633d2, 24ecc80, a08cbb5, 2670aca, abbc9cb, 5fa3068, 4ac33b8, 866c219, 3bef7a4, a45af90, 6f25fac)

[xrmx]

we can test both no?

[sightseeker]

Thank you watching for this PR, sir
But, This is a draft of PR.
Could you waiting for ready.

[sightseeker]

@xrmx
Thank you for your patience. Would you mind taking a look and reviewing this PR?

[zhengkezhou1]

this PR is so large that it is difficult to review. I suggest splitting it into several smaller PRs, as that would make more sense.

[sightseeker]

@zhengkezhou1

Thanks for the feedback! This instrumentation PR is actually a near-one-for-one copy of the existing Redis instrumentation, with only the service-specific bits renamed and a handful of Valkey-specific tweaks. To see how small the diff really is, you can run:

git diff --no-index instrumentation/opentelemetry-instrumentation-redis/src \
                    instrumentation/opentelemetry-instrumentation-valkey/src

git diff --no-index instrumentation/opentelemetry-instrumentation-redis/tests/__init__.py \
                    instrumentation/opentelemetry-instrumentation-valkey/tests/__init__.py

git diff --no-index instrumentation/opentelemetry-instrumentation-redis/tests/test_redis.py \
                    instrumentation/opentelemetry-instrumentation-valkey/tests/test_valkey.py

git diff --no-index instrumentation/opentelemetry-instrumentation-redis/LICENCE \
                    instrumentation/opentelemetry-instrumentation-valkey/LICENCE

git diff --no-index instrumentation/opentelemetry-instrumentation-redis/pyproject.toml \
                    instrumentation/opentelemetry-instrumentation-valkey/pyproject.toml

git diff --no-index instrumentation/opentelemetry-instrumentation-redis/README.rst \
                    instrumentation/opentelemetry-instrumentation-valkey/README.rst

git diff --no-index instrumentation/opentelemetry-instrumentation-redis/test-requirements.txt \
                    instrumentation/opentelemetry-instrumentation-valkey/test-requirements.txt

git diff --no-index tests/opentelemetry-docker-tests/tests/redis/test_redis_functional.py \
                    tests/opentelemetry-docker-tests/tests/valkey/test_valkey_functional.py

Because the core of this PR is simply “copy + rename + small adjustments,” I think a single PR still keeps reviewable granularity. Please let me know if you’d prefer me to split out any particular piece!