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:
|
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
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.