RDS Events

Updated on 2022-09-14 GMT+08:00

View PDF

RDS is an online relational database service based on the cloud computing platform. RDS is reliable, scalable, and easy to manage, and immediately ready for use. When using relational databases, you need to pay attention to the database status. You can use event monitoring to track abnormal events to ensure stable service running.

**Table 1** Key RDS events
Event Name	Event Description	Handling Method
DB instance creation failure	Generally, DB instances fail to be created because the number and quota of disks are small, and the underlying resources are exhausted.	Check the number and quota of disks. Release resources and create DB instances again.
Full backup failure	A single full backup failure does not affect the files that have been successfully backed up, but prolongs the incremental backup time during the point-in-time restore (PITR).	Create a manual backup again.
Primary/standby switchover failure	The standby DB instance does not take over services from the primary DB instance due to some network or server failures. The original primary DB instance continues to provide services within a short time.	Check whether the connection between the application and the database is re-established.
Replication status abnormal	The replication delay between the primary and standby DB instances is too long (usually occurs when a large amount of data is written to databases or a large transaction is performed). During off-peak hours, the replication delay between the primary and standby DB instances gradually decreases. Another possible cause is that the network between the primary and standby DB instances is interrupted. However, the network interruption does not interrupt data read and write of a single DB instance, and customers' applications are unaware of the interruption.	Submit a service ticket for processing.
DB instance faulty	A single or primary DB instance is faulty due to a disaster or a server failure. This event is critical and may cause database service unavailability.	Check whether an automated backup policy has been configured for the DB instance and submit a service ticket for processing.
Failure of changing single DB instance to primary/standby	During the standby DB instance creation or after the standby DB instance is created, the configuration synchronization between the primary DB instance and the standby DB instance is faulty. Generally, the fault is caused by insufficient resources of the data center where the standby DB instance is located. This event does not cause the data read and write interruption of the original single DB instance, and customers' applications are unaware of this event.	Submit a service ticket for processing.
Replication status recovered	The replication delay between the primary and standby DB instances is within the normal range, or the network connection between the two is restored.	No action is required.
DB instance recovered	RDS uses high availability tools to rebuild the standby DB instance for disaster recovery.	No action is required.

Procedure

Log in to the management console.
In the upper left corner, select a region and a project.
Choose Service List > Cloud Eye.
In the navigation pane on the left, choose Event Monitoring. In the upper right corner, click Create Alarm Rule and set parameters as prompted.
NOTE:

In this example, Event Name is set to Full backup failure. Set the event name based on the site requirements. For details about other parameters, see Creating an Alarm Rule to Monitor an Event.

Click Create.
When abnormal DB instance events occur, Cloud Eye notifies you in real time through the SMN service.