Set Severity Text = WARN as defined#3566
Merged
ocelotl merged 4 commits intoopen-telemetry:mainfrom Feb 10, 2024
pegasas:issues3548
Merged
Set Severity Text = WARN as defined#3566ocelotl merged 4 commits intoopen-telemetry:mainfrom pegasas:issues3548
ocelotl merged 4 commits intoopen-telemetry:mainfrom
pegasas:issues3548
Conversation
srikanthccv
approved these changes
Dec 31, 2023
6 tasks
ocelotl
approved these changes
Feb 1, 2024
auto-merge was automatically disabled
February 1, 2024 16:28
Pull Request is not mergeable
auto-merge was automatically disabled
February 9, 2024 18:24
Pull Request is not mergeable
Krishnachaitanyakc
added a commit
to Krishnachaitanyakc/opentelemetry-python
that referenced
this pull request
Mar 25, 2026
The OTel specification defines the severity text for the highest severity range as "FATAL", but the Python SDK was passing through Python's native "CRITICAL" level name unchanged. This is the same class of bug that was previously fixed for WARNING -> WARN in open-telemetry#3566. Fixes open-telemetry#4984
4 tasks
Krishnachaitanyakc
added a commit
to Krishnachaitanyakc/opentelemetry-python
that referenced
this pull request
Mar 25, 2026
The OTel specification defines the severity text for the highest severity range as "FATAL", but the Python SDK was passing through Python's native "CRITICAL" level name unchanged. This is the same class of bug that was previously fixed for WARNING -> WARN in open-telemetry#3566. Fixes open-telemetry#4984
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.
Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes #3548
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Does This PR Require a Contrib Repo Change?
Answer the following question based on these examples of changes that would require a Contrib Repo Change:
The OTel specification has changed which prompted this PR to update the method interfaces of
opentelemetry-api/oropentelemetry-sdk/The method interfaces of
test/utilhave changedScripts in
scripts/that were copied over to the Contrib repo have changedConfiguration files that were copied over to the Contrib repo have changed (when consistency between repositories is applicable) such as in
pyproject.tomlisort.cfg.flake8When a new
.github/CODEOWNERis addedMajor changes to project information, such as in:
README.mdCONTRIBUTING.mdYes. - Link to PR:
No.
Checklist: