Logstash is an open-source data-processing engine for moving event data from multiple sources to different destinations. It extracts, transforms, enriches, and routes events through real-time pipelines governed by preconfigured parsing rules. section 1.4.2
A typical Elasticsearch ingestion setup uses Logstash when source data needs reshaping before indexing. Database records, files, logs, metrics, and real-time application events can enter the pipeline and emerge as searchable Elasticsearch data. section 3.1.1
Logstash fits into ingestion workflows by:
- Reading from sources such as files, HTTP, JMS, Kafka, Amazon S3, Twitter, databases, and application event streams. section 1.4.2 section 3.1.1
- Transforming and enriching records whose shape does not yet match Elasticsearch’s indexing needs. section 3.1.1
- Sending processed events to destinations such as Elasticsearch and supporting search, debugging, analysis, and storage. section 1.4.2 section 3.1.1
Database-to-search pipeline
An organization can fetch records from its authoritative database in batches or near real time, use Logstash to transform and enrich them, and index the resulting data into Elasticsearch for efficient search and analytics. section 3.1.1
Use the Elastic Stack diagram to trace Logstash’s position between incoming data sources and Elasticsearch, alongside Beats and Kibana. section 1.4.2
