Configuring the notification aggregation policy

Aggregation principles

• Only alert notifications delivered through the observability service can be aggregated.
• Only alert notifications triggered by the same cluster or system service can be aggregated. For Arcfra Kubernetes Engine, only alert notifications triggered by the AKE system service or the same AKE workload cluster can be aggregated.
• Only alert notifications triggered by the same alert rule can be aggregated.
• Within an aggregation period, if an alert is triggered and resolved simultaneously, the receiver will receive an Unresolved alert and a Resolved alert.

Creating a notification aggregation policy

Prerequisite

The clusters and system services that require configuring a notification aggregation policy should have the observability service associated.

Precaution

As the observability service cannot be configured as aggregation objects, alert notifications related to traffic and the observability service itself cannot be aggregated.

Procedure

1. In the left sidebar of the AOC Alert page, select Notification policy and in the upper-right corner on its page, click + Create policy > Create notification aggregation policy. You should see the pop-up Create notification aggregation policy dialog box.
2. Specify the name for the policy.
3. Select the resource type in the dropdown list and specify the corresponding aggregation object.
4. Set the aggregation cycle.
5. Determine whether to enable the policy (enabled by default). Once enabled, the policy will come into effect immediately after creation.
6. Click Create.

Editing or deleting a notification aggregation policy

1. In the left sidebar of the AOC Alert page, click Notification policy and on its page, click the Aggregation policy tab.
2. In the aggregation policy list, click the target policy. In the pop-up detail panel, you can click Edit or Delete to complete the corresponding operation.