Tencent Cloud Observability Platform
- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Application Performance Management
- Pay-as-you-go (Postpaid)
- Packages (Prepaid)
- Mobile App Performance Monitoring
- Real User Monitoring
- Cloud Automated Testing
- Prometheus Monitoring
- Pay-as-You-Go (Postpaid)
- Quick Start
- EventBridge
- Cloud Product Monitoring
- Tencent Cloud Service Metrics
- Microservice
- Networking
- TencentDB
- TencentDB for Redis Monitoring Metrics
- CPM
- CDN And EdgeOne
- Operation Guide
- Cloud Monitoring Overview
- Monitoring View
- CM Connection to Grafana
- Troubleshooting
- Application Performance Management
- Access Guide
- Accessing Go Application
- Accessing Java Application
- Accessing Python Application
- Accessing Node.js Application
- Accessing PHP Application
- Accessing .NET Application
- Operation Guide
- Resource Management
- Application Monitoring
- Application Diagnosis
- Database Call Monitoring
- Access Management
- Alarm Service
- System Configuration
- Associate Logs
- Inject TraceID Into Logs
- Practical Tutorial
- Parameter Information
- APM Data Protocol Standard
- Mobile App Performance Monitoring
- Access Guide
- Android Use Cases
- iOS Use Cases
- Tencent Cloud Real User Monitoring
- Operation Guide
- Application Management
- Access Management
- Resource Tag
- Connection Guide
- Web Use Cases
- Cloud Automated Testing
- Operation Guide
- Creating Test Task
- Testing Statistics
- Access Management
- References
- Testing Nodes
- FAQs
- Performance Testing Service
- Operation Guide
- Performance Testing in Script Mode
- Script Examples
- HTTP-based Performance Testing
- Performance Testing in JMeter Mode
- Project Management
- Scenario Management
- Advanced Configuration
- Export Stress Test Indicators
- Traffic Recording
- Performance Testing Report
- Access Control
- Alarm Management
- Tag Management
- Practice Tutorial
- JavaScript API List
- pts/http
- Response
- pts/dataset
- pts/grpc
- pts/jsonpath
- pts/redis
- pts/url
- URL
- pts/util
- pts/ws
- pts/socketio
- socketio
- pts/socket
- Prometheus Monitoring
- Product Introduction
- Access Guide
- EMR Integration
- Java Application Integration
- Exporter Integration
- Operation Guide
- Instance
- Recording Rule
- Alerting Rule
- Access Control
- TKE Metrics
- Practical Tutorial
- Terraform
- Grafana
- Operation Guide
- Instance
- Tencent Cloud Service Integration
- Plugin Management
- Dashboard
- Operation Guide
- Configuring Dashboard
- Monitoring Charts
- Creating Chart
- Use Cases of Different Chart Types
- Alarm Management
- Console Operation Guide
- Alarm Policy
- Configuring alert trigger conditions
- Alarm Notification
- Alarm Callback
- Alarm Receiving Channels and SMS Quota
- Dynamic Threshold Alarm
- Silencing Alarm
- EventBridge
- Product Introduction
- Practical Tutorial
- Migrating Event Alarm
- FAQs
- Related Agreements
- API Documentation
- Making API Requests
- Monitoring Data Query APIs
- Alarm APIs
- Notification Template APIs
- Legacy Alert APIs
- Prometheus Service APIs
- Grafana Service APIs
- Event Center APIs
- TencentCloud Managed Service for Prometheus APIs
- Monitoring APIs
DocumentationTencent Cloud Observability PlatformCloud Product MonitoringTencent Cloud Service Metrics TencentDBTencentDB for MariaDB Monitoring MetricsInstance
Instance
Last updated: 2024-01-27 17:44:48
Namespace
Namespace=QCE/MARIADB
Monitoring Metrics
Metric | Meaning | Description | Unit | Dimension | Statistical Periods |
ActiveThreadCount | Number of active threads | Instance-level metric, which is the sum of active threads in the thread pools of the primary and replica nodes | Threads | InstanceId | 60s, 300s, 3600s, 86400s |
BinlogDiskAvailable | Available binlog disk space | Instance-level metric, whose value is the smallest available binlog disk space in the instance's primary and replica nodes | GB | InstanceId | 60s, 300s, 3600s, 86400s |
BinlogUsedDisk | Used binlog disk space | Instance-level metric, whose value is the binlog disk space used in the instance's primary node | GB | InstanceId | 60s, 300s, 3600s, 86400s |
ConnUsageRate | Connection usage | Instance-level metric, whose value is the highest connection usage among the instance's primary and replica nodes | % | InstanceId | 60s, 300s, 3600s, 86400s |
CpuUsageRate | CPU usage | Instance-level metric, whose value is the CPU usage of the instance's primary node | % | InstanceId | 60s, 300s, 3600s, 86400s |
DataDiskAvailable | Available data disk space | Instance-level metric, whose value is the available data disk space in the instance's primary node | GB | InstanceId | 60s, 300s, 3600s, 86400s |
DataDiskUsedRate | Data disk usage | Instance-level metric, whose value is that of the `DataDiskUsedRateNode` metric of the instance's primary node | % | InstanceId | 60s, 300s, 3600s, 86400s |
DeleteTotal | Number of DELETE queries | Instance-level metric, whose value is the number of DELETE queries executed in the instance's primary node | Queries/sec | InstanceId | 60s, 300s, 3600s, 86400s |
IOUsageRate | IO usage | Instance-level metric, whose value is the IO usage of the instance's primary node | % | InstanceId | 60s, 300s, 3600s, 86400s |
InnodbBufferPoolReads | Number of InnoDB disk page reads | Instance-level metric, which is the sum of InnoDB disk page reads in the instance's primary and replica nodes | Times | InstanceId | 60s, 300s, 3600s, 86400s |
InnodbBufferPoolReadAhead | Page read-ahead count of the InnoDB buffer pool | Instance-level metric, which is the sum of page read-aheads in the InnoDB buffer pool in the instance's primary and replica nodes | Times | InstanceId | 60s, 300s, 3600s, 86400s |
InnodbBufferPoolReadRequests | Page read count of the InnoDB buffer pool | Instance-level metric, which is the sum of page reads in the InnoDB buffer pool in the instance's primary and replica nodes | Times | InstanceId | 60s, 300s, 3600s, 86400s |
InnodbRowsDeleted | Number of rows deleted by InnoDB | Instance-level metric, whose value is the number of rows deleted by InnoDB in the instance's primary node | Row | InstanceId | 60s, 300s, 3600s, 86400s |
InnodbRowsInserted | Number of rows inserted by InnoDB | Instance-level metric, whose value is the number of rows inserted by InnoDB in the instance's primary node | Rows | InstanceId | 60s, 300s, 3600s, 86400s |
InnodbRowsRead | Number of rows read by InnoDB | Instance-level metric, which is the sum of rows read by InnoDB in the instance's primary and replica nodes | Rows | InstanceId | 60s, 300s, 3600s, 86400s |
InnodbRowsUpdated | Number of rows updated by InnoDB | Instance-level metric, whose value is the number of rows updated by InnoDB in the instance's primary node | Rows | InstanceId | 60s, 300s, 3600s, 86400s |
InsertTotal | Number of INSERT queries | Instance-level metric, whose value is the number of INSERT queries executed in the instance's primary node | Queries/sec | InstanceId | 60s, 300s, 3600s, 86400s |
LongQueryCount | Number of slow queries | Instance-level metric, whose value is the number of slow queries executed in the instance's primary node | Queries | InstanceId | 60s, 300s, 3600s, 86400s |
MemAvailable | Available memory | Instance-level metric, whose value is the available memory in the instance's primary node | GB | InstanceId | 60s, 300s, 3600s, 86400s |
MemHitRate | Cache hit ratio | Instance-level metric, whose value is the cache hit ratio in the instance's primary node | % | InstanceId | 60s, 300s, 3600s, 86400s |
ReplaceSelectTotal | Number of REPLACE_SELECT queries | Instance-level metric, whose value is the number of REPLACE-SELECT queries executed in the instance's primary node | Queries/sec | InstanceId | 60s, 300s, 3600s, 86400s |
ReplaceTotal | Number of REPLACE queries | Instance-level metric, whose value is the number of REPLACE queries executed in the instance's primary node | Queries/sec | InstanceId | 60s, 300s, 3600s, 86400s |
RequestTotal | Total queries | Instance-level metric, whose value is the total number of queries executed in the instance's primary node plus the number of SELECT queries executed in the replica nodes | Queries/sec | InstanceId | 60s, 300s, 3600s, 86400s |
SelectTotal | Number of SELECT queries | Instance-level metric, which is the sum of SELECT queries executed in the instance's primary and replica nodes | Queries/sec | InstanceId | 60s, 300s, 3600s, 86400s |
SlaveDelay | Primary-replica synchronization delay | Instance-level metric, whose value is the shortest primary-replica synchronization delay among all the instance’s replica nodes | Sec | InstanceId | 60s, 300s, 3600s, 86400s |
UpdateTotal | Number of UPDATE queries | Instance-level metric, whose value is the number of UPDATE queries executed in the instance's primary node | Queries/sec | InstanceId | 60s, 300s, 3600s, 86400s |
ThreadsConnected | Number of threads currently connected | Instance-level metric, whose value is the sum of threads currently connected in the instance’s primary and replica nodes | Threads | InstanceId | 60s, 300s, 3600s, 86400s |
ConnMax | Maximum number of connections | Instance-level metric, whose value is the sum of the maximum number of connections of the instance’s primary and replica nodes | Connections | InstanceId | 60s, 300s, 3600s, 86400s |
ClientConnTotal | Number of client connections | Instance-level metric, which is the sum of connections in the instance’s proxy. This metric represents the actual number of clients connected to the database instance. | Connections | InstanceId | 60s, 300s, 3600s, 86400s |
SQLTotal | Total number of SQL queries | Instance-level metric, which represents the number of SQL queries sent to the instance | Queries | InstanceId | 60s, 300s, 3600s, 86400s |
ErrorSQLTotal | SQL error count | Instance-level metric, which represents the number of queries with execution errors | Queries | InstanceId | 60s, 300s, 3600s, 86400s |
SuccessSQLTotal | Number of successful SQL queries | Instance-level metric, which represents the number of SQL queries executed successfully | Queries | InstanceId | 60s, 300s, 3600s, 86400s |
TimeRange0 | Number of queries that take shorter than 5 ms to execute | Instance-level metric, which represents the number of queries that take shorter than 5 ms to execute | Queries/sec | InstanceId | 60s, 300s, 3600s, 86400s |
TimeRange1 | Number of queries that take 5-20 ms to execute | Instance-level metric, which represents the number of queries that take 5-20 ms to execute | Queries/sec | InstanceId | 60s, 300s, 3600s, 86400s |
TimeRange2 | Number of queries that take 20-30 ms to execute | Instance-level metric, which represents the number of queries that take 20-30 ms to execute | Queries/sec | InstanceId | 60s, 300s, 3600s, 86400s |
TimeRange3 | Number of queries that take longer than 30 ms to execute | Instance-level metric, which represents the number of queries that take longer than 30 ms to execute | Queries/sec | InstanceId | 60s, 300s, 3600s, 86400s |
MasterSwitchedTotal | Number of primary node switchovers | Instance-level metric, which represents the number of times the primary node is switched | Times | InstanceId | 60s, 300s, 3600s, 86400s |
Note:
Statistical periods (period) may vary from metric to metric. You can get the periods different metrics support by calling the
DescribeBaseMetrics API.Dimensions and Parameters
Parameter | Dimension Name | Dimension Description | Format |
Instances.N.Dimensions.0.Name | instanceId | Dimension name of the instance ID | Enter a string-type dimension name: InstanceId |
Instances.N.Dimensions.0.Value | InstanceId | Instance ID | Enter an instance ID, e.g. tdsql-9kjauqq1 |
Input Parameters
To query the instance-level monitoring metrics of TencentDB for MariaDB, use the following input parameters:
&Namespace=QCE/MARIADB
&Instances.N.Dimensions.0.Name=
InstanceId
&Instances.N.Dimensions.0.Value=ID of the instanceWas this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No