Events Supported by Event Monitoring

DDS

DB instance creation failure

DDSCreateInstanceFailed

Major

A DB instance fails to create because the number of disks is insufficient, the quota is insufficient, or underlying resources are exhausted.

Check the number of disks and quota size. Release resources and create DB instances again.

DB instances cannot be created.

Replication status abnormal

DDSAbnormalReplicationStatus

Major

The possible causes are as follows:

1. The replication delay between the primary node and the secondary node or a read replica is too long, which usually occurs when a large amount of data is written to databases or a large transaction is processed. During peak hours, data may be blocked.
2. The network between the primary node and the secondary node or a read replica is disconnected.

Submit a service ticket.

1. Read and write operations on the original instance are not interrupted, but data updates on the secondary node may experience delays.
2. If the replication delay keeps growing between the primary and secondary nodes, the secondary node may be disconnected.

Replication status recovered

DDSReplicationStatusRecovered

Major

The replication delay between the primary and secondary nodes is within the normal range, or the network connection between them has restored.

No further action is required.

None

DB instance faulty

DDSFaultyDBInstance

Major

This event is a key alarm event and is reported when an instance is faulty due to a disaster or a server failure.

Check whether the database service is available, and submit a service ticket.

The database service may be unavailable.

DB instance recovered

DDSDBInstanceRecovered

Major

DDS provides an HA tool to automatically or manually rectify the catastrophic fault. After the fault is rectified, this event is reported.

No further action is required.

None

Node status abnormal

DDSFaultyDBNode

Major

This event is a key alarm event and is reported when a database node is faulty due to a disaster or a server failure.

Check whether the database service is available, and submit a service ticket.

The database service may be unavailable.

DB node recovered

DDSDBNodeRecovered

Major

DDS provides an HA tool to automatically or manually rectify the catastrophic fault. After the fault is rectified, this event is reported.

No further action is required.

None

Primary/secondary switchover or failover

DDSPrimaryStandbySwitched

Major

This event is reported when a primary/secondary switchover or failover is triggered.

No further action is required.

None

Insufficient storage space

DDSRiskyDataDiskUsage

Major

The storage space is insufficient.

Scale up storage space. For details, see Scaling Up Storage Space.

The DB instance becomes read-only, and data cannot be written to the database.

Data disk expanded and being writable

DDSDataDiskUsageRecovered

Major

The capacity of a data disk has been expanded and the data disk becomes writable.

No further action is required.

None

Schedule for deleting a KMS key

planDeleteKmsKey

Major

The user plans to delete a KMS key.

Check whether the DDS instance associated with the key has been deleted or is no longer used. Deleting the key will affect the instance workloads.

The key will be automatically deleted after it expires. Deleting the key will affect the instance workloads.

Full backup failure

DDSFullBackupFailed

Major

A single full backup failure does not affect the files that have been successfully backed up, but prolongs the incremental backup restoration time during the point-in-time recovery (PITR).

Create a full backup again.

If a full backup fails, backup and restoration will be affected.