• Plugin version: v3.0.3
• Released on: 2017-11-07
• Changelog

For other versions, see theVersioned plugin docs.

For plugins not bundled by default, it is easy to install by runningbin/logstash-plugin install logstash-filter-extractnumbers. SeeWorking with plugins for more details.

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.

This filter automatically extracts all numbers found inside a string

This is useful when you have lines that don’t match a grok pattern or use json but you still need to extract numbers.

Each numbers is returned in a@fields.intX or@fields.floatX field where X indicates the position in the string.

The fields produced by this filter are extra useful used in combination with kibana number plotting features.

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 isstring
• Default value is"message"

The source field for the data. By default is message.

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 {  extractnumbers {    add_field => { "foo_%{somefield}" => "Hello world, from %{host}" }  }}

# You can also add multiple fields at once:filter {  extractnumbers {    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 {  extractnumbers {    add_tag => [ "foo_%{somefield}" ]  }}

# You can also add multiple tags at once:filter {  extractnumbers {    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 extractnumbers filters. Adding a named ID in this case will help in monitoring Logstash when using the monitoring APIs.

filter {  extractnumbers {    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 {  extractnumbers {    remove_field => [ "foo_%{somefield}" ]  }}

# You can also remove multiple fields at once:filter {  extractnumbers {    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 {  extractnumbers {    remove_tag => [ "foo_%{somefield}" ]  }}

# You can also remove multiple tags at once:filter {  extractnumbers {    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.