# Bytes Sent shown as 0 for beats monitoring
**URL:** https://discuss.elastic.co/t/bytes-sent-shown-as-0-for-beats-monitoring/163928
**Category:** Beats
**Tags:** elastic-stack-monitoring, filebeat
**Created:** [January 11, 2019, 4:11pm UTC](https://discuss.elastic.co/t/bytes-sent-shown-as-0-for-beats-monitoring/163928 "2019-01-11T16:11:49Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@Hari\_Prasad](https://discuss.elastic.co/u/Hari_Prasad)
#### Post date: [January 11, 2019, 4:11pm UTC](https://discuss.elastic.co/t/bytes-sent-shown-as-0-for-beats-monitoring/163928/1 "2019-01-11T16:11:49Z")
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
---
### Author:  [@shaunak](https://discuss.elastic.co/u/shaunak)
#### Post date: [January 11, 2019, 4:26pm UTC](https://discuss.elastic.co/t/bytes-sent-shown-as-0-for-beats-monitoring/163928/2 "2019-01-11T16:26:29Z")
Hi, what version of Filebeat and Kibana are you using? Also, what operating system are you on?
---
### Author:  [@Hari\_Prasad](https://discuss.elastic.co/u/Hari_Prasad)
#### Post date: [January 11, 2019, 4:48pm UTC](https://discuss.elastic.co/t/bytes-sent-shown-as-0-for-beats-monitoring/163928/3 "2019-01-11T16:48:50Z")
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
---
### Author:  [@shaunak](https://discuss.elastic.co/u/shaunak)
#### Post date: [January 11, 2019, 6:17pm UTC](https://discuss.elastic.co/t/bytes-sent-shown-as-0-for-beats-monitoring/163928/4 "2019-01-11T18:17:56Z")
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?
---
### Author:  [@Hari\_Prasad](https://discuss.elastic.co/u/Hari_Prasad)
#### Post date: [January 12, 2019, 3:18am UTC](https://discuss.elastic.co/t/bytes-sent-shown-as-0-for-beats-monitoring/163928/5 "2019-01-12T03:18:36Z")
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.
---
### Author:  [@xeraa](https://discuss.elastic.co/u/xeraa)
#### Post date: [January 14, 2019, 11:55am UTC](https://discuss.elastic.co/t/bytes-sent-shown-as-0-for-beats-monitoring/163928/6 "2019-01-14T11:55:37Z")
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.
---
### Author:  [@Hari\_Prasad](https://discuss.elastic.co/u/Hari_Prasad)
#### Post date: [January 14, 2019, 12:10pm UTC](https://discuss.elastic.co/t/bytes-sent-shown-as-0-for-beats-monitoring/163928/7 "2019-01-14T12:10:02Z")
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.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 11, 2019, 12:10pm UTC](https://discuss.elastic.co/t/bytes-sent-shown-as-0-for-beats-monitoring/163928/8 "2019-02-11T12:10:03Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.