---
title: Range filter plugin v3.0.1
description: Plugin version: v3.0.1, Released on: 2017-06-23, Changelog. For other versions, see the overview list. To learn more about Logstash, see the Logstash...
url: https://www.elastic.co/docs/reference/logstash/versioned-plugins/v3-0-1-plugins-filters-range
---

# Range filter plugin v3.0.1

- Plugin version: v3.0.1
- Released on: 2017-06-23
- [Changelog](https://github.com/logstash-plugins/logstash-filter-range/blob/v3.0.1/CHANGELOG.md)

For other versions, see the [overview list](https://www.elastic.co/docs/reference/logstash/versioned-plugins/filter-range-index).
To learn more about Logstash, see the [Logstash Reference](https://www.elastic.co/guide/en/logstash/current/index.html).

## Getting help

For questions about the plugin, open a topic in the [Discuss](http://discuss.elastic.co) forums. For bugs or feature requests, open an issue in [Github](https://github.com/logstash-plugins/logstash-filter-range). For the list of Elastic supported plugins, please consult the [Elastic Support Matrix](https://www.elastic.co/support/matrix#matrix_logstash_plugins).

## Description

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 events or for finding anomaly values in fields or too big events that should be dropped.

## Range Filter Configuration Options

This plugin supports the following configuration options plus the [Common options](#v3.0.1-plugins-filters-range-common-options) described later.

| Setting                                                  | Input type                                                             | Required |
|----------------------------------------------------------|------------------------------------------------------------------------|----------|
| [`negate`](#v3.0.1-plugins-filters-range-negate)`negate` | [boolean](/docs/reference/logstash/plugins/value-types#boolean)boolean | No       |
| [`ranges`](#v3.0.1-plugins-filters-range-ranges)`ranges` | [array](/docs/reference/logstash/plugins/value-types#array)array       | No       |

Also see [Common options](#v3.0.1-plugins-filters-range-common-options) for a list of options supported by all filter plugins.

### `negate`

- Value type is [boolean](/docs/reference/logstash/plugins/value-types#boolean)
- Default value is `false`

Negate the range match logic, events should be outsize of the specified range to match.

### `ranges`

- Value type is [array](/docs/reference/logstash/plugins/value-types#array)
- Default value is `[]`

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.

## Common options

These configuration options are supported by all filter plugins:

| Setting                                                                          | Input type                                                             | Required |
|----------------------------------------------------------------------------------|------------------------------------------------------------------------|----------|
| [`add_field`](#v3.0.1-plugins-filters-range-add_field)`add_field`                | [hash](/docs/reference/logstash/plugins/value-types#hash)hash          | No       |
| [`add_tag`](#v3.0.1-plugins-filters-range-add_tag)`add_tag`                      | [array](/docs/reference/logstash/plugins/value-types#array)array       | No       |
| [`enable_metric`](#v3.0.1-plugins-filters-range-enable_metric)`enable_metric`    | [boolean](/docs/reference/logstash/plugins/value-types#boolean)boolean | No       |
| [`id`](#v3.0.1-plugins-filters-range-id)`id`                                     | [string](/docs/reference/logstash/plugins/value-types#string)string    | No       |
| [`periodic_flush`](#v3.0.1-plugins-filters-range-periodic_flush)`periodic_flush` | [boolean](/docs/reference/logstash/plugins/value-types#boolean)boolean | No       |
| [`remove_field`](#v3.0.1-plugins-filters-range-remove_field)`remove_field`       | [array](/docs/reference/logstash/plugins/value-types#array)array       | No       |
| [`remove_tag`](#v3.0.1-plugins-filters-range-remove_tag)`remove_tag`             | [array](/docs/reference/logstash/plugins/value-types#array)array       | No       |


### `add_field`

- Value type is [hash](/docs/reference/logstash/plugins/value-types#hash)
- 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 {
      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 the value above and the `%{host}` piece replaced with that value from the event. The second example would also add a hardcoded field.

### `add_tag`

- Value type is [array](/docs/reference/logstash/plugins/value-types#array)
- 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 {
      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).

### `enable_metric`

- Value type is [boolean](/docs/reference/logstash/plugins/value-types#boolean)
- Default value is `true`

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.

### `id`

- Value type is [string](/docs/reference/logstash/plugins/value-types#string)
- There is no default value for this setting.

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 useful when 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"
      }
    }
```


### `periodic_flush`

- Value type is [boolean](/docs/reference/logstash/plugins/value-types#boolean)
- Default value is `false`

Call the filter flush method at regular interval. Optional.

### `remove_field`

- Value type is [array](/docs/reference/logstash/plugins/value-types#array)
- 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 {
      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 second example would remove an additional, non-dynamic field.

### `remove_tag`

- Value type is [array](/docs/reference/logstash/plugins/value-types#array)
- 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 {
      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 example would remove a sad, unwanted tag as well.