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…

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: # 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 a…

Discuss the Elastic Stack

Non-zero metrics in the last 30s: meaning

Elastic Stack Beats

ptemmer (Pieter Temmerman) March 27, 2019, 3:53pm 3

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

Topic		Replies	Views
Non-zero metrics in the last 30s- Filebeat Beats filebeat	2	374	November 24, 2020
Filebeat - Non-zero metrics in the last 30s Beats docker , filebeat	2	798	July 5, 2021
Metricbeat logs - INFO Non-zero metrics in the last 30s Elasticsearch	1	886	November 6, 2017
.990056 logp.go:232:INFO No non-zero metrics in the last 30s Beats filebeat	7	638	May 29, 2018
INFO No non-zero metrics in the last 30s Beats filebeat	3	2065	June 30, 2017

Elasticsearch is a trademark of Elasticsearch BV, registered in the U.S. and in other countries
Trademarks
Terms
Privacy
Brand
Code of Conduct

Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.

Non-zero metrics in the last 30s: meaning

Related topics