From befe16023e3430b957319d6f014c01b5fdba0a84 Mon Sep 17 00:00:00 2001 From: Duncan Martin Walker Date: Thu, 6 Feb 2020 14:34:01 +0000 Subject: [PATCH] Update journalbeat name to use hostname Currently, journalbeat sets the beat name under which it appears in Kibana to 'journalbeat'. This is unlike the other beats, which don't set the value, and therefore default to using the hostname, whilst containing the beat.type field denoting the beat type. This commit changes the journalbeat configuration to match the other beats, in order to standardise the output data in Elasticsearch and Kibana. Change-Id: Ib43c7e89e6b037f4a6c260f3375f491b65750bd4 --- .../roles/elastic_journalbeat/templates/journalbeat.yml.j2 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/elk_metrics_7x/roles/elastic_journalbeat/templates/journalbeat.yml.j2 b/elk_metrics_7x/roles/elastic_journalbeat/templates/journalbeat.yml.j2 index 864bd7b2..515b5af6 100644 --- a/elk_metrics_7x/roles/elastic_journalbeat/templates/journalbeat.yml.j2 +++ b/elk_metrics_7x/roles/elastic_journalbeat/templates/journalbeat.yml.j2 @@ -57,7 +57,7 @@ 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 +# name: journalbeat # The tags of the shipper are included in their own field with each # transaction published. Tags make it easy to group servers by different