Troubleshooting monitoring in Kibanaedit

Use the information in this section to troubleshoot common problems and find answers for frequently asked questions related to the Kibana monitoring features.

Cannot view the cluster because the license information is invalidedit

Symptoms:

The following error appears in a banner at the top of the screen in Kibana on the Stack Monitoring > Clusters page: You can't view the "<my_cluster>" cluster because the license information is invalid.

Resolution:

You cannot monitor a version 6.3 or later cluster from Kibana version 6.2 or earlier. To resolve this issue, upgrade Kibana to 6.3 or later. See Upgrading the Elastic Stack.

Filebeat index is corruptedit

Symptoms:

The Stack Monitoring application displays a Monitoring Request error indicating that an illegal argument exception has occurred because fielddata is disabled on text fields by default.

Resolution

  1. Stop all your Filebeat instances.
  2. Delete indices beginning with filebeat-$VERSION, where VERSION corresponds to the version of Filebeat running.
  3. Restart all your Filebeat instances.

No monitoring data is visible in Kibanaedit

Symptoms:

The Stack Monitoring page in Kibana is empty.

Resolution:

  1. Confirm that Kibana is seeking monitoring data from the appropriate Elasticsearch URL. By default, data is retrieved from the cluster specified in the elasticsearch.hosts setting in the kibana.yml file. If you want to retrieve it from a different monitoring cluster, set xpack.monitoring.elasticsearch.hosts. See Monitoring settings.
  2. Confirm that there is monitoring data available at that URL. It is stored in indices such as .monitoring-kibana-* and .monitoring-es-*. At a minimum, you must have monitoring data for the Elasticsearch production cluster. Once that data exists, Kibana can display monitoring data for other products in the cluster.
  3. Set the time filter to “Last 1 hour”. When monitoring data appears in your cluster, the page automatically refreshes with the monitoring summary.