We have successfully setup our Elastic Cluster - 7.17.5 with log-stash and search-guard.
We have enrolled ~530 nodes in our elastic cluster.
We tried to enable the HeartBeat to monitor/check the uptime of the nodes and more precisely to check the TLS cert expiration but with no success. The basic configuration we found in the Elasticsearch documentation also results in No Hosts Monitor Id or Url in Uptime.
However, we do see the data in the Observability in Kibana Discover (screenshot attached)
But nothing in the Uptime monitors(screenshot attached)
Configuration is default like available in the elastic documentation but I can share if needed.
We have seen that this issue persisted in version 7.6 of ELK.
Thanks Andrew! We mapped the direct connection to ES and it worked.
For users having similar issue -
To remind, we use version 7.17.5
We deleted the indices firstly, install heartbeat-elastic, configure the basic heartbeat.yml run the setup command, start the service
The heartbeat.yml included with other config the following -
And if you are using Searchguard like us, make sure the user you are using has correct(and limited) permissions in sg_roles.yml and the hash in sg_tenants.yml is correct
You have to restart the service heartbeat-elastic after each change.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.