Open mrdavidlaing opened 9 years ago
Will this also include to split out elasaticsearch itself from the parser job and reuse the elasticsearch job that is already in the release?
Would be great if in the manifest we could say
- name: parser
templates:
- name: elasticsearch
- name: parser
....
so we get more flexibility.
As in our case we would not want to run ES directly on the parsers.
@simonjohansson If you set logstash_parser.use_local_elasticsearch:false
, then the local elasticsearch job isn't run on the parser node
Does that fulfil your requirement?
That would work!
Great
On Tuesday, 20 October 2015, Simon Johansson notifications@github.com wrote:
That would work!
— Reply to this email directly or view it on GitHub https://github.com/logsearch/logsearch-boshrelease/issues/191#issuecomment-149589539 .
David Laing logsearch.io - build your own open source cloud logging cluster http://davidlaing.com
Oh, as long as the elasticsearch output in https://github.com/logsearch/logsearch-boshrelease/blob/develop/jobs/parser/templates/config/input_and_output.conf.erb is disable-able. :)
For those cases where you want to specify all your own outputs via
logstash_filter.outputs