# XPack Monitoring Issue

**URL:** <https://discuss.elastic.co/t/xpack-monitoring-issue/214312>\
**Category:** Kibana\
**Created:** [January 8, 2020, 10:12pm UTC](https://discuss.elastic.co/t/xpack-monitoring-issue/214312 "2020-01-08T22:12:49Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![aniaks](https://avatars.discourse-cdn.com/v4/letter/a/ac8455/32.png) [@aniaks](https://discuss.elastic.co/u/aniaks)\
**Post date:** [January 8, 2020, 10:12pm UTC](https://discuss.elastic.co/t/xpack-monitoring-issue/214312/1 "2020-01-08T22:12:49Z")

</div>

In Kibana when i try to enable to monitoring i am getting the following error

" We checked the cluster defaults settings and found that `xpack.monitoring.enabled` is set to `false` set, which disables monitoring. Removing the `xpack.monitoring.enabled: false` setting from your configuration will put the default into effect and enable Monitoring."

However when i get the cluster settings i am seeing that xpack is enabled

`
{
  "persistent" : {
    "xpack" : {
      "monitoring" : {
        "elasticsearch" : {
          "collection" : {
            "enabled" : "true"
          }
        },
        "collection" : {
          "enabled" : "true"
        }
      }
    }
  },
  "transient" : { }
}
`

---

<div class="post-metadata">

**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\
**Post date:** [January 9, 2020, 4:55pm UTC](https://discuss.elastic.co/t/xpack-monitoring-issue/214312/2 "2020-01-09T16:55:28Z")

</div>

Hi, which version of Kibana do you have?

Do you have more than 1 cluster (e.g. a separate monitoring cluster)?

---

<div class="post-metadata">

**Author:** ![aniaks](https://avatars.discourse-cdn.com/v4/letter/a/ac8455/32.png) [@aniaks](https://discuss.elastic.co/u/aniaks)\
**Post date:** [January 22, 2020, 3:25pm UTC](https://discuss.elastic.co/t/xpack-monitoring-issue/214312/3 "2020-01-22T15:25:21Z")

</div>

thanks for replying, the problem was due to the space issues. Cluster went to read only after it ran out of space. is there a way to delete indices older than number of days via kibana ? which we can use to avoid the space issues.

---

<div class="post-metadata">

**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\
**Post date:** [January 22, 2020, 4:23pm UTC](https://discuss.elastic.co/t/xpack-monitoring-issue/214312/4 "2020-01-22T16:23:06Z")

</div>

> [@aniaks](#):
>
> is there a way to delete indices older than number of days via kibana

In Kibana there is index management: [Index management | Kibana Guide [8.11] | Elastic](https://www.elastic.co/guide/en/kibana/current/managing-indices.html)

If you are looking for a more automated solution, there is an API in Elasticsearch called Index Lifecycle Management: [ILM: Manage the index lifecycle | Elasticsearch Guide [8.11] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/index-lifecycle-management.html)

I hope that helps!

---

<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:** [February 19, 2020, 4:23pm UTC](https://discuss.elastic.co/t/xpack-monitoring-issue/214312/5 "2020-02-19T16:23:14Z")

</div>

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