Help Center/ Cloud Container Engine_Autopilot/ User Guide/ Settings/ Monitoring
Updated on 2026-09-15 GMT+08:00
View PDF
Share

Monitoring

CCE Autopilot monitors applications and resources and collects metrics and events to analyze application health. The Monitoring tab allows you to modify parameters for better O&M.

You will need to enable Monitoring Center by referring to Enabling Cluster Monitoring.

Monitoring Settings

Collection Settings

  • Default Collection Period: specifies the metric collection period of the Cloud Native Cluster Monitoring add-on, in seconds. The default value is 15 seconds.
  • Custom Metric Collection: If this function is enabled, metrics collected by Prometheus will be reported through the VPC endpoint of AOM. You need to create VPC endpoints for AOM beforehand. For details, see Creating an AOM Endpoint.
  • Auto Service Discovery (configurable when Custom Metric Collection is enabled): If this function is enabled, application metrics can be automatically collected by annotation. By default, applications in the kube-system and monitoring namespaces are excluded from collection. For details about how to configure automatic collection of annotations, see Configuring Pod Annotations and Configuring Service Annotations.

Connection to AOM

AOM uses Prometheus for container monitoring. To enable monitoring, you need to select an AOM instance first. After you select the option for reporting the monitoring data to AOM, metrics will be reported to the AOM instance you select. Basic container metrics are free, and other metrics are billed on a pay-per-use basis. For details about free metrics, see Basic Container Metrics.

Connection to a Third-Party Monitoring Platform (available when custom metric collection is enabled)

After this function is enabled, Prometheus data can be reported to a third-party monitoring platform. You must obtain the data reporting address and authentication credentials from the third-party platform beforehand. For details, see Reporting Prometheus Monitoring Data to a Third-Party Monitoring Platform.

Log Settings

Collection Settings

CCE Autopilot cluster logs, including container logs and Kubernetes events, are collected. You can quickly query and analyze the collected logs.

A default log group named k8s-logs-{cluster-ID} will be created for CCE Autopilot cluster logs reported to LTS, and you will be billed for log storage on LTS. For details about LTS pricing, see Price Calculator.

Table 1 Cluster logs and events

Item

Log Type

LTS Log Group Name

Status

Reference

Container logs

Container stdout

stdout-{clusterId}

To enable log collection, you need to install the Cloud Native Log Collection add-on by referring to Cloud Native Log Collection.

Collecting Logs

Kubernetes events

Kubernetes events

event-{clusterId}

To enable log collection, you need to install the Cloud Native Log Collection add-on by referring to Cloud Native Log Collection.

Collecting Kubernetes Events

Report Kubernetes Events to AOM

Once the Cluster Native Logging add-on (Cloud Native Log Collection) is installed in a cluster, Kubernetes events are reported to LTS by default, while this feature can be used to report Kubernetes events to AOM.

  • Abnormal events: This option is enabled by default. All abnormal events are reported to AOM. You can configure a blocklist to add events that do not need to be reported to the blocklist. You can query event names in CCE Autopilot Cluster Events.
  • Normal events: If this option is enabled, normal events will be reported to AOM. CCE Autopilot is pre-configured to report some normal events. If you need custom events reporting, configure a trustlist and add the events that need to be reported to the trustlist. You can query event names in CCE Autopilot Cluster Events.
Parent Topic: Settings