# Filebeat Metrics

**URL:** https://discuss.elastic.co/t/filebeat-metrics/98127
**Category:** Beats
**Tags:** filebeat
**Created:** [August 23, 2017, 8:27pm UTC](https://discuss.elastic.co/t/filebeat-metrics/98127 "2017-08-23T20:27:17Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![akosmin](https://avatars.discourse-cdn.com/v4/letter/a/7ea924/32.png) [@akosmin](https://discuss.elastic.co/u/akosmin)
#### Post date: [August 23, 2017, 8:27pm UTC](https://discuss.elastic.co/t/filebeat-metrics/98127/1 "2017-08-23T20:27:17Z")

</div>

I know Filebeat can output metrics in its logfile but they appear to only be a subset of what is available via a GET /debug/vars when filebeat is running with -httpprof. If I am correct, I have some questions:

1. Why a subset? It seems there are some important metrics missing such as libbeat.logstash.published\_but\_not\_acked\_events

2. Are there any plans to extend what is output when metrics.enabled is set as True? I checked the release notes for the most current beta and see no activity regarding this.

3. Are there any plans to actually document these metrics anywhere? At this point, a user is left to interpret their meaning based on each metric's name. For some, the meaning many be obvious. For others, not so much.

Thanks in advance.

---

<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: [September 20, 2017, 8:27pm UTC](https://discuss.elastic.co/t/filebeat-metrics/98127/2 "2017-09-20T20:27:22Z")

</div>

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