# Elasticsearch 7.17 spamming INFO \[monitoring\] log/log.go:184 Non-zero metrics in the last 30s

**URL:** https://discuss.elastic.co/t/elasticsearch-7-17-spamming-info-monitoring-log-log-go-184-non-zero-metrics-in-the-last-30s/361600
**Category:** Elasticsearch
**Tags:** elastic-stack-monitoring, runtime-fields
**Created:** [June 17, 2024, 8:49pm UTC](https://discuss.elastic.co/t/elasticsearch-7-17-spamming-info-monitoring-log-log-go-184-non-zero-metrics-in-the-last-30s/361600 "2024-06-17T20:49:07Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![joeelasticsearch](https://avatars.discourse-cdn.com/v4/letter/j/edb3f5/32.png) [@joeelasticsearch](https://discuss.elastic.co/u/joeelasticsearch)
#### Post date: [June 17, 2024, 8:49pm UTC](https://discuss.elastic.co/t/elasticsearch-7-17-spamming-info-monitoring-log-log-go-184-non-zero-metrics-in-the-last-30s/361600/1 "2024-06-17T20:49:07Z")

</div>

Hello, I am supporting a few barebones installations of Elasticsearch running on Kubernetes. Is there a way I can get this log to go away? I do not need to see it every 30s. I've tried using the following but it didn't do anything. I am not entirely sure where the log is originating from:

```auto
curl -X PUT "localhost:9200/_cluster/settings?pretty" -H 'Content-Type: application/json' -d'
{
  "persistent": {
    "xpack.monitoring.collection.enabled": false
  }
}
'

```

Here is full log:

```auto
INFO [monitoring] log/log.go:184 Non-zero metrics in the last 30s {"monitoring": {"metrics": {"beat":{"cpu":{"system":{"ticks":620,"time":{"ms":3}},"total":{"ticks":1730,"time":{"ms":7},"value":1730},"user":{"ticks":1110,"time":{"ms":4}}},"handles":{"limit":{"hard":1048576,"soft":1048576},"open":11},"info":{"ephemeral_id":"adc44a73-a9bc-479d-bca3-2e89727d8e90","uptime":{"ms":3660115},"version":"7.17.6"},"memstats":{"gc_next":21560440,"memory_alloc":11605552,"memory_total":153605880,"rss":111964160},"runtime":{"goroutines":73}},"filebeat":{"harvester":{"open_files":0,"running":0}},"libbeat":{"config":{"module":{"running":1}},"output":{"events":{"active":0}},"pipeline":{"clients":7,"events":{"active":0}}},"registrar":{"states":{"current":0}},"system":{"load":{"1":8.39,"15":11.41,"5":9.97,"norm":{"1":0.5244,"15":0.7131,"5":0.6231}}}}}}

```

---

<div class="post-metadata">

### Author: ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)
#### Post date: [June 17, 2024, 9:52pm UTC](https://discuss.elastic.co/t/elasticsearch-7-17-spamming-info-monitoring-log-log-go-184-non-zero-metrics-in-the-last-30s/361600/2 "2024-06-17T21:52:48Z")

</div>

This log isn't coming from Elasticsearch AFAICT, it looks like it's from one of your Beats:

> <https://github.com/elastic/beats/blob/cb3e08503453562298f747b13e3cbc1c413d5896/libbeat/monitoring/report/log/log.go#L192>