# Interpreting Filebeat INFO logs

**URL:** https://discuss.elastic.co/t/interpreting-filebeat-info-logs/93589
**Category:** Beats
**Tags:** filebeat
**Created:** [July 18, 2017, 1:05pm UTC](https://discuss.elastic.co/t/interpreting-filebeat-info-logs/93589 "2017-07-18T13:05:31Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![hding](https://avatars.discourse-cdn.com/v4/letter/h/eb9ed0/32.png) [@hding](https://discuss.elastic.co/u/hding)
#### Post date: [July 18, 2017, 1:05pm UTC](https://discuss.elastic.co/t/interpreting-filebeat-info-logs/93589/1 "2017-07-18T13:05:31Z")

</div>

I'm trying to understand the following Filebeat INFO log:

> INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=2 filebeat.harvester.open\_files=-1 filebeat.harvester.running=-2 libbeat.es.call\_count.PublishEvents=138 libbeat.es.publish.read\_bytes=2730237 libbeat.es.publish.write\_bytes=555960458 libbeat.es.published\_and\_acked\_events=635669 libbeat.publisher.published\_events=545753 publish.events=917504 registrar.states.update=917504 registrar.writes=7

In particular, what do the following values mean? What are their differences? Which values are the important ones?

Events related:  
`libbeat.es.call_count.PublishEvents`  
`libbeat.es.published_and_acked_events`  
`libbeat.publisher.published_events`  
`publish.events`

Bytes related:  
`libbeat.es.publish.read_bytes`  
`libbeat.es.publish.write_bytes`

Thanks!

---

<div class="post-metadata">

### Author: ![hding](https://avatars.discourse-cdn.com/v4/letter/h/eb9ed0/32.png) [@hding](https://discuss.elastic.co/u/hding)
#### Post date: [July 18, 2017, 9:33pm UTC](https://discuss.elastic.co/t/interpreting-filebeat-info-logs/93589/2 "2017-07-18T21:33:36Z")

</div>

My guess is that:

`libbeat.es.published_and_acked_events`: The events actually published, which is equal to the number of documents indexed successfully in Elasticsearch.

`libbeat.publisher.published_events`: If everything goes smooth, this should be equal to `libbeat.es.published_and_acked_events`. Otherwise, `libbeat.publisher.published_events` = `libbeat.es.published_and_acked_events` + `#not_acked_events`.

`publish.events`: The number of events in the original log files, including both the events being published, and the events excluded. Hence, if you drop/exclude some events/lines in Filebeat prospector, then `publish.events` = `libbeat.publisher.published_events` + `#excluded_lines`.

I am still trying to understand `libbeat.es.publish.read_bytes` and `libbeat.es.publish.write_bytes`. The size of my log files is 42GB. The size of the relevant lines in my log files is 37,508,554,927B (37.5GB). But after running `expvar_rates.py`, I get `libbeat.es.publish.read_bytes: total 243121926` and `libbeat.es.publish.write_bytes: total 56386818739`, which do not match my data properties.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [August 8, 2017, 1:05pm UTC](https://discuss.elastic.co/t/interpreting-filebeat-info-logs/93589/3 "2017-08-08T13:05:35Z")

</div>

This topic was automatically closed after 21 days. New replies are no longer allowed.
