This section describes how to install an ICAgent on an ECS and monitor its resources on the AOM console.
Prerequisites
- You have created an ECS.
- You have obtained an AK/SK.
- The time of the local browser must be consistent with that of the ECS.
Installing an ICAgent
- Log in to the AOM console. In the navigation pane, choose Configuration Management > Agent Management.
- Select Other: custom hosts, and click Install ICAgent.
- On the page that is displayed, enter an AK/SK to generate an ICAgent installation command, and click Copy Command to copy the command for further use in 5.-
Ensure that the AK/SK are correct. Otherwise, the ICAgent cannot be installed.
- - Log in to the ECS remotely.
Specifically, log in to the ECS console, click Remote Login in the Operation column of the target ECS, and then log in to the ECS as the root user.
- - Run the ICAgent installation command.
On the ECS page, click Copy & Paste. On the page that is displayed, press Ctrl+V to paste the ICAgent installation command obtained in 3, and click Send to send the command to the CLI, as shown in the following figure. In the CLI, press Enter to run the ICAgent installation command.
-If the message "ICAgent install success" is displayed, the ICAgent is successfully installed in the /opt/oss/servicemgr/ directory. After a while, return to the Agent Management page, select Other: custom hosts, and check whether the ICAgent status of the ECS is Running.- If the ICAgent status is Running, the ICAgent is successfully installed.
- If the ICAgent status is Offline, view details. The AK/SK or ECS agency may be incorrect. In this case, obtain the correct AK/SK or reconfigure the ECS agency, and then reinstall the ICAgent.
Installing an ICAgent
- Log in to the AOM console. In the navigation pane, choose Configuration Management > Agent Management.
- Select Other: custom hosts, and click Install ICAgent.
- Click Copy Command to copy the installation command.
- Log in to the ECS remotely.
Specifically, log in to the ECS console, click Remote Login in the Operation column of the target ECS, and then log in to the ECS as the root user.
+ - Run the ICAgent installation command.
On the ECS page, click Copy & Paste. On the page that is displayed, press Ctrl+V to paste the ICAgent installation command obtained in 3, and click Send to send the command to the CLI, as shown in the following figure. In the CLI, press Enter to run the ICAgent installation command.
+If the message "ICAgent install success" is displayed, the ICAgent is successfully installed in the /opt/oss/servicemgr/ directory. Wait for a while and go back to the Agent Management page to check whether the ICAgent status of the ECS is Running.- If the ICAgent status is Running, the ICAgent is successfully installed.
- If the ICAgent status is Offline, view details. The AK/SK or ECS agency may be incorrect. In this case, obtain the correct AK/SK or reconfigure the ECS agency, and then reinstall the ICAgent.
- On the AOM console, monitor the ECS.
After the ICAgent is installed, wait for about 1–2 minutes. Then, in the navigation pane, choose Overview > O&M to monitor the ECS.
Set the full-screen online duration
- Select the target dashboard and click
in the upper right corner of the Dashboard page. - In the dialogue box that is displayed, set the full-screen online duration.Figure 8 Setting the online duration-
NOTE:- Custom: The default online duration is 1 hour. You can enter 1–24 (unit: hour) in the text box.
For example, if you enter 2 in the text box, the login page is automatically displayed 2 hours later.
+- Select the target dashboard and click in the upper right corner of the Dashboard page.
- In the dialogue box that is displayed, set the full-screen online duration.NOTE:
- Custom: The default online duration is 1 hour. You can enter 1–24 (unit: hour) in the text box.
For example, if you enter 2 in the text box, the login page is automatically displayed 2 hours later.
- Always online: The full-screen online duration is not restricted. That is, you can always implement full-screen monitoring and the login page will never be displayed.
- Rotation Period: Set Rotation Period and Dashboard if rotation display is enabled. Range: 10s (default) to 120s.
- Custom: The default online duration is 1 hour. You can enter 1–24 (unit: hour) in the text box.
- Click OK to enter the full-screen mode.
Edit
Choose Edit, Copy, Delete, and View Larger (only a line graph can be enlarged) from the Operation column. The Time Select option is available only in a line graph. This option allows you to set a temporary time range and statistical cycle so that you can view the resource data within a specified time range.
-Figure 9 Operations on a graph
NOTE:In the dashboard, when resources such as hosts and components are deleted, graphs created for these resources are not automatically deleted. To improve system performance, manually delete unnecessary graphs.
In the host list, click Add alias in the Operation column.
- Adding a tag
A tag is the identifier of a host. You can manage and classify hosts by tag. After a tag is added, you can quickly identify, select, or search for a host.
In the host list, choose More > Add tags in the Operation column, enter a tag, and click
-
and OK to add a tag. The Tags column of the host list is hidden by default. You can click 
in the upper right corner and select or deselect Tags to show or hide tags.- Synchronizing host data
In the host list, locate the target host and choose More > Sync Host Data in the Operation column to synchronize host data.
+- Synchronizing host data
In the host list, locate the target host and choose More > Sync Host Data in the Operation column to synchronize host data.
- Set filter criteria to search for the desired host.
diff --git a/docs/aom/umn/aom_02_0012.html b/docs/aom/umn/aom_02_0012.html index a88e7e34..3e01312a 100644 --- a/docs/aom/umn/aom_02_0012.html +++ b/docs/aom/umn/aom_02_0012.html @@ -1,7 +1,7 @@ Hosts cannot be searched by alias.
Installing an ICAgent
-ICAgent is used to collect metrics, logs, and application performance data. For servers that are directly purchased on the Elastic Cloud Server (ECS) or Bare Metal Server (BMS) console, manually install an ICAgent. For hosts purchased through Cloud Container Engine (CCE), an ICAgent is automatically installed.
+ICAgents collect metrics, logs, and application performance data in real time. For hosts purchased from the ECS or BMS console, you need to manually install the ICAgent. For hosts purchased from the CCE console, the ICAgent is automatically installed.
@@ -85,15 +85,15 @@ AOM and LTS use the same ICAgent functions. All metric data collected by ICAgents will be reported to AOM for analysis and processing. However, for logs, only those matching the latest log collection configuration in the system will be collected.
For example, if you configure log collection paths in AOM for ECSs, the previous LTS collection configurations of all ECSs under the resource set become invalid.
Initial Installation
After you apply for a server and install an ICAgent for the first time, perform the following operations:
- Obtain an Access Key ID/Secret Access Key (AK/SK).
- If you have obtained the AK/SK, skip this step.
- If you have not obtained an AK/SK, obtain them first.
- In the navigation pane, choose Configuration Management > Agent Management.
- Select Other: custom hosts, click Install ICAgent.
- (Optional) To prevent your AK/SK from being disclosed, select the check box shown in the following figure to disable historical record collection.Figure 1 Copying the ICAgent installation command-
- Generate the ICAgent installation command, and copy and run it to install an ICAgent.
- After the ICAgent is installed, run the following command to enable historical record collection:set -o history
- If the message ICAgent install success is displayed, the ICAgent has been installed in the /opt/oss/servicemgr/ directory. After the ICAgent has been installed, choose Configuration Management > Agent Management to view the ICAgent status.
- If the ICAgent fails to be installed, uninstall the ICAgent according to Uninstalling the ICAgent by Logging In to the Server and then install it again. If the problem persists, contact technical support.
- In the navigation pane, choose Configuration Management > Agent Management.
- Select Other: custom hosts, and click Install ICAgent.
- Click Copy Command to copy the installation command.
- Use a remote login tool to log in to the target server as the root user, and run the following command to disable historical record collection:
set +o history
+- Run the copied installation command and enter the obtained AK and SK as prompted.
- After the ICAgent is installed, run the following command to enable historical record collection:
set -o history - If the message ICAgent install success is displayed, the ICAgent has been installed in the /opt/oss/servicemgr/ directory. After the ICAgent has been installed, choose Configuration Management > Agent Management to view the ICAgent status.
- If the ICAgent fails to be installed, uninstall the ICAgent according to Uninstalling the ICAgent by Logging In to the Server and then install it again. If the problem persists, contact technical support.
Inherited Installation
If an ICAgent has been installed on a server and the ICProbeAgent.zip installation package exists in the /opt/ICAgent/ directory of this server, use this method to install an ICAgent on a remote server with a few clicks.
- Run the following command (x.x.x.x indicates the server IP address) on the server where an ICAgent has been installed:
bash /opt/oss/servicemgr/ICAgent/bin/remoteInstall/remote_install.sh -ip x.x.x.x
- - Enter the password of the root user as prompted. @@ -104,7 +104,7 @@
- Inherited installation is not supported when ICAgents are installed using an IAM agency.
- If both the expect tool and the ICAgent have been installed on the server, an ICAgent will be installed on the remote server after the preceding command is executed. If an ICAgent has been installed on the server, but the Expect tool has not, enter the information as prompted for installation.
- Ensure that the root user can run the SSH or SCP command on the server where an ICAgent has been installed to remotely communicate with the server where an ICAgent is to be installed.
- If the message ICAgent install success is displayed, the ICAgent has been installed in the /opt/oss/servicemgr/ directory. After the ICAgent has been installed, choose Configuration Management > Agent Management to view the ICAgent status.
- If the ICAgent fails to be installed, uninstall the ICAgent according to Uninstalling the ICAgent by Logging In to the Server and then install it again. If the problem persists, contact technical support.
- Enter the password of the root user as prompted.
- Inherited installation is not supported when ICAgents are installed using an IAM agency.
- If both the expect tool and the ICAgent have been installed on the server, an ICAgent will be installed on the remote server after the preceding command is executed. If an ICAgent has been installed on the server, but the Expect tool has not, enter the information as prompted for installation.
- Ensure that the root user can run the SSH or SCP command on the server where an ICAgent has been installed to remotely communicate with the server where an ICAgent is to be installed.
- If the message ICAgent install success is displayed, the ICAgent has been installed in the /opt/oss/servicemgr/ directory. After the ICAgent has been installed, choose Configuration Management > Agent Management to view the ICAgent status.
- If the ICAgent fails to be installed, uninstall the ICAgent according to Uninstalling the ICAgent by Logging In to the Server and then install it again. If the problem persists, contact technical support.
Prerequisites
The IP addresses and passwords of all servers on which an ICAgent is to be installed have been collected, sorted in the iplist.cfg file, and uploaded to the /opt/ICAgent/ directory on the server where an ICAgent has been installed. The following is an example of the iplist.cfg file, where IP addresses and passwords are separated by spaces.
192.168.0.109 password (Set the password as required.)
-192.168.0.39 password (Set the password as required.)
+192.168.0.39 password (Set the password as required.)
@@ -122,7 +122,7 @@ End of install agent: 192.168.0.39 End of install agent: 192.168.0.109 All hosts install icagent finish. - Because the iplist.cfg file contains sensitive information, you are advised to clear the information in time.
- If the passwords of all servers are the same, list IP addresses in the iplist.cfg file and enter the password during execution. If the password of an IP address is different from those of other IP addresses, enter the password next to this IP address.
- Batch installation depends on Python 3.x. If the system displays a message indicating that Python cannot be found during the installation, install Python and try again.
- Before the installation, check whether the Python command file exists. If the file does not exist, create a soft link.
Wait until the message All hosts install icagent finish. is displayed, which indicates that the ICAgent has been installed on all the hosts listed in the configuration file.
-- After the ICAgent has been installed, choose Configuration Management > Agent Management to view the ICAgent status.
+- After the ICAgent has been installed, choose Configuration Management > Agent Management to view the ICAgent status.
diff --git a/docs/aom/umn/aom_02_002301.html b/docs/aom/umn/aom_02_002301.html index fa2038ee..4eb6597b 100644 --- a/docs/aom/umn/aom_02_002301.html +++ b/docs/aom/umn/aom_02_002301.html @@ -1,7 +1,7 @@Installing an ICAgent
-ICAgent is used to collect metrics, logs, and application performance data. For servers that are directly purchased on the Elastic Cloud Server (ECS) or Bare Metal Server (BMS) console, manually install an ICAgent. For hosts purchased through Cloud Container Engine (CCE), an ICAgent is automatically installed.
+ICAgents collect metrics, logs, and application performance data in real time. For hosts purchased from the ECS or BMS console, you need to manually install the ICAgent. For hosts purchased from the CCE console, the ICAgent is automatically installed.
Prerequisites
- Before installing an ICAgent, ensure that the time and time zone of the local browser are consistent with those of the server. If multiple servers are deployed, ensure that the local browser and multiple servers use the same time zone and time. Otherwise, metric data of applications and servers displayed on the UI may be incorrect.
- An ICAgent process needs to be installed and run by the root user.
Installation Methods
There are two methods to install an ICAgent. Note that the two methods are not applicable to container nodes created using CCE. For container nodes, you do not need to manually install an ICAgent. Instead, you only need to perform certain operations when creating clusters or deploying applications.
@@ -32,9 +32,9 @@Initial Installation
After you apply for a server and install an ICAgent for the first time, perform the following operations:
- Obtain an Access Key ID/Secret Access Key (AK/SK).
- If you have obtained the AK/SK, skip this step.
- If you have not obtained an AK/SK, obtain them first.
- In the navigation pane, choose Configuration Management > Agent Management.
- Select Other: custom hosts, and click Install ICAgent.
- (Optional) To prevent your AK/SK from being disclosed, select the check box shown in the following figure to disable historical record collection.Figure 1 Copying the ICAgent installation command-
- Generate the ICAgent installation command, and copy and run it to install an ICAgent.
- After the ICAgent is installed, run the following command to enable historical record collection:
set -o history
- - If the message ICAgent install success is displayed, the ICAgent has been installed in the /opt/oss/servicemgr/ directory. After the ICAgent is successfully installed, choose Configuration Management > Agent Management in the navigation pane on the left, and select Other: custom hosts to view the ICAgent status of the server.
- If the ICAgent fails to be installed, uninstall the ICAgent according to Uninstalling the ICAgent by Logging In to the Server and then install it again. If the problem persists, contact technical support.
- In the navigation pane, choose Configuration Management > Agent Management.
- Select Other: custom hosts, and click Install ICAgent.
- Click Copy Command to copy the installation command.
- Use a remote login tool to log in to the target server as the root user, and run the following command to disable historical record collection:
set +o history
+- Run the copied installation command and enter the obtained AK and SK as prompted.
- After the ICAgent is installed, run the following command to enable historical record collection:
diff --git a/docs/aom/umn/aom_02_0037.html b/docs/aom/umn/aom_02_0037.html index 0b005c7b..8b2e435e 100644 --- a/docs/aom/umn/aom_02_0037.html +++ b/docs/aom/umn/aom_02_0037.html @@ -6,10 +6,14 @@set -o history
+ - If the message ICAgent install success is displayed, the ICAgent has been installed in the /opt/oss/servicemgr/ directory. After the ICAgent has been installed, choose Configuration Management > Agent Management in the navigation pane to view the ICAgent status.
- If the ICAgent fails to be installed, uninstall the ICAgent according to Uninstalling the ICAgent by Logging In to the Server and then install it again. If the problem persists, contact technical support.
- Overview
+ - Alarm Tags and Annotations
+ - Creating a Threshold Rule
- Creating a Static Threshold Template
+ - Creating an Event Alarm Rule
+
diff --git a/docs/aom/umn/aom_02_0039.html b/docs/aom/umn/aom_02_0039.html index 12f4f9e3..49bb1dcb 100644 --- a/docs/aom/umn/aom_02_0039.html +++ b/docs/aom/umn/aom_02_0039.html @@ -2,9 +2,9 @@Configuring VM Log Collection Paths
AOM can collect and display VM logs. VM refers to an Elastic Cloud Server (ECS) or a Bare Metal Server (BMS) running Linux. To use this function, first configure a log collection path according to the following procedure.
-Prerequisites
- Ensure that your VMs are ECSs or BMSs running Linux.
- You have installed an ICAgent on a VM according to Installing an ICAgent. Wait for about 5 minutes after the installation is complete. Then you can view the VM in the VM list on the Path Configuration page.
-Prerequisites
- You have installed an ICAgent on a VM according to Installing an ICAgent. Wait for about 5 minutes after the installation is complete. Then you can view the VM in the VM list on the Path Configuration page.
Precautions
- If you specify a directory, all .log, .trace, and .out text log files in this directory are collected by default. If you specify a log file, only this file is collected. The specified file must be a text file. Other types of log files, such as binary log files, cannot be collected.
- Ensure that an absolute path of a log directory or file is configured and the path exists. For example, /opt/yilu/work/xig or /opt/yilu/work/xig/debug_cpu.log.
- The ICAgent does not collect log files from subdirectories. For example, the ICAgent does not collect log files from the /opt/yilu/work/xig/debug subdirectory of /opt/yilu/work/xig.
- A maximum of 20 log collection paths can be configured for a VM.
- If the difference between the last modification time of a log file and the current time exceeds 12 hours, the log file will not be collected.
- For ECSs in the same resource set, logs will be collected based on the latest log collection configuration. AOM and LTS log collection configurations cannot take effect at the same time. For example, if you configure log collection paths in AOM for ECSs, the previous LTS collection configurations of all ECSs under the resource set become invalid.
Precautions
- Ensure that your VMs are ECSs or BMSs running Linux.
- If you specify a directory, all .log, .trace, and .out text log files in this directory are collected by default. If you specify a log file, only this file is collected. The specified file must be a text file. Other types of log files, such as binary log files, cannot be collected.
- Ensure that an absolute path of a log directory or file is configured and the path exists. For example, /opt/yilu/work/xig or /opt/yilu/work/xig/debug_cpu.log.
- The ICAgent does not collect log files from subdirectories. For example, the ICAgent does not collect log files from the /opt/yilu/work/xig/debug subdirectory of /opt/yilu/work/xig.
- A maximum of 20 log collection paths can be configured for a VM.
- If the difference between the last modification time of a log file and the current time exceeds 12 hours, the log file will not be collected.
- For ECSs in the same resource set, logs will be collected based on the latest log collection configuration. AOM and LTS log collection configurations cannot take effect at the same time. For example, if you set log collection paths in AOM for ECSs, the previous LTS collection configurations of all ECSs under the resource set become invalid.
- When configuring the collection path of VM logs, do not use the log paths for mapping container service logs to VMs. Otherwise, the collected VM logs may be overwritten by container logs.
Configuring Log Collection Paths for a Single VM Through the Console
- Log in to the AOM console. In the navigation pane, choose Log > Path Configuration. The Host Log tab page is displayed.
- In the VM list, click Configure in the Operation column to configure one or more log collection paths for a VM.You can use the paths automatically identified by the ICAgent or manually configure paths.diff --git a/docs/aom/umn/aom_02_0060.html b/docs/aom/umn/aom_02_0060.html index db327275..030c2b22 100644 --- a/docs/aom/umn/aom_02_0060.html +++ b/docs/aom/umn/aom_02_0060.html @@ -1,7 +1,7 @@
- Using the Paths Automatically Identified by the ICAgent
The ICAgent automatically scans the log files of your VM, and displays all the .log, .trace, or .out log files with handles and their paths on the page.
You can click
diff --git a/docs/aom/umn/aom_02_0044.html b/docs/aom/umn/aom_02_0044.html index 93f6a35e..ab6c6b23 100644 --- a/docs/aom/umn/aom_02_0044.html +++ b/docs/aom/umn/aom_02_0044.html @@ -10,6 +10,10 @@
in the Operation column to add a path automatically identified by the ICAgent to the log collection path list. To configure multiple paths, repeat this operation. - Viewing Events
+ - Alarm Action Rules
+
+ - Alarm Noise Reduction
+
Creating a Threshold Rule
-You can set threshold conditions for resource metrics by setting threshold rules. If a metric value meets the threshold condition, a threshold alarm will be generated. If no metric data is reported, an insufficient data event will be generated.
+You can set threshold conditions for resource metrics by setting threshold rules. If a metric value meets a threshold condition, a threshold alarm will be reported. If there is no metric data, an insufficient data event will be reported.
Creation Methods
There are two creation methods: Directly Creating Threshold Rules and Using Templates to Create Threshold Rules. Only one rule is generated at a time. All resources are monitored using the same rule. To use the second method to create threshold rules, ensure that a static threshold template has been created according to Creating a Static Threshold Template.
Precautions
- If you use a threshold rule to monitor the same metric of multiple resources in batches, pay attention to the following:
- If the metric status of a resource is Exceeded, the status of the threshold rule is also Exceeded.
- If the metric status of one or more resources is Insufficient or Normal, the status of the threshold rule is Normal.
- Auto input: used when you do not know the metric information or are unfamiliar with the Prometheus format. The command can only be automatically filled when you switch from the Metric Monitoring page.
Specifically, choose Monitoring > Metric Monitoring in the navigation pane. Then, click Add Metric and select Dimension or Resource for Add By. Select up to 12 metrics to monitor. Next, click
in the Operation column. The system automatically switches to the threshold rule creation page and fills the Prometheus command for your metric.
- Set an alarm condition. Click Custom and set information such as Statistical Period, Consecutive Periods, and Threshold Criterion. Table 1 describes the parameters. +
- Set an alarm condition. Click Custom and set information such as Statistical Period, Consecutive Periods, and Threshold Criterion. Table 1 describes the parameters.
Figure 1 Setting an alarm condition-
- Set alarm tags and annotations to group alarms. +
- Set alarm tags and annotations to group alarms. They can be associated with alarm noise reduction policies for sending alarm notifications. For details, see Alarm Tags and Annotations.
+Click Add Tag or Add Annotation.
- Set an alarm notification policy. There are two alarm notification modes.
- Direct Alarm Reporting: An alarm is directly sent when the alarm condition is met.
- Specify whether to enable an alarm action rule. After an alarm action rule is enabled, the system sends notifications based on the associated SMN topic and message template. If the existing alarm action rules cannot meet your requirements, click Create Rule to create one. For details, see Creating an Alarm Action Rule.
- After an alarm action rule is selected, specify whether to enable alarm clearance notification. After alarm clearance notification is enabled, if the alarm clearance condition set in Advanced Settings > Alarm Clearance is met, alarm clearance notifications are sent based on the selected action rule.
Figure 2 Selecting the direct alarm reporting mode+
- Alarm Noise Reduction: Alarms are sent only after being processed based on noise reduction rules, preventing alarm storms.
Select a grouping rule from the drop-down list. If existing grouping rules cannot meet your requirements, click Create Rule to create one. For details, see Creating a Grouping Rule.
+Figure 3 Selecting the alarm noise reduction mode+
- Click Create Now. As shown in the following figure, a threshold rule is created. Click
to monitor the same metric of multiple resources.In the expanded list, if the metric data of a host meets the preset alarm condition, a threshold alarm is generated on the alarm page. To view the alarm, go to the AOM console and choose Alarm Center > Alarm List in the navigation pane.
-Figure 2 Creating a threshold rule+
Figure 4 Creating a threshold ruleUsing Templates to Create Threshold Rules
Before creating threshold rules, ensure that a static threshold template has been created according to Creating a Static Threshold Template.
-- Log in to the AOM console. In the navigation pane, choose Alarm Center > Alarm Rules. Then, click Create Alarm Rule in the upper right corner.
- Set a threshold rule.
- Set basic information such as the rule name and description.
- Set details about the rule.
- Set Rule Type to Threshold alarm.
- Select monitored objects. When a template is used to create a threshold rule, you can select metrics only by dimension or resource. The command input mode is not supported.
- Set an alarm condition. Click Template, select the created static threshold template from the drop-down list, and set parameters, such as Alarm Clearance and Action Taken for Insufficient Data.Figure 3 Setting an alarm condition+
- Log in to the AOM console. In the navigation pane, choose Alarm Center > Alarm Rules. Then, click Create Alarm Rule in the upper right corner.
- Set a threshold rule.
- Set basic information such as the rule name and description.
- Set details about the rule.
- Set Rule Type to Threshold alarm.
- Select monitored objects. When a template is used to create a threshold rule, you can select metrics only by dimension or resource. The command input mode is not supported.
- Set an alarm condition. Click Template, select the created static threshold template from the drop-down list, and set parameters, such as Alarm Clearance and Action Taken for Insufficient Data.Figure 5 Setting an alarm condition@@ -125,7 +134,7 @@
Table 2 Alarm condition parameters Category
- Set alarm tags and annotations to group alarms.
+- Set an alarm notification policy. There are two alarm notification modes.
- Direct Alarm Reporting: An alarm is directly sent when the alarm condition is met.
- Specify whether to enable an alarm action rule. After an alarm action rule is enabled, the system sends notifications based on the associated SMN topic and message template. If the existing alarm action rules cannot meet your requirements, click Create Rule to create one. For details, see Creating an Alarm Action Rule.
- After an alarm action rule is selected, specify whether to enable alarm clearance notification. After alarm clearance notification is enabled, if the alarm clearance condition set in Advanced Settings > Alarm Clearance is met, alarm clearance notifications are sent based on the selected action rule.
Figure 6 Selecting the direct alarm reporting mode+
- Alarm Noise Reduction: Alarms are sent only after being processed based on noise reduction rules, preventing alarm storms.
Select a grouping rule from the drop-down list. If existing grouping rules cannot meet your requirements, click Create Rule to create one. For details, see Creating a Grouping Rule.
+Figure 7 Selecting the alarm noise reduction mode+
- Click Create Now. As shown in the following figure, a threshold rule is created. Click
to monitor the same metric of multiple resources.In the expanded list, if the metric data of a host meets the preset alarm condition, a threshold alarm is generated on the alarm page. To view the alarm, go to the AOM console and choose Alarm Center > Alarm List in the navigation pane.
-Figure 4 Creating a threshold rule+Figure 8 Creating a threshold ruleMore Operations
After creating a threshold rule, perform the operations listed in Table 3 if needed.
@@ -147,7 +157,7 @@Starting or stopping a threshold rule
Click Start or Stop in the Operation column.
+Click Start or Stop in the Operation column.
NOTE:Single-resource threshold rules cannot be started or stopped.
Creating an Event Alarm Rule
++You can set event conditions for services by setting event alarm rules. When the resource data meets an event condition, an event alarm is generated.
++Precautions
If you want to receive email or SMS notifications when the resource data meets the event condition, set an alarm action rule according to Creating an Alarm Action Rule.
++Procedure
- Log in to the AOM console. In the navigation pane, choose Alarm Center > Alarm Rules. Then, click Create Alarm Rule in the upper right corner.
- Set an event alarm rule.
- Set basic information such as the rule name and description.Figure 1 Setting basic information+
- Set details about the rule.
- Set Rule Type to Event alarm.
- Set the alarm source, trigger object, and trigger policy.
++
+Table 1 Alarm rule parameters Parameter
+Description
+Alarm Source
+Name of the service for which an event alarm is reported. You can select a service from the service list.
+Trigger Object
+Select criteria to filter service events. You can select Notification Type, Event Name, Alarm Severity, Custom Attributes, Namespace, or Cluster Name as the filter criterion. One or more criteria can be selected.
+Trigger Policy
+Policy for triggering event alarms.
+- Accumulated Triggering: An alarm action rule is triggered when the accumulated number of times you preset is reached in a monitoring period.
- Immediate Triggering: An alarm is generated immediately when the filter criterion is met.
Figure 2 Setting an alarm rule+
- Set an alarm notification policy. There are two alarm notification modes.
- Direct Alarm Reporting: An alarm is directly sent when the alarm condition is met.
You need to configure whether to enable an alarm action rule. After this function is enabled, the system sends alarm notifications based on the associated SMN topic and message template. If the existing alarm action rules cannot meet your requirements, click Create Rule to create one. For details, see Creating an Alarm Action Rule.
+Figure 3 Selecting the direct alarm reporting mode+
- Alarm Noise Reduction: Alarms are sent only after being processed based on noise reduction rules, preventing alarm storms.
Select a grouping rule from the drop-down list. If existing grouping rules cannot meet your requirements, click Create Rule to create one. For details, see Creating a Grouping Rule.
+Figure 4 Selecting the alarm noise reduction mode+
- Direct Alarm Reporting: An alarm is directly sent when the alarm condition is met.
- Set basic information such as the rule name and description.
- Click Create Now. An event alarm rule is created, as shown in the following figure.
This rule monitors critical alarm events of AOM. When a service event meets the preset notification policy, the system sends an alarm notification to specified personnel by email or SMS.
+Figure 5 Event alarm rule+
+Related Operations
After creating an event alarm rule, perform the operations listed in Table 2 if needed.
+ ++
+Table 2 Related operations Operation
+Description
+Editing an event alarm rule
+Click Edit in the Operation column.
+Deleting event alarm rules
+- To delete an event alarm rule, click Delete in the Operation column.
- To delete one or more event alarm rules, select the check boxes before them and click Delete above the rule list.
Starting or stopping an event alarm rule
+Click Start or Stop in the Operation column.
+Searching for an event alarm rule
+You can search for a rule by rule name, description, or metric name. Simply enter a keyword in the search box in the upper right corner and click
+
.++ diff --git a/docs/aom/umn/aom_02_0062.html b/docs/aom/umn/aom_02_0062.html index 9879984f..7b60d941 100644 --- a/docs/aom/umn/aom_02_0062.html +++ b/docs/aom/umn/aom_02_0062.html @@ -1,9 +1,9 @@++Parent topic: Alarm Rules+Overview
-By setting alarms rules, you can define threshold conditions for resource metrics. A threshold alarm is generated when the metric data of a resource meets the threshold condition. An insufficient data event is generated when no metric data is reported.
-Generally, threshold rules are used to monitor the usage of resources such as hosts and components in the environment in real time.
-The total number of threshold rules is 1000. If the number of alarm rules has reached the upper limit, delete unnecessary rules and create new ones.
+By setting alarms rules, you can define event conditions for services or threshold conditions for resource metrics. If the resource data of a service meets the event condition, an event alarm will be generated. If a metric value meets a threshold condition, a threshold alarm will be reported. If there is no metric data, an insufficient data event will be reported.
+Alarm rules are classified into threshold rules and event alarm rules. Generally, threshold rules monitor the usage of resources such as hosts and components in real time. If there are too many resource usage alarms and notifications are sent too often, use an event alarm rule to identify a type of resource usage problems for simplified notification.
+The total number of threshold rules and event alarm rules is 1000. If the number of alarm rules has reached the upper limit, delete unnecessary rules and create new ones.
diff --git a/docs/aom/umn/aom_02_0080.html b/docs/aom/umn/aom_02_0080.html index ae44e719..755476a9 100644 --- a/docs/aom/umn/aom_02_0080.html +++ b/docs/aom/umn/aom_02_0080.html @@ -152,7 +152,7 @@Target OBS Bucket
OBS bucket that store logs.
-NOTE:If no OBS bucket is available, click View OBS to create a bucket on the OBS console.
+NOTE:- If no OBS bucket is available, click View OBS to create a bucket on the OBS console.
- If you select an unauthorized OBS bucket, AOM will take 15 minutes to authorize the ACL for the bucket. If your configuration fails, try again 15 minutes later.
obs-store-test
diff --git a/docs/aom/umn/aom_02_008203.html b/docs/aom/umn/aom_02_008203.html index d79827cb..3e425400 100644 --- a/docs/aom/umn/aom_02_008203.html +++ b/docs/aom/umn/aom_02_008203.html @@ -1,10 +1,10 @@Metric Configuration
-Metric Collection determines whether to collect metrics (excluding SLA and custom metrics).
+You can determine whether to enable Metric Collection to collect metrics (excluding SLA and custom metrics).
Before enabling this function, ensure that you have installed the ICAgent on an Elastic Cloud Server (ECS) according to Installing an ICAgent.
-- Log in to the AOM console. In the navigation pane, choose Configuration Management > Metric Configuration.
- Enable or disable metric collection.Figure 1 Configuring metric collection-
After the metric collection function is disabled, ICAgents will stop collecting metric data and related metric data will not be updated. However, custom metrics can still be reported.
+- Log in to the AOM console. In the navigation pane, choose Configuration Management > Metric Configuration.
- Enable or disable metric collection.Figure 1 Configuring metric collection+
After metric collection is disabled, ICAgents will stop collecting metric data and related metric data will not be updated. However, custom metrics can still be reported.
Creating a User and Granting Permissions
-This chapter describes how to use Identity and Access Management (IAM) for fine-grained permissions control for your Application Operations Management (AOM) resources. With IAM, you can:
-- Create IAM users for employees based on the organizational structure of your enterprise. Each IAM user has their own security credentials, providing access to AOM resources.
- Grant only the permissions required for users to perform a task.
- Entrust an account or a cloud service to perform professional and efficient O&M on your AOM resources.
If your account does not need individual IAM users, then you may skip over this chapter.
+This chapter describes how to use Identity and Access Management (IAM) for fine-grained permissions control for your AOM resources. With IAM, you can:
+- Create IAM users for employees based on the organizational structure of your enterprise. Each IAM user has their own security credentials, providing access to AOM resources.
- Grant only the permissions required for users to perform a task.
- Entrust a cloud account or service to perform professional and efficient O&M on your AOM resources.
If your account does not need individual IAM users, then you may skip over this section.
This section describes the procedure for granting permissions (see Figure 1).
-Prerequisites
Learn about the permissions supported by AOM and choose policies or roles according to your requirements. See AOM Permissions. For the permissions of other services, see Permission Description.
+Prerequisites
Learn about the permissions (see AOM Permissions) supported by AOM and choose policies or roles according to your requirements. For the permissions of other services, see Permission Description.
Process
- Create a user group and assign permissions.
Create a user group on the IAM console, and assign the AOM ReadOnlyAccess policy to the group.
diff --git a/docs/aom/umn/aom_02_0091.html b/docs/aom/umn/aom_02_0091.html index 0df12845..58f870aa 100644 --- a/docs/aom/umn/aom_02_0091.html +++ b/docs/aom/umn/aom_02_0091.html @@ -4,7 +4,7 @@Custom policies can be created as a supplement to the system policies of AOM.
You can create custom policies in either of the following two ways:
- Visual editor: Select cloud services, actions, resources, and request conditions. This does not require knowledge of policy syntax.
- JSON: Edit JSON policies from scratch or based on an existing policy.
For details about how to create custom policies, see Creating a Custom Policy. For example custom policies, see the following description.
+For details about how to create custom policies, see Creating a Custom Policy. For example custom policies, see the following description.
Example Custom Policies
- Example 1: Allowing a user to create threshold rules
{ "Version": "1.1", "Statement": [ diff --git a/docs/aom/umn/aom_02_0112.html b/docs/aom/umn/aom_02_0112.html index fdc11538..89ba4d26 100644 --- a/docs/aom/umn/aom_02_0112.html +++ b/docs/aom/umn/aom_02_0112.html @@ -1,18 +1,18 @@Upgrading to AOM 2.0
-This section describes how to migrate data from AOM 1.0 to AOM 2.0. Currently, only collector, and alarm rule upgrades are supported.
-Functions
- Collector Upgrade
After the collector is upgraded, the process discovery capability is enhanced and the collector can automatically adapt to functions related to CMDB, and monitoring center.
- - Alarm Rule Upgrade
After alarm rules are upgraded, alarm rule data is smoothly switched from AOM 1.0 to AOM 2.0, and is automatically adapted to alarm rule functions of AOM 2.0.
+This section describes how to migrate data from AOM 1.0 to AOM 2.0. Currently, only alarm rule and collector upgrades are supported.
+-Introduction
- Collector Upgrade
After the upgrade, the process discovery capability is enhanced and the collector can automatically adapt to functions related to CMDB, and monitoring center.
+ - Alarm Rule Upgrade
After the upgrade, alarm rule data is smoothly switched from AOM 1.0 to AOM 2.0, and is automatically adapted to alarm rule functions of AOM 2.0.
Collector Upgrade
- Log in to the AOM 1.0 console.
- In the navigation pane, choose Configuration Management > Agent Management.
- Select Other: custom hosts from the drop-down list on the right of the page.
- Select a host and click Upgrade ICAgent.
- Select a target AOM 2.0 version from the drop-down list and click OK.
- Wait for the upgrade, which may take about 1 minute to complete. When the ICAgent status changes from Updating to Running, the ICAgent has been upgraded.
If the ICAgent state is abnormal after the upgrade or the upgrade fails, log in to the node and run the installation command to reinstall the ICAgent. (The original configuration can be overwritten, so there is no need for you to uninstall the ICAgent.)
+-Collector Upgrade
- Log in to the AOM 1.0 console.
- In the navigation pane, choose Configuration Management > Agent Management.
- Select Other: custom hosts from the drop-down list on the right of the page.
- Select a host and click Upgrade ICAgent.
- Select a target version from the drop-down list and click OK.
- Wait for the upgrade. This process takes about one minute. When the ICAgent status changes from Updating to Running, the ICAgent has been upgraded.
If the ICAgent is abnormal after the upgrade or if the upgrade fails, log in to the host and run the installation command again. There is no need for you to uninstall the original ICAgent.
Alarm Rule Upgrade
- Log in to the AOM 1.0 console.
- In the navigation pane on the left, choose Alarm Center > Alarm Rules.
- Select one or more alarm rules and click Migrate to AOM 2.0 above the rule list.diff --git a/docs/aom/umn/aom_02_0115.html b/docs/aom/umn/aom_02_0115.html index 588dd6b4..10a00b3a 100644 --- a/docs/aom/umn/aom_02_0115.html +++ b/docs/aom/umn/aom_02_0115.html @@ -156,14 +156,14 @@
diff --git a/docs/aom/umn/aom_02_0113.html b/docs/aom/umn/aom_02_0113.html new file mode 100644 index 00000000..e1e8d808 --- /dev/null +++ b/docs/aom/umn/aom_02_0113.html @@ -0,0 +1,15 @@ + + +- Migration cannot be undone. Exercise caution when performing this operation.
- If the alarm rules to be migrated depend on alarm templates, these alarm templates will also be migrated.
Alarm Rule Upgrade
- Log in to the AOM 1.0 console.
- In the navigation pane on the left, choose Alarm Center > Alarm Rules.
- Select one or more alarm rules and click Migrate to AOM 2.0 above the rule list.-
- Migration cannot be undone. Exercise caution when performing this operation.
- If the alarm rules to be migrated depend on alarm templates, these alarm templates will also be migrated.
- In the displayed dialog box, click Confirm. The selected alarm rules will be migrated to AOM 2.0 in batches.
- In the displayed dialog box, click Confirm. The selected alarm rules will be migrated to AOM 2.0 in batches.
Alarm Tags and Annotations
++When creating alarm rules, you can set alarm tags and annotations. Tags are attributes that can be used to identify alarms. They are applied to the alarm noise reduction scenario. Annotations are attributes that cannot be used to identify alarms. They are applied to scenarios such as alarm notification and message templates.
++Alarm Tags
- Alarm tags can apply to grouping rules, suppression rules, and silence rules. The alarm management system manages alarms and notifications based on the tags.
- Each tag is in "key:value" format and can be customized. The key and value can contain only letters, digits, and underscores (_) and cannot start with an underscore (_). You can create up to 10 custom tags.
- If you set a tag when creating an alarm rule, the tag is automatically added as an alarm attribute when an alarm is triggered.
- In the message template, the $event.metadata.key1 variable specifies the tag. For details, see Table 1.
+Alarm Annotations
- Annotations are attributes that cannot be used to identify alarms. They are applied to scenarios such as alarm notification and message templates.
- Each annotation is in "key:value" format and can be customized. The key and value can contain only letters, digits, and underscores (_) and cannot start with an underscore (_). You can create up to 10 custom annotations.
- In the message template, the $event.annotations.key2 variable specifies the annotation. For details, see Table 1.
++ diff --git a/docs/aom/umn/aom_02_0114.html b/docs/aom/umn/aom_02_0114.html index 73de622c..a105e88f 100644 --- a/docs/aom/umn/aom_02_0114.html +++ b/docs/aom/umn/aom_02_0114.html @@ -7,7 +7,7 @@++Parent topic: Alarm Rules+
- Collector Upgrade
- Collector Upgrade
Creating or modifying an application discovery rule
apminventory
+apminventory
addOrUpdateAppRules
+addOrUpdateAppRules
Deleting an application discovery rule
apminventory
+apminventory
deleteAppRules
Viewing Audit Logs
-For details, see Querying Real-Time Traces.
+Querying Real-Time Traces
++Scenarios
After you enable CTS and the management tracker is created, CTS starts recording operations on cloud resources. CTS stores operation records generated in the last seven days.
+This section describes how to query and export operation records of the last seven days on the CTS console.
+ +Viewing Real-Time Traces in the Trace List
- Log in to the management console.
- Click
in the upper left corner and choose Management & Deployment > Cloud Trace Service. The CTS console is displayed. - Choose Trace List in the navigation pane on the left.
- Set filters to search for your desired traces, as shown in Figure 1. The following filters are available:
++
- Trace Type, Trace Source, Resource Type, and Search By: Select a filter from the drop-down list.
- If you select Resource ID for Search By, specify a resource ID.
- If you select Trace name for Search By, specify a trace name.
- If you select Resource name for Search By, specify a resource name.
- Operator: Select a user.
- Trace Status: Select All trace statuses, Normal, Warning, or Incident.
- Time range: You can query traces generated during any time range in the last seven days.
- Click Export to export all traces in the query result as a CSV file. The file can contain up to 5000 records.
- Trace Type, Trace Source, Resource Type, and Search By: Select a filter from the drop-down list.
- Click Query.
- On the Trace List page, you can also export and refresh the trace list.
- Click Export to export all traces in the query result as a CSV file. The file can contain up to 5000 records.
- Click
to view the latest information about traces.
- Click
on the left of a trace to expand its details.
+
+ +
- Click View Trace in the Operation column. The trace details are displayed.
+
- For details about key fields in the trace structure, see section "Trace References" > "Trace Structure" and section "Trace References" > "Example Traces" in the CTS User Guide.
diff --git a/docs/aom/umn/aom_02_0925.html b/docs/aom/umn/aom_02_0925.html new file mode 100644 index 00000000..5d39dad6 --- /dev/null +++ b/docs/aom/umn/aom_02_0925.html @@ -0,0 +1,19 @@ + + +Alarm Action Rules
+ ++ + ++ diff --git a/docs/aom/umn/aom_02_0926.html b/docs/aom/umn/aom_02_0926.html new file mode 100644 index 00000000..7e34a4d2 --- /dev/null +++ b/docs/aom/umn/aom_02_0926.html @@ -0,0 +1,84 @@ + + +++Parent topic: Alarm Management+Creating an Alarm Action Rule
+++Prerequisites
- A topic has been created.
- A topic policy has been set.
- A subscriber, that is, an email or SMS message recipient has been added to the topic.
+Precaution
You can create a maximum of 1000 alarm action rules. If this number has been reached, delete unnecessary rules.
++Procedure
- Log in to the AOM console. In the navigation pane, choose Alarm Center > Alarm Action Rules. On the displayed page, click Create in the upper left corner.
- Set parameters such as Rule Name and Action Type.Figure 1 Creating an alarm action rule+ + +
+
+Table 1 Parameters for configuring an alarm action rule Parameter
+Description
+Rule Name
+Name of an action rule. Enter 3 to 36 characters, and do not start or end with an underscore (_). Only digits, letters, and underscores are allowed.
+Description
+Description of the action rule.
+Action Type
+Type of action that is associated with the SMN topic and message template. Select your desired action from the drop-down list. Currently, only Notification is supported.
+Topic
+SMN topic. Select your desired topic from the drop-down list.
+If there is no topic you want to select, create one on the SMN console.
+Message Template
+Notification message template. Select your desired template from the drop-down list.
+If there is no message template you want to select, create one by referring to Creating a Message Template.
+
- Click OK.
+More Operations
After an alarm action rule is created, you can perform operations described in Table 2.
+ ++
+Table 2 Related operations Operation
+Description
+Modifying an alarm action rule
+Click Edit in the Operation column.
+Deleting an alarm action rule
+- To delete a single rule, click Delete in the Operation column in the row that contains the rule, and then click Yes on the displayed page.
- To delete one or more rules, select them, click Delete above the rule list, and then click Yes on the displayed page.NOTE:+
Before deleting an alarm action rule, you need to delete the alarm rule bound to the action rule.
+
Searching for an alarm action rule
+Enter a rule name in the search box in the upper right corner and click
+
.++ diff --git a/docs/aom/umn/aom_02_0927.html b/docs/aom/umn/aom_02_0927.html new file mode 100644 index 00000000..38144f5d --- /dev/null +++ b/docs/aom/umn/aom_02_0927.html @@ -0,0 +1,177 @@ + + +++Parent topic: Alarm Action Rules+Creating a Message Template
++You can create message templates to customize notifications. When a preset notification rule is triggered, notifications can be sent to specified personnel by emails, SMS, voice calls, HTTP, or HTTPS. If no message template is created, the default message template will be used.
++Creating a Message Template
- Log in to the AOM console and choose Alarm Center > Alarm Action Rules in the navigation pane. On the displayed page, click the Message Templates tab.
- On the Message Templates page, click Create.
- Enter a template name.
- Enter a template description.
- Select a language.
- Customize the template content. (Default fields are automatically filled when a message template is created.)+ +
- You can create up to 100 message templates. If this number has been reached, delete unnecessary templates.
- There are two default message templates. If you do not customize any message template, notifications will be sent based on default templates. The default templates cannot be deleted or edited.
- In addition to default fields, the message template also allows you to add custom fields. You need to define values for custom fields for event alarm reporting. For details about the parameters, see the alarm reporting structs in the following message template.
- Custom fields support the JSONPath format. Example: $event.metadata.case1 or $event.metadata.case[0].
- In the upper right corner of the Body area, click Add Variables to add required variables.
- If you select Email, you can click Preview to view the final effect. On the Preview page, change the message topic if necessary.
+
+Table 1 Variables in the default message template Variable
+Description
+Definition
+OTC account
+Account used to log in to the management console.
+${domain_name}
+Notification Type
+Type selected when a notification rule is created, which can be Alarm or Event.
+${event_type}
+Severity
+Alarm or event severity, which can be Critical, Major, Minor, or Warning.
+${event_severity}
+Name
+Name of the alarm or event that triggers the notification rule.
+$event.metadata.event_name
+Occurred
+Time when the alarm or event is triggered.
+${starts_at}
+Source
+Name of the service corresponding to the alarm or event that triggers the notification rule.
+$event.metadata.resource_provider
+Resource Type
+Type of the resource selected when you customize a threshold rule or define alarm reporting.
+$event.metadata.resource_type
+Resource Identifier
+Resource that triggers the alarm or event.
+${resources}
+Custom tag
+Extended tag.
+$event.metadata.key1
+Possible Cause
+Cause of the alarm. For non-custom reporting, "NA" is displayed.
+${alarm_probableCause_zh}
+Additional Info
+Additional alarm description, such as the metric name and alarm rule status change.
+${message}
+Suggestion
+Suggestion on how to handle the alarm. For non-custom reporting, "NA" is displayed.
+${alarm_fix_suggestion_zh}
+Custom annotation
+Extended annotation.
+$event.annotations.key2
+Alarm reporting structs corresponding to the message template+{ + "event": { + "starts_at": 1579420868000, //${starts_at} + "ends_at": 1579420868000, + "timeout": 60000, + "resource_group_id": "5680587ab6*******755c543c1f", + "metadata": { + "event_name": "test", //${metadata.event_name} + "event_severity": "Major", //${metadata.event_severity} + "event_type": "alarm", //${metadata.event_type} + "resource_provider": "ecs", //${metadata.resource_provider} + "resource_type": "vm", //${metadata.resource_type} + "resource_id": "ecs123", + "key1": "Custom field" //$event.metadata.key1 + }, + "annotations": { + "alarm_probableCause_zh_cn": "possible cause", //${annotations.alarm_probableCause_zh} + "alarm_fix_suggestion_zh_cn": "fix suggestion", //${annotations.alarm_fix_suggestion_zh} + "key2": "Custom field" //$event.annotations.key2 + } + } +} ++ - Click Confirm. The message template is created.
+More Operations
After creating a message template, you can perform the operations listed in Table 2.
+ ++
+Table 2 Related operations Operation
+Description
+Editing a message template
+Click Edit in the Operation column.
+Copying a message template
+Click Copy in the Operation column.
+Deleting a message template
+- To delete a single message template, click Delete in the Operation column in the row that contains the template, and then click Yes on the displayed page.
- To delete one or more message templates, select them, and click Delete above the template list, and then click Yes on the displayed page.NOTE:+
Before deleting a message template, you need to delete the alarm action rules bound to it.
+
Searching for a message template
+Enter a template name in the search box in the upper right corner and click
+
.++ diff --git a/docs/aom/umn/aom_02_0933.html b/docs/aom/umn/aom_02_0933.html new file mode 100644 index 00000000..12ed68c6 --- /dev/null +++ b/docs/aom/umn/aom_02_0933.html @@ -0,0 +1,11 @@ + + +++Parent topic: Alarm Action Rules+Overview
++AOM allows you to customize alarm action rules. You can create an alarm action rule to associate an SMN topic with a message template. You can also customize notification content based on a message template. After an alarm action rule is created, choose Alarm Center > Alarm Noise Reduction in the navigation pane. Then, click the Grouping Rules tab and click Create. On the displayed page, specify an alarm action rule.
+++ diff --git a/docs/aom/umn/aom_02_0950.html b/docs/aom/umn/aom_02_0950.html new file mode 100644 index 00000000..75874302 --- /dev/null +++ b/docs/aom/umn/aom_02_0950.html @@ -0,0 +1,21 @@ + + +++Parent topic: Alarm Action Rules+Alarm Noise Reduction
+ ++ + ++ diff --git a/docs/aom/umn/aom_02_0951.html b/docs/aom/umn/aom_02_0951.html new file mode 100644 index 00000000..a0b7cc45 --- /dev/null +++ b/docs/aom/umn/aom_02_0951.html @@ -0,0 +1,36 @@ + + +++Parent topic: Alarm Management+Overview
++AOM supports alarm noise reduction. Alarms can be processed based on the alarm noise reduction rules to prevent notification storms.
+Alarm noise reduction consists of four parts: grouping, deduplication, suppression, and silence.
+AOM uses built-in deduplication rules. The service backend automatically deduplicates alarms. You do not need to manually create rules.
+Figure 1 Alarm noise reduction process+
You need to manually create grouping, suppression, and silence rules. For details, see the following description.
++ - This module is used only for message notification. All triggered alarms and events can be viewed on the Alarm List and Event List pages.
- All conditions of alarm noise reduction rules are obtained from metadata in alarm structs. You can use the default fields or customize your own fields.
{ + "starts_at" : 1579420868000, + "ends_at" : 1579420868000, + "timeout" : 60000, + "resource_group_id" : "5680587ab6*******755c543c1f", + "metadata" : { + "event_name" : "test", + "event_severity" : "Major", + "event_type" : "alarm", + "resource_provider" : "ecs", + "resource_type" : "vm", + "resource_id" : "ecs123" , + "key1" : "value1" // Alarm tag configured when the alarm rule is created + }, + "annotations" : { + "alarm_probableCause_en_us": " Possible causes", + "alarm_fix_suggestion_en_us": "Handling suggestion" + } +}+
++ diff --git a/docs/aom/umn/aom_02_0952.html b/docs/aom/umn/aom_02_0952.html new file mode 100644 index 00000000..4463d629 --- /dev/null +++ b/docs/aom/umn/aom_02_0952.html @@ -0,0 +1,107 @@ + + +++Parent topic: Alarm Noise Reduction+Creating a Grouping Rule
++You can filter alarm subsets and then group them based on the grouping conditions. Alarms in the same group are aggregated to trigger one notification.
+As shown in Figure 1, when Alarm Severity under Grouping Condition is set to Critical, the system filters out the critical alarms, and then combines these alarms based on the specified mode. The combined alarms can then be associated with an action rule for sending notifications.
+ ++Creating a Grouping Rule
You can create up to 100 grouping rules.
+- In the navigation pane, choose Alarm Center > Alarm Noise Reduction.
- On the Grouping Rules tab page, click Create and set parameters such as the rule name and grouping condition. For details, see Table 1.Figure 2 Creating a grouping rule+ +
+
+Table 1 Setting a grouping rule Category
+Parameter
+Description
+-
+Rule Name
+Grouping rule name, which can contain up to 100 characters and cannot start or end with an underscore (_). Only letters, digits, and underscores are allowed.
+Description
+Grouping rule description, which can contain up to 1024 characters.
+Grouping rules
+Grouping Condition
+Conditions set to filter alarms. After alarms are filtered out, you can set alarm action rules for them.
+You can create a maximum of 10 parallel conditions, each of which can contain up to 10 serial conditions. One or more alarm action rules can be set for each parallel condition.
+Serial conditions are in the AND relationship whereas parallel conditions are in the OR relationship. An alarm must meet all serial conditions under one of the parallel conditions.
+For example, if two serial conditions (that is, Alarm Severity = Critical and Provider = AOM) are set under a parallel condition, critical AOM alarms are filtered out, and notification actions are performed based on the alarm action rule you set.
+Combination rules
+Combine Notifications
+Notifications for alarms with certain fields to be the same will be combined.
+Notifications can be combined:
+- By alarm source
- By alarm source + severity
- By alarm source + all tags
Initial Wait Time
+Interval for sending an alarm notification after alarms are combined for the first time. It is recommended that the time be set to seconds to prevent alarm storms.
+Value range: 0s to 10 minutes. Recommended: 15s.
+Batch Processing Interval
+Waiting time for sending an alarm notification after the combined alarm data changes. It is recommended that the time be set to minutes. If you want to receive alarm notifications as soon as possible, set the time to seconds.
+The change here refers to a new alarm or an alarm status change.
+Value range: 5s to 30 minutes. Recommended: 60s.
+Repeat Interval
+Waiting time for sending an alarm notification after the combined alarm data becomes duplicate. It is recommended that the time be set to hours.
+Duplication means that no new alarm is generated and no alarm status is changed while other attributes (such as titles and content) are changed.
+Value range: 0 minutes to 15 days. Recommended: 1 hour.
+ - Click Create Now.
+More Operations
After creating a grouping rule, perform the operations listed in Table 2 if needed.
+ ++
+Table 2 Related operations Operation
+Description
+Modifying a grouping rule
+Click Modify in the Operation column.
+Deleting a grouping rule
+- To delete a single rule, click Delete in the Operation column in the row that contains the rule.
- To delete one or more rules, select them and click Delete above the rule list.
Searching for a grouping rule
+Enter a rule name in the search box in the upper right corner and click
+
.++ diff --git a/docs/aom/umn/aom_02_0953.html b/docs/aom/umn/aom_02_0953.html new file mode 100644 index 00000000..8f56fb15 --- /dev/null +++ b/docs/aom/umn/aom_02_0953.html @@ -0,0 +1,85 @@ + + +++Parent topic: Alarm Noise Reduction+Creating a Suppression Rule
++By using suppression rules, you can suppress or block notifications related to specific alarms. For example, when a major alarm is generated, less severe alarms can be suppressed. Another example, when a node is faulty, all other alarms of the processes or containers on this node can be suppressed.
++Precautions
If the source alarm corresponding to the suppression condition is cleared before the alarm notification is sent, the suppression rule becomes invalid. For the suppressed object (alarm suppressed by the source alarm), the alarm notification can still be sent as usual.
+You can create up to 100 suppression rules.
++Creating a Suppression Rule
- In the navigation pane, choose Alarm Center > Alarm Noise Reduction.
- On the Suppression Rules tab page, click Create and set parameters such as the rule name and root alarm.Figure 1 Creating a suppression rule+ +
+
+Table 1 Setting a suppression rule Category
+Parameter
+Description
+-
+Rule Name
+Suppression rule name, which can contain up to 100 characters and cannot start or end with an underscore (_). Only letters, digits, and underscores are allowed.
+Description
+Suppression rule description, which can contain up to 1024 characters.
+Suppression rules
+Source Alarm
+Alarm that triggers suppression.
+You can create up to 10 parallel conditions under Source Alarm, and up to 10 serial conditions under each parallel condition. Serial conditions are in the AND relationship whereas parallel conditions are in the OR relationship. An alarm must meet all serial conditions under one of the parallel conditions.
+For a serial condition, if Alarm Severity is set to Critical, critical alarms are filtered out as the root alarms.
+Suppressed Alarm
+Alarm that is suppressed by the root alarm.
+Set parameters for the suppressed alarm in the same way that you set parameters for the source alarm.
+If Serial Condition of Source Alarm is set to Critical and that of Suppressed Alarm is set to Warning, warnings will be suppressed when critical alarms are generated.
+ - After you finish setting the parameters, click Create Now.
After a suppression rule is created, it will take effect for all alarms that are grouped.
+
+More Operations
After creating a suppression rule, perform the operations listed in Table 2 if needed.
+ ++
+Table 2 Related operations Operation
+Description
+Modifying a suppression rule
+Click Modify in the Operation column.
+Deleting a suppression rule
+- To delete a single rule, click Delete in the Operation column in the row that contains the rule.
- To delete one or more rules, select them and click Delete above the rule list.
Searching for a suppression rule
+Enter a rule name in the search box in the upper right corner and click
+
.++ diff --git a/docs/aom/umn/aom_02_0954.html b/docs/aom/umn/aom_02_0954.html new file mode 100644 index 00000000..2ed3168f --- /dev/null +++ b/docs/aom/umn/aom_02_0954.html @@ -0,0 +1,86 @@ + + +++Parent topic: Alarm Noise Reduction+Creating a Silence Rule
++You can shield alarm notifications in a specified period. A silence rule takes effect immediately after it is created.
++Creating a Silence Rule
You can create up to 100 silence rules.
+- In the navigation pane, choose Alarm Center > Alarm Noise Reduction.
- On the Silence Rules tab page, click Create and set parameters such as the rule name and silence condition.Figure 1 Creating a silence rule+ +
+
+Table 1 Setting a silence rule Category
+Parameter
+Description
+-
+Rule Name
+Silence rule name, which can contain up to 100 characters and cannot start or end with an underscore (_). Only letters, digits, and underscores are allowed.
+Description
+Silence rule description, which can contain up to 1024 characters.
+Silence rules
+Silence Condition
+Any alarm notifications that meet the silence condition will be shielded.
+You can create up to 10 parallel conditions under Silence Condition, and up to 10 serial conditions under each parallel condition. Serial conditions are in the AND relationship whereas parallel conditions are in the OR relationship. An alarm must meet all serial conditions under one of the parallel conditions.
+For a serial condition, if Alarm Severity is set to Critical, critical alarms are shielded.
+Silence Time
+Time when alarm notifications are shielded. There are two options:
+- Fixed time: Alarm notifications are shielded only in a specified period.
- Cycle time: Alarm notifications are shielded periodically.
Time Zone/Language
+Time zone and language for which alarm notifications are shielded. The time zone and language configured in Preferences are selected by default. You can change them as required.
+ - Click Create Now.
+More Operations
After creating a silence rule, perform the operations listed in Table 2 if needed.
+ ++
+Table 2 Related operations Operation
+Description
+Modifying a silence rule
+Click Modify in the Operation column.
+Deleting a silence rule
+- To delete a single rule, click Delete in the Operation column in the row that contains the rule.
- To delete one or more rules, select them and click Delete above the rule list.
Searching for a silence rule
+Enter a rule name in the search box in the upper right corner and click
+
.++ diff --git a/docs/aom/umn/aom_02_1011.html b/docs/aom/umn/aom_02_1011.html index 24e5b1da..57725847 100644 --- a/docs/aom/umn/aom_02_1011.html +++ b/docs/aom/umn/aom_02_1011.html @@ -8,11 +8,16 @@++Parent topic: Alarm Noise Reduction+2023-08-09
+2024-07-15
- Added the following sections: -
- Optimized the following sections: -
- Added Service Overview, Getting Started, and FAQs sections.
Added section Upgrading to AOM 2.0.
+2024-04-17
+- Added the following sections: +
- Optimized the following sections: +
- Added sections Service Overview, Getting Started, and FAQs.
2022-09-29
diff --git a/docs/aom/umn/aom_03_0002.html b/docs/aom/umn/aom_03_0002.html index 5898c6cd..fac03c89 100644 --- a/docs/aom/umn/aom_03_0002.html +++ b/docs/aom/umn/aom_03_0002.html @@ -35,7 +35,11 @@2.3 64-bit
2.5 64-bit
+2.5 64-bit
+2.9 64-bit
+2.10 64-bit
CentOS
@@ -95,6 +99,11 @@9.0.0 64-bit
Kylin
+Kylin V10 SP1 64-bit
+
- Using the Paths Automatically Identified by the ICAgent
Number of resources, threshold rules, components, or hosts in a graph
- A maximum of 100 resources across clusters can be added to a line graph.
- Only one resource can be added to a digit graph.
- A maximum of 10 threshold rules can be added to a threshold status graph.
- A maximum of 10 hosts can be added to a host status graph.
- A maximum of 10 components can be added to a component status graph.
- A maximum of 100 resources across clusters can be added to a line 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.
- A maximum of 10 threshold rules can be added to a threshold status graph.
- A maximum of 10 hosts can be added to a host status graph.
- A maximum of 10 components can be added to a component status graph.
Metric
@@ -193,7 +202,7 @@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. That is, the log will be discarded.
+The maximum size of each log is 10 KB. If a log is greater than that, the ICAgent will not collect it. In that case, the log will be discarded.
Log traffic
@@ -226,7 +235,7 @@Log loss
When a single log line exceeds 10,240 bytes, the line will be discarded.
+When a single log line exceeds 1024 bytes, this line will be discarded.
Log repetition
@@ -257,7 +266,7 @@ -diff --git a/docs/aom/umn/aom_03_0005.html b/docs/aom/umn/aom_03_0005.html index 4cb2b1aa..acfefb1a 100644 --- a/docs/aom/umn/aom_03_0005.html +++ b/docs/aom/umn/aom_03_0005.html @@ -1,9 +1,9 @@Service Usage Restrictions
If the AMS-Access service is powered off or restarted unexpectedly when you use AOM, a metric data breakpoint occurs on some resources such as hosts, components, and containers in a collection period. This breakpoint is visible on the monitoring page and has no impacts. To avoid breakpoints in a metric graph, set the value of Interpolation Mode to 0 or average on the Metric Monitoring page. In this way, the system automatically replaces breakpoints with 0 or average values, as shown in Figure 1.
+Service Usage Restrictions
If the AMS-Access service is powered off or restarted unexpectedly when you use AOM, a metric data breakpoint occurs on some resources such as hosts, components, and containers in a collection period. This breakpoint is visible on the monitoring page and has no impacts. To avoid breakpoints in a metric graph, set the value of Interpolation Mode to 0 or average on the Metric Monitoring page. In this way, the system automatically replaces breakpoints with 0 or average values, as shown in Figure 1.
How Do I Distinguish Alarms from Events?
-Similarities Between Alarms and Events
Both alarms and events are the information reported to AOM when the status of AOM or an external service, such as Cloud Container Engine (CCE) changes.
+-Similarities Between Alarms and Events
Both alarms and events are the information reported to AOM when the status of AOM or an external service (such as CCE) changes.
Differences Between Alarms and Events
- Alarms are reported when AOM or an external service, such as CCE is abnormal or may cause exceptions. Alarms must be handled. Otherwise, service exceptions may occur.
- Events generally carry some important information. They are reported when AOM or an external service, such as CCE encounters some changes. Such changes do not necessarily cause service exceptions. Events do not need to be handled.
Differences Between Alarms and Events
- Alarms are reported when AOM or an external service (such as CCE) is abnormal or may cause exceptions. Alarms must be handled. Otherwise, service exceptions may occur.
- Events generally carry some important information. They are reported when AOM or an external service (such as CCE) has some changes. Such changes do not necessarily cause service exceptions. Events do not need to be handled.
diff --git a/docs/aom/umn/aom_03_0006.html b/docs/aom/umn/aom_03_0006.html index 3913efef..8c683377 100644 --- a/docs/aom/umn/aom_03_0006.html +++ b/docs/aom/umn/aom_03_0006.html @@ -20,6 +20,8 @@- What Can I Do If an ICAgent Is Offline?
+
- Why Is "no crontab for root" Displayed During ICAgent Installation?
+diff --git a/docs/aom/umn/aom_03_0010.html b/docs/aom/umn/aom_03_0010.html index 985ecc19..59a55415 100644 --- a/docs/aom/umn/aom_03_0010.html +++ b/docs/aom/umn/aom_03_0010.html @@ -19,7 +19,7 @@@@ -125,7 +134,7 @@Uninstalled
Install the ICAgent according to Installing an ICAgent.
+Installing
@@ -29,7 +29,7 @@Installation failed
Uninstall the ICAgent according to Uninstalling the ICAgent by Logging In to the Server and then install it again.
+Uninstall the ICAgent by logging in to the server and then install it again.
Upgrading
@@ -39,7 +39,7 @@Upgrade failed
Uninstall the ICAgent according to Uninstalling the ICAgent by Logging In to the Server and then install it again.
+Uninstall the ICAgent by logging in to the server and then install it again.
Offline
diff --git a/docs/aom/umn/aom_03_0021.html b/docs/aom/umn/aom_03_0021.html index ad7626cd..51f5c25d 100644 --- a/docs/aom/umn/aom_03_0021.html +++ b/docs/aom/umn/aom_03_0021.html @@ -35,8 +35,6 @@- In the Windows environment, manually add log collection paths. The ICAgent can collect .log, .trace, and .out files, but does not collect binary files or Windows system logs.
What Can I Do If the ICAgent Is Successfully Installed on ECS but Its Status Is Abnormal on the Agent Management Page?
The AK/SK is incorrect, or no agency is set when Installation Mode is set to Create Agency. Perform operations according to and install the ICAgent again.
-diff --git a/docs/aom/umn/aom_03_0024.html b/docs/aom/umn/aom_03_0024.html index 35e5db9c..0dd99734 100644 --- a/docs/aom/umn/aom_03_0024.html +++ b/docs/aom/umn/aom_03_0024.html @@ -13,31 +13,31 @@-Agency Name
Set an agency name.
-NOTE:The agency name must be apm_admin_trust.
+NOTICE:The agency name must be apm_admin_trust.
apm_admin_trust
+-
Agency Type
Select Account.
+Select Cloud service.
Common account
+Cloud service
Delegated Account
+Cloud Service
Specify an account to delegate.
+Select Application Operations Management (AOM).
op_svc_apm
+-
Validity Period
Select Unlimited.
Unlimited
+Unlimited
Description
@@ -50,7 +50,7 @@- On the Permissions area, click Assign Permissions.
- Add the following permissions: DMS User (or DMS UserAccess), CCE Administrator, and ECS User (or ECS CommonOperations), and select a region in Project [Region].
- Click OK.
+- On the Permissions area, click Assign Permissions.
- Select the DMS UserAccess permission, and select the projects where you want the configuration to take effect.
- Click OK.
diff --git a/docs/aom/umn/aom_03_0037.html b/docs/aom/umn/aom_03_0037.html new file mode 100644 index 00000000..65fc169d --- /dev/null +++ b/docs/aom/umn/aom_03_0037.html @@ -0,0 +1,18 @@ + + +Why Is "no crontab for root" Displayed During ICAgent Installation?
+++Symptom
During ICAgent installation, the system displays the message "no crontab for root".
+Figure 1 Installing an ICAgent+
+Possible Causes
When you execute the script for installing an ICAgent, crontab scheduled tasks will also be installed. The message "no crontab for root" indicates that there is no scheduled task of the root user.
++Solution
No measure needs to be taken.
+If the command output contains "ICAgent install success", the ICAgent is successfully installed and O&M data can be collected.
+++ diff --git a/docs/aom/umn/aom_06_0001.html b/docs/aom/umn/aom_06_0001.html index 4b1b7715..a16125af 100644 --- a/docs/aom/umn/aom_06_0001.html +++ b/docs/aom/umn/aom_06_0001.html @@ -35,7 +35,11 @@++Parent topic: Usage FAQs+2.3 64-bit
2.5 64-bit
+2.5 64-bit
+2.9 64-bit
+2.10 64-bit
CentOS
@@ -95,6 +99,11 @@9.0.0 64-bit
Kylin
+Kylin V10 SP1 64-bit
+Number of resources, threshold rules, components, or hosts in a graph
- A maximum of 100 resources across clusters can be added to a line graph.
- Only one resource can be added to a digit graph.
- A maximum of 10 threshold rules can be added to a threshold status graph.
- A maximum of 10 hosts can be added to a host status graph.
- A maximum of 10 components can be added to a component status graph.
- A maximum of 100 resources across clusters can be added to a line 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.
- A maximum of 10 threshold rules can be added to a threshold status graph.
- A maximum of 10 hosts can be added to a host status graph.
- A maximum of 10 components can be added to a component status graph.
Metric
@@ -193,7 +202,7 @@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. That is, the log will be discarded.
+The maximum size of each log is 10 KB. If a log is greater than that, the ICAgent will not collect it. In that case, the log will be discarded.
Log traffic
@@ -226,7 +235,7 @@Log loss
When a single log line exceeds 10,240 bytes, the line will be discarded.
+When a single log line exceeds 1024 bytes, this line will be discarded.
Log repetition
@@ -257,7 +266,7 @@ -diff --git a/docs/aom/umn/aom_06_0002.html b/docs/aom/umn/aom_06_0002.html index a7bad6f2..576df018 100644 --- a/docs/aom/umn/aom_06_0002.html +++ b/docs/aom/umn/aom_06_0002.html @@ -3,7 +3,7 @@Service Usage Restrictions
If the AMS-Access service is powered off or restarted unexpectedly when you use AOM, a metric data breakpoint occurs on some resources such as hosts, components, and containers in a collection period. This breakpoint is visible on the monitoring page and has no impacts. To avoid breakpoints in a metric graph, set the value of Interpolation Mode to 0 or average on the Metric Monitoring page. In this way, the system automatically replaces breakpoints with 0 or average values, as shown in Figure 1.
+Service Usage Restrictions
If the AMS-Access service is powered off or restarted unexpectedly when you use AOM, a metric data breakpoint occurs on some resources such as hosts, components, and containers in a collection period. This breakpoint is visible on the monitoring page and has no impacts. To avoid breakpoints in a metric graph, set the value of Interpolation Mode to 0 or average on the Metric Monitoring page. In this way, the system automatically replaces breakpoints with 0 or average values, as shown in Figure 1.
Basic Concepts
Metrics
Metrics reflect resource performance data or status. A metric consists of a namespace, dimension, name, and unit.
Metric namespaces can be regarded as containers for storing metrics. Metrics in different namespaces are independent of each other so that metrics of different applications will not be aggregated to the same statistics information. Each metric has certain features, and a dimension may be considered as a category of such features. Figure 1 describes the relationships among namespaces, dimensions, and cluster metrics.
- +diff --git a/docs/aom/umn/aom_06_0005.html b/docs/aom/umn/aom_06_0005.html index 3d48a0a0..b75c9cb9 100644 --- a/docs/aom/umn/aom_06_0005.html +++ b/docs/aom/umn/aom_06_0005.html @@ -15,7 +15,9 @@Hosts
Each host of AOM corresponds to a VM or physical machine. A host can be your own VM or physical machine, or a VM (for example, an ECS) that you created. A host can only be connected to AOM for monitoring when its OS is supported by AOM and an ICAgent has been installed on the host.
-Alarm Management
The alarm list helps you manage alarms and events.
You can create threshold rules for key resource metrics. When the metric value reaches the threshold, AOM will generate alarms.
Log Management
AOM provides powerful log management capabilities. Log search enables you to quickly search for required logs from massive quantities of logs. Log dump enables you to store logs for a long time. After you create statistical rules, AOM can periodically count keywords in logs and generate metric data, so that you can monitor system performance and services in real time. By configuring delimiters, you can divide log content into multiple words and use these words to search for logs.
++Log Management
AOM provides powerful log management capabilities. Log search enables you to quickly search for required logs from massive quantities of logs. Log dump enables you to store logs for a long period. By configuring delimiters, you can divide log content into multiple words and use these words to search for logs.
+Metric Browsing
The Metric Browsing page displays metric data of each resource. You can monitor metric values and trends in real time, and create alarm rules for desired metrics. In this way, you can monitor services in real time and perform data correlation analysis.
diff --git a/docs/aom/umn/aom_06_0010.html b/docs/aom/umn/aom_06_0010.html index 09165a08..398132da 100644 --- a/docs/aom/umn/aom_06_0010.html +++ b/docs/aom/umn/aom_06_0010.html @@ -149,7 +149,7 @@Byte/s
Total physical memory (aom_cluster_memory_total_megabyte)
+Total physical memory (aom_cluster_memory_total_megabytes)
Total physical memory that has been applied for a measured object
Product Architecture
AOM is a multi-dimensional O&M platform that focuses on resource data and associates log, metric, resource, alarm, and event data. It consists of the data collection and access layer, transmission and storage layer, and service computing layer.
-Architecture Description
- Data collection and access layer
- Collecting data by using ICAgent
You can install the ICAgent (a plug-in data collector) on a host and use it to report O&M data.
+diff --git a/docs/aom/umn/aom_06_0014.html b/docs/aom/umn/aom_06_0014.html index eef94d26..a08bcc30 100644 --- a/docs/aom/umn/aom_06_0014.html +++ b/docs/aom/umn/aom_06_0014.html @@ -2,7 +2,7 @@Architecture Description
- Data collection and access layer -
- Transmission and storage layer
- Data transmission: AOM Access is a proxy for receiving O&M data. After O&M data is received, such data will be placed in the Kafka queue. Kafka then transmits the data to the service computing layer in real time based on its high-throughput capability.
- Data storage: After being processed by the AOM backend, O&M data is written into a database. Cassandra stores sequential data, Redis is used for cache query, etcd stores AOM configuration data, and Elasticsearch stores resources, logs, alarms, and events.
- Transmission and storage layer
- Data transmission: AOM Access is a proxy for receiving O&M data. After O&M data is received, such data will be placed in the Kafka queue. Kafka then transmits the data to the service computing layer in real time based on its high-throughput capability.
- Data storage: After being processed by the AOM backend, O&M data is written into databases. Cassandra stores metric data of time series, Redis is used for cache query, etcd stores AOM configuration data, and Elasticsearch stores resources, logs, alarms, and events.
- Service computing layer
AOM provides basic O&M services such as alarm management, log management, and resource monitoring (such as metric monitoring).
Introduction
Metrics reflect resource performance data or status. A metric consists of a namespace, dimension, name, and unit. Metrics can be divided into:
-- System metrics: basic metrics provided by AOM, such as CPU usage and used CPU cores.
- Custom metrics: user-defined metrics. Custom metrics can be reported using the following methods:
- Method 1: Use AOM APIs. For details, see "Adding Monitoring Data" and "Querying Monitoring Data" in the Application Operations Management (AOM) API Reference.
- Method 2: When creating containerized applications on CCE, interconnect with Prometheus to report custom metrics. For details, see "Custom Monitoring" in Cloud Container Engine (CCE) User Guide.
- System metrics: basic metrics provided by AOM, such as CPU usage and used CPU cores.
- Custom metrics: user-defined metrics. Custom metrics can be reported using the following methods:
- Method 1: Use AOM APIs. For details, see "Adding Monitoring Data" and "Querying Monitoring Data" in the Application Operations Management (AOM) API Reference.
- Method 2: When creating containerized applications on CCE, interconnect with Prometheus to report custom metrics. For details, see "Custom Monitoring" in Cloud Container Engine (CCE) User Guide.
Metric Namespaces
A namespace is an abstract collection of resources and objects. Metrics in different namespaces are independent of each other so that metrics of different applications will not be aggregated to the same statistics information.
- Namespaces of system metrics are fixed and started with PAAS.. For details, see Table 1. diff --git a/docs/aom/umn/aom_06_0015.html b/docs/aom/umn/aom_06_0015.html index d8fd7654..7400027d 100644 --- a/docs/aom/umn/aom_06_0015.html +++ b/docs/aom/umn/aom_06_0015.html @@ -23,7 +23,7 @@
- Collecting data by using ICAgent
Downlink rate (PPS) (aom_node_network_receive_packets)
Number of data packets received by an NIC per second
+Number of data packets received by a NIC per second
≥ 0
Downlink error rate (aom_node_network_receive_error_packets)
Number of error packets received by an NIC per second
+Number of error packets received by a NIC per second
≥ 0
Uplink error rate (aom_node_network_transmit_error_packets)
Number of error packets sent by an NIC per second
+Number of error packets sent by a NIC per second
≥ 0
Uplink rate (PPS) (aom_node_network_transmit_packets)
Number of data packets sent by an NIC per second
+Number of data packets sent by a NIC per second
≥ 0
Cluster namespace
netDevice
+netDevice
NIC name
Cluster name
fileSystem
+fileSystem
File system
Host ID
mountPoint
+mountPoint
Mount point
Used physical memory (aom_container_memory_used_megabytes)
Used physical memory of a measured object
-NOTE:If the cluster version is 1.2.1 or later, this metric indicates the used working set memory and is equivalent to container_memory_working_set_bytes on the CCE console.
-≥ 0
Downlink rate (PPS) (aom_container_network_receive_packets)
Number of data packets received by an NIC per second
+Number of data packets received by a NIC per second
≥ 0
Downlink error rate (aom_container_network_receive_error_packets)
Number of error packets received by an NIC per second
+Number of error packets received by a NIC per second
≥ 0
Uplink error rate (aom_container_network_transmit_error_packets)
Number of error packets sent by an NIC per second
+Number of error packets sent by a NIC per second
≥ 0
Uplink rate (PPS) (aom_container_network_transmit_packets)
Number of data packets sent by an NIC per second
+Number of data packets sent by a NIC per second
≥ 0
Permissions
If you need to assign different permissions to employees in your enterprise to access your AOM resources, Identity and Access Management (IAM) is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, helping you secure access to your AOM resources.
-With IAM, you can use your account to create IAM users for your employees, and assign permissions to the users to control their access to specific types of resources. For example, some software developers in your enterprise need to use AOM resources but must not delete them or perform any high-risk operations such as deleting application discovery rules. To achieve this result, you can create IAM users for the software developers and grant them only the permissions required for using AOM resources.
-If your account does not need individual IAM users for permissions management, you may skip over this chapter.
+With IAM, you can use your account to create IAM users for your employees, and assign permissions to the users to control their access to specific types of resources. For example, some software developers in your enterprise need to use AOM resources but are not allowed to delete them or perform any high-risk operations such as deleting application discovery rules. To achieve this result, you can create IAM users for the software developers and grant them only the permissions required for using AOM resources.
+If your cloud account does not need individual IAM users for permissions management, you may skip over this chapter.
IAM can be used free of charge. You pay only for the resources in your account. For more information about IAM, see IAM Service Overview.
AOM Permissions
By default, new IAM users do not have any permissions assigned. You need to add a user to one or more groups, and assign permissions policies or roles to these groups. The user then inherits permissions from the groups it is a member of. This process is called authorization. After authorization, the user can perform specified operations on AOM.
AOM is a project-level service deployed and accessed in specific physical regions. To assign AOM permissions to a user group, specify the scope as region-specific projects and select projects for the permissions to take effect. If All projects is selected, the permissions will take effect for the user group in all region-specific projects. When accessing AOM, the users need to switch to a region where they have been authorized to use this service.
@@ -20,7 +20,7 @@AOM Admin
+AOM Admin
Administrator permissions for AOM. Users granted these permissions can operate and use AOM.
CCE Administrator, OBS Administrator, and LTS FullAccess
AOM Viewer
+AOM Viewer
Read-only permissions for AOM. Users granted these permissions can only view AOM data.
-Table 2 Common operations supported by each system-defined policy of AOM Operation
AOM Admin
+AOM Admin
AOM Viewer
+AOM Viewer
x
Creating a dashboard
-√
-x
-Modifying a dashboard
-√
-x
-Deleting a dashboard
-√
-x
-Creating an application discovery rule
√
@@ -148,48 +127,6 @@x
Viewing bucket logs
-√
-√
-Adding a log dump
-√
-x
-Modifying a log dump
-√
-x
-Deleting a log dump
-√
-x
-Starting periodical dump
-√
-x
-Stopping periodical dump
-√
-x
-Configuring a delimiter
√
@@ -221,7 +158,7 @@To use a custom fine-grained policy, log in to IAM as the administrator and select fine-grained permissions of AOM as required. For details about fine-grained permissions of AOM, see Table 3.
+To use a custom fine-grained policy, log in to IAM as the administrator and select fine-grained permissions of AOM as required. For details, see Table 3
Table 3 Fine-grained permissions of AOM Permission Name
- Select the target dashboard and click
- Custom: The default online duration is 1 hour. You can enter 1–24 (unit: hour) in the text box.
