add experimental option to avoid lettuce noisy span events #14750
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
trask
reviewed
Sep 22, 2025
…nstrumentation into redis-lettuce-noisy-span-events
laurit
reviewed
Sep 23, 2025
laurit
reviewed
Sep 23, 2025
...g/src/main/java/io/opentelemetry/instrumentation/lettuce/v5_1/AbstractLettuceClientTest.java
Outdated
Show resolved
Hide resolved
laurit
approved these changes
Sep 26, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using
lettuce, the current instrumentation produces lotsredis.encode.startandredis.encode.endspan events which can be noisy.otel.instrumentation.lettuce.experimental.command-encoding-events.enabledconfiguration option, defaults tofalsethus a minor breaking change.TracedCommandlettuce classThis solves the same issue that was reported in ApplicationInsights-Java#1586 and elastic-otel-java#796, for now the workaround is to post-process and filter the span events at the collector level.