For other versions, see theVersioned plugin docs.
For plugins not bundled by default, it is easy to install by running bin/logstash-plugin install logstash-filter-range
. See Working with plugins for more details.
For questions about the plugin, open a topic in the Discuss forums. For bugs or feature requests, open an issue in Github.For the list of Elastic supported plugins, please consult the Elastic Support Matrix.
This filter is used to check that certain fields are within expected size/length ranges.Supported types are numbers and strings.Numbers are checked to be within numeric value range.Strings are checked to be within string length range.More than one range can be specified for same fieldname, actions will be applied incrementally.When field value is within a specified range an action will be taken.Supported actions are drop event, add tag, or add field with specified value.
Example use cases are for histogram-like tagging of eventsor for finding anomaly values in fields or too big events that should be dropped.
This plugin supports the following configuration options plus the Common Options described later.
Also see Common Options for a list of options supported by allfilter plugins.
false
Negate the range match logic, events should be outsize of the specified range to match.
[]
An array of field, min, max, action tuples.Example:
filter { range { ranges => [ "message", 0, 10, "tag:short", "message", 11, 100, "tag:medium", "message", 101, 1000, "tag:long", "message", 1001, 1e1000, "drop", "duration", 0, 100, "field:latency:fast", "duration", 101, 200, "field:latency:normal", "duration", 201, 1000, "field:latency:slow", "duration", 1001, 1e1000, "field:latency:outlier", "requests", 0, 10, "tag:too_few_%{host}_requests" ] }}
Supported actions are drop tag or field with specified value.Added tag names and field names and field values can have %{dynamic}
values.
The following configuration options are supported by all filter plugins:
Setting | Input type | Required |
---|---|---|
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
{}
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 { range { add_field => { "foo_%{somefield}" => "Hello world, from %{host}" } }}
# You can also add multiple fields at once:filter { range { 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 field foo_hello
if it is present, with thevalue above and the %{host}
piece replaced with that value from theevent. The second example would also add a hardcoded field.
[]
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 { range { add_tag => [ "foo_%{somefield}" ] }}
# You can also add multiple tags at once:filter { range { add_tag => [ "foo_%{somefield}", "taggedy_tag"] }}
If the event has field "somefield" == "hello"
this filter, on success,would add a tag foo_hello
(and the second example would of course add a taggedy_tag
tag).
true
Disable or enable metric logging for this specific plugin instanceby default we record all the metrics we can, but you can disable metrics collectionfor a specific plugin.
Add a unique ID
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 usefulwhen you have two or more plugins of the same type, for example, if you have 2 range filters.Adding a named ID in this case will help in monitoring Logstash when using the monitoring APIs.
filter { range { id => "ABC" }}
false
Call the filter flush method at regular interval.Optional.
[]
If this filter is successful, remove arbitrary fields from this event.Example:
filter { range { remove_field => [ "foo_%{somefield}" ] }}
# You can also remove multiple fields at once:filter { range { remove_field => [ "foo_%{somefield}", "my_extraneous_field" ] }}
If the event has field "somefield" == "hello"
this filter, on success,would remove the field with name foo_hello
if it is present. The secondexample would remove an additional, non-dynamic field.
[]
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 { range { remove_tag => [ "foo_%{somefield}" ] }}
# You can also remove multiple tags at once:filter { range { remove_tag => [ "foo_%{somefield}", "sad_unwanted_tag"] }}
If the event has field "somefield" == "hello"
this filter, on success,would remove the tag foo_hello
if it is present. The second examplewould remove a sad, unwanted tag as well.