# Is it possible to monitor elasticsearch using metricbeat and custom index name?

**URL:** https://discuss.elastic.co/t/is-it-possible-to-monitor-elasticsearch-using-metricbeat-and-custom-index-name/280084
**Category:** Beats
**Tags:** metricbeat
**Created:** [July 30, 2021, 2:00pm UTC](https://discuss.elastic.co/t/is-it-possible-to-monitor-elasticsearch-using-metricbeat-and-custom-index-name/280084 "2021-07-30T14:00:12Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)
#### Post date: [July 31, 2021, 4:03pm UTC](https://discuss.elastic.co/t/is-it-possible-to-monitor-elasticsearch-using-metricbeat-and-custom-index-name/280084/3 "2021-07-31T16:03:43Z")

</div>

I do not think it is possible anymore, Kibana expects the monitoring data to be in the `.monitoring-*` index.

This is a similar question where it is confirmed that you can't change: [Change monitoring index name for Kibana UI](https://discuss.elastic.co/t/change-monitoring-index-name-for-kibana-ui/268530)

The currently recommended way to monitor the stack is to use metricbeat shipping the data directly to elasticsearch.

You can create a template for the monitoring index and add an alias `lab-metricbeat` so your ILM policy will still apply.

---

_[View the full topic](https://discuss.elastic.co/t/is-it-possible-to-monitor-elasticsearch-using-metricbeat-and-custom-index-name/280084)._