- 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
IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
Monitoring
editMonitoring
editX-Pack monitoring in Kibana serves two separate purposes:
- To visualize monitoring data from across the Elastic Stack. You can view health and performance data for Elasticsearch, Logstash, and Beats in real time, as well as analyze past performance. For more information, see Monitor a cluster.
- To monitor Kibana itself and route that data to the monitoring cluster.
If you enable X-Pack monitoring across the Elastic Stack, a monitoring agent runs on
each Elasticsearch node, Logstash node, Kibana instance, and Beat to collect and index
metrics. Each node and instance is considered unique based on its persistent
UUID, which is written to the path.data directory when the node
or instance starts.
Was this helpful?
Thank you for your feedback.