Skip to content

Unset log record severity is not INFO #4509

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
pellared wants to merge 16 commits into from
Closed

Unset log record severity is not INFO #4509

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
16 commits
Select commit Hold shift + click to select a range
03e9737
Unset log record severity is not INFO
pellared May 13, 2025
81f64da
Update changelog entry
pellared May 13, 2025
1a08dda
SeverityNumber zero value exception
pellared May 13, 2025
69fd343
Refine
pellared May 13, 2025
7ef0c06
Update CHANGELOG.md
pellared May 13, 2025
12c6820
Merge branch 'main' into rem-interpet
pellared May 14, 2025
2634f7b
Update CHANGELOG.md
pellared May 14, 2025
bc37f7e
Update data-model.md
pellared May 14, 2025
28fd201
Update supplementary-guidelines.md
pellared May 14, 2025
c1d0f94
Replace with better guidelines
pellared May 15, 2025
1f9e36b
Format
pellared May 15, 2025
63f183a
Refine
pellared May 15, 2025
3ab4568
Merge branch 'main' into rem-interpet
pellared May 20, 2025
297ab80
Merge branch 'main' into rem-interpet
pellared May 22, 2025
a8ffe4b
Merge branch 'main' into rem-interpet
pellared May 23, 2025
cf91cc0
Merge branch 'main' into rem-interpet
pellared May 27, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,8 @@ release.

- Add optional `Event Name` parameter to `Logger.Enabled` and `LogRecordProcessor.Enabled`.
([#4489](https://github.com/open-telemetry/opentelemetry-specification/pull/4489))
- Remove the suggestion that backends or UI may represent log records with unset `SeverityNumber` and `SeverityText` as INFO severity.
([#4509](https://github.com/open-telemetry/opentelemetry-specification/pull/4509))

### Baggage

Expand Down
6 changes: 0 additions & 6 deletions specification/logs/data-model.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -328,12 +328,6 @@ For example if the source format has an "Informational" log level and no other
log levels with similar meaning then it is recommended to use
`SeverityNumber=9` for "Informational".

Source formats that do not define a concept of severity or log level MAY omit
`SeverityNumber` and `SeverityText` fields. Backend and UI may represent log
Comment thread
pellared marked this conversation as resolved.
records with missing severity information distinctly or may interpret log
records with missing `SeverityNumber` and `SeverityText` fields as if the
`SeverityNumber` was set equal to INFO (numeric value of 9).

#### Reverse Mapping

When performing a reverse mapping from `SeverityNumber` to a specific format
Expand Down
Loading