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
--
Cloudsoft Corporation Limited, Registered in Scotland No: SC349230.
Registered Office: 13 Dryden Place, Edinburgh, EH9 1RP
This e-mail message is confidential and for use by the addressee only. If
the message is received by anyone other than the addressee, please return
the message to the sender by replying to it and then delete the message
from your computer. Internet e-mails are not necessarily secure. Cloudsoft
Corporation Limited does not accept responsibility for changes made to this
message after it was sent.
Whilst all reasonable care has been taken to avoid the transmission of
viruses, it is the responsibility of the recipient to ensure that the
onward transmission, opening or use of this message and any attachments
will not adversely affect its systems or data. No responsibility is
accepted by Cloudsoft Corporation Limited in this regard and the recipient
should carry out such virus and other checks as it considers appropriate.
