rename processor specifies a list of fields to rename. Under the
key, each entry contains a
from: old-key and a
to: new-key pair, where:
fromis the original field name. It’s supported to use
fromand rename keys in the event metadata instead of event fields.
tois the target field name
rename processor cannot be used to overwrite fields. To overwrite fields
either first rename the target field, or use the
drop_fields processor to drop
the field and then rename the field.
You can rename fields to resolve field name conflicts. For example, if an
event has two fields,
b is a subfield of
scalar values results in an Elasticsearch error at ingest time. The assignment
"c.b": 2} would result in an error because
c is an object and cannot be
assigned a scalar value. To prevent this conflict, rename
before assigning values.
processors: - rename: fields: - from: "a.g" to: "e.d" ignore_missing: false fail_on_error: true
rename processor has the following configuration settings:
(Optional) If set to true, no error is logged in case a key
which should be renamed is missing. Default is
(Optional) If set to true, in case of an error the renaming of
fields is stopped and the original event is returned. If set to false, renaming
continues also if an error happened during renaming. Default is
See Conditions for a list of supported conditions.
You can specify multiple
rename processors under the
Intro to Kibana
ELK for Logs & Metrics