- 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.
Elastic Agent to Elasticsearch: Agent installed
editElastic Agent to Elasticsearch: Agent installed
edit- Ingest model
-
Control path: Elastic Agent to Fleet to Elasticsearch
Data path: Elastic Agent to Elasticsearch - Use when
- An Elastic Agent integration exists in the Kibana integrations UI for the software you want to monitor, observe, and protect.
- Examples
-
- System integration that collects metrics and logs from operating systems
- Kubernetes integration that collects metrics and logs from Kubernetes master and worker nodes, and from workloads running on worker node pods
Process overview
edit- Find the integration for your data source. In Kibana, go to Management> Integrations.
- Enable the integration and set up Elastic Agent.
- Launch discover/dashboard to explore.
For details and next steps, check out the Elastic Agent integrations docs for your data source.
On this page
Was this helpful?
Thank you for your feedback.