# No monitoring data found **URL:** \ **Category:** Kibana\ **Tags:** elastic-stack-monitoring\ **Created:** [April 22, 2021, 7:39pm UTC](https://discuss.elastic.co/t/no-monitoring-data-found/271008 "2021-04-22T19:39:31Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![Chris\_Gatihi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chris_gatihi/32/25820_2.png) [@Chris\_Gatihi](https://discuss.elastic.co/u/Chris_Gatihi)\ **Post date:** [April 22, 2021, 7:39pm UTC](https://discuss.elastic.co/t/no-monitoring-data-found/271008/1 "2021-04-22T19:39:31Z")
Hi, I'm running on version 7.11.1 and I'm getting a "No monitoring data found" when I navigate to stack monitoring in Kibana. Kibana can access my Elasticsearch cluster just fine when going through the dev tools console or looking at the indices via the stack management UI. But for some reason the monitoring fails and if you look at the console in my screenshot it's failing to get anything back when it's making an AJAX call to for cluster and node info. ![Screen Shot 2021-04-22 at 12.34.00 PM](https://us1.discourse-cdn.com/elastic/original/3X/9/3/934fe7fa7dabf6b7a3724fa7ad634e9a8f37bf89.png) I also noticed that there are no monitoring indices being created (`GET /_cat/indices/.monitoring*?v` returns nothing). Any ideas what might be happening and how I might address this? Thanks, Chris ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [April 27, 2021, 1:51am UTC](https://discuss.elastic.co/t/no-monitoring-data-found/271008/2 "2021-04-27T01:51:43Z")
Did you make any configuration changes for Monitoring? ---
**Author:** ![Chris\_Gatihi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chris_gatihi/32/25820_2.png) [@Chris\_Gatihi](https://discuss.elastic.co/u/Chris_Gatihi)\ **Post date:** [April 27, 2021, 3:09am UTC](https://discuss.elastic.co/t/no-monitoring-data-found/271008/3 "2021-04-27T03:09:39Z")
Do you mean changes to `kibana.yml`? ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [April 27, 2021, 4:38am UTC](https://discuss.elastic.co/t/no-monitoring-data-found/271008/4 "2021-04-27T04:38:50Z")
Or to the Elasticsearch config, yep. ---
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [April 27, 2021, 5:02am UTC](https://discuss.elastic.co/t/no-monitoring-data-found/271008/5 "2021-04-27T05:02:18Z")
Hi @Chris_Gatihi you need to explicitly enable monitoring of an elasticsearch cluster see the overview [Here](https://www.elastic.co/guide/en/elasticsearch/reference/current/monitor-elasticsearch-cluster.html) and [The specifics Here](https://www.elastic.co/guide/en/elasticsearch/reference/current/configuring-metricbeat.html) ---
**Author:** ![Chris\_Gatihi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chris_gatihi/32/25820_2.png) [@Chris\_Gatihi](https://discuss.elastic.co/u/Chris_Gatihi)\ **Post date:** [April 27, 2021, 5:20am UTC](https://discuss.elastic.co/t/no-monitoring-data-found/271008/6 "2021-04-27T05:20:51Z")
No, no changes to either `elasticsearch.yml` or `kibana.yml` other than what was necessary to upgrade due to breaking changes. What's even more strange is that I have the same configuration in multiple regions monitoring works in the other regions but not in this one for some reason. And it used to work in this particular reason but for some reason stopped working recently. ---
**Author:** ![Chris\_Gatihi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chris_gatihi/32/25820_2.png) [@Chris\_Gatihi](https://discuss.elastic.co/u/Chris_Gatihi)\ **Post date:** [April 27, 2021, 5:23am UTC](https://discuss.elastic.co/t/no-monitoring-data-found/271008/7 "2021-04-27T05:23:09Z")
Monitoring has already been explicitly enabled for a while. I upgraded to the latest version recently and it wasn't working for a while on 6.8, neither is it now working on 7.11. I'm pretty sure it worked when I first got on 6.8. And the strangest part is that I have other regions and this same configuration works in other regions, just not this one. ---
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [April 27, 2021, 5:27am UTC](https://discuss.elastic.co/t/no-monitoring-data-found/271008/8 "2021-04-27T05:27:58Z")
The old / legacy self monitoring (click and enable) has been deprecated that may be why it is no longer working for you in 7.11. I suggest you look the docs that were referenced above. In the end the new way to do it is with metricbeat The legacy method should still work but I suspect the settings have changed since 6.8 ---
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [April 27, 2021, 5:41am UTC](https://discuss.elastic.co/t/no-monitoring-data-found/271008/9 "2021-04-27T05:41:03Z")
I just set up a fresh 7.11.1 Cluster with Elasticsearch No Changes to the .ymls I setup the legacy default monitoring and it still works. ![Screen Shot 2021-04-26 at 10.36.26 PM](https://us1.discourse-cdn.com/elastic/original/3X/1/4/149f8b3a2eb087e5cd16d3cdf1486a534a077050.png) ![Screen Shot 2021-04-26 at 10.36.48 PM](https://us1.discourse-cdn.com/elastic/original/3X/1/7/17ef446828f6a6ce07ec144bf5ba1aa8a71df1e0.png) ``` GET _cat/indices/.mon*/?v health status index uuid pri rep docs.count docs.deleted store.size pri.store.size green open .monitoring-kibana-7-2021.04.27 jNEqquJGQKu69G9LNPf9Sg 1 0 20 0 159.6kb 159.6kb green open .monitoring-es-7-2021.04.27 LvxAIGA7SvOn8nEoXyeiLQ 1 0 218 160 238.3kb 238.3kb ``` ![Screen Shot 2021-04-26 at 10.40.26 PM](https://us1.discourse-cdn.com/elastic/original/3X/3/1/31473237e93192d2c05ae982e127d9b37b7199af.png) Check your cluster settings to see `GET _cluster/settings` And take look at `xpack.monitoring.collection.enabled` If doing legacy on localhost should look something like ``` { "persistent" : { "xpack" : { "monitoring" : { "collection" : { "enabled" : "true" } } } }, "transient" : { } } ``` ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 25, 2021, 5:41am UTC](https://discuss.elastic.co/t/no-monitoring-data-found/271008/10 "2021-05-25T05:41:41Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.