# Filebeat metric

**URL:** https://discuss.elastic.co/t/filebeat-metric/55661
**Category:** Beats
**Created:** [July 15, 2016, 10:14pm UTC](https://discuss.elastic.co/t/filebeat-metric/55661 "2016-07-15T22:14:13Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![yanjun](https://avatars.discourse-cdn.com/v4/letter/y/a6a055/32.png) [@yanjun](https://discuss.elastic.co/u/yanjun)
#### Post date: [July 15, 2016, 10:14pm UTC](https://discuss.elastic.co/t/filebeat-metric/55661/1 "2016-07-15T22:14:13Z")

</div>

Hi, Does filebeat outputs any metrics. We 'd like to track its throughput and something like the lag offsets to the end of the files etc.

---

<div class="post-metadata">

### Author: ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)
#### Post date: [July 18, 2016, 6:14am UTC](https://discuss.elastic.co/t/filebeat-metric/55661/2 "2016-07-18T06:14:40Z")

</div>

Filebeat exposes some metrics through `-httpprof`: [https://www.elastic.co/guide/en/beats/filebeat/1.2/filebeat-command-line.html](https://www.elastic.co/guide/en/beats/filebeat/1.2/filebeat-command-line.html) In Filebeat 1.x there are very few variables. More were added in the 5.0 release, but still more have to be added. Part of this issue here is add additional "expvar" variables: [https://github.com/elastic/beats/issues/1913](https://github.com/elastic/beats/issues/1913) It would be interesting to hear which are the ones you are most interested in?

---

<div class="post-metadata">

### Author: ![yanjun](https://avatars.discourse-cdn.com/v4/letter/y/a6a055/32.png) [@yanjun](https://discuss.elastic.co/u/yanjun)
#### Post date: [July 25, 2016, 6:58pm UTC](https://discuss.elastic.co/t/filebeat-metric/55661/3 "2016-07-25T18:58:52Z")

</div>

Thanks for the reply. It's nice to have expvar interface. One potential use case we have is to use filebeat to simulate some Kafka behavior. So we are very interested in offset management. Very simple one is to know the current lag offset (how many bytes remaining to be be read). It will also be nice if we can reset or rewind the offset.

---

<div class="post-metadata">

### Author: ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)
#### Post date: [July 26, 2016, 6:33am UTC](https://discuss.elastic.co/t/filebeat-metric/55661/4 "2016-07-26T06:33:49Z")

</div>

The problem about the remaining offset is that it constantly changes. I can see that this could be useful for a predefined tests but not sure how this would be useful during daily production. Would you expect it to be an average over time or just the value of a point in time?

Expvar does only expose variables, it is not possible to interact with filebeat throug expvar. Means resetting / rewinding of offset is not possible. This goes more in the direction of an admin interface.

---

<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 5, 2016, 10:14pm UTC](https://discuss.elastic.co/t/filebeat-metric/55661/5 "2016-08-05T22:14:43Z")

</div>

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