[db/oracledb] Update area name to oracledb from oracle#3316
Merged
lmolkova merged 2 commits intoopen-telemetry:mainfrom Jan 21, 2026
Merged
[db/oracledb] Update area name to oracledb from oracle#3316lmolkova merged 2 commits intoopen-telemetry:mainfrom
lmolkova merged 2 commits intoopen-telemetry:mainfrom
Conversation
geekdave
approved these changes
Jan 21, 2026
Contributor
geekdave
left a comment
There was a problem hiding this comment.
👍 LGTM.
Note: I'm not in any of the requested approvers groups, but I am in the oracle-cloud approvers group, and this change will help to disambiguate the semconv areas for oracle cloud vs oracle db.
lmolkova
approved these changes
Jan 21, 2026
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 #
Changes
update the area name to
oracle.dbfromoracle.Important
Pull requests acceptance are subject to the triage process as described in Issue and PR Triage Management.
PRs that do not follow the guidance above, may be automatically rejected and closed.
Merge requirement checklist
[chore]