# No monitoring data found **URL:** \ **Category:** Elasticsearch\ **Created:** [February 12, 2018, 5:00pm UTC](https://discuss.elastic.co/t/no-monitoring-data-found/119516 "2018-02-12T17:00:06Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![alexvollmer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexvollmer/32/27381_2.png) [@alexvollmer](https://discuss.elastic.co/u/alexvollmer)\ **Post date:** [February 12, 2018, 5:00pm UTC](https://discuss.elastic.co/t/no-monitoring-data-found/119516/1 "2018-02-12T17:00:06Z")
We've been running Kibana and ES 5.6 with the basic license for quite a few months for the monitoring feature. For some reason now when I go to the monitoring section I get the dreaded "No monitoring data found" error. I've searched the forums and seen that others are having this issue, but none of those topics have resolved the issue for me. I can see that both .monitoring-es-6\* and .monitoring-kibana-6\* indices are being written regularly and appear to be current. I've also restarted both ES and Kibana as well as deleted all of the .monitoring-\* indices and am still seeing the same issue. Any help is appreciated! ---
**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\ **Post date:** [February 16, 2018, 11:30pm UTC](https://discuss.elastic.co/t/no-monitoring-data-found/119516/2 "2018-02-16T23:30:08Z")
When you look at the `/_nodes/settings` API for the "monitored" cluster, do you see any settings such as: ```auto xpack.monitoring.collection.interval ``` ```auto xpack.monitoring.exporters ``` ```auto xpack.monitoring.enabled ``` - If the `enabled` setting is there, it should not be `false` for any of the nodes in the cluster. - If the `collection.interval` setting is there, it should be at least 10 seconds. If it is `-1`, Monitoring is disabled for that node. - If the `exporters` setting is there, it should be the same for all of the nodes in the cluster AND Kibana has to "point" to the monitoring cluster through the `xpack.monitoring.elasticsearch.url` setting in `kibana.yml`. Collection interval and exporters should be the same for every node in the cluster. If you don't have monitoring exporters configured for the nodes, you should not have a `xpack.monitoring.elasticsearch.url` setting in `kibana.yml`. `/_nodes/settings` is one of the Nodes Info APIs: [https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-nodes-info.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-nodes-info.html) Hope that helps! ---
**Author:** ![hahuang65](https://avatars.discourse-cdn.com/v4/letter/h/50afbb/32.png) [@hahuang65](https://discuss.elastic.co/u/hahuang65)\ **Post date:** [February 21, 2018, 7:06pm UTC](https://discuss.elastic.co/t/no-monitoring-data-found/119516/4 "2018-02-21T19:06:39Z")
Checking out your suggestions, I've noticed that the only xpack settings we have are: ```json "xpack": { "ml": { "enabled": "false" }, "security": { "enabled": "false" }, "watcher": { "enabled": "false" } } ``` How would you suggest we move forward? ---
**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\ **Post date:** [February 21, 2018, 8:29pm UTC](https://discuss.elastic.co/t/no-monitoring-data-found/119516/5 "2018-02-21T20:29:04Z")
Other than the cluster's node settings, do you have an `xpack.monitoring.elasticsearch.url` setting in Kibana.yml? ---
**Author:** ![pickypg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pickypg/32/62409_2.png) [@pickypg](https://discuss.elastic.co/u/pickypg)\ **Post date:** [February 22, 2018, 6:15pm UTC](https://discuss.elastic.co/t/no-monitoring-data-found/119516/6 "2018-02-22T18:15:37Z")
@alexvollmer Could you provide the output for: ```auto GET /_cluster/settings ``` as well? As @tsullivan is getting at, there's a few things that can go wrong here: 1. X-Pack monitoring can be disabled via the node's settings. But that appears to be completely using the defaults. 2. If you are / are not defining `xpack.monitoring.elasticsearch.url` within your `kibana.yml`, then the Monitoring UI may be looking at the wrong cluster for monitoring data. 3. With the cluster settings, it's possible to change the exporter(s) to point to a different location. The node settings that you added to this post suggest that it is using the local exporter, which keeps data in the _same_ cluster. If someone overrode this in the cluster settings, then it may be going to a different cluster. This can be done dynamically, so it may explain a sudden change. Hope that helps, Chris ---
**Author:** ![alexvollmer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexvollmer/32/27381_2.png) [@alexvollmer](https://discuss.elastic.co/u/alexvollmer)\ **Post date:** [February 23, 2018, 12:46am UTC](https://discuss.elastic.co/t/no-monitoring-data-found/119516/7 "2018-02-23T00:46:06Z")
It looks like our cluster settings are empty: ``` { “transient”: {}, “persistent”: {} } ``` ---
**Author:** ![pickypg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pickypg/32/62409_2.png) [@pickypg](https://discuss.elastic.co/u/pickypg)\ **Post date:** [February 23, 2018, 1:42am UTC](https://discuss.elastic.co/t/no-monitoring-data-found/119516/8 "2018-02-23T01:42:57Z")
Hi @alexvollmer, That's pretty normal. If X-Pack monitoring settings have not been messed with, then it's enabled by default and it uses the local exporter (routes documents to the same cluster). The things left to check are number 2 from above, and: ```auto GET /_cat/indices/.monitoring*?v ``` If this returns no indices, then this is likely the cause. Thanks, Chris ---
**Author:** ![alexvollmer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexvollmer/32/27381_2.png) [@alexvollmer](https://discuss.elastic.co/u/alexvollmer)\ **Post date:** [February 26, 2018, 5:38pm UTC](https://discuss.elastic.co/t/no-monitoring-data-found/119516/9 "2018-02-26T17:38:24Z")
That's the weird thing about this. When I check, there are monitoring indices: ``` [6626L02]: http prod-esw.smmt.io:8080/_cat/indices/.monitoring\*\?v HTTP/1.1 200 OK Connection: keep-alive Content-Length: 640 Content-Type: text/plain; charset=UTF-8 Date: Mon, 26 Feb 2018 17:35:36 GMT Server: nginx/1.12.1 content-encoding: gzip health status index uuid pri rep docs.count docs.deleted store.size pri.store.size yellow open .monitoring-kibana-6-2018.02.26 ogapX5UWTtSzdY5DJmF0hg 1 1 6294 0 4.4mb 4.4mb yellow open .monitoring-kibana-6-2018.02.24 036cKPiiRPyBieEMnrVx_w 1 1 8638 0 3.1mb 3.1mb yellow open .monitoring-es-6-2018.02.26 OIRJnER6TmCALS3JrfgwOA 1 1 1628561 11557 993.5mb 993.5mb yellow open .monitoring-es-6-2018.02.21 GGLOm3neSZmbh1_eYRrl1Q 1 1 2131526 7544 1.2gb 1.2gb yellow open .monitoring-es-6-2018.02.22 BkJ2qy5GStCcBldS9cLRIg 1 1 2148853 15834 1.2gb 1.2gb yellow open .monitoring-kibana-6-2018.02.22 vR3e5kaoQTSTIFz49WCooQ 1 1 8639 0 3.1mb 3.1mb yellow open .monitoring-kibana-6-2018.02.20 MPRs3_zTQ2OzD1e9o_RQTw 1 1 8638 0 3.1mb 3.1mb yellow open .monitoring-es-6-2018.02.24 29vVnW5_SYqvWvqavXJfJg 1 1 2183491 15604 1.2gb 1.2gb yellow open .monitoring-kibana-6-2018.02.21 wUtoydc8TiKKjVbnaoh-WQ 1 1 8638 0 3.1mb 3.1mb yellow open .monitoring-es-6-2018.02.23 Pona51QKTHWRfXRHlgywNQ 1 1 2165927 12976 1.2gb 1.2gb yellow open .monitoring-kibana-6-2018.02.23 M0br5L1_SliA0lB8eI1GqA 1 1 8638 0 3.1mb 3.1mb yellow open .monitoring-es-6-2018.02.25 3KTwIplGSPmt4qvWyOlaOA 1 1 2203234 7023 1.2gb 1.2gb yellow open .monitoring-kibana-6-2018.02.25 xjaGQ18UTFCstZ89pkSg7g 1 1 8635 0 3mb 3mb yellow open .monitoring-es-6-2018.02.20 M6WK8Lg9Qr2rajtCsOwOWA 1 1 2113960 10538 1.2gb 1.2gb ``` The indices appear to be current, but it's as if Kibana just doesn't know about them. I'll take a look at the `kibana.yml` settings. ---
**Author:** ![pickypg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pickypg/32/62409_2.png) [@pickypg](https://discuss.elastic.co/u/pickypg)\ **Post date:** [February 26, 2018, 5:55pm UTC](https://discuss.elastic.co/t/no-monitoring-data-found/119516/10 "2018-02-26T17:55:47Z")
Thanks, let us know. If Kibana is not seeing it, then that seems like the cause. There is a possibility that the monitoring indices are missing some data, but the index document counts look pretty consistent so I doubt it. Chris ---
**Author:** ![alexvollmer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexvollmer/32/27381_2.png) [@alexvollmer](https://discuss.elastic.co/u/alexvollmer)\ **Post date:** [February 27, 2018, 1:01am UTC](https://discuss.elastic.co/t/no-monitoring-data-found/119516/11 "2018-02-27T01:01:16Z")
So here's another data-point. We run Kibana as Docker images. As an experiment I kicked off another Docker image of Kibana running 5.6.6 (same as our ES node). Sure enough, monitoring returned. Digging deeper into our existing Kibana setup we were running an older Kibana (5.4.3). Once I redeployed it with the newer version the monitoring returned. ---
**Author:** ![pickypg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pickypg/32/62409_2.png) [@pickypg](https://discuss.elastic.co/u/pickypg)\ **Post date:** [February 27, 2018, 5:21am UTC](https://discuss.elastic.co/t/no-monitoring-data-found/119516/12 "2018-02-27T05:21:02Z")
Ah, that makes sense. There was a change in Monitoring 5.5+ that expected both sides to have 5.5+. Glad that you were able to find the cause! Chris ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 27, 2018, 5:21am UTC](https://discuss.elastic.co/t/no-monitoring-data-found/119516/13 "2018-03-27T05:21:48Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.