- Function Overview
- Product Bulletin
- Service Overview
- Billing
- Getting Started
-
User Guide
- Clusters
- Workloads
- Network
- Storage
- O&M
- Namespaces
- ConfigMaps and Secrets
- Auto Scaling
- Add-ons
- Helm Chart
- Permissions
- Settings
- Best Practices
-
API Reference
- Before You Start
- API Overview
- Calling APIs
-
APIs
- Autopilot Cluster Management
- Add-on Management for Autopilot Clusters
-
Autopilot Cluster Upgrade
- Upgrading a Cluster
- Obtaining Cluster Upgrade Task Details
- Retrying a Cluster Upgrade Task
- Obtaining a List of Cluster Upgrade Task Details
- Performing a Pre-upgrade Check for a Cluster
- Obtaining Details About a Pre-upgrade Check Task of a Cluster
- Obtaining a List of Pre-upgrade Check Tasks of a Cluster
- Performing a Post-upgrade Check for a Cluster
- Backing Up a Cluster
- Obtaining a List of Cluster Backup Task Details
- Obtaining the Cluster Upgrade Information
- Obtaining a Cluster Upgrade Path
- Obtaining the Configuration of Cluster Upgrade Feature Gates
- Enabling the Cluster Upgrade Process Booting Task
- Obtaining a List of Upgrade Workflows
- Obtaining Details About a Specified Cluster Upgrade Booting Task
- Updating the Status of a Specified Cluster Upgrade Booting Task
- Quota Management for Autopilot Clusters
- Tag Management for Autopilot Clusters
-
Chart Management for Autopilot Clusters
- Uploading a Chart
- Obtaining a Chart List
- Obtaining a Release List
- Creating a Release
- Updating a Chart
- Deleting a Chart
- Updating a Release
- Obtaining a Chart
- Deleting a Release
- Obtaining a Release
- Downloading a Chart
- Obtaining Chart Values
- Obtaining Historical Records of a Release
- Obtaining the Quota of a User Chart
- Kubernetes APIs
- Permissions and Supported Actions
- Appendix
-
FAQs
- Billing
- Workloads
- Network Management
-
Storage
- Can PVs of the EVS Type in a CCE Autopilot Cluster Be Restored After They Are Deleted or Expire?
- What Can I Do If a Storage Volume Fails to Be Created?
- Can CCE Autopilot PVCs Detect Underlying Storage Faults?
- How Can I Delete the Underlying Storage If It Remains After a Dynamically Created PVC is Deleted?
- Permissions
- General Reference
Copied.
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 Configuration
Collection Configuration
Default Collection Period: specifies the metric collection period of the Cloud Native Cluster Monitoring add-on. The default value is 15 seconds.
Interconnection with 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.
Log Configuration
Collection Configuration
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.
Item |
Log Type |
LTS Log Group Name |
Status |
Reference |
---|---|---|---|---|
Container logs |
Container standard output |
stdout-{clusterId} |
To enable log collection, you need to install the Cloud Native Log Collection add-on by referring to Cloud Native Log Collection. |
|
Kubernetes events |
Kubernetes events |
event-{clusterId} |
To enable event collection, you need to install the Cloud Native Log Collection add-on by referring to Cloud Native Log Collection. |
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 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.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot