Use a regular notification rule to receive Auto Scaling activity results by internal message and email. When exceptions occur, you handle them manually based on the notification content.
Prerequisites
No advanced notification rule exists for the scaling group.
If one does, delete it before proceeding — you cannot create a regular notification rule while an advanced notification rule is active.
Background
When using the regular notification feature, notifications can be received via internal messages, emails. You need to handle them manually after receiving the notifications.
If you need to automatically subscribe to Elastic Scaling-related events through a program, please create an event notification feature and configure event subscriptions via CloudMonitor, MNS topics, or MNS queues. After defining custom processing policies in these products, they can automatically initiate the processing flow when events are received. For detailed steps, see Configure event notifications.
Create a regular notification rule
Log on to the ESS console。
In the left-side navigation pane, click Scaling Groups.
In the top navigation bar, select the region where Auto Scaling is activated.
Open the scaling group details page using one of the following methods:
Click the ID of the scaling group in the Scaling Group Name/ID column.
Click Details in the Actions column.
Click the Event and adhesive hook tab.
Click Create Regular Rule in the Notification module.
Configure the notification method and contact:
In the Create Regular Rule dialog box, click Message Settings.
On the Common Settings page, select Product Message > Notifications Regarding the Creation and Activation of Product Instances, then configure the notification method and contact.
Back in the Create Regular Rule dialog box, select the scaling events for which to receive notifications, then click OK.
Scaling event
Description
Successful Scaling Activity
ECS instances or elastic instances are added or removed.
Scaling Activity Failed
The scaling activity is triggered, but ECS instances or elastic container instances are not added or removed.
Scaling Activity Rejected
The scaling activity request is received but rejected because the trigger conditions are not met.