brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hadrian Zbarcea <hzbar...@gmail.com>
Subject Re: Brooklyn logstash enricher
Date Tue, 25 Aug 2015 15:21:23 GMT
Shouldn't this be a policy?
Hadrian

On 08/25/2015 10:45 AM, Duncan Grant wrote:
> I'm considering adding logstash functionality so that a blueprint can be
> extended so that logstash is installed on each vm and collect logs and
> forward them to something like elastic search.
>
> My initial plan is to create a logstash enricher that can be attached to an
> entity.  It would install logstash and configure it to look at the parent
> entity's log location.  The filter and output config would be configurable
> on the enricher making it fairly straightforward to configure where the
> logs are sent e.g. elastic search.
>
> So yaml might look something like
>
> services:
> -type: BasicEntity
>    brooklyn.enrichers:
>    - type: Logstash
>      brooklyn.config:
>        input:
>          file
>            path: "/path/to/file"
>        filter:
>          grok:
>            match:
>              message: "%{COMBINEDAPACHELOG}"
>        output:
>          elasticsearch
>            protocol: "http"
>
> With default behaviour for each of input, filter, output if they are not in
> the yaml.
>
> Does this make sense?
>
> Regards
>
> Duncan
>

Mime
View raw message