Skip to content

Description conflicts between spec and proto on UNSPECIFIED severity number #4716

New issue
New issue
Open
open-telemetry/opentelemetry-proto
#736
Open
Description conflicts between spec and proto on UNSPECIFIED severity number#4716
open-telemetry/opentelemetry-proto
#736
Assignees
pellared
Labels
sig-issueA specific SIG should look into this before discussing at the specspec:logsRelated to the specification/logs directoryspec:protocolRelated to the specification/protocol directory
@tisonkun

Description

@tisonkun
tisonkun
opened on Oct 29, 2025

From the proto definition, 0 MUST NOT be used.

https://github.com/open-telemetry/opentelemetry-proto/blob/68f9c6329ca91f96333ee5b240e305945b122b70/opentelemetry/proto/logs/v1/logs.proto#L87-L88

// Possible values for LogRecord.SeverityNumber.
enum SeverityNumber {
  // UNSPECIFIED is the default SeverityNumber, it MUST NOT be used.
  SEVERITY_NUMBER_UNSPECIFIED = 0;

Originally posted by @tisonkun in #4552

Metadata

Metadata

Assignees

Labels

sig-issueA specific SIG should look into this before discussing at the specspec:logsRelated to the specification/logs directoryspec:protocolRelated to the specification/protocol directory

Type

No type

Projects

Logs SIG

Status

No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions