db.operation.parameter.<key> should not be captured for batch operations#2034
Merged
lmolkova merged 3 commits intoopen-telemetry:mainfrom Mar 29, 2025
Merged
Conversation
trask
changed the title
db.operation.parameter.<key> should not be captured on batch operationsdb.operation.parameter.<key> should not be captured for batch operations
trask
force-pushed
the
batch-operation-parameters
branch
from
a622852 to
d7776ea
Compare
lmolkova
approved these changes
Mar 29, 2025
lmolkova
moved this from Untriaged
to Needs More Approval
in Semantic Conventions Triage
maryliag
approved these changes
Mar 29, 2025
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
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.
Fixes #2026
It is not clear if/how to capture them on batch operations, so let's explicitly exclude them for now.