Document database semantic convention opt-in - #4985
Open
miachillgood wants to merge 1 commit into
Open
Conversation
Pull request dashboard statusWaiting on reviewers · refreshed 2026-08-22 05:24 UTC Review the latest changes. Status above doesn't look right?
|
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
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.
Description
Document the database semantic convention migration modes in each instrumentation module that currently supports them. The new sections explain the
databaseanddatabase/dupvalues, comma-separated opt-ins, and the legacy default behavior.Because the instrumentation reference pages render these module docstrings, the guidance appears directly in each affected package's documentation.
Fixes #4980
Type of change
How Has This Been Tested?
python3 -m compilealluvx pre-commit run --files <changed files>(ruff, ruff-format, and Towncrier formatting passed)Does This PR Require a Core Repo Change?
Checklist: