cf-charmers team mailing list archive

[Kapil Thangavelu <kapil.thangavelu@xxxxxxxxxxxxx>]

per email update on this earlier today, recent versions of logstash in dev
are at

cs:~lazypower/trusty/logstash-agent
cs:~lazypower/trusty/logstash

not sure i would use the agent (jruby + jvm) as its heavyweight, but the
server is reasonable and supports redis inputs per the std scaling semantic
around logstash.

-k


On Mon, Oct 20, 2014 at 6:23 PM, Alexander Lomov <lomov.as@xxxxxxxxx> wrote:

> Hey, all.
>
> Today I tried to create juju bundle with
> logstash+elasticsearch+kibana+rails. Here is approximate bundle that I used
> - https://gist.github.com/allomov/088d54229c051a6266b4 (I needed to do
> some stuff manually). Here is my impressions and experience:
>
>    1. logstash charms are outdated:
>       1. current logstash stable version is 1.4.2 vs 1.1/1.2 in the
>       charms;
>       2. charms are written in bash without using charmhelpers;
>       3. embedded elasticsearch of logstash-indexer charm is not
>       compatible with actual version of kibana charm;
>       4. current version of elasticsearch charm doesn't support relation
>       with logstash-indexer.
>    2. logstash-agent is build to use redis embedded in logstash-indexer.
>    I'm not sure that this is correct solution since user may want to connect
>    his redis to charms or create redis cluster. Adding implicit connection
>    of logstash-agent to logstash-indexer through redis will make architecture
>    more clear.
>
> I'm pretty sure that logstash charms need to be updated with latest
> charmhelpers and python implementation. What do you think about it ?
>
> Thank you,
> Alex L.
>
>
> --
> Mailing list: https://launchpad.net/~cf-charmers
> Post to     : cf-charmers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~cf-charmers
> More help   : https://help.launchpad.net/ListHelp
>
>