Loading

ECE platform monitoring

ECE

By default, Elastic Cloud Enterprise 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 host that is part of your Elastic Cloud Enterprise installation and includes:

  • Logs for all core services that are a part of Elastic Cloud Enterprise
  • 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 stack monitoring you might have enabled for specific clusters, which also provides monitoring metrics that you can access in Kibana.

In this section, you'll learn the following about using ECE platform monitoring:

  • Proxy log fields: The fields that are included in proxy logs. Proxy logs capture the search and indexing requests that proxies have sent to the Elasticsearch cluster, and requests that proxies have sent to the Kibana instance.
  • Set the retention period for logging and metrics indices: How to set the retention period for the indices that Elastic Cloud Enterprise collects.

For information about troubleshooting Elastic Cloud Enterprise using these metrics, and guidance on capturing other diagnostic information like heap dumps and thread dumps, refer to Troubleshoot Elastic Cloud Enterprise.

Important

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.