Product |
The service that you want to monitor. Select WAF from the drop-down list.
|
Resource Range |
The scope of the domain names that you want to monitor. Valid values:
- All Resources: monitors all the domain names that are added to WAF. If the alert rule is triggered
for one of the domain names, an alert notification is sent.
- Instance: monitors specific domain names. An alert notification is sent only when the alert
rule is triggered for all the selected domain names.
|
Region |
The region where the WAF instance resides. This parameter is required only if you
select Instance from the Resource Range drop-down list.
Valid values:
- China East 1 (Hangzhou): specifies a WAF instance in mainland China.
- Asia Pacific SE 1 (Singapore): specifies a WAF instance outside mainland China.
|
Instance |
The ID of the WAF instance. This parameter is required only if you select Instance from the Resource Range drop-down list.
After you configure Region, the ID of the WAF instance in the selected region automatically appears. You do
not need to modify this parameter. If no WAF instances are purchased in the selected
region, No Data appears.
|
domain |
The domain name that you want to monitor. This parameter is required only if you select
Instance from the Resource Range drop-down list.
Select the domain name that you want to monitor from the domain names that are added
to the WAF instance. You can select multiple domain names.
|
Alert Rule |
The name of the alert rule. |
Rule Description |
The content of the alert rule. This parameter defines the condition that triggers
the alert rule.
Note We recommend that you configure alert thresholds for different metrics based on your
business requirements. For more information about the metrics, see WAF service metrics supported. A low threshold may trigger frequent alerts and affect user experience. A high threshold
may not provide you with sufficient time to respond to exceptions detected in metrics.
Example of an alert rule:
If you configure the following rule, CloudMonitor determines whether to trigger an
alert based on the QPS detected in three consecutive cycles. CloudMonitor reports
a data point at an interval of 60s. A total of 15 data points are reported in the
three consecutive cycles. If the maximum QPS among the reported data points is greater
than 200, an alert is triggered.
 You can click Add Alert Rule to create more rules. You must configure Alert Rule and Rule Description for each rule.
|
Mute for |
The interval of re-sending the notification for an alert before the alert is cleared.
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. CloudMonitor sends
alert notifications within the effective period and only records alerts beyond the
effective period.
|
Notification Contact |
The alert group that receives alert notifications. |
Notification Methods |
The method that is used to send alert notifications. Different levels of alerts are
sent by using different methods. Alert levels are Critical, Warning, and Info. Valid
values: Email + DingTalk (Info).
|
Auto Scaling |
If you select Auto Scaling, no additional configurations are required. After you select
a scaling rule, it is triggered when an alert is generated.
|
Log Service |
If you select Log Service, the alert information is written to Log Service when an
alert is generated. You must also configure Region, Project, and Logstore.
For more information about how to create a project and a Logstore, see Quick start.
|
Email Subject |
The subject of the alert notification email.
By default, the email subject is in the format of service name + metric name + instance
ID.
|
Email Remark |
The additional information that you want to include in the alert notification email.
|
HTTP CallBack |
The URL to which CloudMonitor sends alert notifications by using HTTP POST. You can
enter only an HTTP URL.
|