- Kibana Guide: other versions:
- Introduction
- Set Up Kibana
- Installing Kibana
- Starting and stopping Kibana
- Configuring Kibana
- Running Kibana on Docker
- Accessing Kibana
- Connect Kibana with Elasticsearch
- Using Kibana with Tribe nodes
- Using Kibana in a production environment
- Upgrading Kibana
- Installing X-Pack
- Configuring Monitoring
- Configuring Security
- X-Pack Settings
- Breaking Changes
- Getting Started
- Discover
- Visualize
- Dashboard
- Timelion
- Machine Learning
- APM
- Graphing Connections in Your Data
- Dev Tools
- Monitoring
- Management
- Reporting from Kibana
- REST API
- Kibana Plugins
- Contributing to Kibana
- Limitations
- Release Highlights
- Release Notes
- Kibana 6.3.2
- Kibana 6.3.1
- Kibana 6.3.0
- Kibana 6.2.4
- Kibana 6.2.3
- Kibana 6.2.2
- Kibana 6.2.1
- Kibana 6.2.0
- Kibana 6.1.4
- Kibana 6.1.3
- Kibana 6.1.2
- Kibana 6.1.1
- Kibana 6.1.0
- Kibana 6.0.1
- Kibana 6.0.0
- Kibana 6.0.0-rc2
- Kibana 6.0.0-rc1
- Kibana 6.0.0-beta2
- Kibana 6.0.0-beta1
- Kibana 6.0.0-alpha2
- Kibana 6.0.0-alpha1
Cluster Alerts
editCluster Alerts
editThe Monitoring > Clusters page in Kibana summarizes the status of your Elastic stack. You can drill down into the metrics to view more information about your cluster and specific nodes, instances, and indices.
The Top Cluster Alerts shown on the Clusters page notify you of conditions that require your attention:
- Elasticsearch Cluster Health Status is Yellow (missing at least one replica) or Red (missing at least one primary).
- Elasticsearch Version Mismatch. You have Elasticsearch nodes with different versions in the same cluster.
- Kibana Version Mismatch. You have Kibana instances with different versions running against the same Elasticsearch cluster.
-
Logstash Version Mismatch. You have Logstash nodes with different versions reporting stats to the same monitoring cluster.
If you do not preserve the data directory when upgrading a Kibana or Logstash node, the instance is assigned a new persistent UUID and shows up as a new instance
-
X-Pack License Expiration. When the X-Pack license expiration date approaches, you will get notifications with a severity level relative to how soon the expiration date is:
- 60 days: Informational alert
- 30 days: Low-level alert
- 15 days: Medium-level alert
-
7 days: Severe-level alert
The 60-day and 30-day thresholds are skipped for Trial licenses, which are only valid for 30 days.
Monitoring checks the cluster alert conditions every minute. Cluster alerts are automatically dismissed when the condition is resolved.
Watcher must be enabled to view cluster alerts. If you have a Basic license, Top Cluster Alerts are not displayed.
Email Notifications
editTo receive email notifications for the Cluster Alerts:
- Configure an email account as described in Configuring email accounts.
- Navigate to the Management page in Kibana.
-
Go to the Advanced Settings page, find the
xpack:defaultAdminEmail
setting, and enter your email address.
Email notifications are sent only when Cluster Alerts are triggered and resolved.
On this page
ElasticON events are back!
Learn about the Elastic Search AI Platform from the experts at our live events.
Register now