Tencent Cloud

Recent Pages

TencentDB for MySQL

Last updated: 2024-11-18 14:05:48

The monitoring events generated by the resource instances and products that customers purchase and use on the cloud are as follows:
Event Name
Event Type
Dimension
Recovery Concept Availability
Event Description
Solutions and Suggestions
OutOfMemory
Exception Event
TencentDB for MySQL instance dimension
Yes
Database memory is overloaded.
Evaluate whether the current database memory specifications meet business needs. If additional memory is required, consider upgrading the MySQL memory configuration.
Switch
Exception Event
TencentDB for MySQL instance dimension
Yes
A switch occurs between the primary and secondary instances.
This event may be triggered by a physical server failure. Please check whether the instance status is normal.
RORemoval
Exception Event
TencentDB for MySQL instance dimension
Yes
The RO instance has failed or exceeded the latency threshold.
If there is only one RO instance in the RO group and the instance is removed, promptly switch the read traffic to prevent a single point of failure. It is recommended to have at least two RO instances in the group.
ServerfailureInstanceMigration
Exception Event
TencentDB for MySQL instance dimension
Yes
Instance migration is initiated due to server failure.
The migration switch time is based on the maintenance window. If you need to change the switch time, adjust it promptly; the switch will follow the updated maintenance window.
Auditclose
Exception Event
TencentDB for MySQL instance dimension
No
This event is deprecated and no longer in use.
This event is deprecated and no longer in use.
InstRepStatus
Exception Event
TencentDB for MySQL instance dimension
Yes
Indicates whether primary/secondary synchronization between the RO instance and the primary instance is normal; RO instance configuration is required.
This exception may occur due to limitations in the RO instance specifications or large transactions on the primary instance. Consider increasing the RO instance configuration or reducing large transactions.
ProxyNodeRemoval
Exception Event
TencentDB for MySQL instance dimension
Yes
RO nodes that exceed latency thresholds, encounter connection issues, or experience I/O or SQL thread exceptions will be removed, provided they meet the minimum retained RO node count and latency removal time.
If the database proxy has only one RO instance, removing that instance may lead to a single point of failure. To prevent this, it is recommended to configure at least two RO instances for the database proxy.
ProxyNotAvailable
Exception Event
TencentDB for MySQL instance dimension
Yes
The proxy node encounters an issue, rendering it unable to provide proxy services.
When a database proxy failure occurs, accessing the database instance via the database proxy VIP is not possible. Ensure that database proxy failover is enabled.
Outofstorage
Exception Event
TencentDB for MySQL instance dimension
Yes
Database disk is overloaded.
Evaluate whether the current database disk specifications meet business needs. If additional disk space is required, consider scaling out the MySQL disk capacity.
PlannedSwitch
Exception Event
TencentDB for MySQL instance dimension
No
The primary/secondary switch is triggered and completed due to manual operations (such as configuration change, upgrade, or intentional switch).
The primary/secondary switch is triggered and completed due to manual operations (such as configuration change, upgrade, or intentional switch). During the restart process, a momentary disconnection lasting a few seconds may occur. Please check whether your application’s connection is stable, and consider enabling an automatic reconnection mechanism to minimize the impact.
MemoryUsedHigh
Exception Event
TencentDB for MySQL instance dimension
Yes
The memory utilization is excessively high.
High memory utilization has been detected for this instance, presenting a potential operational risk. To reduce the risk for the database instance, consider scaling out the memory specification or performing an operational analysis using TencentDB for DBbrain.
BackendInstanceMigration
Exception Event
TencentDB for MySQL instance dimension
Yes
Instance migration is initiated due to operational risks detected on the server.
Hardware risks have been detected in the operating environment of the instance. To reduce the probability of database instance failure, an instance migration has been initiated, which will not affect business operations during the process. The database instance will switch during your specified maintenance window, causing a momentary disconnection lasting a few seconds. Ensure that your business includes a reconnection mechanism. If you need to change the switch time, adjust the maintenance window accordingly, as the switch time will follow the updated maintenance window.
﻿
CPUExpansion
Exception Event
TencentDB for MySQL instance dimension
﻿
No
﻿
CPU scale-out is triggered based on the specified threshold.
﻿
The instance triggers a CPU performance scale-out when CPU utilization reaches the specified threshold. This scale-out does not impact the instance’s operation.
﻿
CPUExpansionFailed
Exception Event
TencentDB for MySQL instance dimension
No
﻿
CPU scale-out failure is triggered based on the specified threshold.
﻿
The instance fails to scale out CPU performance due to insufficient local resources. A new scale-out attempt will be initiated shortly.
﻿
CPUContraction
Exception Event
TencentDB for MySQL instance dimension
No
﻿
CPU scale-in is triggered based on the specified threshold.
﻿
The instance triggers a CPU performance scale-in when CPU utilization reaches the specified threshold. After the scale-in, monitor whether the current configuration meets the business needs.
Instance rebuilt caused by exception
Exception Event
TencentDB for MySQL instance dimension
No
Instance computing resources are rebuilt due to a database exception.
Instance resources are rebuilt due to an operational failure of the current database. Please assess whether the current database specifications meet business needs; if higher specifications are required, consider upgrading the MySQL configuration.
OverusedReadonlySet
Exception Event
TencentDB for MySQL instance dimension
No
Due to exceeded disk space usage, the database instance is set to a locked status, preventing further data writes or service availability.
1. You can reduce the local binlog retention time to free up some space.
2. Try deleting unnecessary databases and tables to free up space.
3. Scale out the database instance’s disk upper limit.
OverusedReadWriteSet
Exception Event
TencentDB for MySQL instance dimension
No
The database instance is unlocked and resumes full database services.
1. You can reduce the local binlog retention time to free up some space.
2. Try deleting unnecessary databases and tables to free up space.
3. Scale out the database instance’s disk upper limit.
OverusedPreReadonly
Exception Event
TencentDB for MySQL instance dimension
No
Due to exceeded disk space usage, the database instance is about to be locked. Once it is locked, data writes or service availability will be disabled.
1. You can reduce the local binlog retention time to free up some space.
2. Try deleting unnecessary databases and tables to free up space.
3. Scale out the database instance’s disk upper limit.
AuditLowRisk
Exception Event
TencentDB for MySQL instance dimension
No
The audit log has matched a low-risk rule.
Go to the console to view detailed alarm log information and address it based on your business needs. The alarm is triggered because the audit log has matched a low-risk rule.
AuditMediumRisk
Exception Event
TencentDB for MySQL instance dimension
No
The audit log has matched a medium-risk rule.
Go to the console to view detailed alarm log information and address it based on your business needs. The alarm is triggered because the audit log has matched a medium-risk rule.
AuditHighRisk
Exception Event
TencentDB for MySQL instance dimension
No
The audit log has matched a high-risk rule.
Go to the console to view detailed alarm log information and address it based on your business needs. The alarm is triggered because the audit log has matched a high-risk rule.
Console operations (CloudAudit)
Exception Event
Instance Dimension
No
Operation events such as instance addition, deletion, and configuration changes.
Manual troubleshooting.
Cloud API actions (CloudAudit)
Exception Event
Instance Dimension
No
Operation events such as instance addition, deletion, and configuration changes.
Manual troubleshooting.
Mini program operations (CloudAudit)
Exception Event
Instance Dimension
No
Operation events such as instance addition, deletion, and configuration changes.
Manual troubleshooting.
MasterHealthCheckError
Exception Event
TencentDB for MySQL instance dimension
No
The primary instance may be unable to determine the current primary instance node service status as active due to high load, maximum number of connections reached, runtime exceptions, network fluctuations, etc.
The node configurations can be appropriately added to reduce the probability of risk occurrence.
1. If you receive a MasterHealthCheckRecovery event, it means that the primary node has been recovered, HA has been switched to rollback, and no actual HA has occurred.
2. If you receive both Switch and SlaveHealthCheckRecovery events, it indicates that HA switch has occurred and recovery succeeded.
3. If you receive a Switch event but do not receive a SlaveHealthCheckRecovery event, it means that HA has occurred and the original primary instance has been rebuilt.
MasterHealthCheckRecovery
Recovery event
TencentDB for MySQL instance dimension
No
Recovery after the database primary node encounters a service exception.
The service exception (MasterHealthCheckError) on the database primary node has been recovered and is now operating normally.
SlaveHealthCheckError
Exception Event
TencentDB for MySQL instance dimension
No
The secondary instance might be unable to determine the current secondary instance node service status as active due to high load, the maximum number of connections reached, runtime exceptions, and network fluctuations, etc.
Node configurations or the number of read-only nodes can be appropriately increased to reduce the probability of risk occurrence.
1. If you receive SlaveHealthCheckRecovery, it indicates that the secondary node has been recovered.
2. If you have not received SlaveHealthCheckRecovery, it indicates that the secondary node test has timed out and is being rebuilt.
SlaveHealthCheckRecovery
Recovery event
TencentDB for MySQL instance dimension
No
1. Recovery after the database secondary node encounters a service exception.
2. The original primary node is abnormal. After the primary-secondary switchover, the originally abnormal primary node is recovered as the secondary node.
1. The service exception (SlaveHealthCheckError) on the database secondary node has been recovered and is now operating normally.
2. The service exception (MasterHealthCheckError) on the database original primary node has been recovered and is now operating normally.
The monitoring events generated by the TencentDB for MySQL Cluster Edition instances that customers purchase and use on the cloud are as follows:
Event Name
Event Type
Dimension
Recovery Concept Availability
Event Description
Solutions and Suggestions
Restart
Exception Event
TencentDB for MySQL instance dimension
Yes
1. The instance restarts due to manual operations, such as restarting CVM instances or changing parameters.
2. An event alarm is triggered during the restart process in the workflow.
1. The instance restarts due to manual operations, such as restarting CVM instances or changing parameters. During the restart process, a momentary disconnection lasting a few seconds may occur. Please check whether your application’s connection is stable, and consider enabling an automatic reconnection mechanism to minimize the impact. This event has a recovery status; monitor subsequent event notifications.
2. An event alarm is triggered during the restart process in the workflow. Such alarms can be monitored alongside other related events.
OutOfMemory
Exception Event
TencentDB for MySQL node dimension
Yes
Database memory is overloaded.
Evaluate whether the current database memory specifications meet business needs. If additional memory is required, consider upgrading the MySQL memory configuration. This event has a recovery status; monitor subsequent event notifications.
Switch
Exception Event
TencentDB for MySQL instance dimension
Yes
A switch occurs between the primary and secondary instances.
This event may be triggered by a physical server failure. Please check whether the instance status is normal. This event has a recovery status; monitor subsequent event notifications.
ServerFailureNodeMigration
Exception Event
TencentDB for MySQL node dimension
Yes
A node rebuild is initiated due to a cluster edition node failure.
The migration switch time is based on the maintenance window. If you need to change the switch time, adjust it promptly; the switch will follow the updated maintenance window. This event has a recovery status; monitor subsequent event notifications.
RoNodeRepStatus
Exception Event
TencentDB for MySQL node dimension
Yes
Indicates whether primary/secondary synchronization between the cluster edition RO node and the primary instance is normal; RO node configuration is required.
This exception may occur due to limitations in the RO node specifications or large transactions on the primary instance. Consider increasing the RO node configuration or reducing large transactions. This event has a recovery status; monitor subsequent event notifications.
OverusedReadonlySet
Exception Event
TencentDB for MySQL instance dimension
No
Due to exceeded disk space usage, the database instance is set to a locked status, preventing further data writes or service availability.
1. You can reduce the local binlog retention time to free up some space.
2. Try deleting unnecessary databases and tables to free up space.
3. Scale out the database instance’s disk upper limit.
OverusedReadWriteSet
Exception Event
TencentDB for MySQL instance dimension
No
The database instance is unlocked and resumes full database services.
The database instance (OverusedReadonlySet) is unlocked.
PlannedSwitch
Exception Event
TencentDB for MySQL instance dimension
No
The primary/secondary switch is triggered and completed due to manual operations (such as configuration change, upgrade, or intentional switch).
The primary/secondary switch is triggered and completed due to manual operations (such as configuration change, upgrade, or intentional switch). During the restart process, a momentary disconnection lasting a few seconds may occur. Please check whether your application’s connection is stable, and consider enabling an automatic reconnection mechanism to minimize the impact.
RWNodeException
Exception Event
TencentDB for MySQL node dimension
No
The read/write node may fail to determine its active status due to high load, maximum connections, or operational issues.
Consider increasing node configurations to reduce the risk. Use RWNodeExceptionRecovery to view whether the service has recovered and Switch to view whether this exception triggered a switch.
RWNodeExceptionRecovery
Exception Event
TencentDB for MySQL node dimension
No
The operational status of the read/write node has recovered.
The operational status of the read/write node (RWNodeException) has recovered.
RONodeException
Exception Event
TencentDB for MySQL node dimension
No
The RO node may fail to determine its active status due to high load, maximum connections, or operational issues.
Consider increasing node configurations or the number of RO nodes to reduce the risk. Use RONodeExceptionRecovery to view whether the service has recovered and Switch to view whether this exception triggered a switch.
RONodeExceptionRecovery
Exception Event
TencentDB for MySQL node dimension
No
The operational status of the RO node has recovered.
The operational status of the RO node (RONodeException) has recovered.

Contact Us

Contact our sales team or business advisors to help your business.

Technical Support

Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

7x24 Phone Support

tencent cloud

Recent Pages

TencentDB for MySQL

Was this page helpful?

Was this page helpful?

Event Name	Event Type	Dimension	Recovery Concept Availability	Event Description	Solutions and Suggestions
OutOfMemory	Exception Event	TencentDB for MySQL instance dimension	Yes	Database memory is overloaded.	Evaluate whether the current database memory specifications meet business needs. If additional memory is required, consider upgrading the MySQL memory configuration.
Switch	Exception Event	TencentDB for MySQL instance dimension	Yes	A switch occurs between the primary and secondary instances.	This event may be triggered by a physical server failure. Please check whether the instance status is normal.
RORemoval	Exception Event	TencentDB for MySQL instance dimension	Yes	The RO instance has failed or exceeded the latency threshold.	If there is only one RO instance in the RO group and the instance is removed, promptly switch the read traffic to prevent a single point of failure. It is recommended to have at least two RO instances in the group.
ServerfailureInstanceMigration	Exception Event	TencentDB for MySQL instance dimension	Yes	Instance migration is initiated due to server failure.	The migration switch time is based on the maintenance window. If you need to change the switch time, adjust it promptly; the switch will follow the updated maintenance window.
Auditclose	Exception Event	TencentDB for MySQL instance dimension	No	This event is deprecated and no longer in use.	This event is deprecated and no longer in use.
InstRepStatus	Exception Event	TencentDB for MySQL instance dimension	Yes	Indicates whether primary/secondary synchronization between the RO instance and the primary instance is normal; RO instance configuration is required.	This exception may occur due to limitations in the RO instance specifications or large transactions on the primary instance. Consider increasing the RO instance configuration or reducing large transactions.
ProxyNodeRemoval	Exception Event	TencentDB for MySQL instance dimension	Yes	RO nodes that exceed latency thresholds, encounter connection issues, or experience I/O or SQL thread exceptions will be removed, provided they meet the minimum retained RO node count and latency removal time.	If the database proxy has only one RO instance, removing that instance may lead to a single point of failure. To prevent this, it is recommended to configure at least two RO instances for the database proxy.
ProxyNotAvailable	Exception Event	TencentDB for MySQL instance dimension	Yes	The proxy node encounters an issue, rendering it unable to provide proxy services.	When a database proxy failure occurs, accessing the database instance via the database proxy VIP is not possible. Ensure that database proxy failover is enabled.
Outofstorage	Exception Event	TencentDB for MySQL instance dimension	Yes	Database disk is overloaded.	Evaluate whether the current database disk specifications meet business needs. If additional disk space is required, consider scaling out the MySQL disk capacity.
PlannedSwitch	Exception Event	TencentDB for MySQL instance dimension	No	The primary/secondary switch is triggered and completed due to manual operations (such as configuration change, upgrade, or intentional switch).	The primary/secondary switch is triggered and completed due to manual operations (such as configuration change, upgrade, or intentional switch). During the restart process, a momentary disconnection lasting a few seconds may occur. Please check whether your application’s connection is stable, and consider enabling an automatic reconnection mechanism to minimize the impact.
MemoryUsedHigh	Exception Event	TencentDB for MySQL instance dimension	Yes	The memory utilization is excessively high.	High memory utilization has been detected for this instance, presenting a potential operational risk. To reduce the risk for the database instance, consider scaling out the memory specification or performing an operational analysis using TencentDB for DBbrain.
BackendInstanceMigration	Exception Event	TencentDB for MySQL instance dimension	Yes	Instance migration is initiated due to operational risks detected on the server.	Hardware risks have been detected in the operating environment of the instance. To reduce the probability of database instance failure, an instance migration has been initiated, which will not affect business operations during the process. The database instance will switch during your specified maintenance window, causing a momentary disconnection lasting a few seconds. Ensure that your business includes a reconnection mechanism. If you need to change the switch time, adjust the maintenance window accordingly, as the switch time will follow the updated maintenance window.
CPUExpansion	Exception Event	TencentDB for MySQL instance dimension	No	CPU scale-out is triggered based on the specified threshold.	The instance triggers a CPU performance scale-out when CPU utilization reaches the specified threshold. This scale-out does not impact the instance’s operation.
CPUExpansionFailed	Exception Event	TencentDB for MySQL instance dimension	No	CPU scale-out failure is triggered based on the specified threshold.	The instance fails to scale out CPU performance due to insufficient local resources. A new scale-out attempt will be initiated shortly.
CPUContraction	Exception Event	TencentDB for MySQL instance dimension	No	CPU scale-in is triggered based on the specified threshold.	The instance triggers a CPU performance scale-in when CPU utilization reaches the specified threshold. After the scale-in, monitor whether the current configuration meets the business needs.
Instance rebuilt caused by exception	Exception Event	TencentDB for MySQL instance dimension	No	Instance computing resources are rebuilt due to a database exception.	Instance resources are rebuilt due to an operational failure of the current database. Please assess whether the current database specifications meet business needs; if higher specifications are required, consider upgrading the MySQL configuration.
OverusedReadonlySet	Exception Event	TencentDB for MySQL instance dimension	No	Due to exceeded disk space usage, the database instance is set to a locked status, preventing further data writes or service availability.	1. You can reduce the local binlog retention time to free up some space. 2. Try deleting unnecessary databases and tables to free up space. 3. Scale out the database instance’s disk upper limit.
OverusedReadWriteSet	Exception Event	TencentDB for MySQL instance dimension	No	The database instance is unlocked and resumes full database services.	1. You can reduce the local binlog retention time to free up some space. 2. Try deleting unnecessary databases and tables to free up space. 3. Scale out the database instance’s disk upper limit.
OverusedPreReadonly	Exception Event	TencentDB for MySQL instance dimension	No	Due to exceeded disk space usage, the database instance is about to be locked. Once it is locked, data writes or service availability will be disabled.	1. You can reduce the local binlog retention time to free up some space. 2. Try deleting unnecessary databases and tables to free up space. 3. Scale out the database instance’s disk upper limit.
AuditLowRisk	Exception Event	TencentDB for MySQL instance dimension	No	The audit log has matched a low-risk rule.	Go to the console to view detailed alarm log information and address it based on your business needs. The alarm is triggered because the audit log has matched a low-risk rule.
AuditMediumRisk	Exception Event	TencentDB for MySQL instance dimension	No	The audit log has matched a medium-risk rule.	Go to the console to view detailed alarm log information and address it based on your business needs. The alarm is triggered because the audit log has matched a medium-risk rule.
AuditHighRisk	Exception Event	TencentDB for MySQL instance dimension	No	The audit log has matched a high-risk rule.	Go to the console to view detailed alarm log information and address it based on your business needs. The alarm is triggered because the audit log has matched a high-risk rule.
Console operations (CloudAudit)	Exception Event	Instance Dimension	No	Operation events such as instance addition, deletion, and configuration changes.	Manual troubleshooting.
Cloud API actions (CloudAudit)	Exception Event	Instance Dimension	No	Operation events such as instance addition, deletion, and configuration changes.	Manual troubleshooting.
Mini program operations (CloudAudit)	Exception Event	Instance Dimension	No	Operation events such as instance addition, deletion, and configuration changes.	Manual troubleshooting.
MasterHealthCheckError	Exception Event	TencentDB for MySQL instance dimension	No	The primary instance may be unable to determine the current primary instance node service status as active due to high load, maximum number of connections reached, runtime exceptions, network fluctuations, etc.	The node configurations can be appropriately added to reduce the probability of risk occurrence. 1. If you receive a MasterHealthCheckRecovery event, it means that the primary node has been recovered, HA has been switched to rollback, and no actual HA has occurred. 2. If you receive both Switch and SlaveHealthCheckRecovery events, it indicates that HA switch has occurred and recovery succeeded. 3. If you receive a Switch event but do not receive a SlaveHealthCheckRecovery event, it means that HA has occurred and the original primary instance has been rebuilt.
MasterHealthCheckRecovery	Recovery event	TencentDB for MySQL instance dimension	No	Recovery after the database primary node encounters a service exception.	The service exception (MasterHealthCheckError) on the database primary node has been recovered and is now operating normally.
SlaveHealthCheckError	Exception Event	TencentDB for MySQL instance dimension	No	The secondary instance might be unable to determine the current secondary instance node service status as active due to high load, the maximum number of connections reached, runtime exceptions, and network fluctuations, etc.	Node configurations or the number of read-only nodes can be appropriately increased to reduce the probability of risk occurrence. 1. If you receive SlaveHealthCheckRecovery, it indicates that the secondary node has been recovered. 2. If you have not received SlaveHealthCheckRecovery, it indicates that the secondary node test has timed out and is being rebuilt.
SlaveHealthCheckRecovery	Recovery event	TencentDB for MySQL instance dimension	No	1. Recovery after the database secondary node encounters a service exception. 2. The original primary node is abnormal. After the primary-secondary switchover, the originally abnormal primary node is recovered as the secondary node.	1. The service exception (SlaveHealthCheckError) on the database secondary node has been recovered and is now operating normally. 2. The service exception (MasterHealthCheckError) on the database original primary node has been recovered and is now operating normally.

tencent cloud

Sign Up

Log in

Recent Pages

TencentDB for MySQL

Was this page helpful?

Was this page helpful?