Application Real-Time Monitoring Service:CreateOrUpdateAlertRule

The ID of the alert rule.

• If you do not specify this parameter, a new alert rule is created.
• If you specify this parameter, the specified alert rule is modified.

The name of the alert rule.

The region ID.

The type of the alert rule. Valid values:

• APPLICATION_MONITORING_ALERT_RULE: alert rule for Application Monitoring
• BROWSER_MONITORING_ALERT_RULE: alert rule for Browser Monitoring
• PROMETHEUS_MONITORING_ALERT_RULE: alert rule for Managed Service for Prometheus
• XTRACE_MONITORING_ALERT_RULE: alert rule for Managed Service for OpenTelemetry
• EBPF_MONITORING_ALERT_RULE: alert rule for Application Monitoring eBPF Edition
• RUM_MONITORING_ALERT_RULE: alert rule for Real User Monitoring

The status of the alert rule. Valid values:

• RUNNING (default)
• STOPPED

The notification policy.

• If you set this parameter to null, no notification policy is specified. After you create an alert rule, you can create a notification policy and specify match rules and match conditions. For example, you can specify the name of the alert rule as the match condition. When the alert rule is triggered, an alert event is generated and an alert notification is sent to the contacts or contact groups that are specified in the notification policy.
• To specify a notification policy, set this parameter to the ID of the notification policy. Application Real-Time Monitoring Service (ARMS) automatically adds a match rule to the notification policy and specifies the ID of the alert rule as the match condition. The name of the alert rule is also displayed. This way, the alert events that are generated based on the alert rule can be matched by the specified notification policy.

The process ID (PID) that is associated with the Application Monitoring or Browser Monitoring alert rule.

Specifies whether to apply the alert rule to new applications that are created in Application Monitoring or Browser Monitoring. Valid values:

• true: enables the health check feature.
• false: disables the automatic backup feature.

The metric type of the Application Monitoring or Browser Monitoring alert rule. For more information, see the following table.

The filter conditions of the Application Monitoring or Browser Monitoring alert rule. Format:

"DimFilters": [ 
{ 
 "FilterOpt": "ALL",
"FilterValues": [],         //The value of the filter condition.
"FilterKey": "rootIp"     //The key of the filter condition.
}
]

Valid values of FilterOpt:

• STATIC: matches the value of the specified dimension.
• ALL: traverses all dimension values. Dynamic thresholds do not support traversal.
• DISABLE: aggregates the values of all dimensions.

The content of the Application Monitoring or Browser Monitoring alert rule. The following code provides an example of the AlertRuleContent parameter. For more information about the meaning of each field, see the supplementary description.

{ 
    "Condition": "OR",
     "AlertRuleItems": [
             { "Operator": "CURRENT_LTE",
                 "MetricKey": "appstat.jvm.threadcount",
                 "Value": 1000,
                 "Aggregate": "AVG",
                  "N": 10,
                  "Tolerability": 169
            } 
       ]  
  }

The alert check type of the Prometheus alert rule. Valid values:

• STATIC: a static threshold value. If you set the parameter to STATIC, you must specify the MetricsKey parameter. For more information, see the Correspondence between AlertGroup and MetricsKey for Prometheus Service table.
• CUSTOM: a custom PromQL statement. If you set the parameter to CUSTOM, you must specify the PromQL, Duration, and Message parameters to create a Prometheus alert rule.

The ID of the monitored cluster.

The alert contact group ID of the Prometheus alert rule. Valid values:

• -1: custom PromQL
• 1: Kubernetes load
• 15: Kubernetes node

The PromQL statement of the Prometheus alert rule.

The duration of the Prometheus alert rule, in minutes, in the range of [0,1440].

The severity level of the Prometheus alert rule.

• P1: Alert notifications are sent for major issues that affect the availability of core business, have a huge impact, and may lead to serious consequences.
• P2: Alert notifications are sent for service errors that affect the system availability with relatively limited impact.
• P3: Alert notifications are sent for issues that may cause service errors or negative effects, or alert notifications for services that are relatively less important.
• P4: Alert notifications are sent for low-priority issues that do not affect your business.
• Default: Alert notifications are sent regardless of alert levels.

The alert message of the Prometheus alert rule.

The tags of the Prometheus alert rule.

The annotations of the Prometheus alert rule.

The alert metrics. If you set the AlertCheckType parameter to STATIC when you create a Prometheus alert rule, you must specify the MetricsKey parameter.

The list of tags.

Application Tags. Used for application monitoring alert rules, to filter applications associated with alert rules.

Data Configuration. The dataRevision field specifies the data repair method when there is no data for the metric.

• Fill with zero: 0
• Fill with one: 1
• Fill with null: 2 (default, does not trigger an alarm)

The effective time and notification time. This parameter is used to be compatible with the old version of the rule.

The configuration of the alert sending channel. This parameter is used to be compatible with the old version of the rule.

The notification mode. You can specify the normal mode or simple mode.

• DIRECTED_MODE
• NORMAL_MODE

The product code. If you specify this parameter when you create a Prometheus alert rule, the backend checks whether the product exists.

The configurations that are automatically appended to monitor the application based on the specified alert rule.

• autoAddMatchType:

  the matching mode. Valid values: REGULAR and NOT_REGULAR.

• autoAddMatchExp: the regular expression