# Change monitoring index name for Kibana UI

**URL:** https://discuss.elastic.co/t/change-monitoring-index-name-for-kibana-ui/268530
**Category:** Kibana
**Tags:** elastic-stack-monitoring
**Created:** [March 26, 2021, 6:15pm UTC](https://discuss.elastic.co/t/change-monitoring-index-name-for-kibana-ui/268530 "2021-03-26T18:15:59Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![Agraphie\_holidu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/agraphie_holidu/32/79243_2.png) [@Agraphie\_holidu](https://discuss.elastic.co/u/Agraphie_holidu)
#### Post date: [March 26, 2021, 6:15pm UTC](https://discuss.elastic.co/t/change-monitoring-index-name-for-kibana-ui/268530/1 "2021-03-26T18:15:59Z")

</div>

Hi,

I was wondering if it is possible to change the index (pattern) which Kibana uses for the UI under "Stack Monitoring". As far as I see we can already do this for filebeat (for Kibana) via `monitoring.ui.logs.index` so I was wondering if we can do exactly that for the cluster, nodes & index monitoring. As far as I understand it goes to `.monitoring-es-*` by default.

Backstory is that we would like to collect several metricbeat logs into different metricbeat indices with different ILM policies on a different cluster. As we can already specify a remote monitoring cluster configuring the index the UI reads from is the last missing piece.

Regards

---

<div class="post-metadata">

### Author: ![mikecote](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mikecote/32/58549_2.png) [@mikecote](https://discuss.elastic.co/u/mikecote)
#### Post date: [March 29, 2021, 1:58pm UTC](https://discuss.elastic.co/t/change-monitoring-index-name-for-kibana-ui/268530/2 "2021-03-29T13:58:16Z")

</div>

Hi, @Agraphie_holidu,

I can confirm this index name is no longer configurable, and Stack Monitoring will always read from `.monitoring-es-*`.

---

<div class="post-metadata">

### Author: ![Agraphie\_holidu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/agraphie_holidu/32/79243_2.png) [@Agraphie\_holidu](https://discuss.elastic.co/u/Agraphie_holidu)
#### Post date: [April 6, 2021, 7:52am UTC](https://discuss.elastic.co/t/change-monitoring-index-name-for-kibana-ui/268530/3 "2021-04-06T07:52:35Z")

</div>

Hi @mikecote,

thanks for your reply. As far as I see there are a couple of open PRs for changing this, right? E.g. this one [[Monitoring] Ensure Stack Monitoring UI works with `metricbeat-*` indices by chrisronline · Pull Request #96205 · elastic/kibana · GitHub](https://github.com/elastic/kibana/pull/96205)  
So if this gets merged Kibana can read from `metricbeat-*`? However, that still means we can't change the name dynamically.

With everyone (sooner or later) moving to metricbeat now instead of internal monitoring, it makes sense to save the metrics in different indices if you have different clusters (to have different retention times e.g. or just a cleaner setup) and using a separate cluster for storing these indices.

Currently as far as I see it's a paid feature to monitor several clusters through one Kibana. Though we would not require this, we would just like to store metrics from different clusters in one cluster, but observe them from individual Kibanas.

Are there any plans to go down this way?

---

<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: [May 4, 2021, 7:53am UTC](https://discuss.elastic.co/t/change-monitoring-index-name-for-kibana-ui/268530/4 "2021-05-04T07:53:28Z")

</div>

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