# Change the index name used in elasticsearch module
**URL:** https://discuss.elastic.co/t/change-the-index-name-used-in-elasticsearch-module/176700
**Category:** Beats
**Tags:** metricbeat
**Created:** [April 12, 2019, 7:47pm UTC](https://discuss.elastic.co/t/change-the-index-name-used-in-elasticsearch-module/176700 "2019-04-12T19:47:45Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@mtoumi](https://discuss.elastic.co/u/mtoumi)
#### Post date: [April 12, 2019, 7:47pm UTC](https://discuss.elastic.co/t/change-the-index-name-used-in-elasticsearch-module/176700/1 "2019-04-12T19:47:46Z")
Hi
I am trying to monitor an es cluster using metricbeat elasticsearch module for some reason I can't change the index name sent to my monitoring cluster from .monitor-es-6-mb.
```
2019-04-12T19:31:55.671Z DEBUG [publisher] memqueue/ackloop.go:128 ackloop:
return ack to broker loop:17 [81/1959]
2019-04-12T19:31:55.671Z DEBUG [publisher] memqueue/ackloop.go:131 ackloop: done
send ack
2019-04-12T19:31:58.830Z DEBUG [publish] pipeline/processor.go:308 Publish event: {
"@timestamp": "2019-04-12T19:31:56.202Z",
"@metadata": {
"beat": "metricbeat",
"type": "doc",
"version": "6.6.2",
"index": ".monitoring-es-6-mb"
```
here is my config
```
metricbeat:
config:
modules:
path: /usr/share/metricbeat/modules.d/*.yml
reload:
enabled: false
output:
elasticsearch:
hosts:
- https://mycluster:443
index: kube-%{+yyyy.MM.dd}
password:
username:
file:
enabled: false
filename: metricbeat
number_of_files: 5
path: /usr/share/metricbeat/data
rotate_every_kb: 10000
path:
config: /usr/share/metricbeat
data: /usr/share/metricbeat/data
home: /usr/share/metricbeat
logs: /usr/share/metricbeat/logs
processors:
- add_cloud_metadata: null
setup:
template:
enabled: true
name: kube
pattern: kube-*
```
and I already have template called kube in monitoring cluster.
---
### Author:  [@shaunak](https://discuss.elastic.co/u/shaunak)
#### Post date: [April 15, 2019, 12:37pm UTC](https://discuss.elastic.co/t/change-the-index-name-used-in-elasticsearch-module/176700/2 "2019-04-15T12:37:03Z")
Could you post the contents of your `/usr/share/metricbeat/modules.d/elasticsearch.yml`? Please make sure to mask any sensitive information before posting. Thanks!
---
### Author:  [@mtoumi](https://discuss.elastic.co/u/mtoumi)
#### Post date: [April 15, 2019, 2:36pm UTC](https://discuss.elastic.co/t/change-the-index-name-used-in-elasticsearch-module/176700/3 "2019-04-15T14:36:32Z")
here is the config.
```
- hosts:
- http://mycluster:9200
metricsets:
- cluster_stats
- index
- index_summary
- shard
module: elasticsearch
period: 10s
xpack.enabled: true
```
and btw both clusters are running in kube cluster.
---
### Author:  [@shaunak](https://discuss.elastic.co/u/shaunak)
#### Post date: [April 16, 2019, 3:55pm UTC](https://discuss.elastic.co/t/change-the-index-name-used-in-elasticsearch-module/176700/4 "2019-04-16T15:55:47Z")
Are you trying to use Metricbeat to monitor Elasticsearch in order to use the Monitoring UI in Kibana? If so, it's not possible to change the index names from `.monitoring-*` (at least as of today). Those indices are meant to be for internal use only.
Or are you trying to use Metricbeat to monitor Elasticsearch and have its metrics indexed into `metricbeat-*`? In that case, you can simply remove the `xpack.enabled: true` setting from your `/usr/share/metricbeat/modules.d/elasticsearch.yml` config.
---
### Author:  [@mtoumi](https://discuss.elastic.co/u/mtoumi)
#### Post date: [April 18, 2019, 3:58am UTC](https://discuss.elastic.co/t/change-the-index-name-used-in-elasticsearch-module/176700/5 "2019-04-18T03:58:05Z")
the second scenario. for now I used logstash to index them with different name. are you saying. if I removed xpack.enabled: true I would be able to have index name of my choice or this is still not possible as of today. thanks for the help.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [May 16, 2019, 4:03am UTC](https://discuss.elastic.co/t/change-the-index-name-used-in-elasticsearch-module/176700/6 "2019-05-16T04:03:50Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.