Skip to content

Commit 5b0cdae

Browse files
authored
Update log-level.md (#5207)
1 parent 2b8c6a4 commit 5b0cdae

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

docs/search/get-started-with-search/search-page/log-level.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -58,6 +58,10 @@ If the log message is in JSON format, the log level detection method searches fo
5858

5959
And if the log message is in a non-JSON format, the log level detection method looks for keywords such as "debug", "info/information", "warn/warning", and "error". If any of these keywords are found in the log message, their corresponding values will be considered and displayed in the results.
6060

61+
:::note
62+
Sumo Logic does not have any source specific special logic for log level extraction except for OTEL. For OTEL sources, `severityTextField` is used with `severityNumber` as fallback, if `severityTextField` is not populated. For more details, refer to the [OpenTelemetry Logs Data Model](https://opentelemetry.io/docs/specs/otel/logs/data-model/).
63+
:::
64+
6165
:::info
6266
If multiple log levels are detected in the message, they will be prioritized in the following order: ERROR > WARN > INFO > DEBUG.
6367
:::

0 commit comments

Comments
 (0)