What Are the Usage Restrictions of AOM?
OS Usage Restrictions
Application Operations Management (AOM) supports multiple operating systems (OSs). When purchasing a host, ensure that it meets the requirements in Table 1. Otherwise, the host cannot be monitored by AOM.
| OS Version | Version | |||||
|---|---|---|---|---|---|---|
| SUSE | SUSE Enterprise 11 SP4 64-bit | SUSE Enterprise 12 SP1 64-bit | SUSE Enterprise 12 SP2 64-bit | SUSE Enterprise 12 SP3 64-bit | ||
| OpenSUSE | 13.2 64-bit | 42.2 64-bit | 15.0 64-bit (Currently, syslog logs cannot be collected.) | |||
| EulerOS | 2.2 64-bit | 2.3 64-bit | ||||
| CentOS | 6.3 64-bit | 6.5 64-bit | 6.8 64-bit | 6.9 64-bit | 6.10 64-bit | |
| 7.1 64-bit | 7.2 64-bit | 7.3 64-bit | 7.4 64-bit | 7.5 64-bit | 7.6 64-bit | |
| Ubuntu | 14.04 server 64-bit | 16.04 server 64-bit | 18.04 server 64-bit | |||
| Fedora | 24 64-bit | 25 64-bit | 29 64-bit | |||
| Debian | 7.5.0 32-bit | 7.5.0 64-bit | 8.2.0 64-bit | 8.8.0 64-bit | 9.0.0 64-bit | |
- For Linux x86_64 servers, AOM supports all the OSs and versions listed in the preceding table.
- For Linux Arm servers, AOM only supports CentOS 7.4 and later versions, and other OSs and versions listed in the preceding table.
Resource Usage Restrictions
When using AOM, pay attention to the restrictions in Table 2. Resource usage restrictions include quota restrictions. For details, see Quotas.
| Category | Object | Usage Restriction |
|---|---|---|
| Dashboard | Dashboard | A maximum of 50 dashboards can be created in one region, for example, CN North-Beijing1. |
| Graphs in a dashboard | A maximum of 20 graphs can be added to a dashboard. | |
| Number of resources, threshold rules, components, or hosts in a graph |
| |
| Metric | Metric data |
|
| Metric items | After resources such as clusters, components, and hosts are deleted, their related metric items can be stored in the database for a maximum of 7 days. | |
| Dimensions | 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 cycle | The maximum statistical cycle is 1 hour. | |
| Data points returned for a single query | A maximum of 1440 data points can be returned each time. | |
| Custom metrics | No restrictions. | |
| Custom metrics to be reported | A maximum of 40 KB data can be reported each time. | |
| Application metrics Job metrics |
A job automatically exits after it is completed. To monitor metrics of a job, ensure that the 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 greatly affected by the number of containers and processes. On a VM without any services, the ICAgent consumes 30 MB memory and 1% CPU usage. To ensure collection reliability, ensure that the number of containers running on a single node must be less than 1000. | |
| Threshold rules (for all regions except CN North-Beijing1 and CN East-Shanghai2) | Threshold rules | A maximum of 1000 threshold rules can be created in a project. |
| Number of topics that can be selected | A maximum of five topics can be selected for each threshold rule. | |
| Threshold rules (for CN North-Beijing1 and CN East-Shanghai2) | Threshold rules |
|
| Threshold templates |
| |
| Number of topics that can be selected | A maximum of five topics can be selected for each threshold rule. | |
| Notification rules | Number of topics that can be selected | A maximum of five topics can be selected for each notification rule. |
| Logs | Size of a log | The maximum size of each log is 10 KB. If a log exceeds 10 KB, the ICAgent does not collect it. In that case, the log will be discarded. |
| Log traffic | A maximum of 10 MB/s is supported for each tenant in a region. If the log traffic exceeds 10 MB/s, logs may be lost. If you require more log traffic, submit a service ticket according to Submitting a Service Ticket. | |
| Historical logs | The storage duration and prices of log data vary according to editions. For details, see AOM Pricing Details. | |
| Log files | Only text log files can be collected. Other types of log files, such as 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 1000 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 loss | ICAgent uses multiple mechanisms to ensure log collection reliability and prevent data loss. However, logs may be lost in the following scenarios:
| |
| Log discarding | When a single log line exceeds 10,240 bytes, the line will be discarded. | |
| Log repetition | When the ICAgent is restarted, identical data may be collected around the restart time. | |
| Alarm center | Alarms | You can query the alarms generated in the last 30 days. |
| Events | You can query the events generated in the last 30 days. |
Did this article solve your problem?
Thank you for your score！Your feedback would help us improve the website.