Help Center/ TaurusDB/ User Guide/ Monitoring and Alarms/ Event Monitoring/ Events Supported by Event Monitoring
Updated on 2024-11-06 GMT+08:00

Events Supported by Event Monitoring

Table 1 GaussDB(for MySQL)

Event Source

Event Name

Event ID

Alarm Severity

Description

Handling Suggestion

Impact

GaussDB(for MySQL)

Incremental backup failure

TaurusIncrementalBackupInstanceFailed

Major

The network between the instance and the management plane or the OBS is disconnected, or the backup environment created for the instance is abnormal.

Submit a service ticket.

Backup jobs fail.

Read replica creation failure

addReadonlyNodesFailed

Major

The quota is insufficient or underlying resources are exhausted.

Check the read replica quota. Release resources and create read replicas again.

Read replicas fail to be created.

DB instance creation failure

createInstanceFailed

Major

The quota is insufficient or underlying resources are exhausted.

Check the instance quota. Release resources and create instances again.

Instances fail to be created.

Read replica promotion failure

activeStandBySwitchFailed

Major

The read replica fails to be promoted to the primary node due to network or server failures. The original primary node takes over services quickly.

Submit a service ticket.

The read replica fails to be promoted to the primary node.

Instance specifications change failure

flavorAlterationFailed

Major

The quota is insufficient or underlying resources are exhausted.

Submit a service ticket.

Instance specifications fail to be changed.

Faulty DB instance

TaurusInstanceRunningStatusAbnormal

Major

The instance process is faulty or the network between the instance and the DFV storage is disconnected.

Submit a service ticket.

Services may be affected.

DB instance recovered

TaurusInstanceRunningStatusRecovered

Major

The instance is recovered.

Observe the service running status.

None.

Faulty node

TaurusNodeRunningStatusAbnormal

Major

The node process is faulty or the network between the node and the DFV storage is disconnected.

Observe the instance and service running statuses.

A read replica may be promoted to the primary node.

Node recovered

TaurusNodeRunningStatusRecovered

Major

The node is recovered.

View the node running status.

None.

Read replica deletion failure

TaurusDeleteReadOnlyNodeFailed

Major

The network between the management plane and the read replica is disconnected or the VM fails to be deleted from IaaS.

Submit a service ticket.

Read replicas fail to be deleted.

Password reset failure

TaurusResetInstancePasswordFailed

Major

The network between the management plane and the instance is disconnected or the instance is abnormal.

Check the instance status and try again. If the fault persists, submit a service ticket.

Passwords fail to be reset for instances.

DB instance reboot failure

TaurusRestartInstanceFailed

Major

The network between the management plane and the instance is disconnected or the instance is abnormal.

Check the instance status and try again. If the fault persists, submit a service ticket.

Instances fail to be rebooted.

Restoration to new DB instance failure

TaurusRestoreToNewInstanceFailed

Major

The instance quota is insufficient, underlying resources are exhausted, or the data restoration logic is incorrect.

If the new instance fails to be created, check the instance quota, release resources, and try to restore to a new instance again. In other cases, submit a service ticket.

Backup data fails to be restored to new instances.

EIP binding failure

TaurusBindEIPToInstanceFailed

Major

The binding task fails.

Submit a service ticket.

EIPs fail to be bound to instances.

EIP unbinding failure

TaurusUnbindEIPFromInstanceFailed

Major

The unbinding task fails.

Submit a service ticket.

EIPs fail to be unbound from instances.

Parameter modification failure

TaurusUpdateInstanceParameterFailed

Major

The network between the management plane and the instance is disconnected or the instance is abnormal.

Check the instance status and try again. If the fault persists, submit a service ticket.

Instance parameters fail to be modified.

Parameter template application failure

TaurusApplyParameterGroupToInstanceFailed

Major

The network between the management plane and instances is disconnected or the instances are abnormal.

Check the instance status and try again. If the fault persists, submit a service ticket.

Parameter templates fail to be applied to instances.

Full backup failure

TaurusBackupInstanceFailed

Major

The network between the instance and the management plane or the OBS is disconnected, or the backup environment created for the instance is abnormal.

Submit a service ticket.

Backup jobs fail.

Read replica promotion

TaurusActiveStandbySwitched

Major

When the primary node is faulty, a read replica is promoted to the primary node.

Check the instance status. If the fault persists, submit a service ticket.

Services are intermittently interrupted.

Instance read-only

NodeReadonlyMode

Major

The instance supports only query operations.

Submit a service ticket.

After the instance becomes read-only, write requests cannot be processed.

Instance read/write

NodeReadWriteMode

Major

The instance can process both write and read requests.

Submit a service ticket.

None.

Instance DR switchover

DisasterSwitchOver

Major

If an instance is faulty and unavailable, a switchover is performed to ensure that the instance continues to provide services.

Contact technical support.

The database connection is intermittently interrupted. The DR instance is promoted to primary to provide services.

Database process restarted

TaurusDatabaseProcessRestarted

Major

The database process is stopped due to insufficient memory or high load.

Log in to the Cloud Eye console. Check whether the memory usage increases sharply or the CPU usage is too high for a long time. You can increase the specifications or optimize the service logic.

When the database process is suspended, workloads on the node are interrupted. In this case, the HA service automatically restarts the database process and attempts to recover the workloads.

Connection failure between proxy instance and DB instance

proxy_connection_failure_to_db

Major

The database proxy failed to establish a new connection with the primary node of a DB instance, and it may fail to establish a new connection with a read replica. The DB instance or proxy instance is overloaded, or the network between the them is abnormal.

Change values of related parameters based on metrics (Connections, Active Connections, and CPU Usage) of the DB instance and proxy instance. If the metrics are normal, submit a service ticket.

Service requests accessed through the proxy instance are interrupted.

Connection failure between database proxy and read replica

proxy_connection_failure_to_replica

General

The proxy instance failed to establish a new connection with a read replica. The read replica is overloaded, or the network between the proxy instance and read replica is abnormal.

Change values of related parameters based on metrics (Connections, Active Connections, and CPU Usage) of the read replica. If the metrics are normal, submit a service ticket.

Read requests accessed through the proxy instance are interrupted.

Proxy instance access to DB instance failure

proxy_connection_failure_cause_security_group

Major

No rules in the security group allow the proxy instance to access the DB instance.

Add the proxy instance address to the rules of the security group.

Service requests accessed through the proxy instance are interrupted.