Log analytics integration - Errors in filebeat logs

Products

• DX OI SaaS

Issue/Introduction

The version of filebeat (23.12.2.1) is generating error logs "Non-zero metrics in the last 30s". we do not believe this should be an error. Can you please confirm this is ok and if so can you look at changing this to info rather than error?

{"log.level":"info","@timestamp":"2024-02-13T14:10:40.968Z","log.logger":"monitoring","log.origin":{"file.name":"log/log.go","file.line":187},"message":"Non-zero metrics in the last 30s","service.name":"filebeat","monitoring":{"metrics":{"beat":{"cpu":{"system":{"ticks":212490},"total":

Apparently logs are transferred from filebeat to Elasticsearch, however the filebeat logs continuously 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":

Environment

filebeat (23.12.2.1)

Resolution

The Google cloud logging is showing it as "Error"

whereas the messages are info only ( jsonpayload captured by Google)

 

Google cloud solution adds severity: