- Kibana Guide: other versions:
- What is Kibana?
- What’s new in 7.15
- Kibana concepts
- Quick start
- Set up
- Install Kibana
- Configure Kibana
- Alerting and action settings
- APM settings
- Banners settings
- Development tools settings
- Graph settings
- Fleet settings
- i18n settings
- Logging settings
- Logs settings
- Metrics settings
- Machine learning settings
- Monitoring settings
- Reporting settings
- Secure settings
- Search sessions settings
- Security settings
- Spaces settings
- Task Manager settings
- Telemetry settings
- URL drilldown settings
- Start and stop Kibana
- Access Kibana
- Securing access to Kibana
- Add data
- Upgrade Kibana
- Configure security
- Configure reporting
- Configure monitoring
- Production considerations
- Discover
- Dashboard and visualizations
- Canvas
- Maps
- Build a map to compare metrics by country or region
- Track, visualize, and alert on assets in real time
- Map custom regions with reverse geocoding
- Heat map layer
- Tile layer
- Vector layer
- Plot big data
- Search geographic data
- Configure map settings
- Connect to Elastic Maps Service
- Import geospatial data
- Troubleshoot
- Reporting and sharing
- Machine learning
- Graph
- Alerting
- Observability
- APM
- Security
- Dev Tools
- Fleet
- Osquery
- Stack Monitoring
- Stack Management
- REST API
- Get features API
- Kibana spaces APIs
- Kibana role management APIs
- User session management APIs
- Saved objects APIs
- Index patterns APIs
- Alerting APIs
- Action and connector APIs
- Import and export dashboard APIs
- Logstash configuration management APIs
- Shorten URL
- Get Task Manager health
- Upgrade assistant APIs
- Kibana plugins
- Accessibility
- Release notes
- Developer guide
IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
Troubleshooting monitoring in Kibana
editTroubleshooting monitoring in Kibana
editUse 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 invalid
editSymptoms:
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.
No monitoring data is visible in Kibana
editSymptoms:
The Stack Monitoring page in Kibana is empty.
Resolution:
- Confirm that you are not using Kibana 6.7.0 or 6.7.1. If you have a version 7.0 monitoring cluster, a version 6.7 production cluster and Kibana version 6.7.0 or 6.7.1, you cannot see the monitoring data in Kibana. For more information, see https://github.com/elastic/kibana/issues/34357
-
Confirm that Kibana is seeking monitoring data from the appropriate Elasticsearch URL.
By default, data is retrieved from the cluster specified in the
elasticsearch.hostssetting in thekibana.ymlfile. If you want to retrieve it from a different monitoring cluster, setmonitoring.ui.elasticsearch.hosts. See Monitoring settings. -
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. - Set the time filter to “Last 1 hour”. When monitoring data appears in your cluster, the page automatically refreshes with the monitoring summary.
On this page
Was this helpful?
Thank you for your feedback.