From 119907414fa53ce10c49857e5705a03187149905 Mon Sep 17 00:00:00 2001
From: Stef Nestor <26751266+stefnestor@users.noreply.github.com>
Date: Thu, 18 Sep 2025 16:48:55 -0600
Subject: [PATCH] Update diagnose-unassigned-shards.md
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

👋 howdy, team! In order to return JSON as response suggests, the CAT Shards API neesd `&format=json`. TIA! 🙏
---
 troubleshoot/elasticsearch/diagnose-unassigned-shards.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/troubleshoot/elasticsearch/diagnose-unassigned-shards.md b/troubleshoot/elasticsearch/diagnose-unassigned-shards.md
index a06cf8c8c7..82777f8d27 100644
--- a/troubleshoot/elasticsearch/diagnose-unassigned-shards.md
+++ b/troubleshoot/elasticsearch/diagnose-unassigned-shards.md
@@ -45,7 +45,7 @@ In order to diagnose the unassigned shards, follow the next steps:
 4. View the unassigned shards using the [cat shards API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cat-shards).
 
     ```console
-    GET _cat/shards?v=true&h=index,shard,prirep,state,node,unassigned.reason&s=state
+    GET _cat/shards?v=true&h=index,shard,prirep,state,node,unassigned.reason&s=state&format=json
     ```
 
     The response will look like this: