---
title: Cluster metrics lost
description: Describes what AutoOps detects and surfaces with the Cluster metrics lost insight: Cluster metrics stopped arriving within the monitoring window.
url: https://docs-v3-preview.elastic.dev/elastic/autoops-insights/tree/main/elasticsearch/cluster_metrics_lost
products:
  - Elastic Cloud Enterprise
  - Elastic Cloud Hosted
  - Elastic Cloud on Kubernetes
  - Elasticsearch
applies_to:
  - Elastic Cloud Hosted: Generally available
  - Elastic Cloud on Kubernetes: Generally available
  - Elastic Cloud Enterprise: Generally available
  - Self-managed Elastic deployments: Generally available
---

# Cluster metrics lost
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.
<note>
  For a complete list of insights, refer to [AutoOps insights](https://docs-v3-preview.elastic.dev/elastic/autoops-insights/tree/main/elasticsearch).
</note>


## Insight details


| Field     | Value                             |
|-----------|-----------------------------------|
| Component | Elasticsearch                     |
| Severity  | Medium                            |
| Scope     | Cluster                           |
| Domains   | cluster-health, high-availability |


## Customization settings

You can customize these settings to adjust when AutoOps detects this event and presents the insight. Refer to [AutoOps event settings](https://docs-v3-preview.elastic.dev/elastic/docs-content/tree/main/deploy-manage/monitor/autoops/ec-autoops-event-settings) for details.
The default customization settings are:

| Setting                               | Type    | Default |
|---------------------------------------|---------|---------|
| Cluster disconnect timeout in minutes | Integer | `180`   |


## Example: What you might see in AutoOps

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 statistics were received for the cluster


#### What was detected

No metrics received for: node_stats, cluster_stats

#### Recommendations

<note>
  AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
</note>

<dropdown title="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.
</dropdown>


#### Background and impact

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.