The clear interval, when all counters are reset.

If set to -1, the default value, the metrics will never be cleared.Otherwise, should be a multiple of 5s.

The flush interval, when the metrics event is created. Must be a multiple of 5s.

Don’t track events that have @timestamp older than some number of seconds.

This is useful if you want to only include events that are near real-timein your metrics.

For example, to only count events that are within 10 seconds of real-time, youwould do this:

filter {  metrics {    meter => [ "hits" ]    ignore_older_than => 10  }}

syntax: meter => [ "name of metric", "name of metric" ]

The percentiles that should be measured and emitted for timer values.

The rates that should be measured, in minutes.Possible values are 1, 5, and 15.

syntax: timer => [ "name of metric", "%{time_value}" ]

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

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

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

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 metrics filters.Adding a named ID in this case will help in monitoring Logstash when using the monitoring APIs.

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

Call the filter flush method at regular interval.Optional.

If this filter is successful, remove arbitrary fields from this event.Example:

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

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

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