alicloud-monitor-controller is a system component of Alibaba Cloud Container Service for Kubernetes (ACK). It connects to Alibaba Cloud observability services, such as Managed Service for Prometheus, Simple Log Service (SLS), and CloudMonitor. The component synchronizes observability configurations, such as alert rule configurations, and manages their lifecycle. This topic describes the alicloud-monitor-controller component, its usage instructions, and change history.
Component description
alicloud-monitor-controller synchronizes observability feature configurations to various Alibaba Cloud observability services. It provides the following features:
Alert configuration management: Provides the alert management for Container Service feature for ACK. This feature lets you flexibly configure alert information.
Rule synchronization: Synchronizes the default alert configurations in the cluster and the alert rules defined in the AckAlertRule CustomResourceDefinition (CRD) to Alibaba Cloud observability services. These services include Managed Service for Prometheus, Simple Log Service (SLS), and CloudMonitor.
Lifecycle management: Provides complete lifecycle management for alert configurations.
To ensure that new configurations are synchronized correctly, the system prompts you to upgrade alicloud-monitor-controller to the latest version when you navigate to the Alert Configuration page.
Usage instructions
For information about how to use the alicloud-monitor-controller component, see Alert management for Container Service.
Change history
July 2025
Version number | Registry Address | Change time | Changes | Impact |
v1.8.8 | registry.{REGION}.aliyuncs.com/acs/alicloud-monitor-controller:v1.8.8-c22ff94-aliyun | July 25, 2025 |
| This upgrade does not affect your services. |
December 2023
Version number | Registry Address | Change time | Changes | Impact |
v1.8.5 | registry.{REGION}.aliyuncs.com/acs/alicloud-monitor-controller:v1.8.5-88ba904-aliyun | December 25, 2023 | Supports automatic configuration of ACK One and registered clusters, and configures default alert rules in different network environments. | This upgrade does not affect your services. |
December 2023
Version number | Registry Address | Change time | Changes | Impact of the change |
v1.8.5 | registry.{REGION}.aliyuncs.com/acs/alicloud-monitor-controller:v1.8.5-88ba904-aliyun | December 25, 2023 | Supports automatic configuration of ACK One and registered clusters, and configures default alert rules in different network environments. | This upgrade does not affect your services. |
August 2023
Version number | Registry Address | Change time | Changes | Impact |
v1.8.4 | registry.{REGION}.aliyuncs.com/acs/alicloud-monitor-controller:v1.8.4-d2d72d6-aliyun | August 14, 2023 |
| This upgrade does not affect your services. |
July 2023
Version number | Registry Address | Change time | Changes | Impact |
v1.8.3 | registry.{REGION}.aliyuncs.com/acs/alicloud-monitor-controller:v1.8.3-d2d72d6-aliyun | July 25, 2023 |
| This upgrade does not affect your services. |
February 2023
Version number | Registry Address | Change time | Changes | Impact |
v1.8.0-7c28347-aliyun | registry.{REGION}.aliyuncs.com/acs/alicloud-monitor-controller:v1.8.0-7c28347-aliyun | February 24, 2023 |
| This upgrade does not affect your services. |
July 2022
Version number | Registry Address | Change time | Changes | Impact |
v1.6.5-2c5c836-aliyun | registry.{REGION}.aliyuncs.com/acs/alicloud-monitor-controller:v1.6.5-2c5c836-aliyun | July 07, 2022 |
| This upgrade does not affect your services. |
April 2022
Version number | Registry Address | Change time | Changes | Impact |
v1.6.1-aa20856-aliyun | registry.{REGION}.aliyuncs.com/acs/alicloud-monitor-controller:v1.6.1-aa20856-aliyun | April 15, 2022 |
| This upgrade does not affect your services. |
March 2022
Version number | Registry Address | Change time | Changes | Impact |
v1.5.15-ed0a4c72-aliyun | registry.{REGION}.aliyuncs.com/acs/alicloud-monitor-controller:v1.5.15-ed0a4c72-aliyun | March 02, 2022 |
| This upgrade does not affect your services. |
November 2021
Version number | Registry Address | Change time | Changes | Impact |
v1.5.13-6990db0e-aliyun | registry.{REGION}.aliyuncs.com/acs/alicloud-monitor-controller:v1.5.13-6990db0e-aliyun | November 04, 2021 | Supports default alerting for basic cluster resources in the Container Service alert center. | This upgrade does not affect your services. |
August 2021
Version number | Registry Address | Change time | Changes | Impact |
v1.5.12-f7aedb4a-aliyun | registry.{REGION}.aliyuncs.com/acs/alicloud-monitor-controller:v1.5.12-f7aedb4a-aliyun | August 23, 2021 | Optimizes the alert configuration feature for Container Service. | This upgrade does not affect your services. |
v1.5.10-a75e4ee2-aliyun | registry.{REGION}.aliyuncs.com/acs/alicloud-monitor-controller:v1.5.10-a75e4ee2-aliyun | August 19, 2021 | Optimizes the alert configuration feature for Container Service. | This upgrade does not affect your services. |
April 2021
Version number | Registry Address | Change time | Changes | Impact |
v1.5.7-e1d5de8a-aliyun | registry.{REGION}.aliyuncs.com/acs/alicloud-monitor-controller:v1.5.7-e1d5de8a-aliyun | April 23, 2021 | Supports event alerting for Container Service, which lets you configure event alerts using a CRD. | This upgrade does not affect your services. |
July 2020
Version number | Registry Address | Change time | Changes | Impact |
v1.4.0-49ff2362-aliyun | registry.{REGION}.aliyuncs.com/acs/alicloud-monitor-controller:v1.4.0-49ff2362-aliyun | July 24, 2020 |
| This upgrade does not affect your services. |
Troubleshooting
No application groups in CloudMonitor
Perform the following prechecks:
Check whether the alicloud-monitor-controller pod in the kube-system namespace is running as expected.
Check the component version. If the version is not the latest, upgrade the component.
Check the component logs for issues such as network timeouts or SDK call errors.
No data in CloudMonitor application groups
Perform the following prechecks.
Check whether the instance names in the application group correspond to the pod names of the application:
If the instance names are abnormal, perform the checks described in the "No application groups in CloudMonitor" section.
If the instance names are normal, check whether the metrics-server pod in the kube-system namespace is running as expected. Check the logs to confirm that they are being generated. The logs are generated as expected if they contain the entry
Successful write 164190 bytes metrics to monitor server.