New Charm Proposal: Logstash

Bug #1560167 reported by Charles Butler on 2016-03-21
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juju Charms Collection
Undecided
Unassigned

Bug Description

A flexible, open source data collection, enrichment, and transportation pipeline. With connectors to common infrastructure for easy integration, Logstash is designed to efficiently process a growing list of log, event, and unstructured data sources for distribution into a variety of outputs, including Elasticsearch.

The current logstash charm is of questionable quality. This is not my first attempt at disloding it from the store but this is certainly my most comprehensive update to the charm in a long while.

Thus the new charm submission, as this really needs a full stack review from point a to z.

Logstash by itself is not terribly useful, you must deploy it with a data source, and a data repository (see: filebeat, and elasticsearch) in order to get any kind of useful behavior out of the charm. I've added a comprehensive test suite to the ELK bundle (separate PR) if you're looking ot do more than standup validation.

I'll also ping the list about this submission as there is an existing logstash charm in the store, but I highly doubt anyone is using it in a production capacity due to the nature of its st

If there's anything in here that needs attention just let me know. Ta!

Review Queue (review-queue) wrote :

The results (PASS) are in and available here: http://juju-ci.vapour.ws:8080/job/charm-bundle-test-aws/3284/

Hi Charles, thank you for your work on this charm. Please consider a couple of easy fixes gathered in https://github.com/juju-solutions/layer-logstash/pull/16

- There is an issue with the schema of actions.yaml. Generate-noise action could not read the default value of the noise parameter
- Using the Makefile of the basic layer allows you now to not have tests so you can skip having a Makefile in your layer

Thank you for your time an effort.

Changed in charms:
status: New → In Progress

I see that the comments have been addressed in https://github.com/juju-solutions/layer-logstash and since we are not forced to use bzr I am fine with promulgating the charm from: cs:~containers/trusty/logstash-6 (where it is placed)

Thank you again for your time and effort!

Kevin W Monroe (kwmonroe) wrote :

Thanks for the development effort here Charles, and thanks for the review Kostas! There was a minor bump to the ~containers charm, so logstash-7 has been promulgated and is available here:

http://jujucharms.com/logstash

This opens up quite a few interesting ELK bundling capabilities, so this is a great addition to the store. Thanks again!

Changed in charms:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers