It is time to say goodbye: This version of Elastic Cloud Enterprise has reached end-of-life (EOL) and is no longer supported.
The documentation for this version is no longer being maintained. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
Monitoring your installation
editMonitoring your installation
editElastic Cloud Enterprise by default collects monitoring data for your installation using Filebeat and Metricbeat. This data gets sent as monitoring indices to a dedicated logging-and-metrics deployment that is created whenever you install Elastic Cloud Enterprise on your first host. Data is collected on every runner that is part of your Elastic Cloud Enterprise installation and includes:
- Logs for all core services that are a part of Elastic Cloud Enterprise and monitoring metrics for core Elastic Cloud Enterprise services, system processes on the host, and any third-party software
- Logs and monitoring metrics for Elasticsearch clusters and for Kibana instances
These monitoring indices are collected in addition to the monitoring you might have enabled for specific clusters, which also provides monitoring metrics that you can access in Kibana.
In this section:
- Access logs and metrics - Where to find the logs and metrics that are collected.
- Capture heap dumps - Troubleshoot instances that run out of memory.
- Set the Retention Period for Logging and Metrics Indices - Set the retention period for the indices that Elastic Cloud Enterprise collects.
- Scenario: Knowing When You Need More Proxies - Keeping tabs on proxy performance.
The logging-and-metrics deployment is for use by your ECE installation only. You must not use this deployment to index monitoring data from your own Elasticsearch clusters or use it to index data from Beats and Logstash. Always create a separate, dedicated monitoring deployment for your own use.