# Non-zero metrics in the last 30s: meaning

**URL:** <https://discuss.elastic.co/t/non-zero-metrics-in-the-last-30s-meaning/173970>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [March 26, 2019, 4:28pm UTC](https://discuss.elastic.co/t/non-zero-metrics-in-the-last-30s-meaning/173970 "2019-03-26T16:28:38Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ptemmer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ptemmer/32/40184_2.png) [@ptemmer](https://discuss.elastic.co/u/ptemmer)\
**Post date:** [March 26, 2019, 4:28pm UTC](https://discuss.elastic.co/t/non-zero-metrics-in-the-last-30s-meaning/173970/1 "2019-03-26T16:28:38Z")

</div>

Hi,

Apparently logs are transferred from Filebeat to Elasticsearch, however the filebeat logs continiously show this message:

`2019-03-26T16:16:02.557Z	INFO	[monitoring]	log/log.go:144	Non-zero metrics in the last 30s	{"monitoring": {"metrics": {"beat":{"cpu":{"system":{"ticks":4850,"time":{"ms":17}},"total":{"ticks":13270,"time":{"ms":50},"value":13270},"user":{"ticks":8420,"time":{"ms":33}}},"handles":{"limit":{"hard":1048576,"soft":1048576},"open":10},"info":{"ephemeral_id":"7c1c5900-5cd8-4501-b239-e129556ac0c8","uptime":{"ms":8340079}},"memstats":{"gc_next":8065568,"memory_alloc":6501392,"memory_total":829244208}},"filebeat":{"events":{"added":18,"done":18},"harvester":{"open_files":3,"running":3}},"libbeat":{"config":{"module":{"running":0}},"output":{"events":{"acked":18,"batches":8,"total":18},"read":{"bytes":4770},"write":{"bytes":27528}},"pipeline":{"clients":10,"events":{"active":0,"published":18,"total":18},"queue":{"acked":18}}},"registrar":{"states":{"current":8,"update":18},"writes":{"success":8,"total":8}},"system":{"load":{"1":0.16,"15":0.43,"5":0.25,"norm":{"1":0.08,"15":0.215,"5":0.125}}}}}}`

I've been searching the forum, however similar threads do not reveal what this message actually means. Should I worry about it, or rather ignore it?

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![kvch](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kvch/32/72058_2.png) [@kvch](https://discuss.elastic.co/u/kvch)\
**Post date:** [March 27, 2019, 3:27pm UTC](https://discuss.elastic.co/t/non-zero-metrics-in-the-last-30s-meaning/173970/2 "2019-03-27T15:27:23Z")

</div>

It is a periodical metrics report by the Beat. If you are not interested in it or would like to see it less frequently you can configure it:

```auto
# If enabled, filebeat periodically logs its internal metrics that have changed
# in the last period. For each metric that changed, the delta from the value at
# the beginning of the period is logged. Also, the total values for
# all non-zero internal metrics are logged on shutdown. The default is true.
#logging.metrics.enabled: true

# The period after which to log the internal metrics. The default is 30s.
#logging.metrics.period: 30s

```

---

<div class="post-metadata">

**Author:** ![ptemmer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ptemmer/32/40184_2.png) [@ptemmer](https://discuss.elastic.co/u/ptemmer)\
**Post date:** [March 27, 2019, 3:53pm UTC](https://discuss.elastic.co/t/non-zero-metrics-in-the-last-30s-meaning/173970/3 "2019-03-27T15:53:16Z")

</div>

Thank you so much Noémi for pointing that out. Makes much more sense now!

---

<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:** [April 24, 2019, 3:53pm UTC](https://discuss.elastic.co/t/non-zero-metrics-in-the-last-30s-meaning/173970/4 "2019-04-24T15:53:21Z")

</div>

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