Amazon OpenSearch Service has enhanced Cluster Insights with two new insights — Cluster Overload and Suboptimal Sharding Strategy. Suboptimal Sharding Strategy provides instant visibility into shard imbalances that cause uneven workload distribution, while Cluster Overload surfaces elevated cluster resource utilization that can lead to request throttling or rejections. Both insights come with details of affected resources along with actionable mitigation recommendations.
Previously, identifying resource constraints and shard imbalances required manually correlating multiple metrics and logs, making it difficult to detect issues early. With these new insights, you can proactively monitor cluster health and take timely action.
Suboptimal Sharding Strategy detects shard imbalances caused by indices with too few shards relative to the number of data nodes, or by shards carrying disproportionately large amounts of data compared to others. It identifies the root cause of uneven workload distribution and provides recommendations to help you achieve optimal shard distribution for improved query performance and resource utilization. Similarly, Cluster Overload helps you identify elevated resource utilization, including CPU, memory, disk I/O, disk throughput, and disk utilization that can potentially lead to request throttling or rejections. It also provides scale-up recommendations so you can take timely action to protect your critical workloads.
These new insights are available at no additional cost for OpenSearch version 2.17 or later in all Regions where the OpenSearch UI is available. See the complete list of supported Regions here. To learn more, visit the Cluster Insights documentation or view the complete catalog of available insights.
Categories: general:products/amazon-opensearch-service,marketing:marchitecture/analytics
Source: Amazon Web Services
Latest Posts
- Amazon CloudWatch logs centralization rules now support customizable destination log group structure

- Collaborate with Copilot in Outlook while drafting email [MC1239932]
![Collaborate with Copilot in Outlook while drafting email [MC1239932] 3 pexels pixabay 50577](data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==)
- (Updated) Microsoft Teams: Choose to hide inactive channels [MC1141958]
![(Updated) Microsoft Teams: Choose to hide inactive channels [MC1141958] 4 pexels cottonbro 5474294](data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==)
- (Updated) Microsoft Teams: External domains anomalies report [MC1219794]
![(Updated) Microsoft Teams: External domains anomalies report [MC1219794] 5 pexels pixabay 39531](data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==)


![Collaborate with Copilot in Outlook while drafting email [MC1239932] 3 pexels pixabay 50577](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-pixabay-50577-150x150.webp)
![(Updated) Microsoft Teams: Choose to hide inactive channels [MC1141958] 4 pexels cottonbro 5474294](https://mwpro.co.uk/wp-content/uploads/2025/06/pexels-cottonbro-5474294-150x150.webp)
![(Updated) Microsoft Teams: External domains anomalies report [MC1219794] 5 pexels pixabay 39531](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-pixabay-39531-150x150.webp)
