---
title: Partial data Was Received
description: Describes what AutoOps detects and surfaces with the Partial data Was Received insight: AutoOps received only partial metrics from the cluster in a collection cycle.
url: https://docs-v3-preview.elastic.dev/elastic/autoops-insights/tree/main/elasticsearch/partial_data_was_received
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 data Was Received
AutoOps received only partial metrics from the cluster in a collection cycle. Incomplete data limits monitoring accuracy and might hide developing issues.
<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

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

Impact: AutoOps received partial data from your cluster.
There might be several reasons to that:
1. Your cluster is too busy and struggles to return health metrics to the agent
2. There are networking issues between the agent and your cluster.