Related Resource |
Product |
Select NewBGPDDoS (indicates Anti-DDoS Pro) or ddosdip (indicates Anti-DDoS Premium).
|
Resource Range |
The resources to which the alert rule is applied. You can select All Resources or Instances.
- All Resources: The alert rule is applied to all Anti-DDoS Pro or Premium instances. An alert is
triggered when any of the Anti-DDoS instances matches the specified rule.
- Instances: The alert rule is applied to selected Anti-DDoS Pro or Premium instances. An alert
is triggered when one of the selected instances matches the specified rule.
|
Set Alert Rules |
Alarm Rule |
Specify a name for the alert rule. |
Rule Description |
Set the conditions that are used to control how the alert rule is triggered.
Note We recommend that you set the threshold of metrics based on your actual business requirements.
For more information, see Table 1. A low threshold may frequently trigger alerts and negatively impact user experience.
A high threshold may leave insufficient time for you to manage attacks.
Default condition: An Anti-DDoS metric generates a data point every 60 seconds. In the following examples, the Anti-DDoS metrics generate five data points every
five-minute detection period.
- Sample rule description: New connection, 5 minute cycle, 3 periods, once, and > 200.
In this rule, the detection period is set to five minutes. CloudMonitor checks the
data points (number of new connections) generated within three detection periods in
a row, which are 15 data points in total. If any data point shows that the number
of new connections has exceeded 200, an alert is triggered.
- Sample rule description: Out traffic, 5 minute cycle, 3 periods, and ≥ 50 Mbit/s.
In this rule, the detection period is set to five minutes. CloudMonitor checks the
data points (outbound data transfer rate) generated within three detection periods
in a row, which are 15 data points in total. If any data point shows that the outbound
data transfer rate has exceeded 50 Mbit/s, an alert is triggered.
You can click Add Alarm Rule to add more alert rules. Specify a name and rule description for each alert rule.
 |
Mute for |
Set a mute period. If the alert is not cleared within the mute period, a new alert
notification is sent when the mute period ends. The minimum value is 5 minutes and
the maximum value is 24 hours.
|
Effective Period |
The time period during which the alert rule remains effective. The system only sends
alerts within the effective period. The system records alerts if they occur during
a non-effective period.
|
Notification Method |
Notification Contact |
The contact group that receives alerts. |
Notification Methods |
Alert levels include critical, warning, and info. Different levels of alerts are sent
by using different methods.
- Phone + Text Message + Email + DingTalk (Critical)
Note You can select this notification method only after you purchase a notification plan
that supports phone calls.
- Test Message + Email + DingTalk (Warning)
- Email + DingTalk (Info)
|
Auto Scaling |
After you specify a scaling rule, the specified scaling rule is triggered when an
alert occurs. In this example, do not set this parameter.
|
Optional. You can add remarks to email notifications. Remarks is included in email
notifications.
|
HTTP Callback |
CloudMonitor uses a POST request to push an alert to the specified public URL address.
Currently, only HTTP requests are supported.
|