An official English-language version of the documentation is not available. For your convenience only, we have introduced the use of machine-translation software capable of producing rough translations in various languages, including English.This machine-translated version of the documentation was produced using only machine-translation software and without any human intervention. We are making continuous efforts to improve the machine-translation software. HOWEVER, MACHINE TRANSLATIONS MAY CONTAIN ERRORS. ANY RELIANCE BY YOU UPON THIS MACHINE TRANSLATION IS SOLELY AT YOUR OWN RISK, AND ALIBABA CLOUD SHALL NOT BE LIABLE TO YOU OR ANY OTHER PARTIES FOR ANY ADVERSE CONSEQUENCES (DIRECT, INDIRECT, CONSEQUENTIAL OR OTHERWISE) ARISING FROM OR IN CONNECTION WITH THE DOCUMENTATION OR ANY TRANSLATIONS THEREOF.
To request a human-translated version of this article or to comment on the quality of machine translation, please use the "More suggestions" text area in the feedback form below to submit feedback.
Rules are the logic judgment codes placed in functions of function compute. You can reference the preset rules prepared by configuration audit. For more information, see List of preset rules. You can also customize rule functions in function Compute. For more information, see Develop custom rules. You can also submit your requirements to us by submitting a ticket. After the assessment, you can implement pre-configured rules.
- Select a rule creation method: you can select a system-preset rule or "custom rule ". Note: If you select custom rules, enter the name of the rule function that you have configured in function compute in the next step.
- Basic information: you need to set a readable name for the rule, fill in the "remarks" that is, the description content, and then fill in the name of the rule function. ( (If rules are preset for the system, the function name is pre-filled .)
- Trigger mechanism: Select the trigger method of the rule. Real-Time configuration change triggering and periodic execution are supported. When the configuration audit service detects a configuration change of the resource type associated with the rule and the actual content of the change is associated with the input parameters of the rule, the rule is triggered. Currently, rules can be periodically executed every 1, 3, 6, 12, and 24 hours.
- Monitoring scope: configure the resource type associated with the rule. The rule will listen to all physical resources of this resource type under your account. A rule can be associated with multiple resource types.
- Rule parameters: If you select a predefined rule, you must set a threshold value for the predefined rule parameters. If you select custom rules, you must set the Key and threshold of the rule input parameters. Note that the Key of a rule parameter is the input parameter name of the rule function. The input parameter name must be consistent with the actual configuration name of the resource.
- Click OK. The rule is created and in the "application" state ".