---
格式版本: 2
标题: "Say Goodbye to Complex Onboarding: AI Agent Skills Drive Cloud Monitor's Observability Integration"
原文链接: "https://www.alibabacloud.com/blog/say-goodbye-to-complex-onboarding-ai-agent-skills-drive-cloud-monitors-observability-integration_603437"
发布日期: "2026-08-07"
发布时间校准状态: "found"
发布时间需复核: "否"
发布时间来源: "llm:scrape:extracted_text"
发布时间证据: "第21行：August 7, 2026"
发布时间校准原因: "该候选为正文中提取的日期，且无其他候选，排除干扰后判定为文章发布时间。"
发布时间校准置信度: "1"
发布时间候选数量: 1
发布时间严格候选数量: 0
发布时间原页读取状态: "source template page reused from URL open"
发布时间未找到原因: ""
发布时间校准时间: "2026-08-10T15:43:20+08:00"
发布时间仲裁状态: "confirmed"
发布时间仲裁尝试次数: 1
发布时间仲裁耗时毫秒: 5897
发现时间: "2026-08-10T15:38:02+08:00"
入库时间: "2026-08-10T07:43:26.612Z"
来源平台: "固定入口"
搜索渠道: "fixed_url"
搜索词: "https://www.alibabacloud.com/blog"
匹配关键词:
  - "deployment"
  - "performance"
  - "latency"
相关厂家:
  - "阿里"
  - "OpenAI"
相关专家:
  []
内容类型: "网页"
抓取工具: "Free Fetch + Defuddle"
清洗工具: "Defuddle Markdown + Defuddle/Readability 正文提取"
原始附件:
  []
AI优质: "否"
AI打分: 10
AI分档: "非优质"
AI质检状态: "不通过"
AI打分理由: "内容为阿里云可观测性工具集成介绍，与超节点/AI Rack/机柜级AI基础设施及核心部件、供电、散热、互连等完全无关。"
AI质检模型: "deepseek-v4-flash"
AI质检时间: "2026-08-10T15:43:32+08:00"
AI主题相关性: 0
AI来源权威性: 5
AI新颖性: 2
AI技术细节: 0
AI商业部署信号: 0
AI完整性: 3
采集批次: "2026年8月10日15点37分56秒"
采集批次ID: "20260810-153756-703"
去重键: "https://www.alibabacloud.com/blog/say-goodbye-to-complex-onboarding-ai-agent-skills-drive-cloud-monitors-observability-integration_603437"
---

## Background

With the popularization of cloud-native architecture and the rapid growth of AI applications, the types of applications enterprises need to manage are becoming increasingly diverse—from traditional Java microservices to AI Agents, and from Go backends to various AI gateway components. Meanwhile, configuring the integration for observability platforms involves numerous parameters and steps, placing higher demands on operational efficiency.

As the unified observability management platform for Alibaba Cloud, Cloud Monitor (CMS) 2.0 integrates core capabilities such as Application Monitoring (application performance management, APM), Real User Monitoring (RUM), Managed Service for Prometheus, and Alert Management. To enable users to efficiently complete observability integration in terminal environments, the CMS team introduced the `aliyun cms2` **CLI tool**. Taking it a step further, by encapsulating CLI capabilities into the **alibabacloud-cms-manage Skill**, we have achieved intelligent observability integration based on AI Agents. Users simply describe their requirements in natural language, and the AI Agent automatically orchestrates CLI commands to complete the entire process.

This article will introduce the application integration capabilities of the CMS CLI, with a focus on demonstrating how to achieve automated integration in K8s scenarios using the AI Agent Skill.

![1](https://yqintl.alicdn.com/fc5398d99f65ed1362171b91e3a41cd19a761ce6.png "1")  
Figure 1: CMS CLI + AI Agent Skill

## CMS CLI Overview

The `aliyun cms2` is a subcommand plugin for the [Alibaba Cloud CLI](https://github.com/aliyun/aliyun-cli) that covers command-line operations for all modules in CMS 2.0:

| **Module** | **CLI command prefix** | **Typical scenarios** |
| --- | --- | --- |
| **Application Monitoring** | `aliyun cms2 apm` | Application integration, agent management, service registration |
| **RUM** | `aliyun cms2 rum` | Web/Mobile application integration and configuration |
| **Integration Center** | `aliyun cms2 integration` | Cloud product monitoring integration, Addon management |
| **Alert Management** | `aliyun cms2 alert` | Alert rules, templates, and notification channel management |
| **Event Center** | `aliyun cms2 event-hub` | Event aggregation and alert correlation |
| **Metrics Query** | `aliyun cms2 metric` | PromQL queries, metric metadata |

Ensure your environment is ready before use:

```
# Confirm the CLI is installed and the version is >= 3.3.15 
$ aliyun version 
3.3.20

# Verify the cms2 plugin is available
$ aliyun cms2 --help

# Configure credentials (if not configured)
$ aliyun configure
```

## Application Integration Capabilities

### Application Monitoring and AI Observability

The Application Monitoring module of the CMS CLI supports application integration for multiple languages and provides three integration methods: ack-onepilot (for K8s containers), manual proprietary agent, and native OpenTelemetry:

| **Language** | **ack-onepilot (K8s)** | **Proprietary agent** | **OpenTelemetry** |
| --- | --- | --- | --- |
| **Java** | Yes | AliyunJavaAgent | OTel Java Agent |
| **Go** | Yes | instgo | OTel Go SDK |
| **Python** | Yes | aliyun-bootstrap | opentelemetry-instrument |
| **Node.js** | — | @loongsuite/cms\_node\_sdk | OTel Node SDK |
| **PHP** | — | — | OTel PHP extension |
| **.NET** | — | — | OTel.NET Auto-Instrument |

For AI Observability, CMS 2.0 provides an out-of-the-box integration experience for mainstream AI frameworks:

| **AI framework** | **Underlying agent** |
| --- | --- |
| **LangChain/LangGraph** | Python aliyun-bootstrap |
| **DashScope (Qwen)** | Python aliyun-bootstrap |
| **Dify** | Built-in OTel for Dify |
| **AgentScope** | Python aliyun-bootstrap |
| **OpenAI** | Python aliyun-bootstrap |
| **Coze** | Golang instgo |
| **OpenClaw/CoPaw/Hermes** | Dedicated installer script |

### CLI Integration Workflow

Regardless of the application's language or integration method, CLI integration follows these 6 steps:

![2](https://yqintl.alicdn.com/8ab4a5da9739a80784a501ddb5c762fa5cd7fdbb.png "2")  
Figure 2: 6-step CLI integration workflow

Below are the core commands for each step:

```
# Step 1: Get the account ID 
$ aliyun sts get-caller-identity --force -o json 
# → AccountId: 1108xxxxxxxxxxxx

# Step 2: Initialize Application Monitoring infrastructure (idempotent)
$ aliyun cms2 apm configuration create \
    --workspace default-cms-1108xxxxxxxxxxxx-cn-hangzhou \
    --region cn-hangzhou

# Step 3: Get access credentials (license key, endpoint, etc.)
$ aliyun cms2 apm configuration get \
    --workspace default-cms-1108xxxxxxxxxxxx-cn-hangzhou \
    --region cn-hangzhou -o json
```
```
{
  "success": true,
  "data": {
    "entryPointInfo": {
      "authToken": "a]***@***************4b70",
      "privateDomain": "proj-xtrace-***-cn-hangzhou.cn-hangzhou-intranet.log.aliyuncs.com",
      "project": "proj-xtrace-***-cn-hangzhou",
      "publicDomain": "proj-xtrace-***-cn-hangzhou.cn-hangzhou.log.aliyuncs.com"
    },
    "status": "Running",
    "workspace": "default-cms-1108xxxxxxxxxxxx-cn-hangzhou"
  }
}
```
```
# Step 4: Register the application service 
$ aliyun cms2 apm service create \ 
    --workspace default-cms-1108xxxxxxxxxxxx-cn-hangzhou \ 
    --region cn-hangzhou \ 
    --body '{"serviceName":"my-app","serviceType":"TRACE","attributes":"{\"language\":\"java\"}"}' \ 
    < /dev/null 
# → serviceId: a]***@*********************7f1

# Step 5: Get the integration configuration template (using Java OTel as an example)
$ aliyun cms2 integration addon get --addon-name apm-java-batch --env-type Client -o json

# Step 6: Verify the integration
$ aliyun cms2 apm service list \
    --workspace default-cms-1108xxxxxxxxxxxx-cn-hangzhou \
    --service-name my-app --region cn-hangzhou
```

Although the above workflow is clear, executing 6 steps and passing multiple parameters can still present a learning curve for O&M engineers who do not use the CLI frequently. Next, we will introduce how to simplify this entire process into a single natural language sentence using the AI Agent Skill.

![3](https://yqintl.alicdn.com/f19e7e43621b25089e94a4b80d8a8bc69e69d461.png "3")  
Figure 3: Easy integration with a single sentence using the Skill

## Achieving Intelligent Integration via AI Agent Skills

### alibabacloud-cms-manage Skill

The CMS team has encapsulated the complete CLI operational knowledge into an out-of-the-box Skill: [alibabacloud-cms-manage](https://int.alibabacloud.com/m/1000415936/). Its core concept is to **transform the CLI operational workflow into a structured workflow executable by the AI Agent**. Users do not need to memorize commands and parameters; they simply describe their needs in natural language to complete the integration.

The Skill covers the following modules:

| **Module** | **Example trigger keywords** | **Capabilities** |
| --- | --- | --- |
| **Application Monitoring** | "Integrate a Java application", "Python agent", "ack-onepilot" | Mainstream language applications × various mainstream deployment and integration methods |
| **AI Observability** | "LangChain integration", "AI Agent monitoring" | Supports integration for mainstream AI frameworks |
| **Integration Center** | "Monitor ECS instances" | Monitor cloud products |
| **Alert Management** | "Create a CPU alert", "Configure notifications" | Alert rules/templates/notification channels |
| **RUM** | "Integrate with frontend monitoring", "mini-program monitoring" | Enables configuration for frontend application integration |

For details on installing and using the Skill, see [https://skills.alibabacloud.com/skills/alibabacloud-cms-manage](https://int.alibabacloud.com/m/1000415936/).

### Working Mechanism

When a user describes their requirements in Claude Code, the AI Agent operates according to the following workflow:

![4](https://yqintl.alicdn.com/6d4202cf950aa10bd9a64aac84a0846439ca1679.png "4")  
Figure 4: Intelligent Skill integration workflow

### Security Mechanism: Two-Phase Confirmation Protocol

For operations that may affect the user's cluster (such as installing components or deploying patches), the Skill strictly enforces a **two-phase confirmation:**

| **Phase** | **Behavior** |
| --- | --- |
| **Phase A (Plan)** | Displays the target resource, specific command, scope of impact, and rollback plan, **then pauses the current step pending user confirmation** |
| **Phase B (Execution)** | Executes only after explicit user approval ("yes"/"confirm") |

Read-only commands (`get`, `list`) and CMS backend resource creation (`apm configuration create`) do not require confirmation and can be executed directly by the Agent.

![5](https://yqintl.alicdn.com/56cd59c5baa9e88bef1db67216e4599692feb662.png "5")  
Figure 5: Two-phase confirmation protocol

### Demonstration: Automatic Integration for K8s Containers

Below is the complete interaction process for using this Skill to **automatically** **integrate a LangChain application into a Container Service for Kubernetes (ACK) cluster.** The ack-onepilot runs an Agent Pod on each cluster node via a DaemonSet. Once a Deployment is annotated with the specified label, ack-onepilot automatically injects the agent — **no changes to the application code or Dockerfile are required.**

**User:**

Help me integrate the LangChain application `customer-support-agent` in my ACK cluster into CMS.

**AI Agent：**

Detected a container integration scenario. Fetching cluster information...

```
$ aliyun sts get-caller-identity --force -o json
# → AccountId: 1108xxxxxxxxxxxx

$ aliyun cs describe-clusters
# → clusterId: c8d3f***********, region_id: cn-hangzhou
```

Initializing APM infrastructure and obtaining credentials...

```
$ aliyun cms2 apm configuration create \
    --workspace default-cms-1108xxxxxxxxxxxx-cn-hangzhou --region cn-hangzhou
# → 成功

$ aliyun cms2 apm configuration get \
    --workspace default-cms-1108xxxxxxxxxxxx-cn-hangzhou --region cn-hangzhou -o json
# → LicenseKey: a]***@***************4b70

$ aliyun cms2 apm service create \
    --workspace default-cms-1108xxxxxxxxxxxx-cn-hangzhou --region cn-hangzhou \
    --body '{"serviceName":"customer-support-agent","serviceType":"TRACE","attributes":"{\"language\":\"python\"}"}' \
    < /dev/null
# → serviceId: a]***@*********************7f1
```

Checking the status of the ack-onepilot component...

```
$ kubectl get pods -n ack-onepilot
# NAME                      READY   STATUS    RESTARTS   AGE
# ack-onepilot-7d8f9        1/1     Running   0          5d
```

The ack-onepilot is installed and running normally. Searching for the target Deployment...

```
$ kubectl get deployment --all-namespaces | grep customer-support
# default   customer-support-agent   3/3     3    3    12d
```

Found the target Deployment `default/customer-support-agent` (3 replicas). Execution plan — Patch K8s Deployment. Please confirm the execution (`yes` / `no`).

**User:**

yes

**AI Agent：**

Executing the patch...

```
$ kubectl patch deployment customer-support-agent -n default \
    --type=strategic -p '{
      "spec":{"template":{"metadata":{"labels":{
        "aliyun.com/app-language":"python",
        "armsPilotAutoEnable":"on",
        "armsPilotCreateAppName":"customer-support-agent",
        "armsPilotAppWorkspace":"default-cms-1108xxxxxxxxxxxx-cn-hangzhou"
      }}}}}'
# deployment.apps/customer-support-agent patched
```

Verifying the rolling update...

```
$ kubectl rollout status deployment/customer-support-agent -n default --timeout=120s 
# deployment "customer-support-agent" successfully rolled out
```

Integration completed. The application has had the Python agent automatically injected via ack-onepilot. In 2-3 minutes, you will be able to view monitoring data such as LLM invocation latency, Token usage, and Agent traces in the [CMS console](https://int.alibabacloud.com/m/1000415937/).

Throughout this process, the user needed only to provide a single natural language description. The AI Agent automatically handled account retrieval, cluster information derivation (eliminating the need to manually supply a region ID), infrastructure initialization, credential retrieval, service registration, component status checks, and Deployment lookups — while also applying a **two-phase confirmation** mechanism that lets the user review the patch content before execution. Compared with the 8+ commands required for manual operation, this Skill distills the integration experience — from memorizing commands, looking up parameters, and assembling JSON — down to a single sentence.

![6](https://yqintl.alicdn.com/dd7110e14836d0c8db62f1464a90c717d0759507.png "6")  
Figure 6: K8s ack-onepilot automatic integration

If you are interested in the CMS CLI or AI Agent-driven observability integration, check out the following resources:

● [alibabacloud-cms-manage Skill](https://int.alibabacloud.com/m/1000415936/)

● [CMS 2.0 Console](https://int.alibabacloud.com/m/1000415937/)

● [CMS documentation](https://int.alibabacloud.com/m/1000415938/)

● [Alibaba Cloud CLI installation guide](https://int.alibabacloud.com/m/1000415939/)