Monitoring and Alarms
Last updated:2025-07-31 16:41:50
The monitoring feature of TDSQL-C 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 TDSQL-C for MySQL console, cloud APIs, and dashboards of Tencent Cloud Observability Platform (TCOP). This document describes the supported monitoring metrics for read-only analysis engine instances.
Prerequisites
A read-only analysis engine instance is prepared. For details, 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 Viewing Monitoring Data.
Note:
Since the monitoring metrics of a read-only analysis engine instance differ from those of a read-write instance and a regular read-only instance, it is not supported to jointly view read-only analysis engine instances, read-write instances, and read-only instances in the same monitoring chart.
Supported Monitoring Metrics
Category | Monitoring Metric (in the Console) | Monitoring Metric (English) | Unit | Data Aggregation Method |
Overall monitoring of the analysis engine | Analysis engine QPS | LibraDBQps | Count/s | max |
| Total number of connections to the analysis engine | LibraDBConnections | Count | max/last |
| Number of error requests of the analysis engine | LibraDBErrorQueries | Count | sum |
| Number of active connections to the analysis engine | LibraDBActiveConnections | Count | max/last |
| Size of the returned result set from the analysis engine | LibraDBResultSize | MBytes | sum |
| Data latency time of the analysis engine | LibraDBLatency | s | max |
| Number of rows processed by the analysis engine per second | LibraDBSinkRowsPerSec | Count/s | max/avg |
| Number of rows written per second during full loading of the analysis engine | LibraDBDumpRowsPerSec | Count/s | max/avg |
| Amount of data written per second during full loading of the analysis engine | LibraDBDumpSizePerSec | MBytes/s | max/avg |
| Average response time of the analysis engine | LibraDBDuration | Ms | avg |
Node monitoring of analysis engine | CPU utilization of the analysis engine | LibraDBCpuUseRate | % | last |
| Storage utilization of the analysis engine | LibraDBMemUseRate | % | last |
| Analysis engine storage utilization | LibraDBStorageUseRate | % | last |
| Analysis engine storage usage | LibraDBStorageUsed | MBytes | last |
| Analysis engine read throughput | LibraDBReadThroughput | MBytes/s | max |
| Analysis engine write throughput | LibraDBWriteThroughput | MBytes/s | max |
| Network inbound traffic of the analysis engine | LibraDBBytesReceived | MBytes | max/avg |
| Network outbound traffic of the analysis engine | LibraDBBytesSent | MBytes | max/avg |
| Number of CompactRowsets of the analysis engine | LibraDBCompactRowsets | Count | last |
| Number of MPP tasks received by the analysis engine | LibraDBMPPTasks | Count | sum |
| Number of MPP tasks being executed by the analysis engine | LibraDBRunningMPPTasks | Count | last |
| Data file size of the analysis engine | LibraDBDatafileSize | MBytes | last |
| Cache usage of the analysis engine | LibraDBCached | MBytes | last |
| Cache hit rate of the analysis engine | LibraDBCacheHitsRate | % | avg |
| Delay time of the analysis engine node | LibraDBNodeLatency | s | max |
| Number of rows processed by the analysis engine node per second | LibraDBNodeSinkRowsPerSec | Count/s | max |
| Number of rows written per second during full loading of the analysis engine node | LibraDBNodeDumpRowsPerSec | Count/s | max |
| Amount of data written per second during full loading of the analysis engine node | LibraDBNodeDumpSizePerSec | MBytes/s | max |
Alarm Settings
The alarm configuration method for read-only analysis engine instances is the same as that for read-write and read-only instances of TDSQL-C for MySQL. For detailed operations, see Alarm Setting Process Overview.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback