Container Service for Kubernetes:Set up alerting for a registered cluster

Configure alicloud-monitor-controller in the registered cluster

Step 1: Grant RAM permissions to alicloud-monitor-controller

Step 2: Install and update alicloud-monitor-controller

onectl addon install alicloud-monitor-controller

Addon alicloud-monitor-controller, version **** installed.

Set up alerting

Step 1: Enable default alert rules

1. Log on to the ACK console. In the left-side navigation pane, click Clusters.

2. On the Clusters page, find the cluster that you want to manage and click its name. In the left-side pane, choose Operations > Alerts.

3. On the Alert Rules tab, enable the alert rule set.

   

Step 2: Configure alert rules

1. Log on to the ACK console. In the left-side navigation pane, click Clusters.

2. On the Clusters page, find the cluster that you want to manage and click its name. In the left-side pane, choose Operations > Alerts.

3. On the Alert Rules tab, click Modify Contacts to specify the contact groups to which the alerts are sent. You can turn on or turn off Status to enable or disable the alert rule set.

   Feature	Description
   Alert Rules	By default, ACK provides an alert rule template that you can use to generate alerts based on exceptions and metrics. Alert rules are classified into several alert rule sets. You can enable an alert rule set, disable an alert rule set, and configure multiple alert contact groups for an alert rule set. An alert rule set contains multiple alert rules. Each alert rule corresponds to an alert item. You can create a YAML file to configure multiple alert rule sets in a cluster. You can also modify the YAML file to update alert rules. For more information about how to configure alert rules by using a YAML file, see Configure alert rules by using CRDs. For more information about default alert templates, see Default alert rule templates.
   Alert History	You can view up to 100 historical alerts. You can select an alert and click the link in the Alert Rule column to view rule details in the monitoring system. You can click Details to go to the resource page where the alert is triggered. The alert may be triggered by an exception or an abnormal metric.
   Alert Contacts	You can create, edit, or delete alert contacts.
   Alert Contact Groups	You can create, edit, or delete alert contact groups. If no alert contact group exists, the ACK console automatically creates a default alert contact group based on the information that you provided during registration.

Configure alert rules by using CRDs

When the alerting feature is enabled, the system automatically creates an AckAlertRule in the kube-system namespace. The AckAlertRule contains default alert rule templates. You can use the AckAlertRule to configure alert rule sets.

1. Log on to the ACK console. In the left-side navigation pane, click Clusters.

2. On the Clusters page, find the cluster that you want to manage and click its name. In the left-side pane, choose Operations > Alerts.

3. On the Alert Rule Management tab, click Edit Alert Configuration in the upper-right corner. Then, click Actions > YAML in the row of the target rule to view the AckAlertRule resource configuration of the current cluster.

4. Refer to the description of the default alert rule template and modify the sample YAML file.

   Example:

   apiVersion: alert.alibabacloud.com/v1beta1
   kind: AckAlertRule
   metadata:
     name: default
   spec:
     groups:
       # The following is a sample configuration of a cluster event alert rule.
       - name: pod-exceptions                             # The name of the alert rule group, which corresponds to the Group_Name field in the alert template.
         rules:
           - name: pod-oom                                # The name of the alert rule.
             type: event                                  # The type of the alert rule (Rule_Type). Valid values: event and metric-cms.
             expression: sls.app.ack.pod.oom              # The expression of the alert rule. When the rule type is event, the value of the expression is the value of Rule_Expression_Id in the default alert rule template described in this topic.
             enable: enable                               # The status of the alert rule. Valid values: enable and disable.
           - name: pod-failed
             type: event
             expression: sls.app.ack.pod.failed
             enable: enable
       # The following is a sample configuration of a cluster basic resource alert rule.
       - name: res-exceptions                              # The name of the alert rule group, which corresponds to the Group_Name field in the alert template.
         rules:
           - name: node_cpu_util_high                      # The name of the alert rule.
             type: metric-cms                              # The type of the alert rule (Rule_Type). Valid values: event and metric-cms.
             expression: cms.host.cpu.utilization          # The expression of the alert rule. When the rule type is metric-cms, the value of the expression is the value of Rule_Expression_Id in the default alert rule template described in this topic.
             contactGroups:                                # The alert contact group configuration that is mapped to the alert rule. The configuration is generated by the ACK console. The same contact is used for the same account. The contact can be reused in multiple clusters.
             enable: enable                                # The status of the alert rule. Valid values: enable and disable.
             thresholds:                                   # The threshold of the alert rule. For more information, see the section about how to change the threshold of an alert rule.            
               - key: CMS_ESCALATIONS_CRITICAL_Threshold
                 unit: percent
                 value: '1'

Default alert rule templates