Help Center/ Cloud Container Engine/ User Guide/ Settings/ Monitoring
Updated on 2025-02-18 GMT+08:00
View PDF
Share

Monitoring

CCE monitors applications and resources and collects metrics and events to analyze application health status. You can choose Settings from the navigation pane, click the Monitoring tab, and change monitoring parameters on the console.

You will need to enable cluster monitoring (Enabling Monitoring Center) to use all monitoring functions.

Monitoring Configuration

Collection configuration

  • Preset Policies: manage monitoring tasks of the Cloud Native Cluster Monitoring add-on in a visualized manner. For details, see Managing Collection Tasks.
  • ServiceMonitor Policies: define the custom metric collection policies for Services. For details, see Managing Collection Tasks.

    For details about how to create a ServiceMonitor, see Method 4: Configuring ServiceMonitor.

  • PodMonitor Policies: define the custom metric collection policies for pods. For details, see Managing Collection Tasks

    For details about how to create a PodMonitor, see Method 3: Configuring PodMonitor.

  • Targets: statuses of the metric collection targets. For details, see Managing Collection Tasks.
  • Default Collection Period: specifies the metric collection period of the Cloud Native Cluster Monitoring add-on. The default value is 15 seconds.
  • Customized indicator collection strategy: After this function is enabled, Cloud Native Cluster Monitoring will collect custom metrics of applications. You need to provide custom metrics of applications based on Prometheus specifications, expose APIs for these metrics, and use the application images to deploy workloads in clusters. Prometheus will collect these metrics through the collection configuration. For details, see Monitoring Custom Metrics Using Cloud Native Cluster Monitoring.

Connect to AOM monitoring service

AOM uses Prometheus for container monitoring. To enable monitoring, you need to select an AOM instance first. With this function enabled, metrics will be reported to the selected AOM instance. Basic container metrics can be monitored for free, but other metrics are billed on a pay-per-use basis. For details about free metrics, see Basic Metrics: Container Metrics.

Access third-party monitoring platforms

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

Log Configuration

Collection configuration

CCE collects, obtains, and analyzes Kubernetes container logs, including standard container output logs, container log files, node logs, and Kubernetes events.

When logs are reported to LTS, a default log group named k8s-logs-{Cluster ID} will be created and will generate costs. For details about LTS pricing, see Price Calculator.

Log Type

View Log

LTS Log Group Name

Status

Reference

Container log

Container standard output

stdout-{Cluster ID}

To enable service log collection, you need to install the Cloud Native Log Collection add-on (Cloud Native Log Collection).

Collecting Container Logs Using Cloud Native Log Collection

Kubernetes event

Kubernetes event

event-{Cluster ID}

To enable service log collection, you need to install the Cloud Native Log Collection add-on (Cloud Native Log Collection).

Collecting Kubernetes Events

Kubernetes audit log

Kubernetes audit log

audit-{Cluster ID}

The option can be enabled separately.

Collecting Kubernetes Audit Logs

Control plane component log

kube-apiserver log

kube-apiserver-{Cluster ID}

The option can be enabled separately.

Collecting Control Plane Component Logs

kube-controller-manager log

kube-controller-manager-{Cluster ID}

The option can be enabled separately.

kube-scheduler log

kube-scheduler-{Cluster ID}

The option can be enabled separately.

Send stdout Logs to AOM 1.0 (No more evolution): Logging in AOM 1.0 has not been improved, so you are advised to disable this function and use LTS logging instead. Sending logs to AOM results in storage fees.

Kubernetes Events Reported 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 click Configure Blocklist to add events that do not need to be reported to the blocklist. You can obtain event names in CCE Events.
  • Normal events: If this option is enabled, normal events will be reported to AOM. The system is pre-configured to report some normal events. If you need to customize the events to be reported, click Configure Trustlist to add the events to the trustlist. You can obtain event names in CCE Events.
Parent Topic: Settings