| | | | |
| | | | The name of the API. The API name is UpdateEventRule. |
| | | | The API version. The API version is 2018-01-01. |
| | | | |
| | | | Event rule name. - The name must be 1 to 128 characters in length.
- It cannot start with a digit or hyphen (-).
|
| | | This is test rule 01 after updating | Event rule description. - It cannot start with a digit, hyphen (-), or Chinese character.
- It can contain only Chinese characters, letters, digits, underscore (_), hyphen (-), and Chinese characters.
- It must be 0 to 255 characters in length.
|
| | | | Event bus name. Only default is supported. |
| | | | |
| | | [ "ecs:Disk:DiskError.Redeploy.Executing", "ecs:Disk:DiskError.Redeploy.Inquiring", "ecs:Disk:DiskError.Redeploy.Succeeded" ] | |
| | | | Rule status. - enable: The rule is enabled.
- disable: The rule is disabled.
|
| | | | Severity level of the alert. |
| | | | Filter pattern, also known as event matching rules. Custom matching rules are not supported. |
| | | | The period of time during which the rule is active. |
| | | [ "Webhook", "Email", "SMS" ] | Alert notification method. - MQ: Message Queue for Kafka
|
| | | [ "157284********69152" ] | A list of alert contact group IDs. When the ContactMethods parameter is Email, Phone, or SMS, this parameter cannot be empty. |
| | | http://example.com/alert | Callback address to be triggered. This parameter is configurable when ContactMethods options include webhook. warning WebhookIds and Endpoint parameters are mutually exclusive. Only one can be configured per call. |
| | | | TLS configuration when ContactMethods options include TLS. |
| | | | Message queue when ContactMethods options include MQ. |
| | | | A list of alert callback IDs. warning WebhookIds and Endpoint parameters are mutually exclusive. Only one can be configured per call. |
| | | | Notification template configuration. tip Events follow a subscription model. A single event can match multiple event rules, with each event rule configurable with different delivery channels. When contact duplicates exist across rules, event rules are sorted by severity level (descending) + update time (descending). The severity level and notification template of the highest-priority rule are used for event delivery. |