Free Report! Gartner® Hype Cycle™ for Monitoring and Observability.Read more

Parse Severity

MetricsLogsTracesBindPlane Agent


The Parse Severity Processor is designed to normalize severity fields in log data into user-defined values, enhancing the consistency and readability of log data. By allowing users to map existing severity values to standard levels, it aids in the uniform analysis and visualization of logs across varied sources.


The processor is essential in environments where logs from different sources use varied severity naming conventions. By mapping these diverse severity indicators to standard values, it ensures that the severity data remains consistent, making it easier to filter, analyze, and generate insights from the log data.


ConditionAn OTTL condition that must evaluate to true for the processor to be applied to the logs, allowing selective processing of entries.
Log Body, Resource, or AttributesSpecifies the location of the severity value in the log entry: in the log body, resource, or attributes.
Severity FieldThe specific field that contains the severity value to be parsed and normalized.
Severity MappingsA mapping that translates current severity values in the logs to standard values, ensuring consistency across different log sources.

Example Configurations

Normalize Severity Levels in Log Data

In this example, the Parse Severity Processor is configured to normalize severity levels from the "level" field in the log body into user-defined standard levels.

observIQ docs - Parse Severity - image 1

Here is a sample log entry:


2  "message": "An error occurred during processing",
3  "level": "err"

The objective is to map the "err" severity level to a standard "error" level for consistency across all log entries. The configuration for the Parse Severity Processor is as follows:

  • Condition: "true" (applies to all logs)

  • Log Body, Resource, or Attributes: Body

  • Severity Field: level

  • Severity Mappings:

    2  "err": "error",
    3  "warning": "warn",
    4  "information": "info",
    5  "debugging": "debug",
    6  "critical": "fatal"

With this setup, when the log entry is processed, the "severity" field is updated as follows:

Log After Processing:

2  "severity": "error"

The severity level "err" is now normalized to "error," allowing for a uniform representation of severity levels across all log entries. This normalization facilitates more straightforward log analysis, filtering, and alerting, especially when dealing with logs from multiple sources with different severity naming conventions.