Amazon OpenSearch Service has added 17 Cluster Insights that automatically identify why a cluster has entered red or yellow health status. The service now points to the affected nodes and recommends targeted fixes instead of requiring operators to correlate metrics manually across nodes and availability zones.
Six critical insights cover conditions that leave primary shards unassigned, producing a red status. Eleven more, ranging from medium to critical severity, diagnose problems that prevent replica shards from being allocated and leave a cluster yellow. Covered causes include Java Virtual Machine memory exhaustion, sustained CPU saturation, insufficient disk capacity, zone imbalance and incorrectly configured replica counts.
Recommendations vary with the detected cause. OpenSearch may advise moving to larger instances, adding storage or correcting shard-allocation settings. That should shorten a common troubleshooting path in which teams know that shards are unassigned but still have to locate the underlying resource or configuration problem.
The new diagnostics are available at no extra charge for domains running OpenSearch 1.0 or later and Elasticsearch 6.8 or later. Initial availability covers 11 regions across the United States, Canada, Australia, Japan and Europe. Teams outside those regions will need to wait for broader rollout or continue using existing monitoring and manual diagnosis.