Skip to content

Commit 598e12f

Browse files
committed
Added Mayas suggestions
Signed-off-by: Burak Ok <[email protected]>
1 parent 92c21f2 commit 598e12f

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

support/azure/azure-kubernetes/availability-performance/identify-high-disk-io-latency-containers-aks.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Identify containers causing high disk I/O latency in AKS clusters
3-
description: Learn how to use Inspektor Gadget to identify which containers and pods are causing high disk I/O latency in Azure Kubernetes Service clusters.
3+
description: Learn how to identify which containers and pods are causing high disk I/O latency in your Azure Kubernetes Service clusters to easily troubleshoot issues using the open source project Inspektor Gadget.
44
ms.date: 07/16/2025
55
ms.author: burakok
66
ms.reviewer: burakok, mayasingh
@@ -35,7 +35,7 @@ You may suspect disk I/O latency issues when you observe the following behaviors
3535

3636
### Step 1: Profile disk I/O latency with `profile_blockio`
3737

38-
The `profile_blockio` gadget gathers information about block device I/O usage and generates a histogram distribution of I/O latency when the gadget is stopped. This helps you visualize disk I/O performance and identify latency patterns.
38+
The `profile_blockio` gadget gathers information about block device I/O usage and generates a histogram distribution of I/O latency when the gadget is stopped. This helps you visualize disk I/O performance and identify latency patterns. We can use this information to gather evidence to support or refute the hypothesis that the symptoms we are seeing are due to disk I/O issues.
3939

4040
```console
4141
kubectl gadget run profile_blockio --node <node-name>

0 commit comments

Comments
 (0)