- Journalbeat Reference for 6.5-7.15:
- Journalbeat overview
- Quick start: installation and configuration
- Set up and run
- Configure
- Inputs
- General settings
- Project paths
- 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
- community_id
- convert
- copy_fields
- decode_base64_field
- decode_csv_fields
- 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
- rate_limit
- registered_domain
- rename
- script
- timestamp
- translate_sid
- truncate_fields
- urldecode
- Internal queue
- Logging
- HTTP endpoint
- Regular expression support
- Instrumentation
- journalbeat.reference.yml
- How to guides
- Exported fields
- Monitor
- Secure
- Troubleshoot
- Get help
- Debug
- Common problems
- Journalbeat uses too much bandwidth
- 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
Starting in version 7.16, this experimental functionality has been removed. You
should use the journald input in Filebeat instead.
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|
.
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.