Add Windows commands for Log Analysis #9858

Author: Walapalam

en/docs/monitoring/observability/monitoring-correlation-logs.md

@@ -682,7 +682,15 @@ curl -k "Authorization :Bearer <access-token>" -H "activityid:<example-correlati
 2.  Isolate the logs that are correlated.<br/>
     Replace `<correlation_ID>` with the `<example-correlation-ID>` given above.
 
-    `cat correlation.log | grep "<correlation_ID>"`
+    === "Linux/Mac OS"
+        ```bash
+        cat correlation.log | grep "<correlation_ID>"
+        ```
+
+    === "Windows"
+        ```powershell
+        type correlation.log | findstr "<correlation_ID>"
+        ```
 
 ### Reading and analyzing the Correlation logs
 
@@ -790,30 +798,56 @@ Follow the following steps to pinpoint the bottleneck,
 
 You can list the times consumed by the code level, using the following command. This will help you to pinpoint method level latencies.
 
-``` java
-cat correlation.log | grep “|METHOD|” | cut -d “|” -f4 | sort -n
-```
+=== "Linux/Mac OS"
+    ```bash
+    cat correlation.log | grep "|METHOD|" | cut -d "|" -f4 | sort -n
+    ```
+
+=== "Windows"
+    ```powershell
+    type correlation.log | findstr "|METHOD|" | sort
+    ```
 
 This will give the time consumed by each method in ascending order. If a method with a high time consumption is identified, then take the 5 most time consuming service and database calls, with the same correlation ID of the method logs, and find out the unusually time consuming call.
 
-``` java
-cat correlation.log | grep “correlationID” | grep “|HTTP” | cut -d “|” -f4 | sort -n
-cat correlation.log | grep “correlationID” | grep “|jdbc|” | cut -d “|” -f4 | sort -n
-cat correlation.log | grep “correlationID” | grep “|ldap|” | cut -d “|” -f4 | sort -n
-```
+=== "Linux/Mac OS"
+    ```bash
+    cat correlation.log | grep "<correlation_ID>" | grep "|HTTP" | cut -d "|" -f4 | sort -n
+    cat correlation.log | grep "<correlation_ID>" | grep "|jdbc|" | cut -d "|" -f4 | sort -n
+    cat correlation.log | grep "<correlation_ID>" | grep "|ldap|" | cut -d "|" -f4 | sort -n
+    ```
+
+=== "Windows"
+    ```powershell
+    type correlation.log | findstr "<correlation_ID>" | findstr "|HTTP" | sort
+    type correlation.log | findstr "<correlation_ID>" | findstr "|jdbc|" | sort
+    type correlation.log | findstr "<correlation_ID>" | findstr "|ldap|" | sort
+    ```
 
 !!! note
     If a method with a high time consumption cannot be identified, but still a high latency is observed, the following command can be executed to find the highest time recorded.
 
-    ``` java
-    cat correlation.log | cut -d “|” -f4 | sort -n
+=== "Linux/Mac OS"
+    ```bash
+    cat correlation.log | cut -d "|" -f4 | sort -n
+    ```
+
+=== "Windows"
+    ```powershell
+    type correlation.log | for /f "tokens=4 delims=|" %a in ('more') do @echo %a | sort
     ```
     Then the entry that bears the highest duration can be found by searching the file for this time.
 
-    ``` java
+=== "Linux/Mac OS"
+    ```bash
     cat correlation.log | grep "<highest_time>"
     ```
 
+=== "Windows"
+    ```powershell
+    type correlation.log | findstr "<highest_time>"
+    ```
+
 !!! tip
     Alternatively, a log analyzing tool can be used as well to derive this information.