Sleep filter plugin
editSleep filter plugin
edit- Plugin version: v3.0.4
- Released on: 2017-06-23
- Changelog
Getting Help
editFor 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.
Description
editSleep a given amount of time. This will cause logstash to stall for the given amount of time. This is useful for rate limiting, etc.
Sleep Filter Configuration Options
editThis plugin supports the following configuration options plus the Common Options described later.
Also see Common Options for a list of options supported by all filter plugins.
every
edit- Value type is string
-
Default value is
1
Sleep on every N’th. This option is ignored in replay mode.
Example:
filter { sleep { time => "1" # Sleep 1 second every => 10 # on every 10th event } }
replay
edit- Value type is boolean
-
Default value is
false
Enable replay mode.
Replay mode tries to sleep based on timestamps in each event.
The amount of time to sleep is computed by subtracting the previous event’s timestamp from the current event’s timestamp. This helps you replay events in the same timeline as original.
If you specify a time
setting as well, this filter will
use the time
value as a speed modifier. For example,
a time
value of 2 will replay at double speed, while a
value of 0.25 will replay at 1/4th speed.
For example:
filter { sleep { time => 2 replay => true } }
The above will sleep in such a way that it will perform replay 2-times faster than the original time speed.
time
edit- Value type is string
- There is no default value for this setting.
The length of time to sleep, in seconds, for every event.
This can be a number (eg, 0.5), or a string (eg, %{foo}
)
The second form (string with a field value) is useful if
you have an attribute of your event that you want to use
to indicate the amount of time to sleep.
Example:
filter { sleep { # Sleep 1 second for every event. time => "1" } }
Common Options
editThe following configuration options are supported by all filter plugins:
Setting | Input type | Required |
---|---|---|
No |
||
No |
||
No |
||
No |
||
No |
||
No |
||
No |
add_field
edit- Value type is 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 { PLUGIN_NAME { add_field => { "foo_%{somefield}" => "Hello world, from %{host}" } } }
# You can also add multiple fields at once: filter { PLUGIN_NAME { 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
edit- Value type is 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 { PLUGIN_NAME { add_tag => [ "foo_%{somefield}" ] } }
# You can also add multiple tags at once: filter { PLUGIN_NAME { 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
edit- Value type is 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
edit- Value type is string
- There is no default value for this setting.
Add a unique ID
to the plugin instance, this ID
is used for tracking
information for a specific configuration of the plugin.
output { stdout { id => "ABC" } }
If you don’t explicitely set this variable Logstash will generate a unique name.
periodic_flush
edit- Value type is boolean
-
Default value is
false
Call the filter flush method at regular interval. Optional.
remove_field
edit- Value type is 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 { PLUGIN_NAME { remove_field => [ "foo_%{somefield}" ] } }
# You can also remove multiple fields at once: filter { PLUGIN_NAME { 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
edit- Value type is 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 { PLUGIN_NAME { remove_tag => [ "foo_%{somefield}" ] } }
# You can also remove multiple tags at once: filter { PLUGIN_NAME { 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.