- Elastic Ingest Reference Architectures: other versions:
- Ingest architectures
- Elastic Agent to Elasticsearch
- Elastic Agent to Logstash to Elasticsearch
- Elastic Agent to Logstash (for enrichment) to Elasticsearch
- Elastic Agent to Logstash to Elasticsearch: Logstash Persistent Queue (PQ) for buffering
- Elastic Agent to Logstash to Elasticsearch: Logstash as a proxy
- Elastic Agent to Logstash for routing to multiple Elasticsearch clusters and additional destinations
- Elastic Agent to proxy to Elasticsearch
- Elastic Agent to Elasticsearch with Kafka as middleware message queue
- Logstash to Elasticsearch
- Elastic air-gapped architectures
IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
Logstash to Elasticsearch
editLogstash to Elasticsearch
edit- Ingest model
- Logstash to collect data from sources not currently supported by Elastic Agent and sending the data to Elasticsearch. Note that the data transformation still happens within the Elasticsearch ingest pipeline.
- Use when
- Elastic Agent doesn’t currently support your data source.
- Examples
- AWS Kinesis, databases, Kafka
Resources
editBefore you implement this approach, check to see if an Elastic Agent integration exists and, if so, use it instead:
Info on Logstash and Logstash input and output plugins:
Info on Elasticsearch and ingest pipelines:
On this page
Was this helpful?
Thank you for your feedback.