Decode JSON fields
editDecode JSON fields
editThe decode_json_fields
processor decodes fields containing JSON strings and
replaces the strings with valid JSON objects.
Example
edit- decode_json_fields: fields: ["field1", "field2", ...] process_array: false max_depth: 1 target: "" overwrite_keys: false add_error_key: true
Configuration settings
editElastic Agent processors execute before ingest pipelines, which means that your processor configurations cannot refer to fields that are created by ingest pipelines or Logstash. For more limitations, refer to What are some limitations of using processors?
Name | Required | Default | Description |
---|---|---|---|
|
Yes |
Fields containing JSON strings to decode. |
|
|
No |
|
Whether to process arrays. |
|
No |
|
Maximum parsing depth. A value of |
|
No |
Field under which the decoded JSON will be written. By default, the decoded JSON object replaces the string field from which it was read. To merge the decoded JSON fields into the root of the event, specify |
|
|
No |
|
Whether existing keys in the event are overwritten by keys from the decoded JSON object. |
|
No |
Whether keys in the decoded JSON should be recursively de-dotted and expanded into a hierarchical object structure. For example, |
|
|
No |
|
If |
|
No |
JSON key that’s used as the document ID. If configured, the field will be removed from the original JSON document and stored in |