Event monitoring has been upgraded to be fully integrated with event alarms, which were originally separate from event monitoring. This change allows for a unified area for both event queries and event alarms.

Upgrade details

  1. Event alarms have now migrated to the Event Monitoring page of the console. Originally, event alarms were set on the Create Alarm Rule page. This change has the effect that you can no longer create the following event alarms by using alarm templates: CloudMonitor agent no heartbeat alarms; RDS, Redis, and Memcache faults; RDS, Redis, and Memcache master/slave switchover alarms; MongoDB and Container Service status and node exception alarms; RDS and Redis synchronization exception alarms for disaster recovery.
  2. Application groups support event alarm subscription notifications. When you create an application group, you can enable this function. After you enable this feature, you will receive notifications for critical-level and warning-level events for the resources in your application group.
  3. This upgrade does not affect any existing event alarm rules. However, you cannot modify these rules after upgrading. To make modifications, you need to create new alarm rules in the event monitoring console.

The preceding upgrade does not affect your online services and existing alarm configurations.

For more information about the event monitoring feature of CloudMonitor, see Cloud product system event monitoring and Use system event alarms.