# How can i stop to generating monitoring index? its taking too much memory without any index creation

**URL:** <https://discuss.elastic.co/t/how-can-i-stop-to-generating-monitoring-index-its-taking-too-much-memory-without-any-index-creation/208710>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [November 20, 2019, 2:07pm UTC](https://discuss.elastic.co/t/how-can-i-stop-to-generating-monitoring-index-its-taking-too-much-memory-without-any-index-creation/208710 "2019-11-20T14:07:10Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mitesh\_Shah1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mitesh_shah1/32/46106_2.png) [@Mitesh\_Shah1](https://discuss.elastic.co/u/Mitesh_Shah1)\
**Post date:** [November 20, 2019, 2:07pm UTC](https://discuss.elastic.co/t/how-can-i-stop-to-generating-monitoring-index-its-taking-too-much-memory-without-any-index-creation/208710/1 "2019-11-20T14:07:11Z")

</div>

Hi i m using Elasticsearch 7.4  
i just install and setup Elasticsearch and configure network.host & discovery.seed\_hosts Parameter in /etc/elasticsearch/elasticsearch.yml file.  
Now, when i am seeing in kibana , it showing 0 manual index ( which is true as i haven't created any index yet ) but showing 7 system indexes with 2L + documents.  
can someone please help me over here ?  
what is benefits of this monitoring indexes ?  
can we stop it to be automatically generation ? if yes then how ? because xpack.monitoring.collection.enabled : true is not working in elasticsearch.yml file.

Also, in Kibana it showing only 1GB of Disk space available among 8GB.  
what does it mean ?? while using htop command in linux terminal it's showing 2GB in use from 8GB so confusing over here.

Please advise

---

<div class="post-metadata">

**Author:** ![Kaiyan\_Sheng](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kaiyan_sheng/32/38247_2.png) [@Kaiyan\_Sheng](https://discuss.elastic.co/u/Kaiyan_Sheng)\
**Post date:** [December 2, 2019, 10:28pm UTC](https://discuss.elastic.co/t/how-can-i-stop-to-generating-monitoring-index-its-taking-too-much-memory-without-any-index-creation/208710/2 "2019-12-02T22:28:40Z")

</div>

Did you try to set `xpack.monitoring.collection.enabled: false` in cluster setting? I'm not familiar with this part, @shaunak could you help us here please? 🙂

---

<div class="post-metadata">

**Author:** ![shaunak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shaunak/32/6643_2.png) [@shaunak](https://discuss.elastic.co/u/shaunak)\
**Post date:** [December 2, 2019, 11:17pm UTC](https://discuss.elastic.co/t/how-can-i-stop-to-generating-monitoring-index-its-taking-too-much-memory-without-any-index-creation/208710/3 "2019-12-02T23:17:34Z")

</div>

@Kaiyan_Sheng is on the right track here.

@Mitesh_Shah1, could you please run the following API call from Kibana \> Dev Tools \> Console and post the output here?

```auto
GET _cluster/settings?include_defaults=true&filter_path=**.xpack.monitoring

```

---

<div class="post-metadata">

**Author:** ![Mitesh\_Shah1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mitesh_shah1/32/46106_2.png) [@Mitesh\_Shah1](https://discuss.elastic.co/u/Mitesh_Shah1)\
**Post date:** [December 3, 2019, 6:37am UTC](https://discuss.elastic.co/t/how-can-i-stop-to-generating-monitoring-index-its-taking-too-much-memory-without-any-index-creation/208710/4 "2019-12-03T06:37:46Z")

</div>

@shaunak  
{  
"persistent" : {  
"xpack" : {  
"monitoring" : {  
"collection" : {  
"enabled" : "true"  
}  
}  
}  
},  
"defaults" : {  
"xpack" : {  
"monitoring" : {  
"collection" : {  
"cluster" : {  
"stats" : {  
"timeout" : "10s"  
}  
},  
"node" : {  
"stats" : {  
"timeout" : "10s"  
}  
},  
"indices" : ,  
"ccr" : {  
"stats" : {  
"timeout" : "10s"  
}  
},  
"index" : {  
"stats" : {  
"timeout" : "10s"  
},  
"recovery" : {  
"active\_only" : "false",  
"timeout" : "10s"  
}  
},  
"interval" : "10s",  
"ml" : {  
"job" : {  
"stats" : {  
"timeout" : "10s"  
}  
}  
}  
},  
"history" : {  
"duration" : "168h"  
},  
"elasticsearch" : {  
"collection" : {  
"enabled" : "true"  
}  
},  
"enabled" : "true"  
}  
}  
}  
}

after running API call you given, it shows above output.

I already did, xpack.monitoring.collection.enabled: false this in elasticsearch.yml

---

<div class="post-metadata">

**Author:** ![shaunak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shaunak/32/6643_2.png) [@shaunak](https://discuss.elastic.co/u/shaunak)\
**Post date:** [December 5, 2019, 5:38am UTC](https://discuss.elastic.co/t/how-can-i-stop-to-generating-monitoring-index-its-taking-too-much-memory-without-any-index-creation/208710/5 "2019-12-05T05:38:29Z")

</div>

Try issuing this API call:

```auto
PUT _cluster/settings
{
    "persistent": {
        "xpack.monitoring.collection.enabled": false
    }
}

```

Then call:

```auto
DELETE .monitoring*

```

That should delete your existing monitoring indices and not create new ones. You can check this by waiting for a minute or so and then calling:

```auto
GET _cat/indices/.monitoring*

```

You should not see any indices in the response.

Shaunak

---

<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:** [January 2, 2020, 5:38am UTC](https://discuss.elastic.co/t/how-can-i-stop-to-generating-monitoring-index-its-taking-too-much-memory-without-any-index-creation/208710/6 "2020-01-02T05:38:34Z")

</div>

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