Cloud Parallel File Storage:Configure an advanced alert rule

Procedure

1. Add cloud service metrics.

   1. Log on to the Cloud Monitor console.

   2. In the navigation pane, choose Namespace.

   3. On the Namespace page, locate the target namespace and click the link in the Metric Data column.

   4. In the Metric management panel, on the Alibaba Cloud Service Metrics tab, add CPFS metrics.

      Note

      CPFS and NAS share the same console. The dialog box for adding metrics includes metrics for NAS. Select only the metrics where the Metric Category column shows CPFS. For more information about CPFS metrics, see Metrics.

      1. Add the NAS product category.

         1. Click the icon next to Current Account.

         2. In the Add Product dialog box, select NAS, and then click OK.

      2. Add CPFS metrics.

         1. Click NAS, and then click Add Metric.

         2. In the Add Metric dialog box, select the target metrics, and then click OK.

2. Create an alert rule.

   1. On the Namespace page, click Create Alert Rule.

   2. In the Create Alert Rule panel, configure the parameters for the alert rule.

      Parameter	Description
      Rule Name	The name of the alert rule.
      Namespace	Select the namespace to which you added the CPFS metrics in step 1.
      Alert Expression	The core of the alert rule. An alert is triggered when the metric data meets the condition defined in the expression. For example, to create an alert when the used storage of a file system exceeds 80% of its total capacity, use an expression in the following format. AliyunNas_CPFSCapacityUsed{fileSystemId="cpfs-192ec9bd1a47xxxx"} / AliyunNas_CPFSCapacity{fileSystemId="cpfs-192ec9bd1a47xxxx"} > 0.8 Note Note that an alert condition where the number of allocated files exceeds the maximum number of files will never be met.
      Tags	The tags for the alert rule. You can set a key and value for each tag.
      Annotations	The annotations for the alert rule. You can set a key and value for each annotation.
      Mute For	The period Cloud Monitor waits before resending a notification for an unresolved alert. Valid values: 5 Minutes, 15 Minutes, 30 Minutes, 60 Minutes, 3 Hours, 6 Hours, 12 Hours, and 24 Hours. When a metric triggers an alert, a notification is sent. If the metric continues to exceed the threshold, no new notifications are sent during the Mute For period. If the alert is still active after the Mute For period ends, Cloud Monitor sends another notification.
      Effective Period	The time range during which the alert rule is active. The rule is evaluated only within this period.
      Alert Contact Group	The alert contact groups that receive alert notifications. An alert contact group contains one or more alert contacts. For information about how to create alert contacts and alert contact groups, see Create an alert contact or an alert contact group.
      Notification Methods	The alert level and the methods used to send alert notifications. Valid values: Critical (Phone Call + SMS + Email + DingTalk Chatbot) Warning (SMS + Email + DingTalk Chatbot) Info (Email + DingTalk Chatbot) You can also specify the number of consecutive one-minute cycles for which the condition must be met before an alert is triggered. Valid values: 1, 3, 5, 10, 15, 30, 60, 70, 90, 120, and 180.
      Alert Callback	A publicly accessible URL that receives alert information from Cloud Monitor through POST requests. Only the HTTP protocol is supported. To test connectivity to your alert callback URL, do the following. Click Test, located directly to the right of the callback URL. In the WebHook Test panel, use the HTTP status code and test result details to verify and troubleshoot connectivity to your alert callback URL. Note You can also set the Test Template Type: and Language:. Then click Test again to view updated test results. Click Close.
      Auto Scaling	If you enable Auto Scaling, the corresponding scaling rule is triggered when an alert occurs. You must specify the region, ESS Group, and ESS Rule. For more information about how to create a scaling group, see Configure a scaling group. For more information about how to create a scaling rule, see Configure a scaling rule.
      Simple Log Service	If you enable Simple Log Service, alert information is written to Simple Log Service (SLS) when an alert occurs. You must specify the region, ProjectName, and Logstore. For more information about how to create a project and a Logstore, see Collect and analyze ECS text logs by using Logtail.
      Simple Message Queue (formerly MNS) - topic	If you enable the Simple Message Queue (formerly MNS) - Topic switch, alarm information is written to a topic in Simple Message Queue when an alarm occurs. You need to set the region and topic for Simple Message Queue. For more information about how to create a topic, see Create a topic.
      Function Compute	If you enable Function Compute, alert notifications are sent to Function Compute for processing when an alert occurs. You must specify the region, Service, and Function. For more information about how to create a service and a function, see Create a function.
      Method to handle alerts when no monitoring data is found	Specifies how to handle alerts when no metric data is reported. Valid values: Do not do anything (Default) Send alert notifications Treated as normal

   3. Click OK.

3. Optional: View the created alert rule.

   In the navigation pane, choose Alerts.

   On the Alert Rules page, the alert rule you created appears in the list with Prometheus in the Product Name column.

References

• For more information about how to modify an alert rule, see Manage alert rules.

• For more information about how to manage namespaces, see Manage namespaces.