Updated on 2024-08-05 GMT+08:00

Restrictions

Resource Monitoring Restrictions

Table 1 Resource monitoring restrictions

Category

Object

Restriction

Dashboard

Dashboard

A maximum of 1000 dashboards can be created in a region.

Graph

A maximum of 30 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.

Metric

Metric data

  • Basic edition: Metric data can be stored for up to 7 days.
  • Professional edition: Metric data can be stored for up to 30 days.

Metric item

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

Dimension

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

Metric query 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

Job metric

  • When the number of containers on a host exceeds 1000, 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 1000, the ICAgent resumes the collection of application metrics and the ICAgent Stopped Collecting Application Metrics alarm is cleared.

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 1000 containers run on a single node.

Alarm rule

Alarm rule

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

Alarm template

A maximum of 150 alarm templates can be created.

Alarm list

Alarms

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

Events

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.

Collection Management restrictions

  • OS Restrictions
    Table 2 OSs and versions supported

    OS

    Version

    EulerOS

    1.1 64-bit

    2.0 64-bit

    CentOS

    7.1 64-bit

    7.2 64-bit

    7.3 64-bit

    7.4 64-bit

    7.5 64-bit

    7.6 64-bit

    7.7 64-bit

    7.8 64-bit

    7.9 64-bit

    8.0 64-bit

    Ubuntu

    16.04 server 64-bit

    18.04 server 64-bit

    20.04 server 64-bit

    22.04 server 64-bit

    • For Linux x86_64 hosts, all the OSs and versions listed in the preceding table are supported.
    • For Linux Arm hosts, CentOS 7.4/7.5/7.6, EulerOS 2.0, and Ubuntu 18.04 are supported.
  • Resource Restrictions
    Table 3 Resource restrictions

    Object

    Restriction

    Agent client

    When the average CPU usage is greater than 50% or the memory is greater than 100 MB for two minutes, the Agent client automatically restarts.

    Agent installation, upgrade, or uninstallation

    You can install, upgrade, or uninstall Agents for a maximum of 100 hosts at a time.

    Host deletion

    You can delete a maximum of 50 hosts with Agents uninstalled at a time.