Manual pipeline configuration
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. This functionality is in technical preview and is ready for evaluation. Use with caution in production; it is not recommended for mission-critical workloads. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Specific Support terms apply. 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
GA
9.2+
…
Generally available since 9.2
Preview in 9.1
The manual pipeline configuration processor is only available on classic streams.
The Manual pipeline configuration lets you create a JSON-encoded array of ingest pipeline processors. This is helpful if you want to add more advanced processing that isn't currently available as part of the UI-based processors.
Refer to the following documentation for more on manually configuring processors:
- Create readable and maintainable ingest pipelines
- Error handling in ingest pipelines
- Ingest processor reference
To manually create an array of ingest pipeline processors:
- Select Create → Create processor.
- Select Manual pipeline configuration from the Processor menu.
- In Ingest pipeline processors, add JSON to manually configure ingest pipelines.
Conditions defined in the processor JSON take precedence over conditions defined in Optional fields.