Skip to content

logs: SEVERITY_NUMBER_UNSPECIFIED can be used as severity_number is optional #736

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

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

logs: SEVERITY_NUMBER_UNSPECIFIED can be used as severity_number is optional #736

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ef7fd0d
logs: SEVERITY_NUMBER_UNSPECIFIED can be used as severity_number is o…
pellared Nov 3, 2025
68a5c12
add PR number
pellared Nov 3, 2025
44838d1
Fix typo in CHANGELOG.md
pellared Nov 3, 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 @@ -10,6 +10,8 @@ The full list of changes can be found in the compare view for the respective rel

### Fixed

- logs: `SEVERITY_NUMBER_UNSPECIFIED` can be used as the `severity_number` field is optional. [#736](https://github.com/open-telemetry/opentelemetry-proto/pull/736)

### Removed

## 1.9.0 - 2025-10-31
Expand Down
1 change: 0 additions & 1 deletion opentelemetry/proto/logs/v1/logs.proto
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -85,7 +85,6 @@ message ScopeLogs {

// Possible values for LogRecord.SeverityNumber.
enum SeverityNumber {
// UNSPECIFIED is the default SeverityNumber, it MUST NOT be used.
SEVERITY_NUMBER_UNSPECIFIED = 0;
SEVERITY_NUMBER_TRACE = 1;
SEVERITY_NUMBER_TRACE2 = 2;
Expand Down