Cluster metrics lost
Elastic Cloud Hosted lets you manage and configure one or more deployments of the versioned Elastic Stack, hosted on Elastic Cloud. Availability This functionality is generally available and ready for production usage. Elastic Cloud on Kubernetes extends Kubernetes orchestration capabilities to allow you to deploy and manage components of the Elastic Stack. Availability 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. Elastic Cloud Enterprise is a self-managed orchestration platform for deploying and managing the Elastic Stack at scale. Availability 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. Self-managed deployments are Elastic Stack deployments managed without the assistance of an orchestrator. Availability 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.
ECH
Generally available
ECK
Generally available
ECE
Generally available
Self-managed
Generally available
Cluster metrics stopped arriving within the monitoring window. Health and capacity signals are unavailable until collection resumes, which limits visibility into active issues and trends.
For a complete list of insights, refer to AutoOps insights.
| Field | Value |
|---|---|
| Component | Elasticsearch |
| Severity | Medium |
| Scope | Cluster |
| Domains | cluster-health, high-availability |
You can customize these settings to adjust when AutoOps detects this event and presents the insight. Refer to AutoOps event settings for details.
The default customization settings are:
| Setting | Type | Default |
|---|---|---|
| Cluster disconnect timeout in minutes | Integer | 180 |
The following is an example of what you might see when this insight is triggered. Real insights use live data and links from your deployment or cluster.
No metrics received for: node_stats, cluster_stats
AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
Check ingest client configuration
Condition: Always shown for this insight.
Verify the Beats, Elastic Agent, Logstash, or other clients shipping data to this cluster: confirm the process is running, connected to the cluster, and not reporting errors in its logs. Review index names, pipelines, and throughput settings match what you expect for this index pattern.
Monitoring depends on periodic metric collection from your cluster. When no statistics arrive for an extended period, health and capacity analysis runs on incomplete data and active issues might not surface until collection resumes.
Common causes include cluster or deployment unavailability, network issues between the monitoring agent and Elasticsearch, credential or permission problems, and firewall rules blocking the collection path.