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.
For a complete list of insights, refer to AutoOps insights.
| Field | Value |
|---|---|
| Component | Elasticsearch |
| Severity | Medium |
| Scope | Cluster |
| Domains | cluster-health |
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.
Missing or stale metric sets: 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 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.