This functionality is experimental and may be changed or removed completely in a future release. Elastic will take a best effort approach to fix any issues, but experimental features are not subject to the support SLA of official GA features.
« Add Observer metadata DNS Reverse Lookup »
Elastic Docs ›Journalbeat Reference [7.4] ›Configuring Journalbeat ›Filter and enhance the exported data

Dissect strings

edit

Dissect strings

edit

The dissect processor tokenizes incoming strings using defined patterns.

processors:
- dissect:
    tokenizer: "%{key1} %{key2}"
    field: "message"
    target_prefix: "dissect"

The dissect processor has the following configuration settings:

field
(Optional) The event field to tokenize. Default is message.
target_prefix
(Optional) The name of the field where the values will be extracted. When an empty string is defined, the processor will create the keys at the root of the event. Default is dissect. When the target key already exists in the event, the processor won’t replace it and log an error; you need to either drop or rename the key before using dissect.

For tokenization to be successful, all keys must be found and extracted, if one of them cannot be found an error will be logged and no modification is done on the original event.

A key can contain any characters except reserved suffix or prefix modifiers: /,&, + and ?.

See Conditions for a list of supported conditions.

« Add Observer metadata DNS Reverse Lookup »