Generate a fingerprint of an event
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is generally available and ready for production usage. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Generally available
Stack
Generally available
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" e.g: ["log.path.file", "foo"]
processors:
- fingerprint:
fields: ["field1", "field2", ...]
The following settings are supported:
fields- List of fields to use as the source for the fingerprint. The list will be alphabetically sorted by the processor.
ignore_missing- (Optional) Whether to ignore missing fields. Default is
false. target_field- (Optional) Field in which the generated fingerprint should be stored. Default is
fingerprint. method- (Optional) Algorithm to use for computing the fingerprint. Must be one of:
md5,sha1,sha256,sha384,sha512,xxhash. Default issha256. encoding-
(Optional) Encoding to use on the fingerprint value. Must be one of
hex,base32, orbase64. Default ishex.