Edge Delta Parse Severity Processor

The Edge Delta parse severity processor parses the severity level from another field.

4 minute read

Overview

The parse severity processor sets the severity_text field in the data item based on a particular field. You can map your expected field values to the set severity_text levels. The input severity level must be a field value so you may need to parse your body first. The severity text is not case sensitive.

Try this with Pipeline Quickstart: Normalize Severity.

Configuration

The severity_text that the Edge Delta application expects are:

fatal
error
warn
info
debug
trace

To configure the parse severity processor you specify the source field and provide the level mapping: In this instance, the source logs have been parsed into attributes["level"] and they are mapped as follows in the configuration:

Info - info
Notice - info
Warning - warn
Error - error
Critical - error
Alert - fatal
Emergency - fatal

YAML version:

- name: Multi Processor
  type: sequence
  processors:
  - type: ottl_transform
    metadata: '{"id":"WZlLxt0gC4VbRiQWfoCmQ","type":"parse-severity","name":"Parse
      Severity Fields"}'
    data_types:
    - log
    statements: |-
      set(cache["lookup"], {"trace": "trace", "debug": "debug", "info": "info", "notice": "info", "warning": "warn", "error": "error", "critical": "error", "fatal": "fatal", "alert": "fatal", "emergency": "fatal"})
      set(severity_text, cache["lookup"][ToLowerCase(attributes["level"])])

Options

condition

The condition parameter contains a conditional phrase of an OTTL statement. It restricts operation of the processor to only data items where the condition is met. Those data items that do not match the condition are passed without processing. You configure it in the interface and an OTTL condition is generated. It is optional. You can select one of the following operators:

Operator	Name	Description	Example
`==`	Equal to	Returns `true` if both values are exactly the same	`attributes["status"] == "OK"`
`!=`	Not equal to	Returns `true` if the values are not the same	`attributes["level"] != "debug"`
`>`	Greater than	Returns `true` if the left value is greater than the right	`attributes["duration_ms"] > 1000`
`>=`	Greater than or equal	Returns `true` if the left value is greater than or equal to the right	`attributes["score"] >= 90`
`<`	Less than	Returns `true` if the left value is less than the right	`attributes["load"] < 0.75`
`<=`	Less than or equal	Returns `true` if the left value is less than or equal to the right	`attributes["retries"] <= 3`
`matches`	Regex match	Returns `true` if the string matches a regular expression	`isMatch(attributes["name"], ".*\\.name$"`

It is defined in YAML as follows:

- name: _multiprocessor
  type: sequence
  processors:
  - type: <processor type>
    condition: attributes["request"]["path"] == "/json/view"

Parse from

Specify the field containing the severity text.

trace

Specify which levels will be assigned to "severity_text": "trace".

debug

Specify which levels will be assigned to "severity_text": "debug".

info

Specify which levels will be assigned to "severity_text": "info".

warn

Specify which levels will be assigned to "severity_text": "warn".

error

Specify which levels will be assigned to "severity_text": error".

fatal

Specify which levels will be assigned to "severity_text": "fatal".

Final

Determines whether successfully processed data items should continue through the remaining processors in the same processor stack. If final is set to true, data items output by this processor are not passed to subsequent processors within the node—they are instead emitted to downstream nodes in the pipeline (e.g., a destination). Failed items are always passed to the next processor, regardless of this setting.

The UI provides a slider to configure this setting. The default is false. It is defined in YAML as follows:

- name: multiprocessor
  type: sequence
  processors:
    - type: <processor type>
    final: true

Keep original telemetry item

Controls whether the original, unmodified telemetry item is preserved after processing. If keep_item is set to true, the processor emits both:

The original telemetry item (e.g., a log), and
Any new item generated by the processor (e.g., a metric extracted from the log)

Both items are passed to the next processor in the stack unless final is also set.

Interaction with final

If final: true is enabled, any successfully processed data items, whether original, newly created, or both, exit the processor stack or node immediately. No subsequent processors within the same node are evaluated, although downstream processing elsewhere in the pipeline continues. This means:

If keep_item: true and final: true, both the original and processed items bypass the remaining processors in the current node and are forwarded to downstream nodes (such as destinations).
If keep_item: false and final: true, only the processed item continues beyond this processor, skipping subsequent processors in the stack, and the original item is discarded.

Note: If the data item fails to be processed, final has no effect, the item continues through the remaining processors in the node regardless of the keep_item setting.

The app provides a slider to configure keep_item. The default is false.

- name: ed_gateway_output_a3fa_multiprocessor
  type: sequence
  processors:
    - type: <processor_type>
      keep_item: true
      final: true