Loading...
Loading...
Compare original and translation side by side
| Step | Description | CMS 1.0 | Reference |
|---|---|---|---|
| 1 | Context Lock | namespace, region, instances | |
| 2 | Query Generation | Call describe-metric-meta-list to discover metrics for namespace, match to user intent | |
| 3 | Detection Config | threshold, frequency (default 1min) | |
| 4 | Notification | Query contacts → select or create | |
| 5 | Preview & Execute | Show summary → confirm → CLI | |
| 6 | Verification | Check status | |
| 步骤 | 描述 | CMS 1.0 | 参考文件 |
|---|---|---|---|
| 1 | 上下文锁定 | 命名空间、地域、实例 | |
| 2 | 查询生成 | 调用describe-metric-meta-list发现对应命名空间的指标,匹配用户意图 | |
| 3 | 检测配置 | 阈值、频率(默认1分钟) | |
| 4 | 通知配置 | 查询联系人 → 选择或创建 | |
| 5 | 预览与执行 | 展示配置摘要 → 确认 → 执行CLI命令 | |
| 6 | 验证 | 检查创建状态 | |
Before creating ANY alert, complete these API calls to ensure correct workflow execution.
| Step | Required API Call | CLI Command | Purpose |
|---|---|---|---|
| 1 | | | List cloud product namespaces (when product is unclear) |
| 2 | | | Metric Discovery: Get available metrics (fallback: metrics.md) |
| 4 | | | Query existing contact groups |
| 5 | | | Create the alert rule |
These API calls are required for every alert creation. Always query contacts via the designated tools, even if the values seem known.
创建任何告警之前,请完成以下API调用以确保工作流程正确执行。
| 步骤 | 所需API调用 | CLI命令 | 用途 |
|---|---|---|---|
| 1 | | | 当产品不明确时,列出云产品命名空间 |
| 2 | | | 指标发现:获取可用指标(兜底方案:metrics.md) |
| 4 | | | 查询已有的联系人群组 |
| 5 | | | 创建告警规则 |
每次创建告警都需要执行这些API调用。即便看起来已经知道相关值,也始终要通过指定工具查询联系人信息。
This step is REQUIRED and CANNOT be skipped.
describe-contact-group-list该步骤是必填项,不可跳过。
describe-contact-group-listTheparameter MUST always be explicitly passed. Never omit this parameter.--resources
--resources '[{"resource":"_ALL"}]'--resources '[{"resource":"i-xxx"}]'--resources '[{"resource":"i-xxx"},{"resource":"i-yyy"}]'必须始终显式传入参数,不得省略该参数。--resources
--resources '[{"resource":"_ALL"}]'--resources '[{"resource":"i-xxx"}]'--resources '[{"resource":"i-xxx"},{"resource":"i-yyy"}]'| Step 1 | Step 2 | Step 4 | Step 5 |
|---|---|---|---|
| | | |
| 步骤1 | 步骤2 | 步骤4 | 步骤5 |
|---|---|---|---|
| | | |
| User Input | Match Strategy | Common Mappings |
|---|---|---|
| "运维组" / "ops" | Contains/keyword | → |
| "基础设施组" | Contains/keyword | → |
| "DBA团队" | Contains/keyword | → |
| "网络组" | Contains/keyword | → |
| Exact name | Direct match | Use exact name if found |
| 用户输入 | 匹配策略 | 常见映射 |
|---|---|---|
| "运维组" / "ops" | 包含/关键词匹配 | → |
| "基础设施组" | 包含/关键词匹配 | → |
| "DBA团队" | 包含/关键词匹配 | → |
| "网络组" | 包含/关键词匹配 | → |
| 精确名称 | 直接匹配 | 如果找到精确匹配则直接使用 |
aliyunaliyundescribe-metric-rule-list --namespace <ns> --metric-name <metric>describe-metric-rule-list --namespace <ns> --metric-name <metric>cms.aliyuncs.comecs.aliyuncs.comrds.aliyuncs.comslb.aliyuncs.comcms.aliyuncs.comecs.aliyuncs.comrds.aliyuncs.comslb.aliyuncs.comMUST callAPI to discover metrics for the target namespace. DO NOT hardcode metric names. Usedescribe-metric-meta-listonly as fallback when API is unavailable.metrics.md
describe-project-metadescribe-metric-meta-list --namespace <ns>metrics.md必须调用API发现目标命名空间的指标。不要硬编码指标名称。仅当API不可用时才使用describe-metric-meta-list作为兜底方案。metrics.md
describe-project-metadescribe-metric-meta-list --namespace <ns>metrics.md--helpundefined--helpundefined
This is the preferred way to resolve CLI uncertainties rather than guessing parameters.
这是解决CLI使用疑问的首选方式,不要猜测参数。MUST present configuration summary and get explicit user confirmation BEFORE calling.PutResourceMetricRule
调用之前,必须展示配置摘要并获得用户明确确认。PutResourceMetricRule
| Level | Parameter Prefix | Example |
|---|---|---|
| Critical | | |
| Warn | | |
| Info | | |
| 级别 | 参数前缀 | 示例 |
|---|---|---|
| 严重 | | |
| 警告 | | |
| 提示 | | |
| File | Purpose |
|---|---|
| API lookup before CLI calls |
| Context lock |
| Query generation |
| Detection config |
| Notification |
| Preview & execute |
| Verification |
| Common metrics quick reference (fallback) |
| 文件 | 用途 |
|---|---|
| 调用CLI前的API查询参考 |
| 上下文锁定 |
| 查询生成 |
| 检测配置 |
| 通知配置 |
| 预览与执行 |
| 验证 |
| 常用指标快速参考(兜底方案) |
undefinedundefined
**Important**: All `aliyun` CLI calls in this skill MUST include the User-Agent header. Set the environment variable before executing any commands.
**重要提示**:该技能中所有`aliyun` CLI调用都必须包含User-Agent请求头。执行任何命令前请先设置该环境变量。