Indicate that exception.message attribute may contain sensitive information#3310
Merged
lmolkova merged 5 commits intoopen-telemetry:mainfrom Jan 23, 2026
Merged
Conversation
lmolkova
commented
Jan 19, 2026
|
This PR contains changes to area(s) that do not have an active SIG/project and will be auto-closed:
Such changes may be rejected or put on hold until a new SIG/project is established. Please refer to the Semantic Convention Areas |
Merged
arminru
approved these changes
Jan 20, 2026
pellared
approved these changes
Jan 20, 2026
lmolkova
commented
Jan 20, 2026
trask
reviewed
Jan 21, 2026
…kova/semantic-conventions into exception-message-sensitive
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
4 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.
Towards #2967
exception.messageis recorded by default on span-events (for now) and logs. It's stable and too useful.At the same time, there are known cases when exception message contains things like connection strings or user_ids.
It is not recommended to include sensitive information in exception messages.
In many cases, exceptions are thrown and recorded as telemetry by different components. As a result, it may not be possible for instrumentation to prevent sensitive information from being recorded.
Additional processing in the telemetry pipeline may be necessary to remove sensitive information.
So adding sensitivity warning on the attribute. #1594 would improve this story (by making sensitivity note machine readable).