# Monitoring history not being deleted
**URL:** https://discuss.elastic.co/t/monitoring-history-not-being-deleted/217239
**Category:** Elasticsearch
**Created:** [January 30, 2020, 4:05pm UTC](https://discuss.elastic.co/t/monitoring-history-not-being-deleted/217239 "2020-01-30T16:05:49Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Ronin](https://discuss.elastic.co/u/Ronin)
#### Post date: [January 30, 2020, 4:05pm UTC](https://discuss.elastic.co/t/monitoring-history-not-being-deleted/217239/1 "2020-01-30T16:05:49Z")
We have a monitoring cluster that is set up to monitor 3 other clusters and the beats for those clusters. The monitoring cluster is being filled up with indices such as .monitoring-es-7-2019.12.28. Looking at documentation here: [https://www.elastic.co/guide/en/elasticsearch/reference/current/monitoring-settings.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/monitoring-settings.html) with `xpack.monitoring.history.duration` it defaults to 7 days. However, with a note it only impacts local type exporters and not http exporters. I am unclear if, since we are sending the monitoring to the monitoring cluster, that is an http exporter in this case. If that is, then what is the recommended way to handle cleanup of the old indicies in the monitoring cluster? A ILM policy?
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 27, 2020, 4:05pm UTC](https://discuss.elastic.co/t/monitoring-history-not-being-deleted/217239/2 "2020-02-27T16:05:50Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.