tencent cloud

Tencent Kubernetes Engine

Release Notes and Announcements
Release Notes
Announcements
Release Notes
Product Introduction
Overview
Strengths
Architecture
Scenarios
Features
Concepts
Native Kubernetes Terms
Common High-Risk Operations
Regions and Availability Zones
Service Regions and Service Providers
Open Source Components
Purchase Guide
Purchase Instructions
Purchase a TKE General Cluster
Purchasing Native Nodes
Purchasing a Super Node
Getting Started
Beginner’s Guide
Quickly Creating a Standard Cluster
Examples
Container Application Deployment Check List
Cluster Configuration
General Cluster Overview
Cluster Management
Network Management
Storage Management
Node Management
GPU Resource Management
Remote Terminals
Application Configuration
Workload Management
Service and Configuration Management
Component and Application Management
Auto Scaling
Container Login Methods
Observability Configuration
Ops Observability
Cost Insights and Optimization
Scheduler Configuration
Scheduling Component Overview
Resource Utilization Optimization Scheduling
Business Priority Assurance Scheduling
QoS Awareness Scheduling
Security and Stability
TKE Security Group Settings
Identity Authentication and Authorization
Application Security
Multi-cluster Management
Planned Upgrade
Backup Center
Cloud Native Service Guide
Cloud Service for etcd
TMP
TKE Serverless Cluster Guide
TKE Registered Cluster Guide
Use Cases
Cluster
Serverless Cluster
Scheduling
Security
Service Deployment
Network
Release
Logs
Monitoring
OPS
Terraform
DevOps
Auto Scaling
Containerization
Microservice
Cost Management
Hybrid Cloud
AI
Troubleshooting
Disk Full
High Workload
Memory Fragmentation
Cluster DNS Troubleshooting
Cluster kube-proxy Troubleshooting
Cluster API Server Inaccessibility Troubleshooting
Service and Ingress Inaccessibility Troubleshooting
Common Service & Ingress Errors and Solutions
Engel Ingres appears in Connechtin Reverside
CLB Ingress Creation Error
Troubleshooting for Pod Network Inaccessibility
Pod Status Exception and Handling
Authorizing Tencent Cloud OPS Team for Troubleshooting
CLB Loopback
API Documentation
History
Introduction
API Category
Making API Requests
Elastic Cluster APIs
Resource Reserved Coupon APIs
Cluster APIs
Third-party Node APIs
Relevant APIs for Addon
Network APIs
Node APIs
Node Pool APIs
TKE Edge Cluster APIs
Cloud Native Monitoring APIs
Scaling group APIs
Super Node APIs
Other APIs
Data Types
Error Codes
TKE API 2022-05-01
FAQs
TKE General Cluster
TKE Serverless Cluster
About OPS
Hidden Danger Handling
About Services
Image Repositories
About Remote Terminals
Event FAQs
Resource Management
Service Agreement
TKE Service Level Agreement
TKE Serverless Service Level Agreement
Contact Us
Glossary

Overview of Monitoring and Alarms

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2025-09-25 15:43:51

Overview

A healthy monitoring environment ensures the high reliability, high availability, and high performance of Tencent Cloud Tencent Kubernetes Engine (TKE). You can collect monitoring data of different dimensions for different resources, making it easy to understand every resource’s usage information and locate errors quickly. Tencent Cloud TKE features collection and display of monitoring data at 5 levels: cluster, node, workload, pod, and container. The collection of monitoring data allows you to establish normal standards for cluster performance. By testing performance of a container cluster at different times and under different load conditions, you can better understand the normal performance of a container cluster or service. This allows you to quickly determine if the running status is exceptional based on the current monitoring data, and to find solutions promptly. For example, you can monitor a service’s CPU utilization, memory usage, or disk I/O.

Monitoring

For more information on TKE monitoring, please see Viewing Monitoring Data. For more information on the currently supported monitoring metrics, please see List of Monitoring and Alarm Metrics.

Alarms

We recommend that you set the necessary alarms on all production clusters in order to detect TKE exceptions promptly and ensure the stability and reliability of your business. For more information on setting alarms, please see Setting Alarms.
For more information on the currently supported alarm metrics, please see List of Monitoring and Alarm Metrics.
Note:
TKE monitoring and alarm features primarily cover the core metrics and events of Kubernetes objects. To ensure more fine-grained metric coverage, please use these features in combination with the basic resource monitoring provided by Cloud Monitoring, (e.g. CVM, Cloud Block Storage, Load Balancer, etc.).


Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan