ApsaraVideo Media Processing:Monitoring and alerting integration

Configure alert rules

Background

The monitoring service for ApsaraVideo Media Processing (MPS) provides metrics on system performance and resource usage. You can also create custom alert rules to monitor service stability, analyze usage, and promptly identify and diagnose issues. To learn about basic concepts or configure alert contacts and alert contact groups, see Alert rules overview and Create an alert contact or an alert contact group.

Metrics

Procedure

1. Log on to the ApsaraVideo Media Processing console.

2. In the left-side navigation pane, choose Global Settings > MPS queues and callbacks.

3. Click Set Alarm Rule to go to the Alert Rules page.

   When you first access this page, CloudMonitor prompts you to create a service-linked role. Click OK. If you have already authorized this role, skip this step. The CloudMonitor service-linked role confirmation dialog box informs you that a service-linked role named AliyunServiceRoleForCloudMonitor with the AliyunServiceRolePolicyForCloudMonitor permission policy will be automatically created. This role allows CloudMonitor to use Cloud Assistant to run commands for installing the CloudMonitor agent. Click OK.

4. Click Create Alert Rule.

5. Configure the associated resources.

   Parameter	Description
   Product	From the drop-down list, select mps.
   Resource Range	The scope of resources to which the alert rule applies. Valid values: All Resources: The alert rule applies to all resources of the specified cloud product, including new resources that are added. Application Groups: The alert rule applies to all resources within the specified application group, including new resources that are added to the group. Instances: The alert rule applies only to the specific resources that you select.
   Rule Description	Defines the conditions that trigger an alert based on monitoring data. Follow these steps to configure the rule description: Click Add Rule. In the Configure Rule Description panel, set parameters such as the rule name, metric type, metric, threshold, alert level, and notification method. Click OK. Note For information about how to set complex alert conditions, see Expressions of alert rules.
   Mute Period	The interval at which alert notifications are re-sent if an alert is not resolved. Valid values: 5 minutes, 15 minutes, 30 minutes, 60 minutes, 3 hours, 6 hours, 12 hours, and 24 hours. When a metric crosses its threshold, an alert notification is sent. If the metric value continues to exceed the threshold, CloudMonitor does not send another notification during the mute period. After the mute period ends, if the alert is still active, CloudMonitor sends another notification. For example, if you set the Mute Period to 12 Hours, CloudMonitor re-sends a notification after 12 hours if the alert has not been resolved.
   Start Time	The time range during which the alert rule is active. CloudMonitor checks monitoring data and triggers alerts only within this period.
   Alert Contact Group	The contact group that receives alert notifications. Notifications for the application group are sent to the alert contacts in this group. An alert contact group can contain one or more alert contacts. For information about how to create an alert contact and an alert contact group, see Create an alert contact or an alert contact group.
   Alert Callback	A public URL that receives alert notifications from CloudMonitor via POST requests. Only the HTTP protocol is supported. For information about how to set up an alert callback, see Use threshold-triggered alert callbacks. Note Click Advanced Settings to configure this parameter. To test the callback URL's connectivity: Click Test next to the callback URL. In the Webhook Test panel, the returned status code and test results indicate the URL's connectivity. Note You can also set the Callback template type and Language for the webhook and click Test again to view the corresponding results. Click Close.
   Auto Scaling	If you enable the Auto Scaling switch, the corresponding scaling rule is triggered when an alarm occurs. You must set the Region, ESS Group, and ESS Rule. For information about how to create a scaling group, see Manage scaling groups. For information about how to create a scaling rule, see Manage scaling rules. Note Click Advanced Settings to configure this parameter.
   Simple Log Service	If you enable Simple Log Service, alert information is written to a Logstore in Log Service when an alert occurs. You need to set the Region, ProjectName, and Logstore. For information about how to create a project and Logstore, see Use Logtail to collect and analyze text logs from ECS instances. Note Click Advanced Settings to configure this parameter.
   Simple Message Queue (formerly MNS) - topic	If you turn on the Lightweight Message Queue (formerly MNS) - Topic switch, alarm information will be written to a topic in Lightweight Message Queue (formerly MNS) when an alarm occurs. You need to set the region and topic for Lightweight Message Queue (formerly MNS). For information about how to create a topic, see Create a topic. Note Click Advanced Settings to configure this parameter.
   NoDataPolicy	Specifies how to handle an alert when monitoring data is missing. Valid values: Do not do anything (Default) Send alert notifications Treated as recovered Note Click Advanced Settings to configure this parameter.
   Tag	A key-value pair that you can add to the alert rule.

6. Click OK to create the alert rule.

Manage alert rules

1. Log on to the CloudMonitor console.

2. In the left-side navigation pane, choose Alerts > Alert Rules. On the page that appears, you can view, modify, enable, disable, or delete alert rules.