Supported Events of GaussDB

Event monitoring provides event data reporting, query, and alarm reporting. You can create alarm rules for both system and custom events. When specific events occur, Cloud Eye generates alarms for you.

Events are key operations on database resources that are stored and monitored by Cloud Eye. You can view events to see operations performed by specific users on specific resources, for example, changing instance specifications.

Event monitoring provides an API for reporting custom events, which helps you collect and report abnormal events or important change events generated by services to Cloud Eye.

Event monitoring is enabled by default. You can view monitoring details about system events and custom events. For details about system events, see Table 1.

**Table 1** Events supported by GaussDB
Source	Name	ID	Severity	Description	Handling Suggestion	Impact
GaussDB	Process status alarm	ProcessStatusAlarm	Major	Key processes exit, including CMS/CMA, ETCD, GTM, CN, and DN processes.	Wait until the process is automatically recovered or a primary/standby failover is automatically performed. Check whether services are recovered. If not, submit a service ticket by choosing Service Tickets > Create Service Ticket in the upper right corner of the management console.	If processes on primary nodes are faulty, services are interrupted and then rolled back. If processes on standby nodes are faulty, services are not affected.
	Component status alarm	ComponentStatusAlarm	Major	Key components do not respond, including CMA, ETCD, GTM, CN, and DN components.	Wait until the process is automatically recovered or a primary/standby failover is automatically performed. Check whether services are recovered. If not, submit a service ticket by choosing Service Tickets > Create Service Ticket in the upper right corner of the management console.	If processes on primary nodes do not respond, neither do the services. If processes on standby nodes are faulty, services are not affected.
	Cluster status alarm	ClusterStatusAlarm	Major	The cluster is abnormal, including the following faults: The cluster is read-only. The majority of ETCD members are faulty. The cluster resources are unevenly distributed.	In the upper right corner of the management console, submit a service ticket by choosing Service Tickets > Create Service Ticket in the upper right corner of the management console.	If the cluster status is read-only, only read requests are processed. If the majority of ETCD members are faulty, the cluster is unavailable. If resources are unevenly distributed, the instance performance and reliability deteriorate.
	Hardware resource alarm	HardwareResourceAlarm	Major	A major hardware fault occurs in the instance, such as disk damage or GTM network fault.	In the upper right corner of the management console, submit a service ticket by choosing Service Tickets > Create Service Ticket in the upper right corner of the management console.	Some or all services are affected.
	Status transition alarm	StateTransitionAlarm	Major	The following events occur in the instance: DN build attempt, DN build failure, forcible DN promotion, primary/standby DN switchover/failover, or primary/standby GTM switchover/failover.	Wait until the fault is automatically rectified and check whether services are recovered. If not, submit a service ticket by choosing Service Tickets > Create Service Ticket in the upper right corner of the management console.	Some services are interrupted.
	Other abnormal alarm	OtherAbnormalAlarm	Major	Disk usage threshold alarm	Monitor service changes and scale up storage space as needed.	If the used storage space exceeds the threshold, storage space cannot be scaled up.
	Instance running status abnormal	TaurusInstanceRunningStatusAbnormal	Major	This event is a key alarm event and is reported when an instance is faulty due to a disaster or a server failure.	In the upper right corner of the management console, submit a service ticket by choosing Service Tickets > Create Service Ticket in the upper right corner of the management console.	The database service may be unavailable.
	Instance running status recovery	TaurusInstanceRunningStatusRecovered	Major	If a disaster occurs, GaussDB provides an HA tool to automatically or manually rectify the fault. After the fault is rectified, this event is reported.	No further action is required.	None
	Faulty DB node	TaurusNodeRunningStatusAbnormal	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 by choosing Service Tickets > Create Service Ticket in the upper right corner of the management console.	The database service may be unavailable.
	DB node recovered	TaurusNodeRunningStatusRecovered	Major	If a disaster occurs, GaussDB provides an HA tool to automatically or manually rectify the fault. After the fault is rectified, this event is reported.	No further action is required.	None
	Instance creation failure	GaussDBV5CreateInstanceFailed	Major	Instances fail to be created because the quota is insufficient or underlying resources are exhausted.	Release the instances that are no longer used and try to provision new instances again, or submit a service ticket by choosing Service Tickets > Create Service Ticket in the upper right corner of the management console to adjust the quota.	Instances fail to be created.
	Node adding failure	GaussDBV5ExpandClusterFailed	Major	The underlying resources are insufficient.	Submit a service ticket by choosing Service Tickets > Create Service Ticket in the upper right corner of the management console to coordinate resources, delete the nodes that failed to be added, and add nodes again.	None
	Storage scale-up failure	GaussDBV5EnlargeVolumeFailed	Major	The underlying resources are insufficient.	Submit a service ticket by choosing Service Tickets > Create Service Ticket in the upper right corner of the management console to coordinate resources and scale up storage again.	Services may be interrupted.
	Reboot failure	GaussDBV5RestartInstanceFailed	Major	The network is abnormal.	Retry the reboot operation or submit a service ticket by choosing Service Tickets > Create Service Ticket in the upper right corner of the management console.	The database service may be unavailable.
	Full backup failure	GaussDBV5FullBackupFailed	Major	The backup files fail to be exported or uploaded.	Submit a service ticket by choosing Service Tickets > Create Service Ticket in the upper right corner of the management console.	Data cannot be backed up.
	Differential backup failure	GaussDBV5DifferentialBackupFailed	Major	The backup files fail to be exported or uploaded.	Submit a service ticket by choosing Service Tickets > Create Service Ticket in the upper right corner of the management console.	Data cannot be backed up.
	Backup deletion failure	GaussDBV5DeleteBackupFailed	Major	Backup files fail to be cleared.	Submit a service ticket by choosing Service Tickets > Create Service Ticket in the upper right corner of the management console.	There may be residual OBS files.
	EIP binding failure	GaussDBV5BindEIPFailed	Major	The EIP has been used or EIP resources are insufficient.	Submit a service ticket by choosing Service Tickets > Create Service Ticket in the upper right corner of the management console.	The instance cannot be accessed from the public network.
	EIP unbinding failure	GaussDBV5UnbindEIPFailed	Major	The network or the EIP service is faulty.	Retry the unbinding operation or submit a service ticket by choosing Service Tickets > Create Service Ticket in the upper right corner of the management console.	There may be residual IP resources.
	Parameter template application failure	GaussDBV5ApplyParamFailed	Major	Changing a parameter group times out.	Change the parameter group again.	None
	Parameter modification failure	GaussDBV5UpdateInstanceParamGroupFailed	Major	Changing a parameter group times out.	Change the parameter group again.	None
	Backup and restoration failure	GaussDBV5RestoreFromBcakupFailed	Major	The underlying resources are insufficient or backup files fail to be downloaded.	In the upper right corner of the management console, submit a service ticket by choosing Service Tickets > Create Service Ticket in the upper right corner of the management console.	The database service may be unavailable during the restoration failure.