This topic describes the limits for CloudMonitor Basic and Hybrid Cloud Monitoring.
CloudMonitor Basic
Feature | Limit | Maximum |
Alert rules | The number of alert rules that can be created for an Alibaba Cloud account. | 10,000 |
Application groups | The number of tags that can be added to an application group created from tags for an Alibaba Cloud account in a region. | 100 |
The number of resources of each type that can be included in an application group for an Alibaba Cloud account. | 3,000 | |
The number of application groups that can be created for an Alibaba Cloud account. | 20,000 | |
The number of availability monitoring tasks that can be created in an application group for an Alibaba Cloud account. | 500 | |
The number of dynamic rules that can be created for an Alibaba Cloud account. | 1,200 | |
Host monitoring | The number of non-Alibaba Cloud hosts that can be managed by an Alibaba Cloud account. | 15,000 |
Storage duration | The storage duration of monitoring data for cloud services depends on the statistical period (Period). A longer period results in sparser data queries and a longer storage duration. The relationship is as follows:
|
Hybrid Cloud Monitoring
Feature | Limit | Maximum |
Metric store | The number of metric stores that can be created for an Alibaba Cloud account. | 30 |
The number of ECS instances that can be managed in a metric store for an Alibaba Cloud account. | 10,000 | |
Resource usage report | The number of alert contact groups that can be set for a resource usage report task for an Alibaba Cloud account. | 5 |
SLS Log Monitoring | The number of Logstore groups that can be created for an Alibaba Cloud account. | 20 |
The number of Logstores that can be added to a Logstore group for an Alibaba Cloud account. | 25 | |
Alert rules | The number of Prometheus Query Language (PromQL) alert rules that can be created for an Alibaba Cloud account. | 20 |
Intelligent detection | The number of resources that can be added to an intelligent detection task. | 100 |
Prometheus service limits
V2 instances are those stored in the Metricstores of your Simple Log Service projects starting 00:00:00 (UTC+8) on March 12, 2025. To understand legacy V1 instance limits, see Service limits (Legacy, not applicable to Prometheus V2 instances).
Type | Limit | Default quota | Processing limitations |
Data read and write limits | For more information, see the Simple Log Service (SLS) data read and write limits. | ||
Query and analysis limits | For more information, see the Simple Log Service (SLS) MetricStore MetricStore limits. | ||
Data collection and reporting | Maximum number of data points that a single-replica agent with default configurations (3 cores and 4 GB of memory) can collect at a time | 3.5 million | Scale out the replicas. |
Maximum number of targets that a single-replica agent with default configurations (3 cores and 4 GB of memory) can collect | 5,000 | Scale out the replicas. | |
Maximum number of data points that a single target can collect within 30 seconds | 600,000 | Scale out the replicas. | |
Maximum number of replicas for an agent with Horizontal Pod Autoscaler (HPA) enabled | 20 | If the limit is exceeded, you can manually increase the number of replicas in the console. For more information, see Agent auto scaling. | |
Supported ACK cluster versions for the agent | The latest agent (V3.2.1 or later) only supports Kubernetes clusters that are version 1.16 or later. | Upgrade your Kubernetes version. | |
Maximum data volume that a single target can collect | 512 MB | This limit cannot be changed. If the limit is exceeded, all data is discarded. | |
Others | Maximum number of recording rules for a single cluster | 1,000 | Exceeding this limit is allowed, but it may cause calculation delays. |
Maximum number of folders that can be created for each tenant in the shared edition of Grafana | 250 | Upgrade to the Expert Edition of Grafana. | |