Functionbeat will reach End of Support on October 18, 2023. You should consider moving your deployments to the more versatile and efficient Elastic Serverless Forwarder.
« Decode XML Wineventlog Detect mime type »
Elastic Docs ›Functionbeat Reference [8.5] ›Configure Functionbeat ›Filter and enhance data with processors

Decompress gzip fields

edit
IMPORTANT: This documentation is no longer updated. Refer to Elastic's version policy and the latest documentation.

Decompress gzip fields

edit

The decompress_gzip_field processor specifies a field to gzip decompress. The field key contains a from: old-key and a to: new-key pair. from is the origin and to the target name of the field.

To overwrite fields either first rename the target field or use the drop_fields processor to drop the field and then decompress the field.

processors:
  - decompress_gzip_field:
      field:
        from: "field1"
        to: "field2"
      ignore_missing: false
      fail_on_error: true

In the example above: - field1 is decoded in field2

The decompress_gzip_field processor has the following configuration settings:

ignore_missing
(Optional) If set to true, no error is logged in case a key which should be decompressed is missing. Default is false.
fail_on_error
(Optional) If set to true, in case of an error the decompression of fields is stopped and the original event is returned. If set to false, decompression continues also if an error happened during decoding. Default is true.

See Conditions for a list of supported conditions.

« Decode XML Wineventlog Detect mime type »