uuid
edituuid
editThe uuid filter allows you to generate a UUID and add it as a field to each processed event.
This is useful if you need to generate a string that’s unique for every event, even if the same input is processed multiple times. If you want to generate strings that are identical each time a event with a given content is processed (i.e. a hash) you should use the fingerprint filter instead.
The generated UUIDs follow the version 4 definition in RFC 4122) and will be represented as a standard hexadecimal string format, e.g. "e08806fe-02af-406c-bbde-8a5ae4475e57".
Synopsis
editThis plugin supports the following configuration options:
Required configuration options:
uuid { target => ... }
Available configuration options:
Setting | Input type | Required | Default value |
---|---|---|---|
No |
|
||
No |
|
||
No |
|
||
No |
|
||
No |
|
||
No |
|
||
Yes |
Details
edit
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 { uuid { add_field => { "foo_%{somefield}" => "Hello world, from %{host}" } } } [source,ruby] You can also add multiple fields at once: filter { uuid { 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 { uuid { add_tag => [ "foo_%{somefield}" ] } } [source,ruby] You can also add multiple tags at once: filter { uuid { 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).
overwrite
edit- Value type is boolean
-
Default value is
false
If the value in the field currently (if any) should be overridden
by the generated UUID. Defaults to false
(i.e. if the field is
present, with ANY value, it won’t be overridden)
Example:
filter { uuid { target => "@uuid" overwrite => true } }
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 { uuid { remove_field => [ "foo_%{somefield}" ] } } [source,ruby] You can also remove multiple fields at once: filter { uuid { 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 { uuid { remove_tag => [ "foo_%{somefield}" ] } } [source,ruby] You can also remove multiple tags at once: filter { uuid { 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.