heartbeat.monitors:
Notice there is a sample monitor of type http with id my-monitor. Comment out or delete this monitor (but leave the heartbeat.monitors line in the config file).
I received the following error - Exiting: error loading config file: yaml: line 23: did not find expected key.
I am not sure what to comment out and I do not see a solution box to guide me.
Hello Shahzad , I have no idea about heartbeat as I am in the uptime lab. Item 4 below is where I am confused. I am not sure what part to comment out.
I provided a screenshot of what I did comment out and the associated error.
Thank you for your time.
Lab 1.2 - Uptime
Objective:
The goal of this lab is to use Heartbeat to monitor the uptime of various services, including the Pet Clinic client and server, the MySQL database, and your Elasticsearch instance.
First of all, change directories into the heartbeat directory:
Notice there is a sample monitor of type http with id my-monitor. Comment out or delete this monitor (but leave the heartbeat.monitors line in the config file).
Thank you Andre. Unfortunately I do not understand. Is there a way to talk on the phone and see exactly what I should and should not comment out to carry on with the lab request?
Other portions of the lab show what the final version should look like. I am not sure why this one step does not do the same thing.
As a novice to Elastic but with an Admin cert with Splunk, should I even be starting in this area or looking lower level?
I'm sorry you are having troubles. In step 21 you can find the full configuration file. You can copy that to a brand new heartbeat.yml file and you should be able to start heartbeat with the configurations provided through lab instructions.
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.