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 MetricsTKEPod
Pod
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 always required, one of other required dimensions must be passed in, and other dimensions are optional.Namespace
Namespace = QCE/TKE2
Monitoring Metrics
Parameter | Metric | Unit | Dimension | Statistical Period |
K8sPodCpuCoreUsed | CPU usage | Core | Always required dimensions: tke_cluster_instance_id Required dimensions (one of which must be passed in): workload_name, un_instance_id, node Optional dimensions: node_role, workload_kind, namespace, pod_name | 60s, 300s, 3600s, 86400s |
K8sPodMemNoCacheBytes | Memory usage (excluding cache) | MB | Always required dimensions: tke_cluster_instance_id Required dimensions (one of which must be passed in): workload_name, un_instance_id, node Optional dimensions: node_role, workload_kind, namespace, pod_name | 60s,
300s,
3600s,
86400s |
K8sPodNetworkReceivePackets | Network inbound packets | Count/s | Always required dimensions: tke_cluster_instance_id Required dimensions (one of which must be passed in): workload_name, un_instance_id, node Optional dimensions: node_role, workload_kind, namespace, pod_name | 60s, 300s, 3600s, 86400s |
K8sPodRateCpuCoreUsedLimit | CPU utilization (usage/limit) | % | Always required dimensions: tke_cluster_instance_id Required dimensions (one of which must be passed in): workload_name, un_instance_id, node Optional dimensions: node_role, workload_kind, namespace, pod_name | 60s,
300s,
3600s,
86400s |
K8sPodRateMemNoCacheNode | Memory utilization (usage/node, excluding cache) | % | Always required dimensions: tke_cluster_instance_id Required dimensions (one of which must be passed in): workload_name, un_instance_id, node Optional dimensions: node_role, workload_kind, namespace, pod_name | 60s, 300s, 3600s, 86400s |
K8sPodRateMemUsageRequest | Memory usage (usage/request) | % | Always required dimensions: tke_cluster_instance_id Required dimensions (one of which must be passed in): workload_name, un_instance_id, node Optional dimensions: node_role, workload_kind, namespace, pod_name | 60s,
300s,
3600s,
86400s |
K8sPodFsReadBytes | Block device read bandwidth | MB | Always required dimensions: tke_cluster_instance_id Required dimensions (one of which must be passed in): workload_name, un_instance_id, node Optional dimensions: node_role, workload_kind, namespace, pod_name | 60s, 300s, 3600s, 86400s |
K8sPodMemUsageBytes | Memory usage | MB | Always required dimensions: tke_cluster_instance_id Required dimensions (one of which must be passed in): workload_name, un_instance_id, node Optional dimensions: node_role, workload_kind, namespace, pod_name | 60s,
300s,
3600s,
86400s |
K8sPodNetworkTransmitBytes | Network outbound traffic | MB | Always required dimensions: tke_cluster_instance_id Required dimensions (one of which must be passed in): workload_name, un_instance_id, node Optional dimensions: node_role, workload_kind, namespace, pod_name | 60s, 300s, 3600s, 86400s |
K8sPodRateCpuCoreUsedNode | CPU utilization (usage/node) | % | Always required dimensions: tke_cluster_instance_id Required dimensions (one of which must be passed in): workload_name, un_instance_id, node Optional dimensions: node_role, workload_kind, namespace, pod_name | 60s,
300s,
3600s,
86400s |
K8sPodRateMemNoCacheRequest | Memory utilization (usage/request, excluding cache) | % | Always required dimensions: tke_cluster_instance_id Required dimensions (one of which must be passed in): workload_name, un_instance_id, node Optional dimensions: node_role, workload_kind, namespace, pod_name | 60s, 300s, 3600s, 86400s |
K8sPodRestartTotal | Number of Pod restarts | - | Always required dimensions: tke_cluster_instance_id Required dimensions (one of which must be passed in): workload_name, un_instance_id, node Optional dimensions: node_role, workload_kind, namespace, pod_name | 60s,
300s,
3600s,
86400s |
K8sPodFsReadTimes | Number of block device reads | - | Always required dimensions: tke_cluster_instance_id Required dimensions (one of which must be passed in): workload_name, un_instance_id, node Optional dimensions: node_role, workload_kind, namespace, pod_name | 60s, 300s, 3600s, 86400s |
K8sPodNetworkReceiveBytes | Network inbound traffic | MB | Always required dimensions: tke_cluster_instance_id Required dimensions (one of which must be passed in): workload_name, un_instance_id, node Optional dimensions: node_role, workload_kind, namespace, pod_name | 60s,
300s,
3600s,
86400s |
K8sPodNetworkTransmitBytesBw | Network outbound bandwidth | MB/s | Always required dimensions: tke_cluster_instance_id Required dimensions (one of which must be passed in): workload_name, un_instance_id, node Optional dimensions: node_role, workload_kind, namespace, pod_name | 60s, 300s, 3600s, 86400s |
K8sPodRateCpuCoreUsedRequest | CPU utilization (usage/request) | % | Always required dimensions: tke_cluster_instance_id Required dimensions (one of which must be passed in): workload_name, un_instance_id, node Optional dimensions: node_role, workload_kind, namespace, pod_name | 60s,
300s,
3600s,
86400s |
K8sPodRateMemUsageLimit | Memory utilization (usage/limit) | % | Always required dimensions: tke_cluster_instance_id Required dimensions (one of which must be passed in): workload_name, un_instance_id, node Optional dimensions: node_role, workload_kind, namespace, pod_name | 60s, 300s, 3600s, 86400s |
K8sPodStatusReady | Pod_Ready status | - | Always required dimensions: tke_cluster_instance_id Required dimensions (one of which must be passed in): workload_name, un_instance_id, node Optional dimensions: node_role, workload_kind, namespace, pod_name | 60s,
300s,
3600s,
86400s |
K8sPodFsWriteBytes | Block device write bandwidth | MB | Always required dimensions: tke_cluster_instance_id Required dimensions (one of which must be passed in): workload_name, un_instance_id, node Optional dimensions: node_role, workload_kind, namespace, pod_name | 60s, 300s, 3600s, 86400s |
K8sPodNetworkReceiveBytesBw | Inbound bandwidth | MB | Always required dimensions: tke_cluster_instance_id Required dimensions (one of which must be passed in): workload_name, un_instance_id, node Optional dimensions: node_role, workload_kind, namespace, pod_name | 60s,
300s,
3600s,
86400s |
K8sPodNetworkTransmitPackets | Network outbound packets | Count/s | Always required dimensions: tke_cluster_instance_id Required dimensions (one of which must be passed in): workload_name, un_instance_id, node Optional dimensions: node_role, workload_kind, namespace, pod_name | 60s, 300s, 3600s, 86400s |
K8sPodRateMemNoCacheLimit | Memory utilization (usage/limit, excluding cache) | % | Always required dimensions: tke_cluster_instance_id Required dimensions (one of which must be passed in): workload_name, un_instance_id, node Optional dimensions: node_role, workload_kind, namespace, pod_name | 60s,
300s,
3600s,
86400s |
K8sPodRateMemUsageNode | Memory utilization (usage/node) | % | Always required dimensions: tke_cluster_instance_id Required dimensions (one of which must be passed in): workload_name, un_instance_id, node Optional dimensions: node_role, workload_kind, namespace, pod_name | 60s, 300s, 3600s, 86400s |
K8sPodFsWriteTimes | Number of block device writes | - | Always required dimensions: tke_cluster_instance_id Required dimensions (one of which must be passed in): workload_name, un_instance_id, node Optional dimensions: node_role, workload_kind, namespace, pod_name | 60s,
300s,
3600s,
86400s |
K8sPodRateGpuMemoryUsedNode | GPU memory utilization (usage/node) | % | Always required dimensions: tke_cluster_instance_id Required dimensions (one of which must be passed in): workload_name, un_instance_id, node Optional dimensions: node_role, workload_kind, namespace, pod_name | 60s, 300s, 3600s, 86400s |
K8sPodRateGpuMemoryUsedRequest | GPU memory utilization (usage/request) | % | Always required dimensions: tke_cluster_instance_id Required dimensions (one of which must be passed in): workload_name, un_instance_id, node Optional dimensions: node_role, workload_kind, namespace, pod_name | 60s,
300s,
3600s,
86400s |
K8sPodRateGpuUsedNode | GPU utilization (usage/node) | % | Always required dimensions: tke_cluster_instance_id Required dimensions (one of which must be passed in): workload_name, un_instance_id, node Optional dimensions: node_role, workload_kind, namespace, pod_name | 60s, 300s, 3600s, 86400s |
K8sPodRateGpuUsedRequest | GPU utilization (usage/request) | % | Always required dimensions: tke_cluster_instance_id Required dimensions (one of which must be passed in): workload_name, un_instance_id, node Optional dimensions: node_role, workload_kind, namespace, pod_name | 60s,
300s,
3600s,
86400s |
K8sPodGpuMemoryRequestBytes | Number of requested GPU cards | - | Always required dimensions: tke_cluster_instance_id Required dimensions (one of which must be passed in): workload_name, un_instance_id, node Optional dimensions: node_role, workload_kind, namespace, pod_name | 60s, 300s, 3600s, 86400s |
K8sPodGpuMemoryUsedBytes | GPU memory usage | MB | Always required dimensions: tke_cluster_instance_id Required dimensions (one of which must be passed in): workload_name, un_instance_id, node Optional dimensions: node_role, workload_kind, namespace, pod_name | 60s,
300s,
3600s,
86400s |
K8sPodGpuRequest | Number of requested GPU cards | - | Always required dimensions: tke_cluster_instance_id Required dimensions (one of which must be passed in): workload_name, un_instance_id, node Optional dimensions: node_role, workload_kind, namespace, pod_name | 60s, 300s, 3600s, 86400s |
K8sPodGpuUsed | GPU usage | MB | Always required dimensions: tke_cluster_instance_id Required dimensions (one of which must be passed in): workload_name, un_instance_id, node Optional dimensions: node_role, workload_kind, namespace, pod_name | 60s, 300s, 3600s, 86400s |
K8sPodRateCpuCoreUsedResource | CPU utilization | % | Always required dimensions: tke_cluster_instance_id Required dimensions (one of which must be passed in): workload_name, un_instance_id, node Optional dimensions: node_role, workload_kind, namespace, pod_name | 60s,
300s,
3600s,
86400s |
K8sPodRateMemUsageResource | Memory utilization (usage/pod specification) | % | Always required dimensions: tke_cluster_instance_id Required dimensions (one of which must be passed in): workload_name, un_instance_id, node Optional dimensions: node_role, workload_kind, namespace, pod_name | 60s, 300s, 3600s, 86400s |
K8sPodRateMemNoCacheResource | Memory utilization (usage/pod specification, excluding cache) | % | Always required dimensions: tke_cluster_instance_id Required dimensions (one of which must be passed in): workload_name, un_instance_id, node Optional dimensions: node_role, workload_kind, namespace, pod_name | 60s,
300s,
3600s,
86400s |
Statistical Granularity and Time Span
The supported time span varies by statistical granularity. When pulling monitoring data, you should keep in mind 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 |
Dimensions and Parameters
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 | Required (one of which must be passed in) | workload_name | Dimension name of the workload name | Enter a specific workload 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 | node | Dimension name of the node name | Enter a specific workload 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 specific workload 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` |
Conditions.N.Dimensions.N.Name | Optional (zero, one, or multiple of which can be passed in optionally) | workload_kind | Dimension name of the workload type | Enter a specific workload name, such as `workload_kind` |
| Conditions.N.Dimensions.N.Value | workload_kind | Specific workload type | Enter a specific workload name, such as `Deployment` |
| Conditions.N.Dimensions.N.Name | namespace | Dimension name of the namespace | Enter a string-type dimension name, such as `namespace` |
| Conditions.N.Dimensions.N.Value | namespace | Specific namespace | Enter a specific namespace, such as `kube-system` |
| Conditions.N.Dimensions.N.Name | node_role | Dimension name of the cluster | Enter a string-type dimension name, such as `node_role` |
| Conditions.N.Dimensions.N.Value | node_role | Specific node role | Enter a specific node role, such as `node` |
| Conditions.N.Dimensions.N.Name | pod_name | Dimension name of the Pod name | Enter a specific workload name, such as `pod_name` |
| Conditions.N.Dimensions.N.Value | pod_name | Specific Pod name | Enter a specific Pod name, such as `coredns-6ffc45f789-46lpq` |
Input Parameters
In the namespace 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=namespace
&Conditions.N.Dimensions.1.Value=kube-system
In the workload type 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=workload_kind
&Conditions.N.Dimensions.1.Value=Deployment
In the workload name dimension, use the following input parameters:
&Namespace=QCE/TKE
&Conditions.N.Dimensions.0.Name=tke_cluster_instance_id
&Conditions.N.Dimensions.0.Value=cls-fvkxp123
&Conditions.N.Dimensions.1.Name=workload_name
&Conditions.N.Dimensions.1.Value=coredns
In the node role 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_role
&Conditions.N.Dimensions.1.Value=node
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
In the Pod 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=pod_name
&Conditions.N.Dimensions.1.Value=coredns-6ffc45f789-46lpq
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No