Setup of beat exporter doesn't work


I wanted to export filebeat metrics via beat exporter.

  • filebeat has a conf that exposes the metrics

  • beat exporter's documentation also tells me to do the same

  • Filebeat and beat-exporter are running on the same host in the same docker bridge network

  • Out of the box this config doesn't work. To make it work I had to change
    http: enabled: true host: localhost port: 5066
    http: enabled: true host: port: 5066
    Why localhost config doesn't work : If the process inside the container is bound to localhost, localhost uses a special loopback interface that is distinct from regular networking. I am able to access the service from within the container (host) but you won't be able to route its traffic externally

  • In doing so I make the setup work for filebeat and beat-exporter, but cause issues between logstash and filebeat.(filebeat and logstash running on different server) filebeat logs
    2020-06-23T10:50:06.823+0200 ERROR logstash/async.go:256 Failed to publish events caused by: read tcp X.X.X.X:40590->X.X.X.X:5050: read: connection reset by peer 2020-06-23T10:50:06.894+0200 ERROR logstash/async.go:256 Failed to publish events caused by: client is not connected 2020-06-23T10:50:08.708+0200 ERROR pipeline/output.go:121 Failed to publish events: client is not connected

[24th June 2020 14:36 PM] Noticed something :
As soon as I stop beat exporter and restart the filebeat instance, the above mentioned error do not appear and filebeat/logstash work as expected

  • So the setup has a container of filebeat and beat-exporter running on application-server and logstash running on a my log-server
  • With the below config in filebeat. filebeat and logstash work (so i will rule out the possibility that doesn't work )

enabled: true
port: 5066

  • Now when i start beat-exporter, I start to see the above errors (not sure what could cause it)
  • But even after stopping beat-exporter the above errors persist and it only gets resolved once i restart filebeat


This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.