What problem does it solve? Elasticsearch and OpenSearch clusters fail in opaque ways — red cluster status, unassigned shards, JVM heap pressure, and slow queries — and finding the right diagnostic commands under incident pressure is slow and error-prone. ## Core Features & Use Cases - Decision-tree troubleshooting: Step-by-step flows for red/yellow cluster health, shard allocation failures, circuit breakers, and JVM heap pressure, each mapping symptoms to concrete _cluster and _cat API calls. - Query and DSL optimization: Guidance for profiling slow queries, fixing wildcard and deep-pagination anti-patterns, and building efficient aggregations including composite pagination. - Lifecycle and operations runbooks: References covering rolling restarts, node scaling, ILM, snapshot/restore, reindex, shrink/split, and AWS OpenSearch specifics like UltraWarm and CloudWatch alarm thresholds. - Use Case: Your production cluster goes red after a node loss. Follow the decision tree to run _cluster/allocation/explain, identify NO_VALID_SHARD_COPY, and either restore from snapshot or accept data loss with allocate_stale_primary. ## Quick Start Diagnose why my Elasticsearch cluster status is red and give me the exact API calls to fix the unassigned shards.