Bytes Sent shown as 0 for beats monitoring

monitoring

(Hari Prasad) #1

I have enabled beats monitoring by setting the below in the filebeats.yml

xpack.monitoring:
   enabled: true
   elasticsearch:
       hosts: ["http://host1:port","http://host2:port"]

But in Kibana, though i am getting the count of events, I am not getting any value for Bytes Sent

Please help me with any missing configuration in my setup.

Thank you


(Shaunak Kashyap) #2

Hi, what version of Filebeat and Kibana are you using? Also, what operating system are you on?


(Hari Prasad) #3

Thank you for the prompt reply

I am running Filebeat 6.5.3 on CentOS release 6.9 (Final)

My Kibana is Version: 6.4.2 on CentOS Linux release 7.5.1804


(Shaunak Kashyap) #4

I just setup the same versions as you but was unable to reproduce the issue. Could you check if your Filebeat log contains an ERROR messages?


(Hari Prasad) #5

below are the 2 error repeating in the logs but I couldn't find reasons for the same

ERROR pipeline/output.go:121 Failed to publish events: Post http://host1:port/_xpack/monitoring/_bulk?interval=10s&system_api_version=6&system_id=beats: net/http: request can
celed (Client.Timeout exceeded while awaiting headers)

ERROR pipeline/output.go:100 Failed to connect to backoff(failover(publish(elasticsearch(http://Host1:port)),publish(elasticsearch(http://host2:port)))): X-Pack capabilities query failed with: Get http://host1:port/_xpack?filter_path=features.monitoring.enabled: net/http: request canceled (Client.Timeout exceeded while awaiting headers)

I am able to get Monitoring info for other components in the stack.


(xeraa) #6

And that connection is working in general — no firewall blocking it for example? So a simple curl call from the affected instances against both Elasticsearch hosts is succeeding?

Connection error sounds like something relatively low level failing IMO.


(Hari Prasad) #7

I understand that, but why am I able to get the event count and not the bytes.
The screen shot in the first post shows the event count, but the bytes sent us 0.