Monitoring Request Failed

Hi everyone,
I using kibana and elasticsearch verison 7.4.2 .

When I set the time interval between 1-15 minutes in the Kibana Stack Monitoring panel, I get the error 'Monitoring Request Failed: Unable to find the cluster in the selected time range. HTTP 404 '. I solve this problem when I randomly restart the nodes. Is there a way to fix this problem without restarting?

1

Are you using a dedicated monitoring cluster or are you using your production cluster as the monitoring cluster?

More specifically, is there a config for xpack.monitoring.elasticsearch.url in your kibana.yml ?Are you seeing any errors in your Elasticsearch logs?

Perhaps we could try to restart collection and see if that fixes the issue. Please try the following steps next:

  1. Stop all monitoring collection by running the following query against Elasticsearch:

Copy to clipboard

PUT _cluster/settings
{
  "persistent": {
    "xpack.monitoring.collection.enabled": false
  }
}
  1. Wait about 20 seconds. Re-run the query with the long output that you ran earlier. Verify that the timestamp s in the output are at least 20 seconds old. This will confirm that collection has indeed stopped.
  2. Start up collection again:

Copy to clipboard

PUT _cluster/settings
{
  "persistent": {
    "xpack.monitoring.collection.enabled": true
  }
}
  1. Wait about 20 seconds. Re-run the query with the long output that you ran earlier. Verify that the timestamp s in the output are current (or within the last 10 seconds). This will confirm that collection has indeed re-started. Especially verify that the timestamp nested inside the object with "key": "cluster_stats" is current.
  2. If all timestamps are current, visit the Kibana Monitoring UI and check if that's working again.
  3. If all timestamps are not current, check the Elasticsearch master node's logs for any errors and post them here.

Hope it helps,
Rashmi

hi @rashmi,

I get this error in my log file.

[2020-12-23T16:08:01,003][ERROR][o.e.x.m.c.c.ClusterStatsCollector] [master-3] collector [cluster_stats] timed out when collecting data

Shortly after I get this error while transferring data, I get a monitoring error as I mentioned above.

Unsuccessful () low level call on POST: /ticket/_bulk?refresh=false
# Audit trail of this API call:
 - [1] BadResponse: Node: http://192.168.3.71:9200/ Took: 00:01:00.0140872
 - [2] MaxTimeoutReached:
# OriginalException: Elasticsearch.Net.ElasticsearchClientException: Maximum timeout reached 
while retrying request. Call: Status code unknown from: POST /ticket/_bulk?refresh=false ---> 
System.Net.WebException: The operation has timed out
  at System.Net.HttpWebRequest.GetResponse()
   at Elasticsearch.Net.HttpWebRequestConnection.Request[TResponse](RequestData 
requestData)
   --- End of inner exception stack trace ---
# Request:
<Request stream not captured or already read to completion by serializer. Set 
DisableDirectStreaming() on ConnectionSettings to force it to be set on the response.>
# Response:
<Response stream not captured or already read to completion by serializer. Set 
DisableDirectStreaming() on ConnectionSettings to force it to be set on the response.>