---
title: Partial cluster metrics
description: Describes what AutoOps detects and surfaces with the Partial cluster metrics insight: Expected cluster metrics were not fully collected in a recent cycle.
url: https://docs-v3-preview.elastic.dev/elastic/autoops-insights/tree/main/elasticsearch/partial_cluster_metrics
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
---

# Partial cluster metrics
Expected cluster metrics were not fully collected in a recent cycle. Incomplete telemetry limits monitoring accuracy and can hide developing issues until collection recovers.
<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 |


## 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.

### Some statistics were not received for the cluster


#### What was detected

Missing or stale metric sets: 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 one or more metric sets are missing or stale, analysis runs on an incomplete picture of cluster health.
Common causes include an overloaded cluster that responds slowly to stats APIs, network issues between the monitoring agent and Elasticsearch, or transient node unavailability during collection.
If partial collection continues, other conditions might go undetected or insights might be delayed until full statistics return.