Load ingest pipelines
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
Winlogbeat modules are implemented using Elasticsearch ingest node pipelines. The events receive their transformations within Elasticsearch. The ingest node pipelines must be loaded into Elasticsearch. This can happen one of several ways.
Winlogbeat will send ingest pipelines automatically to Elasticsearch if the Elasticsearch output is enabled.
Make sure the user specified in winlogbeat.yml is authorized to set up Winlogbeat.
The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability Planned We plan to add this functionality in a future Elastic Stack update. Subject to changes. 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. To turn off automatic pipeline loading during normal publishing, set:
setup.pipelines.enabled: false
Use this setting only when the required pipelines have already been loaded or are managed separately.
If Winlogbeat is sending events to Logstash or another output you need to load the ingest pipelines with the setup command or manually.
On a machine that has Winlogbeat installed and has Elasticsearch configured as the output, run the setup command with the --pipelines option specified. For example, the following command loads the ingest pipelines:
PS > .\winlogbeat.exe setup --pipelines
Make sure the user specified in winlogbeat.yml is authorized to set up Winlogbeat.
On a machine that has Winlogbeat installed export the the pipelines to disk. This can be done with the export command with pipelines option specified. For example, the following command exports the ingest pipelines:
PS> .\winlogbeat.exe export pipelines --es.version=7.16.0
Once the pipelines have been exported you can load them into Elasticsearch with the _ingest/pipeline REST API call. The user making the REST API call will need to have the ingest_admin role assigned to them.