Restrictions

Dashboards

Dashboards

A maximum of 1,000 dashboards can be created in a region.

Graphs in a dashboard

A maximum of 50 graphs can be added to a dashboard.

Resources in a graph

A maximum of 12 resources can be added to a digit graph. Only one resource can be displayed. By default, the first resource is displayed.

Metrics

Metric storage duration

• Metric data can be stored for up to 30 days.
• ICAgent collects data at an interval of one minute. This interval cannot be changed.

Storage duration of associated metric items

After resources (such as clusters, components, and hosts) are deleted, their metric items can still be stored for up to 30 days.

Metric dimensions

A maximum of 20 dimensions can be configured for a metric.

Metrics queried using the API

A maximum of 20 metrics can be queried at a time.

Statistical period

The maximum statistical period is 1 hour.

Data points returned for a single query

A maximum of 1440 data points can be returned each time.

Custom metric

No restrictions.

Custom metric reported

A single request cannot exceed 40 KB. The timestamp of a reported metric cannot be 10 minutes later than the standard UTC time. In addition, out-of-order metrics are not received. That is, if a metric is reported at a certain time point, the metrics of earlier time points cannot be reported.

Application metric

• When the number of containers on a host exceeds 1,000, the ICAgent stops collecting application metrics and sends the ICAgent Stopped Collecting Application Metrics alarm (ID: 34105).
• When the number of containers on a host within 1,000, the ICAgent resumes the collection of application metrics and the ICAgent Stopped Collecting Application Metrics alarm is cleared.

Job metric

A job automatically exits after it is completed. To monitor metrics of a job, ensure that its survival time is greater than 90s so that the ICAgent can collect its metric data.

Resources consumed by the ICAgent

When the ICAgent collects basic metrics, the resources consumed by the ICAgent are related to the number of containers and processes. On a VM without any services, the ICAgent consumes 30 MB memory and records 1% CPU usage. To ensure collection reliability, ensure that fewer than 1,000 containers run on a single node.

Metric dimension format

Metric dimension tags must comply with the AOM or Prometheus standard format so that the metrics can be reported to AOM.

• AOM standard format: Only letters, digits, and underscores (_) are allowed. Start with a letter or underscore.
• Prometheus standard format: Only ASCII letters, digits, and underscores (_) are allowed. The following regular expression must be met: [a-zA-Z_][a-zA-Z0-9_]*.

Alarm rules

Alarm rules

A maximum of 3,000 alarm rules (including metric alarm rules and event alarm rules) can be created.

Alarm templates

A maximum of 150 alarm templates can be created.

Logs

Restrictions on the log function

For more information, see LTS Usage Restrictions.

Log file

Only text log files can be collected. Other types of log files (for example, binary files) cannot be collected.

The ICAgent can collect a maximum of 20 log files from a volume mounting directory.

The ICAgent can collect a maximum of 1,000 standard container output log files. These files must be in JSON format.

Resources consumed during log file collection

The resources consumed during log file collection are closely related to the log volume, number of files, network bandwidth, and backend service processing capability.

Log discarding

When a single log line exceeds 10,240 bytes, it will be discarded.

Log collection path

Linux

• Collection paths support recursion. You can use double asterisks (**) to collect logs from up to five directory levels. Example: /var/logs/**/a.log
• Collection paths support fuzzy match. You can use an asterisk (*) to represent one or more characters of a directory or file name. Example: /var/logs/*/a.log or /var/logs/service/a*.log
• If the collection path is set to a directory, for example, /var/logs/, only .log, .trace, and .out files in the directory are collected. If the collection path is set to name of a text file, that file is directly collected.
• Each collection path must be unique. That is, the same path of the same host cannot be configured for different log groups and log streams.

Windows

• Collection paths support recursion. You can use double asterisks (**) to collect logs from up to five directory levels. Example: C:\var\service\**\a.log
• Collection paths support fuzzy match. You can use an asterisk (*) to represent one or more characters of a directory or file name. Examples: C:\var\service\*\a.log and C:\var\service\a*.log
• Each collection path must be unique. That is, the same path of the same host cannot be configured for different log groups and log streams.
• Each collection path must be unique. That is, the same path of the same host cannot be configured for different log groups and log streams.

Log repetition

When the ICAgent is restarted, identical data may be collected around the restart time.

Historical logs

The storage duration and prices of log data vary according to editions.

Alarm list

Time range for alarm query

You can query alarms generated within 31 days in the last year.

Time range for event query

You can query events generated within 31 days in the last year.

Application discovery

Application discovery rules

A maximum of 100 application discovery rules can be created.