After configuring and deploying the elasticsearch profile there were no results.
Also No QOS entered into the DB and appeared on the performance report.
Release : 9.2.0
Component : Restmon probe
Check If the status of the QOS_HTTP_STATUS returns is 200. If not, verify the logs to troubleshoot.
Using the REST Client verify that the endpoint is reachable and returns the expected response.
Can see below errors in the restmon logs
2020-06-19 16:38:18 ERROR RestAPICall - org.apache.http.NoHttpResponseException: xxxx:xx:xx:5680 failed to respond
at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:141)
at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:56)
at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:259)
2020-06-19 16:38:18 DEBUG RestAPICall - Finish RestAPICall http://xxxx:xx:xx:5680/_cluster/stats status: 400 time: 30,001 milliseconds
2020-06-19 16:38:18 DEBUG RestAPICall - Finish RestAPICall http://xxxx:xx:xx:5680/_cluster/health?level=indices status: 400 time: 30,001 milliseconds
2020-06-19 16:38:18 INFO DataCollector - ae_cluster~~181~~elasticsearch_monitoring data rowcount: 2
2020-06-19 16:38:18 INFO DataCollector - CollectAllDataAndInsertIntoDB for ae_cluster~~181~~elasticsearch_monitoring finished in 30021 milliseconds
2020-06-19 16:38:18 INFO ProfileHandler - Load metric data for processing ae_cluster~~181~~elasticsearch_monitoring
2020-06-19 16:38:18 INFO ProfileHandler - Loaded metric data for processing ae_cluster~~181~~elasticsearch_monitoring time: 80 milliseconds
In this use case the end server was using https but http was configured in the elalsticsearch profile .After this was changed the QOS data was successfully collected