Kevin Carter ce9007cda5

Thread pools should be based on processor counts ...

The current setup was using processor cores from ansible facts which in
a multi-core, single socket system could result in 1. Using the
processor count will return the logical processor count giving us a more
performant setup when the compute power is present.

Change-Id: Ia5b63d45691f58e848d05cc4a4e5f353b993a347
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>

2018-08-25 01:51:16 -05:00

..

elastic_apm_server

Add Redhat to the ELK deployment capabilities

2018-08-13 18:59:57 -05:00

elastic_auditbeat

Add Redhat to the ELK deployment capabilities

2018-08-13 18:59:57 -05:00

elastic_curator

Update curator to better metric storage

2018-08-14 22:37:28 +00:00

elastic_data_hosts

Thread pools should be based on processor counts

2018-08-25 01:51:16 -05:00

elastic_dependencies

Add Redhat to the ELK deployment capabilities

2018-08-13 18:59:57 -05:00

elastic_filebeat

Add Redhat to the ELK deployment capabilities

2018-08-13 18:59:57 -05:00

elastic_heartbeat

Add Redhat to the ELK deployment capabilities

2018-08-13 18:59:57 -05:00

elastic_journalbeat

Add Redhat to the ELK deployment capabilities

2018-08-13 18:59:57 -05:00

elastic_kibana

Add basic index templates

2018-08-15 21:35:31 -05:00

elastic_logstash

Thread pools should be based on processor counts

2018-08-25 01:51:16 -05:00

elastic_metricbeat

When collecting KVM data use a local connection

2018-08-25 00:02:00 -05:00

elastic_packetbeat

Add Redhat to the ELK deployment capabilities

2018-08-13 18:59:57 -05:00

elastic_repositories

Add Redhat to the ELK deployment capabilities

2018-08-13 18:59:57 -05:00

elastic_retention

Update curator to better metric storage

2018-08-14 22:37:28 +00:00

elastic_rollup

Update curator to better metric storage

2018-08-14 22:37:28 +00:00

elasticsearch

Thread pools should be based on processor counts

2018-08-25 01:51:16 -05:00

go_install_1.10

Add trusty support to the project

2018-08-11 00:00:03 -05:00