huawei-cloud-cce-alarm-correlation-engine

Run huawei_analyze_aom_alarms with the region and cluster_id to get deduplicated, burst, attention, and chronic alarm groupings. Use huawei_list_aom_alarms first to merge active and historical alarms, since active-only views can miss recently recovered issues.

Use huawei_configure_cce_aom_alarm_rules with region, cluster_id, and an explicit bind_notification_rule_id. The tool previews the batch creation first and only executes after you confirm with confirm=true; it never auto-selects a notification rule.

Read-only queries need aom:event:list, aom:alarmRule:list, and aom:actionRule:list. Creating rules requires aom:alarmRule:create, updates need aom:alarmRule:update, and deletions need aom:alarmRule:delete, plus cce:cluster:get for cluster resolution.

The query is missing a cluster_id filter, so it returns all rules in the region. Re-run huawei_list_aom_alarm_rules with the exact cluster_id; cluster names are not accepted as a filter by this tool.

No. Deletion tools like huawei_delete_aom_alarm_rule and huawei_cleanup_cce_aom_alarm_rules are R0 operations that require a preview, explicit user confirmation, and confirm=true before executing. Nothing is deleted automatically.

It only manages AOM alarms, alarm rules, action rules, and mute rule visibility; it does not modify CCE, ECS, ELB, VPC, or Kubernetes resources. Remediation actions are handed off to the auto-remediation-runner skill.