> For the complete documentation index, see [llms.txt](https://asus-isg-aidc.gitbook.io/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://asus-isg-aidc.gitbook.io/guide/latest/portal/aidcstatus.md).

# AIDC Status

| Developer | Last modified |
| --------- | ------------- |
| AIDC Team | 2026/02/04    |

![AIDC Status Feature](https://pub-f334ff01208c4e6195b80133ac6e6030.r2.dev/portal/aidcStatus/aidc-status.png)

## Feature Goal

### Aim

The AIDC Status feature provides real-time monitoring of critical system services and their resource utilization. It enables users to:

* Monitor CPU, Memory, and Disk usage for CLI Service and Portal Service
* Track resource consumption trends for core AIDC services
* Identify resource bottlenecks and capacity issues
* View timestamp of last status update
* Ensure optimal performance of system services running on KVM virtual machines

### User Story

**As a** system administrator or infrastructure engineer\
**I want** to monitor the resource usage of CLI and Portal services in real-time\
**So that** I can proactively manage system capacity, optimize resource allocation, and prevent service degradation

## Feature Description

### 3.1 Location

* **Navigation Path**:
  * Side Menu: `Option` → `AIDC Status`

### 3.2 Operation Requirements

#### Resource Monitoring

The AIDC Status page displays two main service panels:

**CLI Service Panel**

* Displays resource usage for the CLI service virtual machine
* Shows CPU utilization (percentage and core usage)
* Shows Memory consumption (used/total in MiB/GiB)
* Shows Disk usage (used/total in GiB)
* Updates timestamp indicates last data refresh

**Portal Service Panel**

* Displays resource usage for the Portal service virtual machine
* Shows CPU utilization (percentage and core usage)
* Shows Memory consumption (used/total in GiB)
* Shows Disk usage (used/total in GiB)
* Updates timestamp indicates last data refresh

#### Resource Metrics

**CPU**

* **Display Format**: Percentage (%) + Core usage (e.g., "0.13 / 4 Cores")
* **Purpose**: Monitor CPU utilization to identify performance bottlenecks
* **Visual Indicator**: Progress bar showing usage percentage
* **Note**: Both CLI and Portal services run on KVM virtual machine quotas

**Memory**

* **Display Format**: Used/Total (e.g., "568.95 MiB / 3.57 GiB")
* **Purpose**: Track memory consumption and prevent out-of-memory issues
* **Visual Indicator**: Progress bar showing usage percentage
* **Note**: Memory is allocated from KVM VM quota pool

**Disk**

* **Display Format**: Used/Total (e.g., "66.9 GiB / 233.32 GiB")
* **Purpose**: Monitor disk space usage to prevent storage exhaustion
* **Visual Indicator**: Progress bar showing usage percentage
* **Note**: Disk space is allocated from KVM VM storage quota

### 3.4 UI Components

#### Service Status Cards

Each service (CLI and Portal) has a dedicated card displaying:

1. **Service Title**: "CLI Service" or "Portal Service"
2. **Resource Metrics**:
   * CPU icon with percentage and core count
   * Memory icon with usage in MiB/GiB
   * Disk icon with usage in GiB
3. **Progress Bars**: Visual representation of resource usage percentage
4. **Timestamp**: Last update time in format "YYYY/MM/DD HH:MM:SS"

#### Visual Indicators

* **Blue Progress Bars**: Indicate current resource usage level
* **Icon Representations**:
  * CPU: Processor chip icon
  * Memory: RAM module icon
  * Disk: Storage disk icon

### 3.4 Data Update Mechanism

* **Auto-refresh**: Status data updates automatically at regular intervals
* **Update Timestamp**: Each service card shows the last update time
* **Resource Source**: Both CLI and Portal services run on KVM virtual machines with allocated resource quotas

## Use Cases

### 4.1 Health Monitoring

**Scenario**: Regular system health check

**Steps**:

1. Navigate to `Option` → `AIDC Status` from the side menu
2. Review CPU, Memory, and Disk usage for both CLI and Portal services
3. Verify all resources are within normal operating levels
4. Check the timestamp to ensure data is up-to-date

### 4.2 Performance Investigation

**Scenario**: System seems slower than usual

**Steps**:

1. Open AIDC Status page
2. Check if any resource (CPU/Memory/Disk) is showing high usage percentage
3. Compare the usage between CLI and Portal services
4. Contact system administrator if resources consistently exceed 80%

## FAQ

**Q: What do the percentages represent?**\
A: The percentages show the proportion of allocated resources currently in use. For example, 3% CPU means 3% of the allocated 4 CPU cores are active.

**Q: Why are the timestamps different for CLI and Portal services?**\
A: Each service reports its metrics independently. Slight timestamp differences are normal and indicate when each service last updated its metrics.

**Q: What happens if a service reaches 100% resource usage?**\
A: At 100% usage, the service may experience performance degradation. The system should trigger alerts, and administrators should increase VM quotas or optimize the service.

**Q: Are these physical or virtual machine resources?**\
A: These are virtual machine resources. Both CLI and Portal services run as VMs on KVM, with resources allocated from the hypervisor's quota pool.

**Q: Why are the timestamps different for CLI and Portal services?**\
A: Each service reports its metrics independently. Slight timestamp differences are normal.

**Q: What should I do if I see high resource usage (over 80%)?**\
A: Contact your system administrator. High resource usage may indicate the system needs optimization or additional resources.

**Q: Are these physical or virtual machine resources?**\
A: These are virtual machine resources. Both CLI and Portal services run as KVM virtual machines with allocated resource quotas.