- Journalbeat Reference for 6.5-7.15:
- Overview
- Get started
- 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_observer_metadata
- add_process_metadata
- add_tags
- community_id
- convert
- copy_fields
- decode_base64_field
- decode_csv_fields
- decode_json_fields
- decompress_gzip_field
- dissect
- dns
- drop_event
- drop_fields
- extract_array
- fingerprint
- include_fields
- registered_domain
- rename
- script
- timestamp
- translate_sid
- truncate_fields
- urldecode
- Internal queue
- Logging
- HTTP endpoint
- Regular expression support
- journalbeat.reference.yml
- How to guides
- Exported fields
- Monitor
- Secure
- Troubleshoot
This functionality is experimental and may be changed or removed completely in a
future release. Elastic will take a best effort approach to fix any issues, but
experimental features are not subject to the support SLA of official GA
features.
Generate an ID for an event
editGenerate an ID for an event
editThe add_id
processor generates a unique ID for an event.
processors: - add_id: ~
The following settings are supported:
-
target_field
-
(Optional) Field where the generated ID will be stored. Default is
@metadata._id
. -
type
-
(Optional) Type of ID to generate. Currently only
elasticsearch
is supported and is the default. Theelasticsearch
type generates IDs using the same algorithm that Elasticsearch uses for auto-generating document IDs.
Was this helpful?
Thank you for your feedback.