Currently the location where elasticsearch stores its data is hardcoded
in the elasticsearch.yml configuration template to /var/lib/elasticsearch.
This commit allows the option to be configured, and exposes the value as a
default variable. This not only allows the data directory to be changed,
but also for elasticsearch to be configured to use multiple data directories
through a comma separated list. The default behaviour is unchanged.
Change-Id: I21dbcaeab997362f94e245434cc5aa35136aeee9
This update exposes options for configuring beats to communicate on non-standard
interfaces, i.e. not those used by ansible itself, where proxies are enabled.
This includes allowing the elasticsearch and logstash node/bind addresses to be
overridden to use different interfaces, and letting no_proxy environment variables
be specified when the required interface does not match the kibana ansible_host
address. The default behaviour has not changed, these configurations are purely
optional.
Change-Id: I3e2230ce3de349f219306c11d476e46ae3ed8f65
Updated ELK config files to elk 7.x reference samples, bringing over
existing customisation from elk_metrics_6x.
Removed deprecated use of --pipeline in elastic_beat_setup/tasks/main.yml,
--pipeline is no longer a valid cli argument.
Updated logstash-pipelines and removed the dynamic insertion of the date into
index names. This function is now done with the new ILM feature in elasticsearch
rather than logstash.
Installation of each beat creates an ILM policy for that beat and this patch
does not change the default policy. It is possible that the default policy
will exhaust the available storage and future work needs to be done to address
this.
The non-beat elements of the logstash pipeline (syslog, collectd and others)
are not yet updated to be compatible with ILM.
Change-Id: I735b64c2b7b93e23562f35266134a176a00af1b7