Separate logstash package

[elastic]

Separate logstash package

[untergeek]

Are you referring to the fact that the Logstash RPM comes with embedded versions of Elasticsearch and Kibana?

$ du -hs vendor/jar/elasticsearch-1.0.1/
 19M    vendor/jar/elasticsearch-1.0.1/

It would be really cool if we could make the distribution smaller, but the Elasticsearch jars are necessary for Logstash to participate as a client node in a cluster. The only way to omit them is to remove all Elasticsearch plugins, which would present a different set of problems because we'd then have to manage separate packaging schemes, not to mention making people aware of the incompleteness between versions.

$ du -hs vendor/kibana/
3.1M    vendor/kibana/

Kibana is going to be even smaller compressed since it's primarily javascript and other static text files:

$ tar cfz kibana.tar.gz vendor/kibana
$ du -hs kibana.tar.gz
896K    kibana.tar.gz

There are other plugins that require similar gems in order to operate, so the extra space consumed by Kibana's dependencies is also relatively small. It's included because it allows people to do a Proof of Concept without having to install anything else. The space savings is really negligible in this instance.

[chenryn]

+1

I like yum install elasticsearch logstash-core logstash-plugins logstash-contribs kibana

[faxm0dem]

I understand the ES dependency for ppl using ES bulk output.
I understand the relatively small footprint on "modern" hardware.
However, this is how the vast majority of packages work on many GNU/Linux/systemd^W distributions.

Also, a free benefit of this would be your ability to release LS and ES seperately without breaking the bulk output.

Just my two cents here

[jordansissel]

Logstash 1.4.2's release is: logstash's core, ~160 plugins, ~100 gems, Elasticsearch, JRuby, lucene, groovy, log4j, antlr, sigar, spacial4j, geoip data, collectd data, and a few other things I'm forgetting.

All told, that's probably 275 individual packages.

There is no benefit that I can see. We are not providing packages through Red Hat or Debian's distribution channels.

What are the benefits?

---

That said, in the next release of Logstash we are introducing an improved plugin distribution system that will allow you (with the help of fpm, if you so choose) to install plugins as rpms or debs.

[ph]

In Logstash 1.5 we will introduce a new plugin system allowing you to install or remove the plugin. This will allow you to easily customize your own installation. We don't have any plan to create individuals OS package for each plugins. You can get more information about the new architecture in this blog post http://www.elasticsearch.org/blog/plugin-ecosystem-changes/