# alinux-diagnosis

Part of **ALINUX**

<!-- intent-backlink:auto -->

> 💡 **Path Selection**: This skill is one implementation path for [Diagnose and resolve system performance issues](../../intent/alinux-troubleshoot-performance/SKILL.md). If you're unsure which path to take, check the routing skill first.

# Alibaba Cloud Linux System Diagnosis and Troubleshooting Console Guide

## Operations Overview

| Operation | Console Navigation Path | Prerequisites | Description |
|----------|------------------------|---------------|-------------|
| Run Quick Diagnostics | Console > Operating System > System Diagnostics | SysOM component version 3.7.0 or later; Instance in Chinese mainland or China (Hong Kong) region | Perform automated multi-subsystem analysis to identify root causes of performance issues |
| Perform One-Click Comprehensive Diagnosis | Console > Operating System > System Diagnostics | SysOM component version 3.7.0 or later | Execute end-to-end system troubleshooting with unified diagnostic report |
| Analyze OOM Events | Console > ECS > System Diagnostics > Memory Diagnostics > OOM Diagnosis | ECS instance created and running | Diagnose Out-of-Memory events using real-time or historical data |
| Perform Historical OOM Diagnosis | Operating System Console > System Diagnostics | RAM user granted AliyunECSReadOnlyAccess and AliyunSysomFullAccess; Console service enabled | Diagnose OOM events for ACS/ECI instances within the last 14 days, even if destroyed |
| View System Health Status | System Management > Managed Instances > Node Health | SysOM installed; Instance enrolled in management | Monitor cluster/node health scores, analyze anomalies, and access diagnostic reports |

## Step-by-Step Instructions

### Run Quick Diagnostics

**Navigation**: Console > Operating System > System Diagnostics

**Prerequisites**:
- SysOM component version 3.7.0 or later
- Target instance located in Chinese mainland or China (Hong Kong) region

1. Navigate to the System Diagnostics page  
   - Element: **System Diagnostics** (link) — upper-left corner of the page

2. Select the region where the target instance is located  
   - Element: **Region selector** (dropdown) — upper-left corner of the page

3. Set Diagnostics Mode to Node Diagnostics  
   - Element: **Node Diagnostics** (radio) — Diagnostics Mode section

4. Set Diagnostics Type to Scenario Diagnostics  
   - Element: **Scenario Diagnostics** (radio) — Diagnostics Type section

5. Set Diagnostics Item to Quick Diagnostics  
   - Element: **Quick Diagnostics** (radio) — Diagnostics Item section

6. Enter the Instance ID  
   - Element: **Instance ID** (text_input) — Instance ID field

7. Click Execute Diagnosis  
   - Element: **Execute Diagnosis** (button) — bottom of the form  
   - Notes: The process may take 5 to 10 minutes to complete.

| Parameter | Type | Required | Options/Values | Description |
|-----------|------|----------|----------------|-------------|
| Instance ID | text_input | Yes | — | The unique identifier of the target instance to diagnose |
| Diagnostics Mode | radio | Yes | Node Diagnostics | Specifies the diagnostic scope: node-level analysis |
| Diagnostics Type | radio | Yes | Scenario Diagnostics | Defines the diagnostic scenario: based on real-world use cases |
| Diagnostics Item | radio | Yes | Quick Diagnostics | Selects the specific diagnostic task: automated multi-subsystem analysis |

### Perform One-Click Comprehensive Diagnosis

**Navigation**: Console > Operating System > System Diagnostics

**Prerequisites**:
- SysOM component version 3.7.0 or later

1. Access the System Diagnostics page  
 - Element: **-** (link) — top-left of the page

2. Select the region of the target instance  
 - Element: **** (dropdown) — top-left of the page

3. Choose Node Diagnostics mode  
 - Element: **** (radio) — Diagnostics Mode section

4. Select Scenario Diagnostics type  
 - Element: **** (radio) — Diagnostics Type section

5. Choose One-Click Diagnosis item  
 - Element: **** (radio) — Diagnostics Item section

6. Enter the Instance ID  
 - Element: **ID** (text_input) — Diagnosis Configuration area 
   - Notes: Enter a valid Instance ID

7. Click Execute Diagnosis  
 - Element: **** (button) — Action button area 
   - Notes: Diagnosis takes approximately 5–10 minutes; check diagnosis records afterward

| Parameter | Type | Required | Options/Values | Description |
|-----------|------|----------|----------------|-------------|
| ID | text_input | Yes | — | The unique identifier of the instance to be diagnosed |

### Analyze OOM Events

**Navigation**: Console > ECS > System Diagnostics > Memory Diagnostics > OOM Diagnosis

**Prerequisites**:
- ECS instance created
- Instance in Running state

1. In the left navigation pane, click **System Diagnostics**  
 - Element: **** (link) — left navigation bar

2. In the main content area, select **Memory Diagnostics** under Diagnostic Type, then choose **OOM Diagnosis** under Diagnostic Item, configure parameters, and click Execute Diagnosis  
 - Element: **** (button) — main content area 
   - Notes: Instance ID is required; OOM occurrence time is optional

3. In the Diagnosis Records section, click **View Report** to see results  
 - Element: **** (button) — Diagnosis Records area 
   - Notes: Report includes conclusions, recommendations, and detailed analysis

| Parameter | Type | Required | Options/Values | Description |
|-----------|------|----------|----------------|-------------|
| ID | text_input | Yes | — | Target ECS instance ID |
| OOM | dropdown | No | "OOM", "OOM" | Specify time range to locate a specific OOM event |

### Perform Historical OOM Diagnosis

**Navigation**: Operating System Console > System Diagnostics

**Prerequisites**:
- RAM user granted AliyunECSReadOnlyAccess and AliyunSysomFullAccess system policies
- Primary account has enabled console access
- Console service activated on first login

1. Access the System Diagnostics page  
 - Element: **-** (link) — top-left of the page

2. Select Historical Diagnosis mode  
 - Element: **** (button) — upper-middle of the page

3. Enter Instance ID and Diagnosis Time Period, then execute diagnosis  
   - Element: (form_field) — form area  
   - Notes: Supports diagnosis of ACS/ECI instances within the last 14 days, even if destroyed

| Parameter | Type | Required | Options/Values | Description |
|-----------|------|----------|----------------|-------------|
| ID | text_input | Yes | — | Unique identifier of the ACS/ECI instance to diagnose |
| text_input | Yes | — | Time range for diagnosis; supports any period within the last 14 days |

### View System Health Status

**Navigation**: System Management > Managed Instances > Node Health

**Prerequisites**:
- SysOM component installed
- Instance enrolled in management

1. In the left navigation panel, click **System Management**  
 - Element: **** (menu) — left navigation panel

2. Select **Managed Instances**, enter target Instance ID/Name, or filter by conditions  
 - Element: **** (dropdown) — main content area

3. In the Actions column, click **Node Health**  
 - Element: **** (link) — Actions column

4. In the Anomaly Event Analysis panel, click **Diagnose**  
 - Element: **** (button) — Actions column

5. Click **View Diagnosis Report** to review results  
 - Element: **** (button) — Actions column

## FAQ

Q: Where can I find the System Diagnostics feature in the console?
A: You can access it via Console > Operating System > System Diagnostics, or through ECS Console > Operating System Console > System Diagnostics, depending on your entry point.

Q: What happens if I leave the OOM occurrence time blank?
A: If you do not specify a time, the system will automatically analyze the most recent OOM event that occurred on the instance.

Q: Can I diagnose an instance that has already been released or destroyed?
A: Yes, using the Historical Diagnosis feature, you can diagnose ACS/ECI instances for OOM events that occurred within the last 14 days, even if the instance no longer exists.

Q: What permissions are required to use system diagnosis features?
A: Your RAM user must be granted AliyunECSReadOnlyAccess and AliyunSysomFullAccess system policies. Additionally, the primary account must enable console access.

Q: How long does a full diagnosis take to complete?
A: Most diagnostic tasks, including Quick Diagnostics and One-Click Diagnosis, take approximately 5 to 10 minutes to complete. Progress is displayed in real time.

## Pricing & Billing

### Billing Model
All system diagnosis and troubleshooting features described in this guide are provided free of charge.

### Free Tier
- Quick Diagnostics: No cost
- One-Click Diagnosis: Free to use
- OOM Diagnosis: Free service with no additional fees
- Historical Diagnosis: Free for diagnosing events within the last 14 days
- System Health Monitoring: Free with no extra charges

### Quota Limits
- Historical Diagnosis supports events from the past 14 days
- Single diagnosis tasks support up to 10 instances when using batch selection (where applicable)
- Resource usage is constrained by system capacity but no hard quotas are enforced

### Billing Notes
These diagnostic tools consume system resources during execution but do not incur direct billing charges. However, using AccessKey credentials to call underlying OpenAPIs (e.g., in MCP integration) may result in standard API usage fees.