• Plugin version: v3.5.9 (Other versions)
• Released on: 2025-10-31
• Changelog

For questions about the plugin, open a topic in theDiscuss forums. For bugs or feature requests, open an issue inGithub. For the list of Elastic supported plugins, please consult theElastic Support Matrix.

The mutate filter allows you to perform general mutations on fields. You can rename, replace, and modify fields in your events.

Mutations in a config file are executed in this order:

• coerce
• rename
• update
• replace
• convert
• gsub
• uppercase
• capitalize
• lowercase
• strip
• split
• join
• merge
• copy

Each mutation must be in its own code block if the sequence of operations needs to be preserved.

Example:

filter {    mutate {        split => { "hostname" => "." }        add_field => { "shortHostname" => "%{[hostname][0]}" }    }    mutate {        rename => {"shortHostname" => "hostname"}    }}

This plugin supports the following configuration options plus theCommon options described later.

Also seeCommon options for a list of options supported by all filter plugins.

• Value type ishash
• There is no default value for this setting.

Convert a field’s value to a different type, like turning a string to an integer. If the field value is an array, all members will be converted. If the field is a hash no action will be taken.

Conversion insights

The values are converted using Ruby semantics. Be aware that usingfloat andfloat_eu converts the value to a double-precision 64-bit IEEE 754 floating point decimal number. In order to maintain precision due to the conversion, you should use adouble in the Elasticsearch mappings.

Valid conversion targets, and their expected behaviour with different inputs are:

• integer:

  • strings are parsed; comma-separators are supported (e.g., the string"1,000" produces an integer with value of one thousand); when strings have decimal parts, they aretruncated.
  • floats and decimals aretruncated (e.g.,3.99 becomes3,-2.7 becomes-2)
  • boolean true and boolean false are converted to1 and0 respectively

• integer_eu:

  • same asinteger, except string values support dot-separators and comma-decimals (e.g.,"1.000" produces an integer with value of one thousand)

• float:

  • integers are converted to floats
  • strings are parsed; comma-separators and dot-decimals are supported (e.g.,"1,000.5" produces a float with value of one thousand and one half)
  • boolean true and boolean false are converted to1.0 and0.0 respectively

• float_eu:

  • same asfloat, except string values support dot-separators and comma-decimals (e.g.,"1.000,5" produces a float with value of one thousand and one half)

• string:

  • all values are stringified and encoded with UTF-8

• boolean:

  • integer 0 is converted to booleanfalse
  • integer 1 is converted to booleantrue
  • float 0.0 is converted to booleanfalse
  • float 1.0 is converted to booleantrue
  • strings"true","t","yes","y","1"`and `"1.0" are converted to booleantrue
  • strings"false","f","no","n","0" and"0.0" are converted to booleanfalse
  • empty strings are converted to booleanfalse
  • all other values pass straight through without conversion and log a warning message
  • for arrays each value gets processed separately using rules above

This plugin can convert multiple fields in the same document, see the example below.

Example:

filter {  mutate {    convert => {      "fieldname" => "integer"      "booleanfield" => "boolean"    }  }}

• Value type ishash
• There is no default value for this setting.

Copy an existing field to another field. Existing target field will be overriden.

Example:

filter {  mutate {     copy => { "source_field" => "dest_field" }  }}

• Value type isarray
• There is no default value for this setting.

Match a regular expression against a field value and replace all matches with a replacement string. Only fields that are strings or arrays of strings are supported. For other kinds of fields no action will be taken.

This configuration takes an array consisting of 3 elements per field/substitution.

Be aware of escaping any backslash in the config file.

Example:

filter {  mutate {    gsub => [      # replace all forward slashes with underscore      "fieldname", "/", "_",      # replace backslashes, question marks, hashes, and minuses      # with a dot "."      "fieldname2", "[\\?#-]", "."    ]  }}

• Value type ishash
• There is no default value for this setting.

Join an array with a separator character or string. Does nothing on non-array fields.

Example:

filter {  mutate {    join => { "fieldname" => "," }  }}

• Value type isarray
• There is no default value for this setting.

Convert a string to its lowercase equivalent.

Example:

filter {  mutate {    lowercase => [ "fieldname" ]  }}

• Value type ishash
• There is no default value for this setting.

Merge two fields of arrays or hashes. String fields will be automatically be converted into an array, so:

`array` + `string` will work`string` + `string` will result in an 2 entry array in `dest_field``array` and `hash` will not work

Example:

filter {  mutate {     merge => { "dest_field" => "added_field" }  }}

• Value type ishash
• There is no default value for this setting.

Set the default value of a field that exists but is null

Example:

filter {  mutate {    # Sets the default value of the 'field1' field to 'default_value'    coerce => { "field1" => "default_value" }  }}

• Value type ishash
• There is no default value for this setting.

Rename one or more fields.

If the destination field already exists, its value is replaced.

If one of the source fields doesn’t exist, no action is performed for that field. (This is not considered an error; thetag_on_failure tag is not applied.)

When renaming multiple fields, the order of operations is not guaranteed.

Example:

filter {  mutate {    # Renames the 'HOSTORIP' field to 'client_ip'    rename => { "HOSTORIP" => "client_ip" }  }}

• Value type ishash
• There is no default value for this setting.

Replace the value of a field with a new value, or add the field if it doesn’t already exist. The new value can include%{foo} strings to help you build a new value from other parts of the event.

Example:

filter {  mutate {    replace => { "message" => "%{source_host}: My new message" }  }}

• Value type ishash
• There is no default value for this setting.

Split a field to an array using a separator character or string. Only works on string fields.

Example:

filter {  mutate {     split => { "fieldname" => "," }  }}

• Value type isarray
• There is no default value for this setting.

Strip whitespace from field. NOTE: this only works on leading and trailing whitespace.

Example:

filter {  mutate {     strip => ["field1", "field2"]  }}

• Value type ishash
• There is no default value for this setting.

Update an existing field with a new value. If the field does not exist, then no action will be taken.

Example:

filter {  mutate {    update => { "sample" => "My new message" }  }}

• Value type isarray
• There is no default value for this setting.

Convert a string to its uppercase equivalent.

Example:

filter {  mutate {    uppercase => [ "fieldname" ]  }}

• Value type isarray
• There is no default value for this setting.

Convert a string to its capitalized equivalent.

Example:

filter {  mutate {    capitalize => [ "fieldname" ]  }}

• Value type isstring
• The default value for this setting is_mutate_error

If a failure occurs during the application of this mutate filter, the rest of the operations are aborted and the provided tag is added to the event.

These configuration options are supported by all filter plugins:

• Value type ishash
• Default value is{}

If this filter is successful, add any arbitrary fields to this event. Field names can be dynamic and include parts of the event using the%{field}.

Example:

filter {  mutate {    add_field => { "foo_%{somefield}" => "Hello world, from %{host}" }  }}

# You can also add multiple fields at once:filter {  mutate {    add_field => {      "foo_%{somefield}" => "Hello world, from %{host}"      "new_field" => "new_static_value"    }  }}

If the event has field"somefield" == "hello" this filter, on success, would add fieldfoo_hello if it is present, with the value above and the%{host} piece replaced with that value from the event. The second example would also add a hardcoded field.

• Value type isarray
• Default value is[]

If this filter is successful, add arbitrary tags to the event. Tags can be dynamic and include parts of the event using the%{field} syntax.

Example:

filter {  mutate {    add_tag => [ "foo_%{somefield}" ]  }}

# You can also add multiple tags at once:filter {  mutate {    add_tag => [ "foo_%{somefield}", "taggedy_tag"]  }}

If the event has field"somefield" == "hello" this filter, on success, would add a tagfoo_hello (and the second example would of course add ataggedy_tag tag).

• Value type isboolean
• Default value istrue

Disable or enable metric logging for this specific plugin instance by default we record all the metrics we can, but you can disable metrics collection for a specific plugin.

• Value type isstring
• There is no default value for this setting.

Add a uniqueID to the plugin configuration. If no ID is specified, Logstash will generate one. It is strongly recommended to set this ID in your configuration. This is particularly useful when you have two or more plugins of the same type, for example, if you have 2 mutate filters. Adding a named ID in this case will help in monitoring Logstash when using the monitoring APIs.

filter {  mutate {    id => "ABC"  }}

• Value type isboolean
• Default value isfalse

Call the filter flush method at regular interval. Optional.

• Value type isarray
• Default value is[]

If this filter is successful, remove arbitrary fields from this event. Fields names can be dynamic and include parts of the event using the %{field} Example:

filter {  mutate {    remove_field => [ "foo_%{somefield}" ]  }}

# You can also remove multiple fields at once:filter {  mutate {    remove_field => [ "foo_%{somefield}", "my_extraneous_field" ]  }}

If the event has field"somefield" == "hello" this filter, on success, would remove the field with namefoo_hello if it is present. The second example would remove an additional, non-dynamic field.

• Value type isarray
• Default value is[]

If this filter is successful, remove arbitrary tags from the event. Tags can be dynamic and include parts of the event using the%{field} syntax.

Example:

filter {  mutate {    remove_tag => [ "foo_%{somefield}" ]  }}

# You can also remove multiple tags at once:filter {  mutate {    remove_tag => [ "foo_%{somefield}", "sad_unwanted_tag"]  }}

If the event has field"somefield" == "hello" this filter, on success, would remove the tagfoo_hello if it is present. The second example would remove a sad, unwanted tag as well.