Monitoring and Alarms
Last updated: 2025-08-14 11:34:34
The monitoring feature of TencentDB for MySQL allows you to view the complete running information on read-only analysis engine instances. You can view monitoring metrics through multiple methods, such as the console, cloud APIs, and dashboards of Tencent Cloud Observability Platform (TCOP). This document describes the supported monitoring metrics and alarm settings for read-only analysis engine instances.
Prerequisites
You have prepared a read-only analysis engine instance. See Enabling Read-Only Analysis Engine.
The instance is running.
Viewing Monitoring Data
The operation method of viewing monitoring metrics of read-only analysis engine instances is basically the same as that of TXSQL engine instances. For detailed operations, see Monitoring.
Supported Monitoring Metrics
Category | Monitoring Metric (Name Displayed in Console) | Monitoring Metric (English) | Unit | Data Aggregation Method |
Overview monitoring of analysis engine | QPS | LibraDBQps | Count/s | max |
| Total number of connections | LibraDBConnections | Count | max/last |
| Error Requests | LibraDBErrorQueries | Count | sum |
| Number of Active Connections | LibraDBActiveConnections | Count | max/last |
| Size of the returned result set | LibraDBResultSize | MBytes | sum |
| Data Latency Time | LibraDBLatency | s | max |
| Number of rows processed per second | LibraDBSinkRowsPerSec | Count/s | max/avg |
| Number of rows written per second during full load | LibraDBDumpRowsPerSec | Count/s | max/avg |
| Amount of data written per second during full load | LibraDBDumpSizePerSec | MBytes/s | max/avg |
| Average Response Time | LibraDBDuration | Ms | avg |
Node monitoring of analysis engine | CPU Utilization | LibraDBCpuUseRate | % | last |
| Memory usage | LibraDBMemUseRate | % | last |
| Storage Usage | LibraDBStorageUseRate | % | last |
| Storage usage | LibraDBStorageUsed | MBytes | last |
| Read throughput | LibraDBReadThroughput | MBytes/s | max |
| Write throughput | LibraDBWriteThroughput | MBytes/s | max |
| Network inbound traffic | LibraDBBytesReceived | MBytes | max/avg |
| Network outbound traffic | LibraDBBytesSent | MBytes | max/avg |
| CompactRowset count | LibraDBCompactRowsets | Count | last |
| Number of received MPP tasks | LibraDBMPPTasks | Count | sum |
| Number of ongoing MPP tasks | LibraDBRunningMPPTasks | Count | last |
| Size of data files | LibraDBDatafileSize | MBytes | last |
| Cache usage | LibraDBCached | MBytes | last |
| Cache hit rate | LibraDBCacheHitsRate | % | avg |
| Node delay time | LibraDBNodeLatency | s | max |
| Number of rows processed by node per second | LibraDBNodeSinkRowsPerSec | Count/s | max |
| Number of rows written per second during full load of node | LibraDBNodeDumpRowsPerSec | Count/s | max |
| Amount of data written per second during full load of node | LibraDBNodeDumpSizePerSec | MBytes/s | max |
Alarm Settings
The alarm configuration method for read-only analysis engine instances is the same as that for source and read-only instances of TencentDB for MySQL. For detailed operations, see Alarm Policies (TCOP).
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback