# Stack Monitoring only viewing current index

**URL:** https://discuss.elastic.co/t/stack-monitoring-only-viewing-current-index/232604
**Category:** Metrics
**Created:** [May 14, 2020, 9:37am UTC](https://discuss.elastic.co/t/stack-monitoring-only-viewing-current-index/232604 "2020-05-14T09:37:18Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![probson](https://avatars.discourse-cdn.com/v4/letter/p/e47c2d/32.png) [@probson](https://discuss.elastic.co/u/probson)
#### Post date: [May 14, 2020, 9:37am UTC](https://discuss.elastic.co/t/stack-monitoring-only-viewing-current-index/232604/1 "2020-05-14T09:37:19Z")

</div>

Hi,

I am using ILM with metricbeat, within stack monitoring it seems i cannot view data beyond the current index, the previous indexs are available. My ILM policy is simply hot, 30 days or 50GB, no move to warm.

I am on 7.6.1

Thanks  
Phil

---

<div class="post-metadata">

### Author: ![chrisronline](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chrisronline/32/28230_2.png) [@chrisronline](https://discuss.elastic.co/u/chrisronline)
#### Post date: [May 14, 2020, 5:33pm UTC](https://discuss.elastic.co/t/stack-monitoring-only-viewing-current-index/232604/2 "2020-05-14T17:33:44Z")

</div>

Hi @probson,

Stack Monitoring indices (`.monitoring-*`) are not curated or managed by any ILM policy. Curation happens manually by Elasticsearch [through these settings](https://www.elastic.co/guide/en/elasticsearch/reference/current/monitoring-settings.html). Any ILM policies created by Metricbeat do not apply to monitoring indices.

Does that help?

---

<div class="post-metadata">

### Author: ![probson](https://avatars.discourse-cdn.com/v4/letter/p/e47c2d/32.png) [@probson](https://discuss.elastic.co/u/probson)
#### Post date: [May 14, 2020, 5:47pm UTC](https://discuss.elastic.co/t/stack-monitoring-only-viewing-current-index/232604/3 "2020-05-14T17:47:08Z")

</div>

Hi,

I should say that in using metric beat with the xpack modules to monitor rather than xpack monitoring.

Kind regards  
Phil

---

<div class="post-metadata">

### Author: ![chrisronline](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chrisronline/32/28230_2.png) [@chrisronline](https://discuss.elastic.co/u/chrisronline)
#### Post date: [May 14, 2020, 6:16pm UTC](https://discuss.elastic.co/t/stack-monitoring-only-viewing-current-index/232604/4 "2020-05-14T18:16:33Z")

</div>

Hi @probson,

Unfortunately, that doesn't matter for this situation.

[The elasticsearch Metricbeat module](https://www.elastic.co/guide/en/beats/metricbeat/current/metricbeat-module-elasticsearch.html) indexes into different indices based on the `xpack.enabled` flag (which is enabled by default with the `elasticsearch-xpack` module). If `xpack.enabled` is `true`, Metricbeat will index into `.monitoring-es-*` indices. If `xpack.enabled` is `false` (or omitted), Metricbeat will index into `metricbeat-*` indices (or a custom index pattern if one is defined in `metricbeat.yml`).

The ILM policy that applies to `metricbeat-*` (or a custom index pattern defined in `metricbeat.yml`) does not have any effect on `.monitoring-es-*` indices.

It's confusing because Metricbeat almost always indexes into a consistent index pattern, but the `xpack.enabled` flag for the Elastic Stack modules will change this behavior.

Does that help?

---

<div class="post-metadata">

### Author: ![probson](https://avatars.discourse-cdn.com/v4/letter/p/e47c2d/32.png) [@probson](https://discuss.elastic.co/u/probson)
#### Post date: [May 15, 2020, 8:41am UTC](https://discuss.elastic.co/t/stack-monitoring-only-viewing-current-index/232604/5 "2020-05-15T08:41:13Z")

</div>

Hi @chrisronline,

Checked my config, it was logstash that i had xpack.monitoring.enabled: false, although can see .monitoring-logstash indices. Using metricbeat and xpack module for all servers.

I guess in elasticsearch.yml i need to set xpack.monitoring.history.duration  
What would be curating the monitoring.logstash indices in this case?

Thanks  
Phil

---

<div class="post-metadata">

### Author: ![chrisronline](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chrisronline/32/28230_2.png) [@chrisronline](https://discuss.elastic.co/u/chrisronline)
#### Post date: [May 15, 2020, 1:31pm UTC](https://discuss.elastic.co/t/stack-monitoring-only-viewing-current-index/232604/6 "2020-05-15T13:31:00Z")

</div>

HI @probson,

`xpack.monitoring.history.duration` setting in Elasticsearch covers curation for _all_ monitoring documents that live in that cluster, not just `.monitoring-es-*` documents.

---

<div class="post-metadata">

### Author: ![probson](https://avatars.discourse-cdn.com/v4/letter/p/e47c2d/32.png) [@probson](https://discuss.elastic.co/u/probson)
#### Post date: [May 15, 2020, 1:44pm UTC](https://discuss.elastic.co/t/stack-monitoring-only-viewing-current-index/232604/7 "2020-05-15T13:44:37Z")

</div>

Thanks @chrisronline, sounds like that is what i was looking for.

Kind regards  
Phil

---

<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: [June 12, 2020, 1:44pm UTC](https://discuss.elastic.co/t/stack-monitoring-only-viewing-current-index/232604/8 "2020-06-12T13:44:48Z")

</div>

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