.monitoring* indices do not exist

[bobby259]

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"
xpack.monitoring.elasticsearch.url: "http://es-host:9200"
xpack.security.enabled: false
xpack.monitoring.enabled: true
xpack.graph.enabled: false
xpack.watcher.enabled: false

[JKhondhu (Jymit Singh Khondhu)]

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.
ref: https://www.elastic.co/guide/en/x-pack/5.2/monitoring-kibana.html

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

[bobby259]

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?