Viewing instance health status
Last updated: 2023-12-27 10:15:26
The MySQL Instance Details page now displays the health status, exception alarms, and configurations related to availability, performance, and security of the instance. This helps users detect anomalies in a timely manner, so that they can optimize system performance and security configurations, and improve the security and stability of instances. This section describes how to view the health status of the instance and related operations on the Instance Details page.
Prerequisites
Viewing Instance Health Status
1. Log in to the TencentDB for MySQL console..
2. In the instance list, click an instance ID or Manage in the Operation column to enter the instance details page.
3. On the right side of the page, you can view the health status of the instance, including the health status score, exception alarm items, and functional configuration deployment status.
Related Operations
Page | Operation |
Instance Details Page | |
| |
| |
| |
1. One-Click Connection Check
If you cannot access a MySQL instance via either the private or public network, the One-Click Connection Check tool can help to troubleshoot the connection issues. Click the Quick Connection Check following the private network address to navigate to the connection check page. For subsequent operations, please refer to One-Click Connection Check Tool.
2. One-Click Diagnosis****
Under the instance health status, the current instance health score is displayed. With a perfect health score of 100, you can promptly know whether the instance is running healthily. This score can be manually refreshed.
Click the Quick Check button following the score to navigate to the DBbrain console's Exception Diagnosis page. This page offers real-time performance monitoring, health checks, failure diagnosis, and optimization suggestions for the user's instance. It enables users to see the real-time operation status of the database instance intuitively, locate newly emerged performance anomalies, and optimize the system based on the optimization suggestions.
For instructions on viewing monitoring information, diagnostic information, etc. on the exception diagnosis page, please refer to Exception Diagnosis.
3. Viewing Alarms
On the instance details page, the Exception Alarm section displays the exception alarms of the instance within the last three hours. Based on the exception alarm prompts, users can acquire detailed information about risk items of different risk levels at a certain stage of the instance. This information helps users make optimizations and adjustments accordingly. The exception alarm items are collected by the Exception Diagnosis feature of DBbrain.
Click View Alarm. A sidebar is displayed, listing exception alarms of different levels associated with the current instance.
Click Alarm Details in the top-right corner to go to the Exception Alarms page of the DBbrain console. Here you can review details such as basic information about the alarmed instance, risk level, diagnostic items, and the duration. For details about the information and operations on the Exception Alarms page, please refer to Exception Alarms.
4. Viewing Configurations
MySQL provides users with configuration details about database functionality from three perspectives: availability, performance, and security. Users can select a category based on their actual requirements and reference the corresponding configurations.
Click View Configuration. A sidebar is displayed, listing detailed configuration information of the database functionality. As shown in the following table:
Availability (The configuration item description is shown based on the availability level.)
Configuration Item | Description | Configuration Level | Operation |
Space | Forecasts whether the remaining space can satisfy the needs for the forthcoming 30 days. | - | |
Momentary Disconnection Prevention | Ensures application continuity without loss during planned detrimental database instance switches and transfers, thus averting connection interruptions. | Enhanced Configuration | |
Multi-AZ Deployment | The multi-AZ deployment feature of MySQL provides your database instance with high availability and failover support. | - | |
Multi-AZ Deployment (Database Proxy) | The Multi-AZ deployment feature of MySQL database proxy offers multi-region failover support for the proxy. | - | |
Three-Node | The three-node mode employs the backup architecture with one primary and two secondary databases, supporting strong synchronous replication method and offering financial-grade reliability and high availability. | Enhanced Configuration | |
Multiple RO Instances RO Group | A single read-only instance is subject to single point failure risks, hence, it's recommended to keep at least two read-only instances within a single RO group to ensure availability. | Mandatory Configuration | |
Multi-AZ RO Instance | Within a single RO group, RO instances can only be deployed in one AZ. To enable cross-AZ deployment, you can create multiple RO groups. | - | |
Disaster Recovery Instance | Helps users in enhancing their cross-region service continuity at a lower cost while simultaneously improving data reliability. | - | |
Cross-Region Backup | Synchronizes backup files to another region, enabling users to enhance their regulatory compliance and disaster recovery capabilities. | - |
Configuration Item | Description | Configuration Level | Operation |
Space | Forecasts whether the remaining space can satisfy the needs for the forthcoming 30 days. | - | |
Momentary Disconnection Prevention | Ensures application continuity without loss during planned detrimental database instance switches and transfers, thus averting connection interruptions. | Enhanced Configuration | |
Multi-AZ Deployment | MySQL's Multi-AZ deployment ensures high availability and failover support for database instances. | Mandatory Configuration | |
Multi-AZ Deployment (Database Proxy) | The Multi-AZ deployment feature of MySQL database proxy offers multi-region failover support for the proxy. | Mandatory Configuration | |
Three-Node | Three-node instances utilize the architecture with one primary and two secondary databases, which can support a strong synchronous replication mode, and providing finance-grade reliability and high availability. | Enhanced Configuration | |
Multiple RO Instances RO Group | A single read-only instance is subject to single point failure risks, hence, it's recommended to keep at least two read-only instances within a single RO group to ensure availability. | Mandatory Configuration | |
Multi-AZ RO Instance | Within a single RO group, RO instances can only be deployed in one AZ. To enable cross-AZ deployment, you can create multiple RO groups. | Mandatory Configuration | |
Disaster Recovery Instance | Helps users in enhancing their cross-region service continuity at a lower cost while simultaneously improving data reliability. | - | |
Cross-Region Backup | Synchronizes backup files to another region, enabling users to enhance their regulatory compliance and disaster recovery capabilities. | - |
Configuration Item | Description | Configuration Level | Operation |
Space | Forecasts whether the remaining space can satisfy the needs for the forthcoming 30 days. | - | |
Momentary Disconnection Prevention | Ensures application continuity without loss during planned detrimental database instance switches and transfers, thus averting connection interruptions. | Enhanced Configuration | |
Multi-AZ Deployment | MySQL's Multi-AZ deployment ensures high availability and failover support for database instances. | Mandatory Configuration | |
Multi-AZ Deployment (Database Proxy) | The Multi-AZ deployment feature of MySQL database proxy offers multi-region failover support for the proxy. | Mandatory Configuration | |
Three-Node | Three-node instances utilize the architecture with one primary and two secondary databases, which can support a strong synchronous replication mode, and providing finance-grade reliability and high availability. | Enhanced Configuration | |
Multiple RO Instances RO Group | A single read-only instance is subject to single point failure risks, hence, it's recommended to keep at least two read-only instances within a single RO group to ensure availability. | Mandatory Configuration | |
Multi-AZ RO Instance | Within a single RO group, RO instances can only be deployed in one AZ. To enable cross-AZ deployment, you can create multiple RO groups. | Mandatory Configuration | |
Disaster Recovery Instance | Helps users in enhancing their cross-region service continuity at a lower cost while simultaneously improving data reliability. | Mandatory Configuration | |
Cross-Region Backup | Synchronizes backup files to another region, enabling users to enhance their regulatory compliance and disaster recovery capabilities. | Enhanced Configuration |
Configuration Item | Description | Configuration Level | Operation |
Space | Forecasts whether the remaining space can satisfy the needs for the forthcoming 30 days. | - | |
Momentary Disconnection Prevention | Ensures application continuity without loss during planned detrimental database instance switches and transfers, thus averting connection interruptions. | Mandatory Configuration | |
Multi-AZ Deployment | MySQL's Multi-AZ deployment ensures high availability and failover support for database instances. | Mandatory Configuration | |
Multi-AZ Deployment (Database Proxy) | The Multi-AZ deployment feature of MySQL database proxy offers multi-region failover support for the proxy. | Mandatory Configuration | |
Three-Node | Three-node instances utilize the architecture with one primary and two secondary databases, which can support a strong synchronous replication mode, and providing finance-grade reliability and high availability. | Mandatory Configuration | |
Multiple RO Instances RO Group | A single read-only instance is subject to single point failure risks, hence, it's recommended to keep at least two read-only instances within a single RO group to ensure availability. | Mandatory Configuration | |
Multi-AZ RO Instance | Within a single RO group, RO instances can only be deployed in one AZ. To enable cross-AZ deployment, you can create multiple RO groups. | Mandatory Configuration | |
Disaster Recovery Instance | Helps users in enhancing their cross-region service continuity at a lower cost while simultaneously improving data reliability. | Mandatory Configuration | |
Cross-Region Backup | Synchronizes backup files to another region, enabling users to enhance their regulatory compliance and disaster recovery capabilities. | Mandatory Configuration |
Performance
Configuration Item | Description | Operation |
Parallel Query | Harnesses multiple computing kernels, significantly reducing the response time for large-scale queries. | |
Asynchronously Dropping Large Tables | The DROP TABLE operation gradually clears the original database file (.ibd) in the background, mitigating the impact on performance. | |
Instant Column Addition | The Instant Column Addition feature enables swift column addition to large tables by solely modifying the data dictionary, minimizing the impact on system. | |
Instant Column Modification | The Instant Column Modification Feature enables swift column modification in large tables by solely modifying the data dictionary, minimizing the impact on system. | - |
Read-Only Instance | Creates Read-Only instances to facilitate read/write segregation and master-replica application scenarios, thereby enhancing the database's read load capacity. | |
CPU Elastic Scaling | Once Auto CPU Elastic Scaling is activated, it effectively guarantees the stability of online operations. | |
Automatic Read/Write Separation | By configuring access strategies for Read/Write Separation through database proxy, you can achieve elastic expansion of reading capability, thereby mitigating database pressure. |
Security
Configuration Item | Description | Operation |
Security Group | Security group is a type of virtual firewall that regulates the inbound and outbound traffic at the instance level, serving as a crucial means for network security isolation. | |
SSL | SSL authentication is the verification process from the client to the cloud database server, which authenticates both the user and the server. | |
Password Complexity | Configures the password complexity to enhance the robustness of the database access passwords, safeguarding the security of your database. | |
Transparent Data Encryption (TDE) | TDE performs encryption and decryption operations transparently to the user, doing so in real-time, and meets the compliance requirements for static data encryption. | |
Latency Read-Only | By setting delay replication and initiating the recovery to a specific time during the delay period, efficient data rollback and rapid fault traceback can be achieved. | |
Backup Encryption | After the Backup Encryption feature is enabled, newly created physical backup files will be automatically encrypted for storage. | |
Download Restrictions on Backups | By default, backup files can be downloaded over a public or private network. Restrictions can be implemented via the download configuration settings. | |
Database Auditing | Records accesses to databases and execution of SQL statements, improving your database security level. |
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No