From 50d6c36593c45e0a7b8ad18c447c4f4fde79224d Mon Sep 17 00:00:00 2001 From: Stefan Hellkvist Date: Mon, 5 May 2025 16:51:39 +0200 Subject: [PATCH 1/2] This fixes issue #4478 by introducing a SeverityNumber 0 in the specification with the meaning "UNDEFINED" --- specification/logs/data-model.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/specification/logs/data-model.md b/specification/logs/data-model.md index f0db90e8c41..600fa9e1713 100644 --- a/specification/logs/data-model.md +++ b/specification/logs/data-model.md @@ -291,6 +291,7 @@ defines the meaning of `SeverityNumber` value: SeverityNumber range|Range name|Meaning --------------------|----------|------- +0 |UNDEFINED |An event with unset severity. 1-4 |TRACE |A fine-grained debugging event. Typically disabled in default configurations. 5-8 |DEBUG |A debugging event. 9-12 |INFO |An informational event. Indicates that an event happened. @@ -301,7 +302,7 @@ SeverityNumber range|Range name|Meaning Smaller numerical values in each range represent less important (less severe) events. Larger numerical values in each range represent more important (more severe) events. For example `SeverityNumber=17` describes an error that is less -critical than an error with `SeverityNumber=20`. +critical than an error with `SeverityNumber=20`. The exception to this is the zero value (SeverityNumber=0), which, since it means UNDEFINED, cannot be ordered after any importance level. #### Mapping of `SeverityNumber` From 8b14bf7096f56205e23490fe78850bdb4a9903d2 Mon Sep 17 00:00:00 2001 From: Stefan Hellkvist Date: Mon, 5 May 2025 17:23:26 +0200 Subject: [PATCH 2/2] Adding the same syntax to the SeverityNumber example --- specification/logs/data-model.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/specification/logs/data-model.md b/specification/logs/data-model.md index 600fa9e1713..5dabdd702c7 100644 --- a/specification/logs/data-model.md +++ b/specification/logs/data-model.md @@ -302,7 +302,7 @@ SeverityNumber range|Range name|Meaning Smaller numerical values in each range represent less important (less severe) events. Larger numerical values in each range represent more important (more severe) events. For example `SeverityNumber=17` describes an error that is less -critical than an error with `SeverityNumber=20`. The exception to this is the zero value (SeverityNumber=0), which, since it means UNDEFINED, cannot be ordered after any importance level. +critical than an error with `SeverityNumber=20`. The exception to this is the zero value (`SeverityNumber=0`), which, since it means UNDEFINED, cannot be ordered after any importance level. #### Mapping of `SeverityNumber`