One-click IO diagnosis

Limitations

• Region restrictions

• Operating system restrictions

  Architecture	Operating system
  x86 architecture	Rocky Linux 9.5 Rocky Linux 9.1 Ubuntu 20.04 Alibaba Cloud Linux 3 Container Optimized Edition Rocky Linux 8.8 Ubuntu 22.04 Alibaba Cloud Linux 3 Pro Alibaba Cloud Linux 2/3 CentOS 7.6 or later, or CentOS 8 Anolis OS 7/8 Ubuntu 24.04
  ARM architecture	Alibaba Cloud Linux 3 Pro Alibaba Cloud Linux 3

Use cases

• Troubleshoot high IO latency to determine whether the bottleneck is in the operating system (OS) or a backend service.

• Identify the specific process causing abnormal IO traffic.

• Investigate the root cause and problematic IO path of a spike in the IO wait metric.

Prerequisites

• If you use a RAM user, make sure that the Alibaba Cloud account (primary account) has granted the RAM user the AliyunECSReadOnlyAccess and AliyunSysomFullAccess system policies.

• The console permissions are activated.

  The first time you log on to the Operating System Console, click Activate Service to activate the console service.

Procedure

1. Go to Operating System Console.

2. In the left-side navigation pane, click System Diagnosis.

3. In the upper part of the left-side navigation pane, select the region in which the target instance resides.

   

4. From the Diagnosis Type list, select Storage Diagnosis. Then, in the Diagnosis Item section, select One-click IO Diagnosis. Configure the parameters and click Run Diagnosis.

   Note

   If SysOM is not installed, the system automatically installs SysOM on the target ECS instance and then starts the diagnosis after you click Run Diagnosis.

   The following table describes the parameters.

   Parameter	Description	Required
   Instance ID	The ID of the target ECS instance.	Yes
   Diagnosis Duration	The diagnosis duration. A minimum of 30 seconds is recommended.	No

5. In the Diagnosis Records section, click View Report.

Diagnostic report

• Basic Information

  The Basic Information section summarizes the diagnosis with key details, including the instance ID (which serves as the resource ID), diagnosis item, diagnostic report ID, and diagnosis start time.

• Diagnosis conclusion

  If an IO anomaly is detected, this section displays the identified issue and its root cause analysis.

• Recommendations

  This section recommends actions based on the diagnosis results.

• Diagnosis details

  • Diagnosis summary

    If an IO anomaly is found, this section shows the number of anomaly types detected.

  • Diagnosis results

    This section displays the IO anomalies that occurred during the diagnosis period.

    • Device Name: The name of the detected disk or partition.

    • Abnormal Point: The specific symptom of the anomaly.

    • Abnormal Type: The type of the anomaly.

    • Suggestion: Recommended optimizations.

    • Cause: The root cause of the anomaly.