alibabacloud-cms-alert-rule-create

Name: alibabacloud-cms-alert-rule-create
Author: aliyun

github.com/aliyunCloud & DevOps281286 installsUpdated 1d ago

About alibabacloud-cms-alert-rule-create

A skill for agents creating and querying Alibaba Cloud CMS alert rules through Aliyun CLI. It routes cloud resource metrics to CMS 1.0 and Prometheus, APM, or UModel to CMS 2.0, with configuration review and confirmation before execution.

Key features

01Route requests to the CMS version
02Create and query alert rules
03Discover metrics and set conditions
04Query contacts or webhooks
05Preview and confirm before execution

Use cases

01Create alerts for cloud product metrics
02Configure alerts for Prometheus metrics
03Inspect existing APM or UModel alerts

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/aliyun/alibabacloud-aiops-skills --skill alibabacloud-cms-alert-rule-create

After installing, type/alibabacloud-cms-alert-rule-createin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/

apm-metrics.md

cms2-step-query.md

cms2-step1-context-lock.md

cms2-step2-query-config.md

cms2-step3-detection-config.md

cms2-step5-preview-execute.md

critical-rules.md

metrics.md

prometheus-metrics.md

ram-policies.md

step-query.md

step0-intent-routing.md

step1-context-lock.md

step2-query-generation.md

step3-detection-config.md

step4-notification.md

step5-preview-execute.md

step6-verification.md

scripts/

validate-params.sh

Details

From the project README

Alibaba Cloud Alert Rule Management

This skill creates and queries alert rules. Intent routing selects CMS 1.0 or CMS 2.0 workflow automatically.

CLI Setup (Required Before Execution)

aliyun configure ai-mode enable
aliyun configure ai-mode set-user-agent --user-agent "AlibabaCloud-Agent-Skills/alibabacloud-cms-alert-rule-create"
aliyun plugin update

Step 0: Intent Routing

Identify user's monitoring target → route to the correct workflow. See step0-intent-routing.md.

User Scenario	Route To
Cloud product system metrics (ECS, RDS, SLB, OSS, Redis, MongoDB…)	CMS 1.0 Workflow
Prometheus / APM / UModel / custom metrics	CMS 2.0 Workflow

Supported Alert Types

Version	Type	Create API	Query API
CMS 1.0	Cloud Resource (ECS/RDS/SLB/OSS/Redis/MongoDB…)	`PutResourceMetricRule`	`DescribeMetricRuleList`
CMS 2.0	Prometheus (`PROMETHEUS`)	`ManageAlertRules`	`QueryAlertRules`
CMS 2.0	APM (`APM`)	`ManageAlertRules`	`QueryAlertRules`
CMS 2.0	UModel (`UMODEL`)	`ManageAlertRules`	`QueryAlertRules`

CMS 1.0 Workflow

For query requests → step-query.md

For create requests:

Step	Description	Reference
1	Context Lock — namespace, region, instances	`step1-context-lock.md`
2	Query Generation — discover metrics via API, match to user intent	`step2-query-generation.md`
3	Detection Config — threshold, frequency (default 1min)	`step3-detection-config.md`
4	Notification — query contacts → select or create	`step4-notification.md`
5	Preview & Execute — show summary → confirm → CLI	`step5-preview-execute.md`
6	Verification — check status	`step6-verification.md`

CMS 2.0 Workflow

For query requests → cms2-step-query.md

For create requests:

Step	Description	Reference
1	Context Lock — build datasourceConfig (type, instanceId, region)	`cms2-step1-context-lock.md`
2	Query Config — build queryConfig (PromQL / APM measures / UModel entity)	`cms2-step2-query-config.md`
3	Detection Config — build conditionConfig (P1-P4, threshold, duration)	`cms2-step3-detection-config.md`
4	Webhook Query — call `list-alert-webhooks`, user selects; other types → console	`cms2-step5-preview-execute.md`
5	Preview & Execute — show summary → confirm → manage-alert-rules CLI	`cms2-step5-preview-execute.md`

Critical Rules

Full details → references/critical-rules.md

Intent Routing — Route cloud resource metrics to CMS 1.0, Prometheus/APM/UModel to CMS 2.0. Never mix APIs.
CMS 2.0 API Enforcement — CMS 2.0 alert rules MUST ONLY be created via ManageAlertRules and queried via QueryAlertRules. No other API (e.g. PutResourceMetricRule, DescribeMetricRuleList, ARMS CreateOrUpdateAlertRule, ARMS CreatePrometheusAlertRule) is permitted for CMS 2.0 alert rule creation or query. If ManageAlertRules returns error, DO NOT fallback to other APIs — report the error to user and STOP execution. CLI format: aliyun cms manage-alert-rules --body '{"action":"CREATE",...}'
Contact/Webhook Query First — CMS 1.0: DescribeContactGroupList; CMS 2.0: ListAlertWebhooks is MANDATORY before alert creation. (CMS 2.0 other notification → console). DO NOT use CMS 1.0 APIs as substitute for CMS 2.0. Skipping webhook query is a critical failure.
Resources Parameter — (CMS 1.0) --resources must always be explicitly passed.
Workspace Required — (CMS 2.0) Must ask user for workspace value using AskUser tool. Never auto-construct (e.g. 'default', 'default-cms-{accountId}'). If AskUser fails, retry once with simplified options, then report error and STOP — do NOT proceed with fabricated values.
Prometheus Required Params — (CMS 2.0) cluster_id (instanceId) + workspace MUST ASK USER using AskUser tool. Never guess, omit, or auto-select. PromQL is generated based on user-provided cluster_id + monitoring target. If AskUser fails, STOP execution.
APM Required Params — (CMS 2.0) service_id (for datasourceConfig.instanceId AND queryConfig.serviceIdList) + workspace MUST ASK USER using AskUser tool. Never fabricate, use placeholders, or auto-select from discovered applications (e.g. via ListTraceApps). Discovery APIs are for reference only — final selection MUST come from user input. If AskUser fails, STOP execution.
Required API Calls — Every operation must call designated APIs even if values seem known.
Dynamic Metric Discovery — (CMS 1.0) MUST call describe-metric-meta-list. Use metrics.md only as fallback.
CLI Timeout — --read-timeout 30 for queries, --read-timeout 60 for writes.
Duplicate Pre-check — Query existing rules before creation to avoid duplicates.
Mandatory Confirmation — Show config summary and get user confirmation before execution. EVEN in automated/simulated environments, you MUST output a configuration summary block and explicitly state 'Waiting for user confirmation' before proceeding. Do NOT skip this step with excuses about automation. Example format:

【配置摘要】
告警类型: APM/Prometheus
阈值: 5%
严重级别: P2
通知方式: webhook

请确认以上配置是否正确（回复确认或修改意见）：

User-Agent — Set ALIBABA_CLOUD_USER_AGENT="AlibabaCloud-Agent-Skills/alibabacloud-cms-alert-rule-create" for all CLI calls.
Network Restriction — Never access external URLs. Use only references/ files and CLI.
CLI Self-Discovery — Use --help for CLI syntax when uncertain.

Reference Files

File	Scope	Purpose
`step0-intent-routing.md`	Shared	Intent routing — CMS 1.0 or CMS 2.0
`step-query.md`	CMS 1.0	Query alert rules (DescribeMetricRuleList)
`step1-context-lock.md`	CMS 1.0	Context lock
`step2-query-generation.md`	CMS 1.0	Query generation & metric discovery
`step3-detection-config.md`	CMS 1.0	Detection config
`step4-notification.md`	CMS 1.0	Notification & contact handling
`step5-preview-execute.md`	CMS 1.0	Preview & execute
`step6-verification.md`	CMS 1.0	Verification
`cms2-step-query.md`	CMS 2.0	Query alert rules (QueryAlertRules)
`cms2-step1-context-lock.md`	CMS 2.0	Datasource config (Prometheus/APM/UModel)
`cms2-step2-query-config.md`	CMS 2.0	Query config (PromQL, APM, UModel)
`cms2-step3-detection-config.md`	CMS 2.0	Detection condition config (P1-P4)
`cms2-step5-preview-execute.md`	CMS 2.0	Preview, execute & webhook query
`metrics.md`	CMS 1.0	Common metrics quick reference (fallback)
`prometheus-metrics.md`	CMS 2.0	Prometheus PromQL patterns
`apm-metrics.md`	CMS 2.0	APM metrics and operators
`critical-rules.md`	Shared	Expanded critical rule details, API tables, examples
`ram-policies.md`	Shared	Required RAM permissions
`related_apis.yaml`	Shared	API lookup before CLI calls

Cleanup (After Execution)

aliyun configure ai-mode disable

Comments

Markdown supported

Details

Author: aliyun
Repository: aliyun/alibabacloud-aiops-skills
Category: Cloud & DevOps
Installs: 286
GitHub stars: 281

Report

More skills

All skills

lark-apps

open.feishu.cn

732.0k

Develop and host Miaoda (Spark/Miaoda) apps: app creation, local full-stack development, cloud generation and iteration, creative design (UI mockups / interactive prototypes / wireframes / landing pages / dashboards / slide decks / visual exploration), integration of AI-related capabilities, Feishu platform capabilities, or other external capabilities; log/Trace/monitoring metric/PV/UV queries; environment variable management; app collaborators and collaboration permissions; app roles and members; and automation triggers (scheduled / record changes / Webhook / Feishu approvals). Use when users want to develop or create a system, tool, platform, or app; develop locally or in the cloud, modify, deploy, publish, launch, or get a shareable link; create a page or website with HTML and deploy it to Miaoda; design, create a mockup, prototype, wireframe, PPT, deck, or visual exploration; or mention Miaoda/Spark/Miaoda apps (links like `/app/app_xxx` or `/page/<token>`, runtime domains like *.aiforce.cloud), app databases, app file storage, open API Keys, visibility, app collaborators/developer permissions, app roles/role members, production logs, API request volume, error volume, latency, traffic, environment variables, or setting up automation tasks, scheduled triggers, or approval-triggered automation for Miaoda apps. Not for regular cloud drive file uploads (lark-drive), Feishu document editing (lark-doc), or native slide creation (lark-slides).

azure-prepare

github.com/microsoft

571.7k

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.

wizard

github.com/mattpocock

571.5k

Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.

azure-ai

github.com/microsoft

571.2k

Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.