Generate an ID for 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 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
elasticsearchis supported and is the default. Theelasticsearchtype generates IDs using the same algorithm that Elasticsearch uses for auto-generating document IDs.