Install logstash with Homebrew, chocolatey, Nix, scoop

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• logstash
• logstash-plugin

Project history

The official repository describes Logstash as a tool to transport and process logs, events, and other data. Its GitHub repository was created in November 2010, and Elastic's current documentation frames it as a real-time data collection engine that can unify data from many sources and normalize it for downstream analytics and visualization.

Elastic documentation emphasizes Logstash's pipeline model: inputs receive events, filters parse or enrich them, and outputs send them onward. The project also developed a large plugin ecosystem; the upstream README notes more than 200 plugins and points plugin issues to separate repositories under the `logstash-plugins` organization.

Adoption history

Logstash became widely adopted because it paired naturally with Elasticsearch and Kibana for log search and visualization. Elastic's own product pages and stack documentation present Logstash as part of the Elastic Stack alongside Elasticsearch, Kibana, Beats, and newer Elastic Agent components.

A 2014 Elastic press release for Logstash 1.4 described it as one of the most popular open-source log-management tools and tied its growth to the ELK stack. In package-manager terms, the supplied facts show distribution through Homebrew, Chocolatey, Nix, and Scoop, while Elastic also publishes official downloadable binaries and Debian/RPM packages.

How it is used

Users write pipeline configuration files that describe inputs, filters, and outputs, commonly placing `.conf` files under `/etc/logstash/conf.d` on Debian and RPM installations. Settings such as `logstash.yml`, `pipelines.yml`, and JVM options live in the `path.settings` directory.

The official docs also document a Logstash keystore for secrets. Sensitive values such as Elasticsearch passwords can be stored in the keystore and referenced from `logstash.yml` or pipeline configuration as `${KEY}`.

Why package nerds care

Logstash matters to package nerds because it is a heavyweight but scriptable bridge between Unix log files and modern search/observability stacks. It brought plugin-managed, package-distributed ETL behavior into the everyday log pipeline, and its config-file layout is a frequent concern for distro, Docker, and Homebrew packaging.

Timeline

• 2010: Official GitHub repository created.
• 2014: Elastic announces Logstash 1.4 and promotes it as a major ELK-stack log-management component.
• 2015: Elastic blog describes Logstash Forwarder as started by Logstash creator Jordan Sissel and folded into Filebeat.
• 2026: Logstash 9.x tags are active in the official repository.

Related projects

• Logstash is part of the Elastic Stack with Elasticsearch, Kibana, Beats, and Elastic Agent.
• Logstash plugins are maintained separately under the `logstash-plugins` GitHub organization and are published as Ruby gems.

Sources

• https://api.github.com/repos/elastic/logstash
• https://github.com/elastic/logstash#readme
• https://www.elastic.co/about/press/elasticsearch-releases-logstash-1-4-makes-log-analysis-faster-simpler
• https://www.elastic.co/docs/get-started/the-stack
• https://www.elastic.co/docs/reference/logstash
• https://www.elastic.co/logstash
• source_facts.package-manager