You are looking at preliminary documentation for a future release. Not what you want? See the current release documentation.
decode_json_fields processor decodes fields containing JSON strings and
replaces the strings with valid JSON objects.
processors: - decode_json_fields: fields: ["field1", "field2", ...] process_array: false max_depth: 1 target: "" overwrite_keys: false add_error_key: true
decode_json_fields processor has the following configuration settings:
- The fields containing JSON strings to decode.
- (Optional) A boolean that specifies whether to process arrays. The default is false.
(Optional) The maximum parsing depth. A value of 1 will decode the
JSON objects in fields indicated in
fields, a value of 2 will also decode the objects embedded in the fields of these parsed documents. The default is 1.
(Optional) The 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
targetwith an empty string (
target: ""). Note that the
target:) is treated as if the field was not set at all.
- (Optional) A boolean that specifies whether keys that already exist in the event are overwritten by keys from the decoded JSON object. The default value is false.
(Optional) If it set to true, in case of error while decoding json keys
errorfield is going to be part of event with error message. If it set to false, there will not be any error in event’s field. Even error occurs while decoding json keys. The default value is false.
(Optional) JSON key to use as the document id. If configured,
the field will be removed from the original json document and stored in