openstack
/
openstack-ansible-ops
Code Issues Proposed changes

beats: allow definition of custom hostname where necessary 

Adds a variable to enable overriding of the name which beats
use to identify themselves to elasticsearch.

Change-Id: Ic1353431336394d03aadee8dd03333ef138e437e
This commit is contained in:
Andrew Bonney 2022-05-31 15:13:25 +01:00
parent dff4647b70
commit 7dbfa3025c
6 changed files with 18 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
elk_metrics_7x/roles/elastic_auditbeat/templates/auditbeat.yml.j2
View File

@ -207,7 +207,9 @@ auditbeat.modules:
# The name of the shipper that publishes the network data. It can be used to group
# all the transactions sent by a single shipper in the web interface.
# If this options is not defined, the hostname is used.
#name:
{% if elastic_hostname is defined %}
name: {{ elastic_hostname }}
{% endif %}
# The tags of the shipper are included in their own field with each
# transaction published. Tags make it easy to group servers by different

4
elk_metrics_7x/roles/elastic_filebeat/templates/filebeat.yml.j2
View File

@ -1100,7 +1100,9 @@ filebeat.inputs:
# The name of the shipper that publishes the network data. It can be used to group
# all the transactions sent by a single shipper in the web interface.
# If this options is not defined, the hostname is used.
#name:
{% if elastic_hostname is defined %}
name: {{ elastic_hostname }}
{% endif %}
# The tags of the shipper are included in their own field with each
# transaction published. Tags make it easy to group servers by different

4
elk_metrics_7x/roles/elastic_heartbeat/templates/heartbeat.yml.j2
View File

@ -334,7 +334,9 @@ heartbeat.scheduler:
# The name of the shipper that publishes the network data. It can be used to group
# all the transactions sent by a single shipper in the web interface.
# If this options is not defined, the hostname is used.
#name:
{% if elastic_hostname is defined %}
name: {{ elastic_hostname }}
{% endif %}
# The tags of the shipper are included in their own field with each
# transaction published. Tags make it easy to group servers by different

4
elk_metrics_7x/roles/elastic_journalbeat/templates/journalbeat.yml.j2
View File

@ -70,7 +70,9 @@ setup.template.settings:
# The name of the shipper that publishes the network data. It can be used to group
# all the transactions sent by a single shipper in the web interface.
# If this options is not defined, the hostname is used.
# name: journalbeat
{% if elastic_hostname is defined %}
name: {{ elastic_hostname }}
{% endif %}
# The tags of the shipper are included in their own field with each
# transaction published. Tags make it easy to group servers by different

4
elk_metrics_7x/roles/elastic_metricbeat/templates/metricbeat.yml.j2
View File

@ -961,7 +961,9 @@ metricbeat.modules:
# The name of the shipper that publishes the network data. It can be used to group
# all the transactions sent by a single shipper in the web interface.
# If this options is not defined, the hostname is used.
#name:
{% if elastic_hostname is defined %}
name: {{ elastic_hostname }}
{% endif %}
# The tags of the shipper are included in their own field with each
# transaction published. Tags make it easy to group servers by different

4
elk_metrics_7x/roles/elastic_packetbeat/templates/packetbeat.yml.j2
View File

@ -630,7 +630,9 @@ packetbeat.ignore_outgoing: false
# The name of the shipper that publishes the network data. It can be used to group
# all the transactions sent by a single shipper in the web interface.
# If this options is not defined, the hostname is used.
#name:
{% if elastic_hostname is defined %}
name: {{ elastic_hostname }}
{% endif %}
# The tags of the shipper are included in their own field with each
# transaction published. Tags make it easy to group servers by different