You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think the http:// and the port number might be incorrect in the LOGSTASH_HOSTS variable. The variable isn't used in filebeat.yml but it sure looks like it could be! During my tests using the logstash output of Filebeat with SSL/TLS, keeping the protocol (but using port 5044 since this seems to be the convention for Beats, 9600 being the web API endpoint) produced this error:
Failed to connect to backoff(async(tcp://[https://logstash01:5044]:5044)): lookup https://logstash01:5044: no such host
And the link from Filebeat to Logstash doesn't work. The value between square brackets looks strange too?... According to the Filebeat configuration docs and how these variables will be used in filebeat.yml:
After using only host and port, some (expected) error message are seen but the Filebeat-Logstash link eventually works:
Failed to connect to backoff(async(tcp://logstash01:5044)): lookup logstash01 on 127.0.0.11:53: no such host
Failed to connect to backoff(async(tcp://logstash01:5044)): dial tcp 172.27.0.2:5044: connect: connection refused
Finally, I haven't tried putting several hosts in the variables but I wonder if it would work? Should they be comma-separated or something?
I did my best to explain this clearly but I'm still a little bit confused about all this.
TL;DR
I think putting the protocol in LOGSTASH_HOSTS makes Filebeat fail when using the Logstash output
I think the port should be 5044 since that's the convention and the only way I could found to use Logstash from Filebeat was via the Beats input.
It might be better to rename KIBANA_HOSTS to KIBANA_HOST
I wonder if these variables can work with several hosts but I haven't tested it.
The text was updated successfully, but these errors were encountered:
In
docker-compose.yml
, environment variables offilebeat01
are defined like this:I think the
http://
and the port number might be incorrect in theLOGSTASH_HOSTS
variable. The variable isn't used infilebeat.yml
but it sure looks like it could be! During my tests using thelogstash
output of Filebeat with SSL/TLS, keeping the protocol (but using port 5044 since this seems to be the convention for Beats, 9600 being the web API endpoint) produced this error:And the link from Filebeat to Logstash doesn't work. The value between square brackets looks strange too?... According to the Filebeat configuration docs and how these variables will be used in
filebeat.yml
:setup.kibana.host
allows only oneURL
orhost:port
; It might be better to renameKIBANA_HOSTS
toKIBANA_HOST
since the settings expect only one? https://www.elastic.co/guide/en/beats/filebeat/current/setup-kibana-endpoint.htmloutput.elasticsearch.hosts
allows one or severalURL
orhost:port
https://www.elastic.co/guide/en/beats/filebeat/current/elasticsearch-output.html#hosts-optionoutput.logstash.hosts
seem to allow one or severalhost:port
strings. Docs aren't very clear about this though: https://www.elastic.co/guide/en/beats/filebeat/current/logstash-output.html#hostsAfter using only host and port, some (expected) error message are seen but the Filebeat-Logstash link eventually works:
Finally, I haven't tried putting several hosts in the variables but I wonder if it would work? Should they be comma-separated or something?
I did my best to explain this clearly but I'm still a little bit confused about all this.
TL;DR
LOGSTASH_HOSTS
makes Filebeat fail when using the Logstash outputKIBANA_HOSTS
toKIBANA_HOST
The text was updated successfully, but these errors were encountered: