Forwarding rules
This topic describes how to configure a forwarding rule.
Prerequisites
Before configuring a forwarding rule, ensure that the monitoring source for which the forwarding rule is configured has been connected to Integration Management.
Scenarios
Manage forwarding rules. You can customize rules for incidents and alarms based on forwarding rules.
Procedure for Adding a Forwarding Rule
- Log in to COC.
- In the navigation pane on the left, choose Incident Management > Incident Forwarding Rules. The configuration page is displayed.
- In the upper part of the list, click Create Incident Forwarding Rule.
Figure 1 Creating an incident forwarding rule
If the information in the two forwarding rules is similar, click Copy in the Operation column to quickly create a forwarding rule.
- Enter basic information such as the rule name and application name as prompted.
Figure 2 Entering basic information
- In the Trigger Criteria area, select the Trigger Type, select the Data Source for triggering the rule, configure the Triggering Conditions, and select the Incident Level.
Figure 3 Entering a trigger criteria
The key in the trigger conditions is described as follows:
Parameter
Description
CES Alarm Field
AOM Alarm Field
alarmId
Alarm ID
alarm_id
id
alarmName
Alarm name
alarm_name
event_name in metadata
alarmLevel
Specifies the alarm severity, which can be Critical, Major, Minor, or Suggestion.
AlarmLevel
event_severity
time
Time when an alarm is generated
time
starts_at
nameSpace
Specifies the service namespace.
namespace
namespace
region
Region
Region in template_variable
Regions can be distinguished by calling domain name.
application
Application name
/
/
resourceName
Resource name
ResourceName in template_variable
resource_id in metadata
resourceId
Resource ID
ResourceId in template_variable
/
alarmDesc
Alarm description
AlarmDesc in template_variable
/
URL
Original alarm URL
Link in template_variable
/
alarmStatus
Alarm status. The value can be alarm or ok.
alarm_status
/
alarmSource
Alarm source name. For example, if an alarm is reported from CES, the value of this field is CES.
/
/
additional
Additional alarm information. The format is additional.xxx.
Except the preceding parameters, other parameters are contained in this parameter and are represented by additional.xxx. For more information about CES fields, click here
Except the preceding parameters, other parameters are contained in this parameter and are represented by additional.xxx. For more information about AOM fields, click here.
- In the Contingency Plan area, select the scripts or jobs associated with the forwarding rule. For details about how to add a script or job, see Automated O&M.
Figure 4 Entering the contingency plan.
- In the Assignment Details area, select the object and click Submit.
Figure 5 Filling the assignment rule
Procedure for Editing, Enabling, Disabling, and Deleting a Forwarding Rule
- Log in to the management console.
- Click in the upper left corner and select a region and project.
- Click , search for Cloud Operations Center, and click .
- In the navigation pane on the left, choose Incident Management > Incident Forwarding Rules. The configuration page is displayed.
- On the list page, click More > Modify or Delete in the Operation column to modify or delete a rule, click Enable or Disable in the Operation column to enable or disable a forwarding rule. After a forwarding rule is disabled, no incidents or alarms will be triggered.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot