Decompress gzip fields
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is generally available and ready for production usage. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Generally available
Stack
Generally available
The decompress_gzip_field processor specifies a field to gzip decompress.
To overwrite fields, either first rename the target field, or use the drop_fields processor to drop the field, and then decompress the field.
In this example, field1 is decompressed in field2.
- decompress_gzip_field:
field:
from: "field1"
to: "field2"
ignore_missing: false
fail_on_error: true
Elastic 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 |
|---|---|---|---|
field |
Yes | Contains: * from: "old-key", where from is the origin* to: "new-key", where to is the target field name |
|
ignore_missing |
No | false |
Whether to ignore missing keys. If true, no error is logged if a key that should be decompressed is missing. |
fail_on_error |
No | true |
If true and an error occurs, decompression of fields is stopped, and the original event is returned. If false, decompression continues even if an error occurs during decoding. |
See Conditions for a list of supported conditions.