Yes, those are correctly configured. Seeing from the history, we have never faced the issue that the logs in the Discover tab (Kibana GUI) haven not shown up for a single instance and they were shown all the time once someone access the Discover and grep for the logs.
e.g. as below ss
Also I am attaching the details of other configuration file as well.
ls -l
total 12
-rw-r--r-- 1 root root 181 Mar 8 23:07 02-beats-input.conf
-rw-r--r-- 1 root root 436 Jan 12 18:06 30-elasticsearch-output.conf
-rw-r--r-- 1 root root 404 Dec 4 10:28 30-elasticsearch-output.conf_12_jan_bkp
cat 30-elasticsearch-output.conf
output {
if [@metadata][pipeline] {
elasticsearch {
hosts => ["localhost:9200"]
manage_template => false
index => "%{[@metadata][beat]}-%{[@metadata][version]}"
pipeline => "%{[@metadata][pipeline]}"
}
} else {
elasticsearch {
hosts => ["localhost:9200"]
manage_template => false
index => "%{[@metadata][beat]}-%{[@metadata][version]}"
}
}
}
Just FYI from the previous discussions on where we updated the 30-elasticsearch-output.conf