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 MetricsTKECluster Component
Cluster Component
Last updated: 2024-01-27 17:52:39
Notes
This document is only applicable to the DescribeStatisticData API. For all the following metrics, the
tke_cluster_instance_id dimension is required, while other dimensions are optional.Namespace
Namespace = QCE/TKE2
Monitoring Metrics
Note:
The following four metrics are not supported for managed clusters:
K8sComponentApiserverReady, K8sComponentControllerManagerReady, K8sComponentEtcdReady, and K8sComponentSchedulerReady.Parameter | Metric | Unit | Dimension | Statistical Period |
K8sComponent ApiserverReady | kube-apiserver health status | - | Required dimensions: tke_cluster_instance_id Optional dimensions: node, un_instance_id | 60s, 300s, 3600s, 86400s |
K8sComponentControlle ManagerReady | kube-controller-manager health status | - | Required dimensions: tke_cluster_instance_id Optional dimensions: node, un_instance_id | 60s,
300s,
3600s,
86400s |
K8sComponent EtcdReady | etcd health status | - | Required dimensions: tke_cluster_instance_id Optional dimensions: node, un_instance_id | 60s, 300s, 3600s, 86400s |
K8sComponent SchedulerReady | kube-scheduler health status | - | Required dimensions: tke_cluster_instance_id Optional dimensions: node, un_instance_id | 60s,
300s,
3600s,
86400s |
K8sContainerNet workReceiveBytes | Network inbound traffic | MB/s | Required dimensions: tke_cluster_instance_id, workload_name Optional dimensions: node, un_instance_id. At least three dimensions should be input for this metric | 60s, 300s, 3600s, 86400s |
Overview of Parameters in Each Dimension
Parameter Name | Type | Dimension Name | Description | Format |
Conditions.N.Dimensions.N.Name | Required | tke_cluster_instance_id | Dimension name of the cluster | Enter a string-type dimension name, such as `tke_cluster_instance_id` |
| Conditions.N.Dimensions.N.Value | tke_cluster_instance_id | Specific cluster ID | Enter a specific cluster ID, such as cls-fvkxp123 |
| Conditions.N.Dimensions.N.Name | workload_name | Dimension name of the workload name | Enter a string-type dimension name, such as `workload_name` |
| Conditions.N.Dimensions.N.Value | workload_name | Specific workload name | Enter a specific workload name, such as coredns |
Conditions.N.Dimensions.N.Name | Optional (zero, one, or multiple of which can be passed in optionally) | node | Dimension name of the node name | Enter a string-type dimension name, such as `node` |
| Conditions.N.Dimensions.N.Value | node | Specific node name | Enter a specific node name, such as node |
| Conditions.N.Dimensions.N.Name | un_instance_id | Dimension name of the node ID | Enter a string-type dimension name, such as `un_instance_id` |
| Conditions.N.Dimensions.N.Value | un_instance_id | Specific node ID | Enter a specific node ID, such as ins-nwjhh123 |
Statistical Granularity and Time Span
The supported time span varies by statistical granularity. When pulling monitoring data, you should pay attention to the time span restrictions as detailed below:
Statistical Granularity | Maximum Time Span (End Time - Start Time) |
60s | 12 hours |
300s | 3 days |
3600s | 30 days |
86400s | 186 days |
Input Parameter Description
In the cluster dimension, use the following input parameters:
&Namespace=QCE/TKE2
&Conditions.N.Dimensions.0.Name=tke_cluster_instance_id
&Conditions.N.Dimensions.0.Value=cls-fvkxp123
In the node ID dimension, use the following input parameters:
&Namespace=QCE/TKE2
&Conditions.N.Dimensions.0.Name=tke_cluster_instance_id
&Conditions.N.Dimensions.0.Value=cls-fvkxp123
&Conditions.N.Dimensions.1.Name=un_instance_id
&Conditions.N.Dimensions.1.Value=ins-nwjhh123
In the node name dimension, use the following input parameters:
&Namespace=QCE/TKE2
&Conditions.N.Dimensions.0.Name=tke_cluster_instance_id
&Conditions.N.Dimensions.0.Value=cls-fvkxp123
&Conditions.N.Dimensions.1.Name=node
&Conditions.N.Dimensions.1.Value=node
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No