tencent cloud

Tencent Cloud Observability Platform

Release Notes and Announcements
Release Notes
Product Introduction
Overview
Strengths
Basic Features
Basic Concepts
Use Cases
Use Limits
Purchase Guide
Tencent Cloud Product Monitoring
Application Performance Management
Mobile App Performance Monitoring
Real User Monitoring
Cloud Automated Testing
Prometheus Monitoring
Grafana
EventBridge
PTS
Quick Start
Monitoring Overview
Instance Group
Tencent Cloud Product Monitoring
Application Performance Management
Real User Monitoring
Cloud Automated Testing
Performance Testing Service
Prometheus Getting Started
Grafana
Dashboard Creation
EventBridge
Alarm Service
Cloud Product Monitoring
Tencent Cloud Service Metrics
Operation Guide
CVM Agents
Cloud Product Monitoring Integration with Grafana
Troubleshooting
Practical Tutorial
Application Performance Management
Product Introduction
Access Guide
Operation Guide
Practical Tutorial
Parameter Information
FAQs
Mobile App Performance Monitoring
Overview
Operation Guide
Access Guide
Practical Tutorial
Tencent Cloud Real User Monitoring
Product Introduction
Operation Guide
Connection Guide
FAQs
Cloud Automated Testing
Product Introduction
Operation Guide
FAQs
Performance Testing Service
Overview
Operation Guide
Practice Tutorial
JavaScript API List
FAQs
Prometheus Monitoring
Product Introduction
Access Guide
Operation Guide
Practical Tutorial
Terraform
FAQs
Grafana
Product Introduction
Operation Guide
Guide on Grafana Common Features
FAQs
Dashboard
Overview
Operation Guide
Alarm Management
Console Operation Guide
Troubleshooting
FAQs
EventBridge
Product Introduction
Operation Guide
Practical Tutorial
FAQs
Report Management
FAQs
General
Alarm Service
Concepts
Monitoring Charts
CVM Agents
Dynamic Alarm Threshold
CM Connection to Grafana
Documentation Guide
Related Agreements
Application Performance Management Service Level Agreement
APM Privacy Policy
APM Data Processing And Security Agreement
RUM Service Level Agreement
Mobile Performance Monitoring Service Level Agreement
Cloud Automated Testing Service Level Agreement
Prometheus Service Level Agreement
TCMG Service Level Agreements
PTS Service Level Agreement
PTS Use Limits
Cloud Monitor Service Level Agreement
API Documentation
History
Introduction
API Category
Making API Requests
Monitoring Data Query APIs
Alarm APIs
Legacy Alert APIs
Notification Template APIs
TMP APIs
Grafana Service APIs
Event Center APIs
TencentCloud Managed Service for Prometheus APIs
Monitoring APIs
Data Types
Error Codes
Glossary

Cluster Component

PDF
Focus Mode
Font Size
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

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback