Generate a fingerprint of an eventedit
The fingerprint processor generates a fingerprint of an event based on a
specified subset of its fields.
The value that is hashed is constructed as a concatenation of the field name and
field value separated by |. For example |field1|value1|field2|value2|.
Nested fields are supported in the following format: "field1.field2", for example: ["log.path.file", "foo"]
Exampleedit
- fingerprint:
fields: ["field1", "field2", ...]
Configuration settingsedit
Elastic Agent processors execute before ingest pipelines, which means that your processor configurations cannot refer to fields that are created by ingest pipelines or Logstash. For more limitations, refer to What are some limitations of using processors?
| Name | Required | Default | Description |
|---|---|---|---|
|
Yes |
List of fields to use as the source for the fingerprint. The list will be alphabetically sorted by the processor. |
|
|
No |
|
Whether to ignore missing fields. |
|
No |
|
Field in which the generated fingerprint should be stored. |
|
No |
|
Algorithm to use for computing the fingerprint. Must be one of: |
|
No |
|
Encoding to use on the fingerprint value. Must be one of: |