# .monitoring\* indices do not exist

**URL:** https://discuss.elastic.co/t/monitoring-indices-do-not-exist/129656
**Category:** Elasticsearch
**Created:** [April 26, 2018, 12:05pm UTC](https://discuss.elastic.co/t/monitoring-indices-do-not-exist/129656 "2018-04-26T12:05:12Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![bobby259](https://avatars.discourse-cdn.com/v4/letter/b/9de053/32.png) [@bobby259](https://discuss.elastic.co/u/bobby259)
#### Post date: [April 26, 2018, 12:05pm UTC](https://discuss.elastic.co/t/monitoring-indices-do-not-exist/129656/1 "2018-04-26T12:05:13Z")

</div>

On our new 6.2 cluster, I configured x-pack and in monitoring (on kibana) I see "No Monitoring Data Found". When I look back into the indices,  
GET /\_cat/indices?v  
health status index uuid pri rep docs.count docs.deleted store.size pri.store.size  
green open .watcher-history-7-2018.04.25 pGQ2hQB-RyKBNDGevc-Fmg 1 1 744 0 1.3mb 688.2kb  
green open .watches bJjfJ0Y5RYyCSDR9yFwxEg 1 1 6 0 99.9kb 49.9kb  
green open .triggered\_watches \_tu5ce2JS-KRDoVU\_JEniA 1 1 0 0 205.6kb 102.8kb

Here's my elasticsearch.yml config:  
action.auto\_create\_index: .security,.monitoring\*,.watches,.triggered\_watches,.watcher-history\*,.ml\*  
xpack.security.enabled: false  
xpack.monitoring.enabled: true  
xpack.graph.enabled: false  
xpack.watcher.enabled: false

And, kibana.yml  
server.name: "es6-kibana-01"  
elasticsearch.url: "[http://es-host:9200](http://es-host:9200)"  
xpack.monitoring.elasticsearch.url: "[http://es-host:9200](http://es-host:9200)"  
xpack.security.enabled: false  
xpack.monitoring.enabled: true  
xpack.graph.enabled: false  
xpack.watcher.enabled: false

---

<div class="post-metadata">

### Author: ![JKhondhu](https://avatars.discourse-cdn.com/v4/letter/j/ed655f/32.png) [@JKhondhu](https://discuss.elastic.co/u/JKhondhu)
#### Post date: [April 26, 2018, 2:03pm UTC](https://discuss.elastic.co/t/monitoring-indices-do-not-exist/129656/2 "2018-04-26T14:03:06Z")

</div>

Did you install X-Pack on both Elasticsearch and Kibana?

Kibana automatically sends metrics to the Elasticsearch cluster specified in the elasticsearch.url property in kibana.yml, which defaults to [http://localhost:9200](http://localhost:9200).  
ref: [https://www.elastic.co/guide/en/x-pack/5.2/monitoring-kibana.html](https://www.elastic.co/guide/en/x-pack/5.2/monitoring-kibana.html)

After yaml files updated have Elasticsearch and Kibana since been restarted?

---

<div class="post-metadata">

### Author: ![bobby259](https://avatars.discourse-cdn.com/v4/letter/b/9de053/32.png) [@bobby259](https://discuss.elastic.co/u/bobby259)
#### Post date: [April 26, 2018, 2:08pm UTC](https://discuss.elastic.co/t/monitoring-indices-do-not-exist/129656/3 "2018-04-26T14:08:11Z")

</div>

Hi @JKhondhu

Yes, I installed x-pack on both elasticsearch and kibana nodes. And, the cluster has been restarted after config changes.

I do see indices related to watcher on my cluster but nothing related to monitoring. Am I missing any configuration in my .yml files?

---

<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 24, 2018, 2:08pm UTC](https://discuss.elastic.co/t/monitoring-indices-do-not-exist/129656/4 "2018-05-24T14:08:16Z")

</div>

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