- Functionbeat Reference:
- Functionbeat overview
- Quick start: installation and configuration
- Set up and deploy
- Configure
- AWS functions
- General settings
- Output
- Kerberos
- SSL
- Index lifecycle management (ILM)
- Elasticsearch index template
- Processors
- Define processors
- add_cloud_metadata
- add_cloudfoundry_metadata
- add_docker_metadata
- add_fields
- add_host_metadata
- add_id
- add_kubernetes_metadata
- add_labels
- add_locale
- add_network_direction
- add_nomad_metadata
- add_observer_metadata
- add_process_metadata
- add_tags
- append
- community_id
- convert
- copy_fields
- decode_base64_field
- decode_duration
- decode_json_fields
- decode_xml
- decode_xml_wineventlog
- decompress_gzip_field
- detect_mime_type
- dissect
- dns
- drop_event
- drop_fields
- extract_array
- fingerprint
- include_fields
- move_fields
- rate_limit
- registered_domain
- rename
- replace
- syslog
- translate_sid
- truncate_fields
- urldecode
- Internal queue
- Logging
- Regular expression support
- Instrumentation
- functionbeat.reference.yml
- How to guides
- Exported fields
- Monitor
- Secure
- Troubleshoot
- Get help
- Debug
- Understand logged metrics
- Common problems
- Deployment to AWS fails with "failed to create the stack"
- Deployment to AWS fails with "resource limit exceeded"
- Error loading config file
- Found unexpected or unknown characters
- Logstash connection doesn’t work
- Publishing to Logstash fails with "connection reset by peer" message
- @metadata is missing in Logstash
- Not sure whether to use Logstash or Beats
- SSL client fails to connect to Logstash
- Monitoring UI shows fewer Beats than expected
- High RSS memory usage due to MADV settings
Functionbeat reached End of Support on October 18, 2023. You must consider
moving your deployments to the more versatile and efficient Elastic Serverless
Forwarder.
Generate a fingerprint of an event
editGenerate a fingerprint of an event
editThe 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.
Was this helpful?
Thank you for your feedback.