Visualizing monitoring data

From within the Stack Monitoring section of Kibana, you can view health and performance data for Elasticsearch, Logstash, Kibana, and Beats in real time, as well as analyze past performance.

Before you can see this data inside of Kibana, you need to configure stack monitoring and, for Elastic Cloud on Kubernetes and self-managed deployments, configure Kibana to retrieve and display monitoring data.

Review the following topics to learn more about the metrics and visualizations available in the Stack Monitoring area:

• Elasticsearch metrics
• Kibana metrics
• Integrations Server metrics ECH Elastic Cloud Hosted lets you manage and configure one or more deployments of the versioned Elastic Stack, hosted on Elastic Cloud. Availability Generally available This functionality is generally available and ready for production usage. ECE Elastic Cloud Enterprise is a self-managed orchestration platform for deploying and managing the Elastic Stack at scale. Availability Generally available This functionality is generally available and ready for production usage. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
• Beats metrics
• Logstash metrics

From the Stack Monitoring section, you can also configure Kibana alerts for stack monitoring metrics.

To investigate logs alongside the metrics shown in Stack Monitoring, open your shipped logs in Discover and filter by log level and time range to identify failures or anomalies that correlate with the metrics. Kibana provides a dedicated logs experience in Discover for data that matches logs-* indices. The data you query depends on how you ship logs:

• On Elastic Cloud Hosted and Elastic Cloud Enterprise, query FROM elastic-cloud-logs-* in ES|QL mode, or use the elastic-cloud-logs-* data view in classic mode. Kibana sets up the data view automatically when you enable logging and monitoring.
• On Elastic Cloud on Kubernetes and self-managed deployments, query the indices that match your log shipping setup in ES|QL mode, or use the matching data view in classic mode. Examples are the Filebeat or Elastic Agent output indices. For details, refer to Enable stack monitoring on ECK deployments or Enable stack monitoring for Elasticsearch on a self-managed cluster.

If you're having trouble accessing your monitoring data within the Stack Monitoring section, then refer to Troubleshooting visualizing monitoring data in Kibana.

If you enable monitoring across the Elastic Stack, each monitored component is considered unique based on its persistent UUID, which is written to the path.data directory when the node or instance starts.