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 PlatformApplication Performance ManagementOperation GuideApplication MonitoringContainer Monitoring
Container Monitoring
Last updated: 2025-03-04 22:02:22
For applications deployed in Tencent Kubernetes Engine (TKE), you can associate and query container monitoring data, including events and various monitoring metrics.
Notes:
Container monitoring data is obtained from TKE. Self-built Kubernetes clusters are not supported at present.
The TKE cluster where applications reside must be a resource under the current root account. Therefore, this feature is not supported in cross-account reporting scenarios at present.
Currently, only the applications accessing through OpenTelemetry solutions are supported. SkyWalking solutions are not supported at present.
Prerequisites
For the applications adopting automatic access via tencent-opentelemetry-operator in the TKE environment, you can directly use the container monitoring feature. For the applications adopting other access methods, you need to fill in the required TKE environment information in the instance attributes. The required environment information includes:
Field Name | Description |
k8s.region | The region where the TKE cluster resides, such as ap-guangzhou. For more details, see CVM - Regions and AZs. |
k8s.cluster.id | The ID of the TKE cluster. |
k8s.deployment.name | The Deployment where the application is located. |
k8s.namespace.name | The namespace where the application resides. |
k8s.pod.name | The name of the Pod where the application resides. This variable can only be determined after the Pod is created. You can obtain it through Downward API. |
Directions
1. Log in to the TCOP console.
2. In the left sidebar, select Application Performance Management > Application list. Click the name/ID of the application and select Container monitoring.
3. This page will display the workloads associated with the application, and you can view the monitoring charts of the workload.
4. If multiple instances of the application are distributed across different workloads, please select the workload you want to monitor from the dropdown list.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No