fix: map CRITICAL severity text to FATAL per OTel spec#4999
Open
themavik wants to merge 1 commit intoopen-telemetry:mainfrom
Open
fix: map CRITICAL severity text to FATAL per OTel spec#4999themavik wants to merge 1 commit intoopen-telemetry:mainfrom
themavik wants to merge 1 commit intoopen-telemetry:mainfrom
Conversation
…y#4984) Root cause: Python's CRITICAL log level was mapped to severity text 'CRITICAL' instead of 'FATAL' as specified in the OpenTelemetry Logs Data Model specification. Made-with: Cursor
|
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
2 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.
Summary
Fixes #4984.
Root cause: Python's
CRITICALlog level was mapped to severity textCRITICALinstead ofFATALas specified in the OpenTelemetry Logs Data Model specification.Fix: Updated the severity text mapping so
CRITICALmaps toFATAL.Changes
Testing