Monitored Object
diff --git a/docs/ces/umn/ces_01_0017.html b/docs/ces/umn/ces_01_0017.html new file mode 100644 index 00000000..6ce4a700 --- /dev/null +++ b/docs/ces/umn/ces_01_0017.html @@ -0,0 +1,19 @@ + + +Creating a Resource Group
+Scenarios
If you use multiple cloud services, you can add all related resources, such as ECSs, BMSs, EVS disks, elastic IP addresses, bandwidths, and databases to the same resource group for easier management and O&M.
+Restrictions
- Each user can create up to 10 resource groups.
- A resource group must contain 1 to 200 cloud service resources.
- There are restrictions on the number of resources of different types that can be added to a resource group. For details, see the tips on the Cloud Eye console.
Procedure
- Log in to the management console.
- In the upper left corner, select a region and project.
- Click Service List in the upper left corner, and select Cloud Eye.
- In the navigation pane on the left, choose Resource Groups.
- In the upper right corner, click Create Resource Group.
- Enter the group name.
- Select the target cloud service resources. +
- Click Create.
Viewing Resource Groups
+-
+
- Resource Group List
+
+ - Resource Overview
+
+ - Unhealthy Resources
+
+ - Alarm Rules
+
+ - Alarm History
+
+
Resource Group List
+The resource group list displays all resource groups you have on Cloud Eye, the resources they contain, and the health status of each resource group.
+Procedure
- Log in to the management console.
- In the upper left corner, select a region and project.
- Click Service List in the upper left corner, and select Cloud Eye.
- In the navigation pane on the left, choose Resource Groups.On the Resource Groups page, you can view all the resource groups that have been created. +++
+Table 1 Parameters of the resource group list Parameter
+Description
+Name/ID
+Specifies the resource group name and ID.
+NOTE:+The group name can contain a maximum of 128 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.
+Health Status
+- Healthy: No alarms have been generated for the group.
- Unhealthy: An alarm or alarms have been generated for a resource or resources in the group.
- No alarm rule: No alarm rules have been set for the group.
Unhealthy Resources
+Specifies the number of resources in a group whose alarms have been triggered. For example, if there are two ECSs and one EVS disk that are in the Alarm state in a resource group, Unhealthy Resources is 3.
+Total Resources
+Specifies the number of resources in a group. For example, if there are four resources, namely, two ECSs, one EVS disk, and one elastic IP address in a resource group, Total Resources is 4.
+Resource Types
+Specifies the number of different resource types in a group. For example, if there are two ECSs and one EVS disk in a resource group, then there are two types of resources and Resource Types is 2.
+Created
+Specifies the time when the resource group was created.
+Operation
+Specifies the operations that can be performed on a resource group. You can only modify or delete a resource group.
+
Resource Overview
+The Resource Overview page displays all resource types in the current group, the number of resources of each resource type, and Resource Monitoring Preview (Metrics in the Alarm State).
+
Procedure
- Log in to the management console.
- In the upper left corner, select a region and project.
- Click Service List in the upper left corner, and select Cloud Eye.
- In the navigation pane on the left, choose Resource Groups.
- Click a resource group name to go to the Resource Overview page.
Unhealthy Resources
+Unhealthy Resources includes all resources in the Alarm state in a resource group. This feature enables you to quickly view all unhealthy resources and handle faults.
+Procedure
- Log in to the management console.
- In the upper left corner, select a region and project.
- Click Service List in the upper left corner, and select Cloud Eye.
- In the navigation pane on the left, choose Resource Groups.
- Click a resource group name to go to the Resource Overview page.
- In the navigation pane on the left, choose Unhealthy Resources to view all resources in the resource group for which alarms have been triggered.
Alarm Rules
+The Alarm Rules page displays all alarm rules in a resource group. You can enable, disable, modify, or delete alarm rules.
+Procedure
- Log in to the management console.
- In the upper left corner, select a region and project.
- Click Service List in the upper left corner, and select Cloud Eye.
- In the navigation pane on the left, choose Resource Groups.
- Click a resource group name to go to the Resource Overview page.
- In the navigation pane on the left, choose Alarm Rules to view all alarm rules in the resource group.
Alarm History
+The Alarm History page displays the alarm history of all alarm rules in a group.
+Procedure
- Log in to the management console.
- In the upper left corner, select a region and project.
- Click Service List in the upper left corner, and select Cloud Eye.
- In the navigation pane on the left, choose Resource Groups.
- Click a resource group name to go to the Resource Overview page.
- In the navigation pane on the left, choose Alarm History to view the alarm history of all resources in the resource group.
Managing Resource Groups
+If your cloud service requirements change, you may need to modify the resources in a resource group.
+This topic describes how to modify or delete a resource group.
+Modifying a Resource Group
+When you need to add resources to or delete resources from a resource group, modify the resource group.
+Procedure
- Log in to the management console.
- In the upper left corner, select a region and project.
- Click Service List in the upper left corner, and select Cloud Eye.
- In the navigation pane on the left, choose Resource Groups.
- Locate the row containing the target resource group and click Modify in the Operation column.
- On the displayed Modify Resource Group page, modify the resource group.
- Click Modify.
Deleting a Resource Group
+Procedure
- Log in to the management console.
- In the upper left corner, select a region and project.
- Click Service List in the upper left corner, and select Cloud Eye.
- In the navigation pane on the left, choose Resource Groups.
- Locate the row containing the target resource group and click Delete in the Operation column.
- In the displayed Delete Resource Group dialog box, click Yes.
Agent Installation and Configuration
+Based on the OS you are going to use, server quantity, and personal habits, install the Agent by choosing one or more of the following scenarios:
+ +Scenario + |
+Supported Service + |
+Reference + |
+
|---|---|---|
Installing the Agent on a Linux server + |
+ECS and BMS + |
++ | +
Installing the Agent on a Windows server + |
+ECS + |
++ | +
Installing the Agent in batches on Linux servers + |
+ECS + |
++ | +
Agent installation and configuration description:
+- To successfully install the Agent, ensure that both DNS and security group rules are correctly configured.
- After you install the Agent, you can click Restore Agent Configurations on the Cloud Eye console to complete the agency and Agent configuration.
- If the Agent fails to be configured by clicking Restore Agent Configurations or due to other reasons, manually configure it.
Installing the Agent on a Linux Server
+Scenarios
This topic describes how to manually install the Agent on a Linux ECS or BMS.
+Prerequisites
- You have the read and write permissions for the installation directories in Procedure. The Telescope process will not be stopped by other software after the installation.
- You have performed operations described in Modifying the DNS Server Address and Adding Security Group Rules (Linux).
Procedure
- Log in to the ECS or BMS as user root.
- Run the following command to install the Agent:
+
cd /usr/local && wget https://telescope-eu-de.obs.eu-de.otctest.t-systems.com/scripts/agentInstall.sh && chmod 755 agentInstall.sh && ./agentInstall.sh
+The Agent is installed if the following command output is displayed.+Figure 1 Successful installation+
- Configure the Agent by referring to Restoring the Agent Configurations on a Linux Server or (Optional) Manually Configuring the Agent (Linux).+
- Restoring Agent Configurations allows you to configure AK/SK, RegionID, and ProjectId in just a few clicks. You can also modify related configuration files by referring to (Optional) Manually Configuring the Agent (Linux).
- Agent configuration restoration cannot be performed on BMSs. For details about how to modify the Agent configuration file on a BMS, see (Optional) Manually Configuring the Agent (Linux).
- Run the following command to clear the installation script:
if [[ -f /usr/local/uniagent/extension/install/telescope/bin/telescope ]]; then rm /usr/local/agent_install.sh; else rm /usr/local/agentInstall.sh; fi
+
Restoring the Agent Configurations on a Linux Server
+Scenarios
This topic describes how to restore the Agent configurations on the Cloud Eye console (recommended).
+ - The Restore Agent Configurations option is unavailable for BMSs. For details, see (Optional) Manually Configuring the Agent (Linux).
- After you configure the Agent, its status is still displayed as Not installed because no monitoring data is reported yet. Wait 3 to 5 minutes and refresh the page.
- If the Agent is in the Running state, the Agent has been installed and has started to collect fine-grained metric data.
Restoring the Agent Configurations
- Log in to the management console.
- Click Service List in the upper left corner, and select Cloud Eye. In the navigation pane on the left, choose Server Monitoring.
- On the Server Monitoring page, select a server that has the Agent installed.
- Click Restore Agent Configurations.
- In the displayed Restore Agent Configurations dialog box, click One-Click Restore.
If the Agent status changes to Running, the Agent has been installed and has started to collect fine-grained metric data.
+
(Optional) Manually Configuring the Agent (Linux)
+Scenarios
After you install the Agent, configure it by clicking Restore Agent Configurations on the Cloud Eye console. If the Agent fails to be configured by clicking Restore Agent Configurations or due to other reasons, manually configure it by following the instructions provided in this topic.
+This topic takes an ECS as an example. The operations for BMSs are similar.
+Prerequisites
The Agent has been installed.
+Procedure
- Log in to an ECS as user root.
- Run the following command to go to the Agent installation path bin:
cd /usr/local/telescope/bin
+ - Modify configuration file conf.json.
- Run the following command to open conf.json:
vi conf.json
+ - Modify the parameters in the file. For details, see Table 1.
ECS parameters
+{ + "InstanceId":"XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX", + "ProjectId": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", + "AccessKey": "XXXXXXXXXXXXXXXXXXXX", + "SecretKey": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", + "RegionId": "eu-de", + "ClientPort": 0, + "PortNum": 200 +}+BMS parameters
+{ + "InstanceId":"XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX", + "ProjectId": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", + "AccessKey": "XXXXXXXXXXXXXXXXXXXX", + "SecretKey": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", + "RegionId": "eu-de", + "ClientPort": 0, + "PortNum": 200, + "BmsFlag": true +}+ ++
+Table 1 Public parameters Parameter
+Description
+InstanceId
+(Optional) Specifies the ECS ID. You can log in to the management console and view the ECS ID in the ECS list.
+NOTE:+If you do not configure InstanceId, retain "InstanceId":"".
+If you configure it, ensure that the following two requirements are met:
+- The ECS ID must be unique at all sites, that is, in the same region, InstanceId used by the Agent cannot be the same. Otherwise, errors may occur.
- The InstanceId value must be consistent with the actual ECS or BMS ID. Otherwise, you cannot see the OS monitoring data on Cloud Eye.
ProjectId
+(Optional) Specifies the project ID.
+If you do not configure ProjectId, retain "ProjectId": "".
+If you configure it, perform the following operations:
+- Log in to the Cloud Eye console, click the username in the upper right corner, and choose My Credentials.
- Under Projects, obtain the project ID for the region where the ECS or BMS is located.
AccessKey/SecretKey
+To obtain the AK and SK, perform the following operations:
+Log in to the Cloud Eye console, click the username in the upper right corner, and choose My Credentials, and choose Access Keys.
+- If you have obtained the access key, obtain the AccessKey value and the SecretKey value in the credentials.csv file saved when you create Access Keys.
- If no access keys are available, click Create Access Key to create one. Save the credentials.csv file and obtain the AccessKey value and the SecretKey value in it.NOTICE:+
- For security purposes, it is recommended that the user be an IAM user with the CES Administrator permissions only.
RegionId
+Specifies the region ID. For example, if the ECS is located in region EU DE, RegionId is eu-de.
+ClientPort
+Specifies the start port number used by the Agent.
+NOTE:+The default value is 0, indicating that the Agent will randomly use any port. Ports 1 to 1023 are reserved. You are advised not to specify a port in this range for the Agent.
+PortNum
+Specifies the number of ports configured for the Agent.
+NOTE:+The default value is 200. If ClientPort is 5000, the port range will be 5000 to 5199.
+BmsFlag
+Set this parameter to true for a BMS. This parameter is not required by an ECS.
+You do not need to set this parameter for the Windows OS.
+
- Run the following command to open conf.json:
- Modify configuration file conf_ces.json for the Cloud Eye metric collection module.
- Run the following command to open public configuration file conf_ces.json:
vi conf_ces.json
+ - Modify the endpoint in conf_ces.json, and save the conf_ces.json file. For details, see Table 2.
{ + "Endpoint": "https://ces.eu-de.otc.t-systems.com" +}+ ++
+Table 2 Parameter setting of the metric collection module Parameter
+Description
+Endpoint
+Specifies the Cloud Eye endpoint URL in the region of the ECS or BMS. For example, if the ECS or BMS is located in region EU-DE, Endpoint is ces.eu-de.otc.t-systems.com.
++ - After you configure the Agent, its status is still displayed as Uninstalled because no monitoring data is reported yet. Wait 3 to 5 minutes and refresh the page.
- If the Agent is in the Running state, the Agent has been installed and has started to collect fine-grained metric data.
- Run the following command to open public configuration file conf_ces.json:
(Optional) Manually Configuring the Agent on a Windows Server
+Scenarios
After you install the Agent, configure it by clicking Restore Agent Configurations on the Cloud Eye console. If the Agent fails to be configured by clicking Restore Agent Configurations or due to other reasons, manually configure it by following the instructions provided in this topic.
+Constraints
The Agent cannot be installed on Windows BMSs.
+Prerequisites
The Agent has been installed.
+Procedure
- Log in to the ECS.
- Open the conf.json file in the telescope_windows_amd64\bin folder.
- Configure the following parameters. For details, see Table 1.
{ + "InstanceId":"", + "ProjectId": "", + "AccessKey": "", + "SecretKey": "", + "RegionId": "eu-de", + "ClientPort": 0, + "PortNum": 200 +}+ + ++
+Table 1 Public parameters Parameter
+Description
+InstanceId
+(Optional) Specifies the ECS ID. You can log in to the management console and view the ECS ID in the ECS list.
+NOTE:+If you do not configure InstanceId, retain "InstanceId":"". If you configure it, ensure that the following two requirements are met:
+- The ECS ID must be unique at all sites, that is, in the same region, InstanceId used by the Agent cannot be the same. Otherwise, errors may occur.
- The InstanceId value must be consistent with the actual ECS or BMS ID. Otherwise, you cannot see the OS monitoring data on Cloud Eye.
ProjectId
+Specifies the project ID. You do not need to configure ProjectId. Retain "ProjectId": "". If you wish to configure it,
+perform the following operations:
+- Log in to the Cloud Eye console, click the username in the upper right corner, and choose My Credentials.
- Under Projects, obtain the project ID for the region where the ECS or BMS is located.
AccessKey/SecretKey
+To obtain the AK and SK, perform the following operations:
+Log in to the Cloud Eye console, click the username in the upper right corner, and choose My Credentials, and choose Access Keys.
+- If you have obtained the access key, obtain the AccessKey value and the SecretKey value in the credentials.csv file saved when you create Access Keys.
- If no access keys are available, click Create Access Key to create one. Save the credentials.csv file and obtain the AccessKey value and the SecretKey value in it.NOTICE:+
- For security purposes, it is recommended that the user be an IAM user with the CES Administrator permissions only.
RegionId
+Specifies the region ID. For example, if the ECS is located in region EU DE, RegionId is eu-de.
+ClientPort
+Specifies the start port number used by the Agent.
+NOTE:+The default value is 0, indicating that the Agent will randomly use any port. Ports 1 to 1023 are reserved. You are advised not to specify a port in this range for the Agent.
+PortNum
+Specifies the number of ports configured for the Agent.
+NOTE:+The default value is 200. If ClientPort is 5000, the port range will be 5000 to 5199.
+ - Wait for a few minutes.
If Agent Status is Running, the Agent has been installed and starts to collect fine-grained metric data.
+
Installing the Agents in Batches on Linux ECSs
+Scenarios
This topic describes how to batch install the Agents on Linux ECSs.
+Operation
After binding an elastic IP address (EIP) to an ECS, use the ECS as the execution node and run scripts in batches to copy, decompress, and install the Agent package and configuration file to other ECSs (target nodes).
+
- The target nodes in one batch must be deployed in the same VPC.
- For servers running Windows OSs, Agents cannot be installed in batches.
- Agents cannot be installed in batches on BMSs.
Prerequisites
- During the creation, all ECSs use the same PEM file. Upload the PEM file to the /usr/local directory of the ECS on which the Agent has been installed, and name the file user.pem.
- The IP addresses of all ECSs (target nodes) have been listed in a iplist.txt file and uploaded to the /usr/local directory on the execution node.+
In the iplist.txt file, list each IP address on a separate line:
+192.168.1.1 +192.168.1.2
+
Procedure
- Log in to the execution node as user root.
- Run the following commands to set the permission for user.pem to 0600 and download the batch installation script:
cd /usr/local && chmod 0600 user.pem && wget http://telescope-eu-de.obs.eu-de.otctest.t-systems.com/scripts/batchInstall && chmod +x batchInstall
+ - Run the following command to install the Agent on the execution and target nodes:
cd /usr/local && ./batchInstall -pem -c "wget https://telescope-eu-de.obs.eu-de.otctest.t-systems.com/scripts/agentInstall.sh && chmod 755 agentInstall.sh && ./agentInstall.sh"
+ - After the installation completes, log in to the Cloud Eye console.
- In the navigation pane on the left, choose Server Monitoring.View the list of ECSs on which the Agents have been installed.++
After you configure the Agent, its status is still displayed as Uninstalled because the monitoring data is not reported yet. Wait 3 to 5 minutes and refresh the page.
+ - On the Server Monitoring page, select all ECSs and click Restore Agent Configurations.
- Click One-Click Restore.
Managing the Agent
+This topic describes how to manage the Agent, including how to view, start, stop, and uninstall the Agent.
+Managing the Agent (Linux)
+ To view, start, stop, update, and uninstall the Agent, you must log in as user root.
+Checking the Agent Status
Log in to an ECS or BMS as user root and run the following command to check the Agent status:
+service telescoped status
+The following message indicates that the Agent is running properly:
+"Active (running) or "Telescope process is running well."+
Starting the Agent
/usr/local/telescope/telescoped start
+Restarting the Agent
/usr/local/telescope/telescoped restart
+Stopping the Agent
Log in to an ECS or BMS and run the following command to stop the Agent:
+service telescoped stop
+ If the Agent installation fails, it may be impossible to stop the Agent normally. In this case, run the following command to stop the Agent:
+/usr/local/telescope/telescoped stop
+Uninstalling the Agent
Run the following command to uninstall the Agent:
+/usr/local/telescope/uninstall.sh
+ You can manually uninstall the Agent. After the uninstallation, Cloud Eye does not collect the ECS or BMS monitoring data every one minute. To use the Agent again, reinstall it by referring to Installing and Configuring the Agent on a Linux ECS or BMS. Before reinstalling the Agent, manually delete the previous Agent installation package.
+Managing the Agent (Windows)
+The default installation path of the Agent is C:\Program Files\telescope.
+Checking the Agent Status
In the task manager, check the status of the telescope process.
+Starting the Agent
In the directory where the Agent installation package is stored, double-click the start.bat script.
+Stopping the Agent
In the directory where the Agent installation package is stored, double-click the shutdown.bat script.
+Uninstalling the Agent
In the directory where the Agent installation package is stored, double-click the uninstall.bat script.
+ Before reinstalling the Agent, manually delete the previous Agent installation package.
+Process Monitoring
+Creating an Alarm Rule to Monitor a Server
+Scenarios
This topic describes how to create an alarm rule for an ECS or BMS.
+Procedure
- Log in to the management console.
- In the upper left corner, select a region and project.
- Click Service List in the upper left corner, and select Cloud Eye.
- In the navigation pane on the left, choose Server Monitoring.
- Locate the target ECS or BMS. In the Operation column, click More, and select Create Alarm Rule.
- On the Create Alarm Rule page, follow the prompts to configure the parameters.
- Configure the alarm rule name and description.
++
+Table 1 Alarm rule Name and Description Parameter
+Description
+Name
+Specifies the alarm rule name. The system generates a random name, which you can modify.
+Example value: alarm-b6al
+Description
+(Optional) Provides supplementary information about the alarm rule.
+ - You do not need to set the monitored object because it is the current ECS.
- In the Select Metric step, select Create manually and configure parameters based on Table 2.
++
+Table 2 Parameters Parameter
+Description
+Example Value
+Method
+Specifies the means you use to create the alarm rule.
+Create manually
+Metric
+For details about basic monitoring metrics, see Services Interconnected with Cloud Eye.
+N/A
+Mount Point or Disk
+This parameter is mandatory when the metric is a fine-grained disk metric.
+For the Windows OS, enter a drive letter, such as C, D, or E. For the Linux OS, enter a mount point, such as /dev or /opt.
+/dev
+Alarm Policy
+Specifies the policy for triggering an alarm.
+For example, an alarm is triggered if the average value of the monitored metric is 80% or more for three consecutive 5-minute periods.
+N/A
+Alarm Severity
+Specifies the alarm severity, which can be Critical, Major, Minor, or Informational.
+Major
+Alarm Notification
+Specifies whether to notify users when alarms are triggered. Notifications can be sent by email, text message, or HTTP/HTTPS message.
+You can enable (recommended) or disable this function.
+Enable
+Topic
+Specifies the name of the topic the alarm notification is to be sent to.
+If you have enabled Alarm Notification, select a topic. If no desirable topics are available, create one first, whereupon the SMN service is invoked. For details about how to create a topic, see the Simple Message Notification User Guide.
+N/A
+Validity Period
+Cloud Eye sends notifications only within the validity period specified in the alarm rule.
+If Validity Period is set to 00:00-8:00, Cloud Eye sends notifications only within 00:00-8:00.
+N/A
+Trigger Condition
+Specifies the condition for triggering the alarm notification. You can select Generated alarm (when an alarm is generated), Cleared alarm (when an alarm is cleared), or both.
+N/A
+ - Click Create.
- Configure the alarm rule name and description.
+
After the alarm rule is created, if the metric data reaches the specified threshold, Cloud Eye immediately informs you that an exception has occurred.
+Event Monitoring
+Viewing Event Monitoring Data
+Scenarios
This topic describes how to view the event monitoring data.
+Procedure
- Log in to the management console.
- Click Service List in the upper left corner, and select Cloud Eye.
- In the navigation pane on the left, choose Event Monitoring.
On the displayed Event Monitoring page, all system events generated in the last 24 hours are displayed by default.
+You can also click 1h, 3h, 12h, 1d, 7d, or 30d to view events generated in different periods.
+ + - Expand an event, and click View Event in the Operation column to view details about a specific event.
Creating an Alarm Rule to Monitor an Event
+Scenarios
This topic describes how to create an alarm rule to monitor an event.
+Procedure
- Log in to the management console.
- Click Service List in the upper left corner, and select Cloud Eye.
- In the navigation pane on the left, choose Event Monitoring.
- Click Create Alarm Rule.
- Specify resource type and event type.Figure 1 Creating a alarm rule+
+++
+Table 1 Parameter description Parameter
+Description
+Name
+Specifies the alarm rule name. The system generates a random name, which you can modify.
+Description
+(Optional) Provides supplementary information about the alarm rule.
+Resource Type
+Specifies the type of the resource the alarm rule is created for.
+Dimension
+Specifies the metric dimension of the selected resource type.
+Example value: System event
+Method
+It is fixed to Configure manually.
+Event Source
+Specifies the service the event is generated for.
+Example value: Elastic Cloud Server
+Event Name
+Specifies the instantaneous operations users performed on resources, such as login and logout.
+For events supported by event monitoring, see Events Supported by Event Monitoring.
+Example value: Delete ECS
+Monitoring Scope
+Specifies the monitoring scope for event monitoring.
+Example value: All resources
+Trigger Mode
+You can select immediate trigger or accumulative trigger based on the operation severity.
+Example value: Immediate trigger
+Alarm Severity
+Specifies the alarm severity, which can be Critical, Major, Minor, or Informational.
+Example value: Major
+ - Enable the alarm notification function and set event alarm parameters.Figure 2 Create Alarm Rule+ +
+
+Table 2 Parameter description Parameter
+Description
+Alarm Notification
+Specifies whether to notify users when alarms are triggered. Notifications can be sent by email, text message, or HTTP/HTTPS message.
+Validity Period
+Cloud Eye sends notifications only within the validity period specified in the alarm rule.
+If Validity Period is set to 08:00-20:00, Cloud Eye sends notifications only within 08:00-20:00.
+Notification Object
+- Account contact is the mobile phone number and email address of the registered account.
- Topic: A topic is used to publish messages and subscribe to notifications. If the required topic is unavailable, create one first and add subscriptions to it. For details, see Creating a Topic and Adding Subscriptions.
Trigger Condition
+Specifies the trigger of alarm notifications.
+ - Click Create.
The alarm rule is created.
+
Events Supported by Event Monitoring
+ Events in Event Monitoring come from operations on cloud service resources and are not collected by the Agent in Server Monitoring.
+Event Source + |
+Event Name + |
+Event ID + |
+Event Severity + |
+Description + |
+Solution + |
+Impact + |
+
|---|---|---|---|---|---|---|
ECS + |
+Delete ECS + |
+deleteServer + |
+Major + |
+The ECS was deleted +
|
+Check whether the deletion was performed intentionally by a user. + |
+Services are interrupted. + |
+
Reboot ECS + |
+rebootServer + |
+Minor + |
+The ECS was restarted +
|
+Check whether the restart was performed intentionally by a user. +
|
+Services are interrupted. + |
+|
Resize ECS + |
+resizeServer + |
+Minor + |
+The ECS was resized +
|
+
|
+Services are interrupted. + |
+|
Start auto recovery + |
+startAutoRecovery + |
+Major + |
+ECSs on a faulty host would be automatically migrated to another properly-running host. During the migration, the ECSs was restarted. + |
+Wait for the event to end and check whether services are affected. + |
+Services may be interrupted. + |
+|
Stop auto recovery + |
+endAutoRecovery + |
+Major + |
+The ECS was restored to be normal after the automatic migration. + |
+This event indicates that the ECS has been recovered and been working properly. + |
+None + |
+|
Auto recovery timeout (being processed on the backend) + |
+faultAutoRecovery + |
+Major + |
+Migrating the ECS to a normal host timed out. + |
+Migrate services to other ECSs. + |
+Services are interrupted. + |
+|
Improper ECS running + |
+vmIsRunningImproperly + |
+Major + |
+The ECS was faulty or the ECS NIC was abnormal. + |
+Deploy service applications in HA mode. +After the fault is rectified, check whether services recover. + |
+Services are interrupted. + |
+|
Improper ECS running recovered + |
+vmIsRunningImproperlyRecovery + |
+Major + |
+The ECS was restored to the normal status. + |
+Wait for the ECS status to become normal and check whether services are affected. + |
+None + |
+|
VM faults caused by host process exceptions + |
+VMFaultsByHostProcessExceptions + |
+Critical + |
+The processes of the host accommodating the ECS were abnormal. + |
+Contact O&M personnel. + |
+The ECS is faulty. + |
+|
Restarted GuestOS + |
+RestartGuestOS + |
+Minor + |
+The guest OS was restarted. + |
+Contact O&M personnel. + |
+Services may be interrupted. + |
+
Once a physical host running ECSs breaks down, the ECSs are automatically migrated to a functional physical host. During the migration, the ECSs will be restarted.
+Event Source + |
+Event Name + |
+Event ID + |
+Event Severity + |
+Description + |
+Solution + |
+Impact + |
+
|---|---|---|---|---|---|---|
AAD + |
+DDoS Attack Events + |
+ddosAttackEvents + |
+Major + |
+A DDoS attack occurs in the AAD protected lines. + |
+Judge the impact on services based on the attack traffic and attack type. If the attack traffic exceeds your purchased elastic bandwidth, change to another line or increase your bandwidth. + |
+Services may be interrupted. + |
+
Event Source + |
+Event Name + |
+Event ID + |
+Event Severity + |
+Description + |
+Solution + |
+Impact + |
+
|---|---|---|---|---|---|---|
CBR + |
+Failed to create the backup. + |
+backupFailed + |
+Critical + |
+The backup failed to be created. + |
+Manually create a backup or contact customer service. + |
+Data loss may occur. + |
+
Failed to restore the resource using a backup. + |
+restorationFailed + |
+Critical + |
+The resource failed to be restored using a backup. + |
+Restore the resource using another backup or contact customer service. + |
+Data loss may occur. + |
+|
Failed to delete the backup. + |
+backupDeleteFailed + |
+Critical + |
+The backup failed to be deleted. + |
+Try again later or contact customer service. + |
+Charging may be abnormal. + |
+|
Failed to delete the vault. + |
+vaultDeleteFailed + |
+Critical + |
+The vault failed to be deleted. + |
+Try again later or contact technical support. + |
+Charging may be abnormal. + |
+|
Replication failure + |
+replicationFailed + |
+Critical + |
+The backup failed to be replicated. + |
+Try again later or contact technical support. + |
+Data loss may occur. + |
+|
The backup is created successfully. + |
+backupSucceeded + |
+Major + |
+The backup was created. + |
+None + |
+None + |
+|
Resource restoration using a backup succeeded. + |
+restorationSucceeded + |
+Major + |
+The resource was restored using a backup. + |
+Check whether the data is successfully restored. + |
+None + |
+|
The backup is deleted successfully. + |
+backupDeletionSucceeded + |
+Major + |
+The backup was deleted. + |
+None + |
+None + |
+|
The vault is deleted successfully. + |
+vaultDeletionSucceeded + |
+Major + |
+The vault was deleted. + |
+None + |
+None + |
+|
Replication success + |
+replicationSucceeded + |
+Major + |
+The backup was replicated successfully. + |
+None + |
+None + |
+
Event Source + |
+Event Name + |
+Event ID + |
+Event Severity + |
+Description + |
+Solution + |
+Impact + |
+
|---|---|---|---|---|---|---|
RDS + |
+Full backup failure + |
+fullBackupFailed + |
+Major + |
+A single full backup failure does not affect the files that have been successfully backed up, but prolong the incremental backup time during the point-in-time restore (PITR). + |
+Create a manual backup again. + |
+Backup failed. + |
+
Primary/standby switchover or failover + |
+PrimaryStandbySwitched + |
+Major + |
+This event is reported when a primary/standby switchover or a failover is triggered. + |
+
|
+Downtime occurs during the switchover. + |
+|
Replication status abnormal + |
+abnormalReplicationStatus + |
+Major + |
+The possible causes are as follows: +The replication delay between the primary and standby instances is too long, which usually occurs when a large amount of data is written to databases or a large transaction is processed. During peak hours, data may be blocked. +The network between the primary and standby instances is disconnected. + |
+Submit a service ticket. + |
+Your applications are not affected because this event does not interrupt data read and write. + |
+|
Replication status recovered + |
+replicationStatusRecovered + |
+Major + |
+The replication delay between the primary and standby instances is within the normal range, or the network connection between them has restored. + |
+No action is required. + |
+None + |
+|
DB instance faulty + |
+faultyDBInstance + |
+Major + |
+A single or primary DB instance was faulty due to a disaster or a server failure. + |
+Check whether an automated backup policy has been configured for the DB instance and submit a service ticket. + |
+The database service may be unavailable. + |
+|
DB instance recovered + |
+DBInstanceRecovered + |
+Major + |
+RDS rebuilds the standby DB instance with its high availability. After the instance is rebuilt, this event will be reported. + |
+No action is required. + |
+None + |
+|
Failure of changing single DB instance to primary/standby + |
+singleToHaFailed + |
+Major + |
+A fault occurs when RDS is creating the standby DB instance or configuring replication between the primary and standby DB instances. The fault may occur because resources are insufficient in the data center where the standby DB instance is located. + |
+Submit a service ticket. + |
+Your applications are not affected because this event does not interrupt data read and write of the DB instance. + |
+|
Database process restarted + |
+DatabaseProcessRestarted + |
+Major + |
+The database process is stopped due to insufficient memory or high load. + |
+Log in to the Cloud Eye console. Check whether the memory usage increases sharply, the CPU usage is too high for a long time, or the storage space is insufficient. You can increase the CPU and memory specifications or optimize the service logic. + |
+Downtime occurs. When this happens, RDS automatically restarts the database process and attempts to recover the workloads. + |
+|
Instance storage full + |
+instanceDiskFull + |
+Major + |
+Generally, the cause is that the data space usage is too high. + |
+Scale up the instance. + |
+The DB instance becomes read-only because the storage space is full, and data cannot be written to the database. + |
+|
Instance storage full recovered + |
+instanceDiskFullRecovered + |
+Major + |
+The instance disk is recovered. + |
+No action is required. + |
+Cancel the read-only state of the instance and resume write operations. + |
+|
Read replica promotion failure + |
+activeStandBySwitchFailed + |
+Major + |
+The read replica fails to be promoted to the primary DB instance due to network or server failures. The original primary DB instance takes over workloads quickly. + |
+Submit a service ticket. + |
+The read replica fails to be promoted to the primary DB instance. + |
+
Event Source + |
+Event Name + |
+Event ID + |
+Event Severity + |
+Description + |
+Solution + |
+Impact + |
+
|---|---|---|---|---|---|---|
GaussDB(for MySQL) + |
+Incremental backup failure + |
+TaurusIncrementalBackupInstanceFailed + |
+Major + |
+The network between the instance and the management plane (or the OBS) is disconnected, or the backup environment created for the instance is abnormal. + |
+Submit a service ticket. + |
+Backup jobs fail. + |
+
Read replica creation failure + |
+addReadonlyNodesFailed + |
+Major + |
+The quota is insufficient or underlying resources are exhausted. + |
+Check the read replica quota. Release resources and create read replicas again. + |
+Read replicas fail to be created. + |
+|
DB instance creation failure + |
+createInstanceFailed + |
+Major + |
+The instance quota or underlying resources are insufficient. + |
+Check the instance quota. Release resources and create instances again. + |
+DB instances fail to be created. + |
+|
Read replica promotion failure + |
+activeStandBySwitchFailed + |
+Major + |
+The read replica fails to be promoted to the primary node due to network or server failures. The original primary node takes over services quickly. + |
+Submit a service ticket. + |
+The read replica fails to be promoted to the primary node. + |
+|
Instance specifications change failure + |
+flavorAlterationFailed + |
+Major + |
+The quota is insufficient or underlying resources are exhausted. + |
+Submit a service ticket. + |
+Instance specifications fail to be changed. + |
+|
Faulty DB instance + |
+TaurusInstanceRunningStatusAbnormal + |
+Major + |
+The instance process is faulty or the communications between the instance and the DFV storage are abnormal. + |
+Submit a service ticket. + |
+Services may be affected. + |
+|
DB instance recovered + |
+TaurusInstanceRunningStatusRecovered + |
+Major + |
+The instance is recovered. + |
+Observe the service running status. + |
+None + |
+|
Faulty node + |
+TaurusNodeRunningStatusAbnormal + |
+Major + |
+The node process is faulty or the communications between the node and the DFV storage are abnormal. + |
+Observe the instance and service running statuses. + |
+A read replica may be promoted to the primary node. + |
+|
Node recovered + |
+TaurusNodeRunningStatusRecovered + |
+Major + |
+The node is recovered. + |
+Observe the service running status. + |
+None + |
+|
Read replica deletion failure + |
+TaurusDeleteReadOnlyNodeFailed + |
+Major + |
+The communications between the management plane and the read replica are abnormal or the VM fails to be deleted from IaaS. + |
+Submit a service ticket. + |
+Read replicas fail to be deleted. + |
+|
Password reset failure + |
+TaurusResetInstancePasswordFailed + |
+Major + |
+The communications between the management plane and the instance are abnormal or the instance is abnormal. + |
+Check the instance status and try again. If the fault persists, submit a service ticket. + |
+Passwords fail to be reset for instances. + |
+|
DB instance reboot failure + |
+TaurusRestartInstanceFailed + |
+Major + |
+The network between the management plane and the instance is abnormal or the instance is abnormal. + |
+Check the instance status and try again. If the fault persists, submit a service ticket. + |
+Instances fail to be rebooted. + |
+|
Restoration to new DB instance failure + |
+TaurusRestoreToNewInstanceFailed + |
+Major + |
+The instance quota is insufficient, underlying resources are exhausted, or the data restoration logic is incorrect. + |
+If the new instance fails to be created, check the instance quota, release resources, and try to restore to a new instance again. In other cases, submit a service ticket. + |
+Backup data fails to be restored to new instances. + |
+|
EIP binding failure + |
+TaurusBindEIPToInstanceFailed + |
+Major + |
+The binding task fails. + |
+Submit a service ticket. + |
+EIPs fail to be bound to instances. + |
+|
EIP unbinding failure + |
+TaurusUnbindEIPFromInstanceFailed + |
+Major + |
+The unbinding task fails. + |
+Submit a service ticket. + |
+EIPs fail to be unbound from instances. + |
+|
Parameter modification failure + |
+TaurusUpdateInstanceParameterFailed + |
+Major + |
+The network between the management plane and the instance is abnormal or the instance is abnormal. + |
+Check the instance status and try again. If the fault persists, submit a service ticket. + |
+Instance parameters fail to be modified. + |
+|
Parameter template application failure + |
+TaurusApplyParameterGroupToInstanceFailed + |
+Major + |
+The network between the management plane and instances is abnormal or the instances are abnormal. + |
+Check the instance status and try again. If the fault persists, submit a service ticket. + |
+Parameter templates fail to be applied to instances. + |
+|
Full backup failure + |
+TaurusBackupInstanceFailed + |
+Major + |
+The network between the instance and the management plane (or the OBS) is disconnected, or the backup environment created for the instance is abnormal. + |
+Submit a service ticket. + |
+Backup jobs fail. + |
+|
Primary/standby failover + |
+TaurusActiveStandbySwitched + |
+Major + |
+When the network, physical machine, or database of the primary node is faulty, the system promotes a read replica to primary based on the failover priority to ensure service continuity. + |
+
|
+During the failover, database connection is interrupted for a short period of time. After the failover is complete, you can reconnect to the database. + |
+|
Database read-only + |
+NodeReadonlyMode + |
+Major + |
+The database supports only query operations. + |
+Contact the database technical support team. + |
+After the database becomes read-only, write operations cannot be processed. + |
+|
Database read/write + |
+NodeReadWriteMode + |
+Major + |
+The database supports both write and read operations. + |
+None. + |
+None. + |
+
Event Source + |
+Event Name + |
+Event ID + |
+Event Severity + |
+Description + |
+Solution + |
+Impact + |
+
|---|---|---|---|---|---|---|
GaussDB(for openGauss) + |
+Process status alarm + |
+ProcessStatusAlarm + |
+Major + |
+Key processes exit, including: CMS/CMA, ETCD, GTM, CN, or DN process. + |
+Wait until the process is automatically recovered or a primary/standby failover is automatically performed. Check whether services are recovered. If no, contact SRE engineers. + |
+If processes on primary nodes are faulty, services are interrupted and then rolled back. If processes on standby nodes are faulty, services are not affected. + |
+
Component status alarm + |
+ComponentStatusAlarm + |
+Major + |
+Key components do not respond, including: CMA, ETCD, GTM, CN, or DN component. + |
+Wait until the process is automatically recovered or a primary/standby failover is automatically performed. Check whether services are recovered. If no, contact SRE engineers. + |
+If processes on primary nodes do not respond, neither do the services. If processes on standby nodes are faulty, services are not affected. + |
+|
Cluster status alarm + |
+ClusterStatusAlarm + |
+Major + |
+The cluster status is abnormal. For example, the cluster is read-only; majority of ETCDs are faulty; or the cluster resources are unevenly distributed. + |
+Contact SRE engineers. + |
+If the cluster status is read-only, only read services are processed. +If the majority of ETCDs are fault, the cluster is unavailable. +If resources are unevenly distributed, the instance performance and reliability deteriorate. + |
+|
Hardware resource alarm + |
+HardwareResourceAlarm + |
+Major + |
+A major hardware fault occurs in the instance, such as disk damage or GTM network fault. + |
+Contact SRE engineers. + |
+Some or all services are affected. + |
+|
Status transition alarm + |
+StateTransitionAlarm + |
+Major + |
+The following events occur in the instance: DN build failure, forcible DN promotion, primary/standby DN switchover/failover, or primary/standby GTM switchover/failover. + |
+Wait until the fault is automatically rectified and check whether services are recovered. If no, contact SRE engineers. + |
+Some services are interrupted. + |
+|
Other abnormal alarm + |
+OtherAbnormalAlarm + |
+Major + |
+Disk usage threshold alarm + |
+Focus on service changes and scale up storage space as needed. + |
+If the used storage space exceeds the threshold, storage space cannot be scaled up. + |
+|
Faulty DB instance + |
+TaurusInstanceRunningStatusAbnormal + |
+Major + |
+This event is a key alarm event and is reported when an instance is faulty due to a disaster or a server failure. + |
+Submit a service ticket. + |
+The database service may be unavailable. + |
+|
DB instance recovered + |
+TaurusInstanceRunningStatusRecovered + |
+Major + |
+GaussDB(for openGauss) provides an HA tool for automated or manual rectification of faults. After the fault is rectified, this event is reported. + |
+No further action is required. + |
+None + |
+|
Faulty DB node + |
+TaurusNodeRunningStatusAbnormal + |
+Major + |
+This event is a key alarm event and is reported when a database node is faulty due to a disaster or a server failure. + |
+Check whether the database service is available and submit a service ticket. + |
+The database service may be unavailable. + |
+|
DB node recovered + |
+TaurusNodeRunningStatusRecovered + |
+Major + |
+GaussDB(for openGauss) provides an HA tool for automated or manual rectification of faults. After the fault is rectified, this event is reported. + |
+No further action is required. + |
+None + |
+|
DB instance creation failure + |
+GaussDBV5CreateInstanceFailed + |
+Major + |
+Instances fail to be created because the quota is insufficient or underlying resources are exhausted. + |
+Release the instances that are no longer used and try to provision them again, or submit a service ticket to adjust the quota. + |
+DB instances cannot be created. + |
+|
Node adding failure + |
+GaussDBV5ExpandClusterFailed + |
+Major + |
+The underlying resources are insufficient. + |
+Submit a service ticket. The O&M personnel will coordinate resources in the background, and then you delete the node that failed to be added and add a new node. + |
+None + |
+|
Storage scale-up failure + |
+GaussDBV5EnlargeVolumeFailed + |
+Major + |
+The underlying resources are insufficient. + |
+Submit a service ticket. The O&M personnel will coordinate resources in the background and then you scale up the storage space again. + |
+Services may be interrupted. + |
+|
Reboot failure + |
+GaussDBV5RestartInstanceFailed + |
+Major + |
+The network is abnormal. + |
+Retry the reboot operation or submit a service ticket to the O&M personnel. + |
+The database service may be unavailable. + |
+|
Full backup failure + |
+GaussDBV5FullBackupFailed + |
+Major + |
+The backup files fail to be exported or uploaded. + |
+Submit a service ticket to the O&M personnel. + |
+Data cannot be backed up. + |
+|
Differential backup failure + |
+GaussDBV5DifferentialBackupFailed + |
+Major + |
+The backup files fail to be exported or uploaded. + |
+Submit a service ticket to the O&M personnel. + |
+Data cannot be backed up. + |
+|
Backup deletion failure + |
+GaussDBV5DeleteBackupFailed + |
+Major + |
+This function does not need to be implemented. + |
+N/A + |
+N/A + |
+|
EIP binding failure + |
+GaussDBV5BindEIPFailed + |
+Major + |
+The EIP is bound to another resource. + |
+Submit a service ticket to the O&M personnel. + |
+The instance cannot be accessed from the Internet. + |
+|
EIP unbinding failure + |
+GaussDBV5UnbindEIPFailed + |
+Major + |
+The network is faulty or EIP is abnormal. + |
+Unbind the IP address again or submit a service ticket to the O&M personnel. + |
+IP addresses may be residual. + |
+|
Parameter template application failure + |
+GaussDBV5ApplyParamFailed + |
+Major + |
+Modifying a parameter template times out. + |
+Modify the parameter template again. + |
+None + |
+|
Parameter modification failure + |
+GaussDBV5UpdateInstanceParamGroupFailed + |
+Major + |
+Modifying a parameter template times out. + |
+Modify the parameter template again. + |
+None + |
+|
Backup and restoration failure + |
+GaussDBV5RestoreFromBcakupFailed + |
+Major + |
+The underlying resources are insufficient or backup files fail to be downloaded. + |
+Submit a service ticket. + |
+The database service may be unavailable during the restoration failure. + |
+
Data Dump
+ + + diff --git a/docs/ces/umn/ces_01_0056.html b/docs/ces/umn/ces_01_0056.html new file mode 100644 index 00000000..c1f3de40 --- /dev/null +++ b/docs/ces/umn/ces_01_0056.html @@ -0,0 +1,66 @@ + + +Adding a Dump Task
+Scenarios
It helps you dump cloud service monitoring data to DMS for Kafka in real time. You can use the data dump function to query metrics on the DMS for Kafka console or on an open-source Kafka client.
+ An account can create a maximum of 20 data dump tasks.
+Procedure
- Log in to the management console.
- Click Service List in the upper left corner, and select Cloud Eye.
- In the navigation pane, choose Data Dump.
- Click Add Dump Task.
- In the Add Dump Task dialog box, configure parameters as prompted.
++
+Table 1 Dump task parameters Parameter
+Description
+Name
+Specifies the dump task name.
+The name can contain 1 to 64 characters and consist of only letters, digits, underscores (_), and hyphens (-).
+Example value: dataShareJob-ECSMetric
+Resource Type
+Specifies the type of resources monitored by Cloud Eye.
+Example value: Elastic Cloud Server
+Dimension
+Specifies the dimension of the monitored object.
+For details, see Metrics and Dimension on the monitoring metric description page.
+If All is selected, all monitored objects of the selected service will be dumped to Kafka.
+If another dimension is selected, monitored objects of this dimension will be dumped.
+Example value: All
+Monitoring Scope
+The scope can only be All resources, indicating that all metrics of the specified monitored object will be dumped to DMS for Kafka.
+Resource Type
+The type can only be Distributed Message Service for Kafka.
+Destination
+Specifies the Kafka instance name and topic name the data is to be dumped to.
+If no Kafka instance or topic is available, see Creating an Instance and Creating a Topic in a Kafka Premium Instance.
+ - Click Add.+
You can query the dumped data in Kafka.
+
Modifying, Deleting, Enabling, or Disabling a Dump Task
+Scenarios
This topic describes how to modify, disable, enable, or delete dump tasks.
+Modifying a Dump Task
- Log in to the management console.
- Click Service List in the upper left corner, and select Cloud Eye.
- In the navigation pane, choose Data Dump.
- Click Modify in the Operation column.
The Modify Dump Task page is displayed.
+ - Modify the task settings.
- Click Modify.
Disabling a Dump Task
Locate the dump task and click Disable in the Operation column.
+Enabling a Dump Task
Locate a dump task whose status is Disabled and click Enable in the Operation column.
+Deleting a Dump Task
Locate the dump task and click Delete in the Operation column.
+Cloud Service Monitoring
+ + + diff --git a/docs/ces/umn/ces_01_0067.html b/docs/ces/umn/ces_01_0067.html index 9007552e..927a6444 100644 --- a/docs/ces/umn/ces_01_0067.html +++ b/docs/ces/umn/ces_01_0067.html @@ -1,8 +1,7 @@Using the Alarm Function
-- Introduction to the Alarm Function
@@ -11,7 +10,7 @@ - Creating Alarm Rules
- - Viewing Alarm Records
+ - Viewing Alarm History
- Alarm Rule Management
diff --git a/docs/ces/umn/ces_01_0074.html b/docs/ces/umn/ces_01_0074.html
index 5d85d35a..39826689 100644
--- a/docs/ces/umn/ces_01_0074.html
+++ b/docs/ces/umn/ces_01_0074.html
@@ -29,7 +29,7 @@
- Log in to the management console.
- In the upper left corner, select a region and project.
- Click Service List in the upper left corner, and select Cloud Eye.
- Choose Alarm Management > Alarm Records.
On the Alarm Records page, you can view the status changes of all alarm rules from the last 7 days.
- - You can select a time range to search for the alarm records.
- In the upper right corner of the alarm record list, you can filter the alarm records by the alarm rule name, resource ID, and alarm rule ID.
Procedure
- Log in to the management console.
- In the upper left corner, select a region and project.
- Click Service List in the upper left corner, and select Cloud Eye.
- Choose Alarm Management > Alarm History.
On the Alarm History page, you can view the status changes of all alarm rules from the last 7 days.
+- - You can select a time range to view the alarm history.
- In the upper right corner of the alarm record list, you can filter the Alarm History by the alarm rule name, resource ID, and alarm rule ID.
- Click the target alarm rule to go to the Alarm Rules page. In the lower part of the Alarm Records area, you can view the history of the selected alarm rule from the last 30 days.In the alarm record list, you can check whether resources are abnormal and handle the exceptions, if any.
- Typically, alarms are triggered based on calculation. Therefore, the alarm triggering time may be a few seconds later than the time the threshold was reached.
- If you have created or modified an alarm rule after obtaining the monitoring data and an alarm is triggered, the alarm triggering time is the time when you created or modified the alarm rule.
- Click the target alarm rule to go to its details page. In the lower part of the displayed page, you can view the alarm history of the selected alarm rule from the last 30 days.
diff --git a/docs/ces/umn/ces_01_0077.html b/docs/ces/umn/ces_01_0077.html index be87e3cd..6bb869b5 100644 --- a/docs/ces/umn/ces_01_0077.html +++ b/docs/ces/umn/ces_01_0077.html @@ -5,6 +5,8 @@In the Alarm History list, you can check whether resources are abnormal and handle the exceptions, if any. - Typically, alarms are triggered based on calculation. Therefore, the alarm triggering time may be a few seconds later than the time the threshold was reached.
- If you have created or modified an alarm rule after obtaining the monitoring data and an alarm is triggered, the alarm triggering time is the time when you created or modified the alarm rule.
-
+
- Viewing Details of an Alarm Rule
+ - Modifying an Alarm Rule
- Disabling Alarm Rules
diff --git a/docs/ces/umn/ces_01_0078.html b/docs/ces/umn/ces_01_0078.html index 3432c66d..511ffdfd 100644 --- a/docs/ces/umn/ces_01_0078.html +++ b/docs/ces/umn/ces_01_0078.html @@ -2,7 +2,7 @@Modifying an Alarm Rule
-Procedure
- Log in to the management console.
- In the upper left corner, select a region and project.
- Click Service List in the upper left corner, and select Cloud Eye.
- Choose Alarm Management > Alarm Rules.
- On the displayed Alarm Rules page, use either of the following two methods to modify an alarm rule:
- Locate the row containing the alarm rule you want to modify, click More in the Operation column, and choose Modify.
- Click the name of the alarm rule you want to modify. On the page displayed, click Modify in the upper right corner.
- On the Modify Alarm Rule page, modify alarm rule parameters as needed. +
- On the Modify Alarm Rule page, modify alarm rule parameters as needed.
Table 1 Parameters Parameter
Description
diff --git a/docs/ces/umn/ces_01_0083.html b/docs/ces/umn/ces_01_0083.html index 6b3bff47..72cd7f77 100644 --- a/docs/ces/umn/ces_01_0083.html +++ b/docs/ces/umn/ces_01_0083.html @@ -11,13 +11,13 @@Resource Type
Specifies the type of the resource the alarm rule is created for.
-Example value: Elastic Cloud Server
+Example value: Elastic Cloud Server
Dimension
Specifies the metric dimension of the selected resource type.
-Example value: ECSs
+Example value: ECSs
Import Template
@@ -31,7 +31,7 @@
- Click Next to go to the Add Alarm Rule step. Specify parameters listed in Table 2. You can add one or more rules to the alarm template.
+- Click Next to go to the Add Alarm Rule step. Specify parameters listed in Table 2. You can add one or more rules to the alarm template.
diff --git a/docs/ces/umn/ces_faq_0012.html b/docs/ces/umn/ces_faq_0012.html index e2a763e8..3e10095d 100644 --- a/docs/ces/umn/ces_faq_0012.html +++ b/docs/ces/umn/ces_faq_0012.html @@ -2,11 +2,10 @@Table 2 Parameters Parameter
Description
diff --git a/docs/ces/umn/ces_01_0085.html b/docs/ces/umn/ces_01_0085.html index b5f16b56..991654d3 100644 --- a/docs/ces/umn/ces_01_0085.html +++ b/docs/ces/umn/ces_01_0085.html @@ -1,7 +1,7 @@Deleting a custom alarm template
-In the navigation pane on the left, choose Alarm Management > Alarm Templates and click the Custom Templates tab. Locate the template you want to delete and click Delete in the Operation column. In the displayed Delete Custom Template dialog box, click Yes.
+In the navigation pane on the left, choose Alarm Management > Alarm Templates and click the Custom Templates. Locate the template you want to delete and click Delete in the Operation column. In the displayed Delete Custom Template dialog box, click Yes.
diff --git a/docs/ces/umn/ces_01_0097.html b/docs/ces/umn/ces_01_0097.html index f6e9f86e..29d2d471 100644 --- a/docs/ces/umn/ces_01_0097.html +++ b/docs/ces/umn/ces_01_0097.html @@ -8,16 +8,51 @@2019-11-30
+2022-10-10
+This release incorporates the following changes:
+- Added the following services in Services Interconnected with Cloud Eye: GaussDB NoSQL, GaussDB(for MySQL), and GaussDB(for openGauss).
2020-11-10
+This release incorporates the following changes:
+Added Resource Groups.
+2019-11-18
+Accepted for RM-1369, RM-2022, RM-385, RM-645, RM-666, RM-893.
+2019-11-30
This release incorporates the following changes:
-- Added the metric IDs for Scalable File Service (SFS) metrics.
- Deleted example values in Creating an Alarm Rule by Using an Alarm Template.
- Added the metric IDs for Scalable File Service (SFS) metrics.
- Deleted example values in Creating an Alarm Rule by Using an Alarm Template.
- Added unit minute for ECS and BMS OS monitoring metrics.
2019-11-22
+This release incorporates the following changes:
+- Added ECS and BMS OS monitoring metrics.
- Added operations to modify BMS security groups in Modifying the DNS Server Address and Adding Security Group Rules (Linux).
- Updated parameter descriptions in (Optional) Manually Configuring the Agent on a Windows Server.
- Added operations to query BMS OS monitoring metrics in Viewing Server Monitoring Metrics.
2019-08-31
+This release incorporates the following changes:
+- Added Event Monitoring.
2019-07-31
+This release incorporates the following changes:
+- Added Using Server Monitoring.
- Added Server Monitoring.
- Added Why Is the Monitoring Data Not Displayed on the Cloud Eye Console?
- Added the following four Scalable File Service (SFS) metrics: Read OPS, Write OPS, Read Write OPS, and Used Capacity.
2019-03-30
This release incorporates the following changes:
-- Changed Virtual Private Cloud (VPC) to Elastic IP (EIP) and Bandwidth in section "Elastic IP (EIP) and Bandwidth Metrics."
- Optimized Distributed Message Service (DMS) metrics.
- Changed Virtual Private Cloud (VPC) to Elastic IP (EIP) and Bandwidth in section "Elastic IP (EIP) and Bandwidth Metrics."
- Optimized the Distributed Message Service (DMS) metrics.
2018-12-30
diff --git a/docs/ces/umn/ces_01_0109.html b/docs/ces/umn/ces_01_0109.html new file mode 100644 index 00000000..24aa9be2 --- /dev/null +++ b/docs/ces/umn/ces_01_0109.html @@ -0,0 +1,14 @@ + + +Introduction to Cloud Service Monitoring
+++Scenarios
Cloud Service Monitoring collects data of built-in metrics of cloud services. You can monitor these metrics to track the status of corresponding cloud services. On the Cloud Service Monitoring page, in addition to viewing monitoring data, you can also create alarm rules and export raw data.
++What You Can Do with Cloud Service Monitoring
- Viewing metrics: On the page displaying metrics, you can view graphs of raw data collected from lats 1 hour, 3 hours, 12 hours, and 24 hours. You can customize the metrics to be viewed and view monitoring data that is automatically refreshed.
- Create alarm rules: You can create alarm rules for key metrics of cloud services. When the conditions in the alarm rule are met, Cloud Eye sends emails, or text messages, or sends HTTP/HTTPS messages, enabling you to quickly respond to resource changes.
- Exporting monitoring data: Cloud Service Monitoring allows you to export a maximum of 10 monitoring items in your selected time range and rollup period. The exported monitoring report contains the username, region name, service name, instance name, instance ID, metric name, metric data, time, and timestamp, facilitating query and filtering.
++ diff --git a/docs/ces/umn/ces_01_0110.html b/docs/ces/umn/ces_01_0110.html new file mode 100644 index 00000000..4b6a4754 --- /dev/null +++ b/docs/ces/umn/ces_01_0110.html @@ -0,0 +1,17 @@ + + +++Parent topic: Cloud Service Monitoring+Viewing Metrics
++- Log in to the management console.
- In the upper left corner, select a region and project.
- Click Service List in the upper left corner, and select Cloud Eye.
- In the navigation pane on the left, choose Cloud Service Monitoring and select the cloud service whose resources you want to view.
- Locate the target cloud service resource, in the Operation column, click View Metric.+
- You can sort graphs by dragging them based on service requirements.
- If Auto Refresh is enabled, data is automatically refreshed every minute.
- Some cloud services allow you to view resource details. You can click View Resource Details in the upper part of the page to view details about monitored resources.
- You can search for a specific metric in the search box.
- To export monitoring data, see How Can I Export Collected Data?.
- Near the top right corner of the page, click Select Metric.
The Select Metric dialog box is displayed.
+Select at least one metric. Drag and drop the selected metrics at desired locations to sort them. This helps you customize metrics to be viewed.
+ - Hover your mouse over a graph. In the upper right corner, click
to view monitoring details on an enlarged graph. You can select a time period or customize a time range to view the metric trend in a specific monitoring interval.+ - If you select 1h, 3h, 12h, or 1d, raw data is displayed by default. Near the top left corner of the page, you can click Settings to change the rollup period of the monitoring data. For details about rollup periods, see What Is Rollup?.
- If you select 7d or 30d, aggregated data is displayed by default. Near the top left corner of the page, you can click Settings to change the rollup period of the monitoring data.
- In the upper right corner of the monitoring graph, click
to create alarm rules for the metric. For details about the parameters, see Creating an Alarm Rule for a Specific Metric.
++ diff --git a/docs/ces/umn/ces_01_0120.html b/docs/ces/umn/ces_01_0120.html new file mode 100644 index 00000000..a40e1f00 --- /dev/null +++ b/docs/ces/umn/ces_01_0120.html @@ -0,0 +1,28 @@ + + +++Parent topic: Cloud Service Monitoring+Server Monitoring
+++++ diff --git a/docs/ces/umn/ces_06_0001.html b/docs/ces/umn/ces_06_0001.html index 8ffdd891..c0cc2866 100644 --- a/docs/ces/umn/ces_06_0001.html +++ b/docs/ces/umn/ces_06_0001.html @@ -9,6 +9,12 @@-
+
- Introduction to Server Monitoring
+
+ - Agent Installation and Configuration
+
+ - Installing and Configuring the Agent on a Linux ECS or BMS
+
+ - Installing and Configuring the Agent on a Windows ECS
+
+ - Installing the Agents in Batches on Linux ECSs
+
+ - Managing the Agent
+
+ - Process Monitoring
+
+ - Viewing Server Monitoring Metrics
+
+ - Creating an Alarm Rule to Monitor a Server
+
+
- Querying Metrics of a Cloud Service
+
- Using Server Monitoring
+
+- Using Custom Monitoring
+
+- Using Event Monitoring
diff --git a/docs/ces/umn/ces_06_0002.html b/docs/ces/umn/ces_06_0002.html index 4a0fb10e..d0d38cb8 100644 --- a/docs/ces/umn/ces_06_0002.html +++ b/docs/ces/umn/ces_06_0002.html @@ -6,7 +6,7 @@
+-Resource Monitoring Preview (in the Alarm State)
Graphs are used to display the metric status of service resources in the Alarm status, helping you to know the resource status and handle exceptions in a timely manner. Click the resource name, and you can go to the page displaying alarm rule details configured for this resource.
Alarm Statistics
Alarm statistics display the number of critical, major, minor, and informational alarms. Click the number of one alarm severity, and you will be directed to the Alarm Records page displaying alarm rules of this severity.
+Alarm Statistics
Alarm statistics display the number of critical, major, minor, and informational alarms. Click the number of one alarm severity, and you will be directed to the Alarm History page displaying alarm rules of this severity.
diff --git a/docs/ces/umn/ces_06_0003.html b/docs/ces/umn/ces_06_0003.html new file mode 100644 index 00000000..e4c9b807 --- /dev/null +++ b/docs/ces/umn/ces_06_0003.html @@ -0,0 +1,24 @@ + + +diff --git a/docs/ces/umn/ces_07_0003.html b/docs/ces/umn/ces_07_0003.html index 3bcd08c0..db9b7f17 100644 --- a/docs/ces/umn/ces_07_0003.html +++ b/docs/ces/umn/ces_07_0003.html @@ -3,13 +3,15 @@Using Server Monitoring
++Server monitoring includes basic monitoring, process monitoring, and OS monitoring for servers.
+- Basic monitoring provides Agent-free monitoring for basic ECS or BMS metrics.
- OS monitoring provides proactive and fine-grained OS monitoring for servers, and it requires the Agent (a plug-in) to be installed on all servers that will be monitored.
- Process monitoring provides monitoring of active processes on hosts.
+ Agent access statement: After the Agent is installed, it collects and reports server monitoring data to the Cloud Eye service. When you update the Agent software package, Cloud Eye accesses the software package repository address to update the software. In addition to the preceding behaviors, the Agent does not access any other addresses.
++Functions
- Various Metrics
Server monitoring provides more than 40 metrics, such as metrics for CPU, memory, disk, and network usage, meeting the basic monitoring and O&M requirements for servers.
+ - Fine-grained Monitoring
After the Agent is installed, the metrics collected by the Agent are reported every minute.
+ - Process Monitoring
CPU usage, memory usage, and number of opened files used by active processes are monitored to help you better understand the resource usages on ECSs and BMSs.
+
+Using Server Monitoring
- Log in to the management console.
- Click Service List in the upper left corner, and select Cloud Eye.
- In the navigation pane on the left, choose Server Monitoring.
- Select the target ECS or BMS and install the Agent on it.
- Change the DNS server address of and add security group rules to the target ECS or BMS. For details, see Modifying the DNS Server Address and Adding Security Group Rules (Linux) or Modifying the DNS Server Address and Adding Security Group Rules (Windows).
- Install the Agent. For details, see Installing the Agent on a Linux Server or Installing and Configuring the Agent on a Windows Server.
- After 5 minutes, check whether the Agent status is Running.
If yes, the Agent has been installed successfully.
+On the right of the ECS, click View Metric in the Operation column to view the monitoring data.
+
++ diff --git a/docs/ces/umn/ces_06_0005.html b/docs/ces/umn/ces_06_0005.html new file mode 100644 index 00000000..0874291d --- /dev/null +++ b/docs/ces/umn/ces_06_0005.html @@ -0,0 +1,20 @@ + + +++Parent topic: Getting Started+Using Custom Monitoring
++The Custom Monitoring page displays all custom metrics reported by users. You can use simple API requests to report collected monitoring data of those metrics to Cloud Eye for processing and display.
+For details about how to add monitoring data, see section "Adding Monitoring Data" in the Cloud Eye API Reference.
++Viewing Custom Monitoring
- Log in to the management console.
- Click Service List in the upper left corner, and select Cloud Eye.
- In the navigation pane on the left, choose Custom Monitoring.
- On the Custom Monitoring page, view the data reported by yourself through API requests, including custom services and metrics.
- Locate the row that contains the target cloud service resource and click View Metric in the Operation column.
On the page displayed, you can view graphs based on raw data collected in 1h, 3h, and 12h. In the upper right corner of each graph, the maximum and minimum values of the metric in the corresponding time periods are dynamically displayed.
+ - If you want to view metric details, hover your mouse over a graph and click
in the upper right corner.In the upper left corner, you can see six default monitoring periods: 1h, 3h, 12h, 1d, 7d, and 30d. To view historical monitoring data for any period during the last six months, customize the monitoring period by setting Select Range in the upper right corner.
+In the upper left corner of the graph, click Settings to configure the rollup method.
+
+Creating an Alarm Rule
- Log in to the management console.
- Click Service List in the upper left corner, and select Cloud Eye.
- In the navigation pane on the left, choose Custom Monitoring.
- Locate the target cloud service resource and click Create Alarm Rule in the Operation column.
- Configure the alarm rule name, alarm policy, and alarm notification as prompted.
After you create the alarm rule, if the custom metric data reaches the threshold, Cloud Eye immediately notifies you through SMN that an exception has occurred.
+
++ diff --git a/docs/ces/umn/ces_06_0006.html b/docs/ces/umn/ces_06_0006.html new file mode 100644 index 00000000..5280c069 --- /dev/null +++ b/docs/ces/umn/ces_06_0006.html @@ -0,0 +1,20 @@ + + +++Parent topic: Getting Started+Using Event Monitoring
++You can query system events and custom events reported to Cloud Eye through the API. You can create alarm rules for both system events and custom events. When specific events occur, Cloud Eye generates alarms for you.
+Events are key operations on cloud service resources that are stored and monitored by Cloud Eye. You can view events to see operations performed by specific users on specific resources, such as deleting or rebooting an ECS.
+Event monitoring is enabled by default. You can view monitoring details about system events and custom events. For details about the supported system events, see Events Supported by Event Monitoring.
+Event monitoring provides an API for reporting custom events, which helps you collect and report abnormal events or important change events generated by services to Cloud Eye.
++Viewing Event Monitoring Graphs
- Log in to the management console.
- Click Service List in the upper left corner, and select Cloud Eye.
- In the navigation pane on the left, choose Event Monitoring.
On the page displayed, all system events and custom events of the last 24 hours are displayed by default.
+ - Select an event and click View Graph in the Operation column.
+Creating an Alarm Rule
- Log in to the management console.
- Click Service List in the upper left corner, and select Cloud Eye.
- In the navigation pane on the left, choose Event Monitoring.
- In the event list, locate the event and click Create Alarm Rule in the Operation column.
- Configure the alarm rule name, alarm policy, and alarm notification as prompted.
After you create the alarm rule, if the metric data reaches the threshold, Cloud Eye immediately notifies you through SMN that an exception has occurred.
+
++ diff --git a/docs/ces/umn/ces_07_0001.html b/docs/ces/umn/ces_07_0001.html index f53270d5..0ac9419f 100644 --- a/docs/ces/umn/ces_07_0001.html +++ b/docs/ces/umn/ces_07_0001.html @@ -14,7 +14,7 @@++Parent topic: Getting Started+- Constraints
-
- Region and AZ
+- Region and AZ
Application Scenarios
+Cloud Service Monitoring
After enabling a cloud service supported by Cloud Eye, you can view the cloud service status and metric data, and create alarm rules for metrics on the Cloud Eye console.
Server Monitoring
By monitoring the ECS or BMS metrics, such as CPU usage, memory usage, and disk usage, you can ensure that the ECS or BMS run normally and prevent service interruptions caused by overuse of resources.
+Performance Issues
When an alarm rule's conditions are met, Cloud Eye generates an alarm and invokes the SMN API to send notifications, allowing you to identify root causes of performance issues.
Capacity Expansion
After you create alarm rules for metrics such as CPU usage, memory usage, and disk usage, you can track the statuses of cloud services. If the service volume increases, Cloud Eye sends you an alarm notification, enabling you to manually expand the capacity or configure AS policies to automatically increase capacity.
-Custom Monitoring
Custom monitoring supplements cloud service monitoring. If Cloud Eye does not provide the required metrics, you can use custom monitoring and report the collected monitoring data to Cloud Eye. Cloud Eye helps to display those monitoring data in graphs and allows you to create alarm rules for those custom metrics.
Log Monitoring
Log monitoring enables you to monitor log content in real time. You can set alarm rules on Cloud Eye to monitor the logs, thus to reduce your O&M cost for log monitoring and simplify the log monitoring process.
+Log Monitoring
Log monitoring enables you to monitor log content in real time. You can set alarm rules on Cloud Eye to monitor the logs collected by Log Tank Service (LTS), thus to reduce your O&M cost for log monitoring and simplify the log monitoring process.
diff --git a/docs/ces/umn/ces_07_0006.html b/docs/ces/umn/ces_07_0006.html index 3701a8fe..c462a522 100644 --- a/docs/ces/umn/ces_07_0006.html +++ b/docs/ces/umn/ces_07_0006.html @@ -11,7 +11,7 @@Event Monitoring
In event monitoring, you can query system events that are automatically reported to Cloud Eye and custom events reported to Cloud Eye through the API. You can create alarm rules for both system events and custom events. When specific events occur, Cloud Eye generates alarms for you.
-Topics
A topic is used to publish messages and subscribe to notifications. Topics provide you with one-to-many publish subscription and message notification functions. You can send messages to different types of endpoints with just one message request. Cloud Eye uses SMN to notify you of cloud service resource changes, enabling you to track the cloud service status in a timely manner.
Alarm Rules
You can create alarm rules to set thresholds for cloud service metrics. When the status (Alarm and OK) of the alarm rule changes, Cloud Eye notifies you by sending emails, text messages, or by sending HTTP/HTTPS messages to servers.
+Alarm Rules
You can create alarm rules to set thresholds for cloud service metrics. When the status (Alarm and OK) of the alarm rule changes, Cloud Eye notifies you by sending emails, text messages, or HTTP/HTTPS messages to servers.
diff --git a/docs/ces/umn/ces_07_0007.html b/docs/ces/umn/ces_07_0007.html index ce7a2f48..5e850960 100644 --- a/docs/ces/umn/ces_07_0007.html +++ b/docs/ces/umn/ces_07_0007.html @@ -1,7 +1,7 @@Alarm Templates
Alarm templates contain one or more alarm rules for specific services. The templates help you create alarm rules for multiple cloud services, improving O&M efficiency.
Constraints
-Table 1 lists Cloud Eye resource limits for a user. For details about how to adjust quotas, see Quota Adjustment.
+Table 1 lists Cloud Eye resource limits for a user. The alarm rule quota can be increased. For details about how to adjust quotas, see Quota Adjustment.
diff --git a/docs/ces/umn/ces_faq_0006.html b/docs/ces/umn/ces_faq_0006.html index df0886aa..e407fadd 100644 --- a/docs/ces/umn/ces_faq_0006.html +++ b/docs/ces/umn/ces_faq_0006.html @@ -4,7 +4,7 @@Table 1 User resource limits Item
Time that the alarm history can be kept
7 days
+720 hours
+Instances that can be selected for single alarm rule creation
+50
+Alarm rules that can be created at a time
+1,000
+NOTE:If you select 50 monitored objects and 20 metrics, the number of alarm rules that can be created is 1,000.
+Topics that can be selected for receiving notifications
@@ -44,6 +56,19 @@5
Monitoring data records that can be exported at a time
+400
+NOTE:+If 400 monitored objects are to be exported, only records of one metric can be exported.
+If 80 monitored objects are to be exported, records of 5 metrics can be exported.
+Resource groups that can be created
+10
+Alarm notifications are email or SMS messages that are sent out when an alarm status is Alarm, OK, or both.
You can configure Cloud Eye to send or not send alarm notifications when you create or modify an alarm rule.
Cloud Eye can:
-- Send you email or text message notifications, or send HTTP/HTTPS messages to servers.
- Work with Auto Scaling to trigger the system to automatically add or remove servers.
- Send you email notifications.
- Work with Auto Scaling to trigger the system to automatically add or remove servers.
diff --git a/docs/ces/umn/ces_faq_0010.html b/docs/ces/umn/ces_faq_0010.html index dc7e71b9..1b4655a9 100644 --- a/docs/ces/umn/ces_faq_0010.html +++ b/docs/ces/umn/ces_faq_0010.html @@ -24,16 +24,6 @@155 days
4 hours
-300 days
-1 day
-5 years
-How Can I Export Collected Data?
- On the Cloud Eye console, choose Cloud Service Monitoring or Server Monitoring.
- Click Export Data.
- Configure the time range, resource type, dimension, monitored object, and metric.
- Click Export.
You can export data for multiple metrics at a time to a CSV file.
+- The first row in the exported monitoring report displays the username, region, service, instance name, instance ID, metric name, metric data, time, and timestamp. You can view historical monitoring data.
- To convert the time using a Unix timestamp to the time of the target time zone, perform the following steps:
- Use Excel to open a .csv file.
- Use the following formula to convert the time:
Target time = [Unix timestamp/1000 + (Target time zone) x 3600]/86400 + 70 x 365 + 19
- - Set cell format to Date.
To convert a Unix timestamp of 1475918112000 to Shanghai time (UTC+8), using the formula from step b:
-Target time = [1475918112000/1000 + (+8) x 3600]/86400 + 70 x 365 + 19
-Set the cell format to date and select a presentation format such as 2016/3/14 13:30. Then, the target time obtained will be presented as 2016/10/8 17:15.
-
- Set cell format to Date.
diff --git a/docs/ces/umn/ces_faq_0025.html b/docs/ces/umn/ces_faq_0025.html new file mode 100644 index 00000000..a06923a7 --- /dev/null +++ b/docs/ces/umn/ces_faq_0025.html @@ -0,0 +1,15 @@ + + +What Should I Do If the Agent Status Is Faulty?
++The OS monitoring Agent sends a heartbeat message to Cloud Eye every minute. If Cloud Eye does not receive any heartbeat messages for 3 minutes, Agent Status is displayed as Faulty.
+It may because:
+- The account is in arrears.
- If the Agent process is faulty, restart it by following the instructions provided in Managing the Agent. If the restart fails, related files have been deleted by mistake. In this case, reinstall the Agent.
It may be that the Agent is incorrectly configured. Check whether the DNS server address is correct. If it is, check the Agent configurations by referring to Modifying the DNS Server Address and Adding Security Group Rules (Linux) and (Optional) Manually Configuring the Agent (Linux).
+Locate the cause in log /usr/local/telescope/log/common.log.
+++ diff --git a/docs/ces/umn/ces_faq_0027.html b/docs/ces/umn/ces_faq_0027.html new file mode 100644 index 00000000..33871de3 --- /dev/null +++ b/docs/ces/umn/ces_faq_0027.html @@ -0,0 +1,12 @@ + + +++Parent topic: Server Monitoring+How Can I Quickly Restore the Agent Configuration?
++After the Agent is installed, you can configure AK/SK, RegionID, and ProjectId in one-click mode. This saves manual configuration and improves configuration efficiency.
+If you are in a region that does not support one-click configuration restoration of the Agent, on the Server Monitoring page, select the target ECS and click Restore Agent Configurations. In the displayed Restore Agent Configurations dialog box, click One-Click Restore.
+++ diff --git a/docs/ces/umn/ces_faq_0028.html b/docs/ces/umn/ces_faq_0028.html new file mode 100644 index 00000000..a22cfcb4 --- /dev/null +++ b/docs/ces/umn/ces_faq_0028.html @@ -0,0 +1,55 @@ + + +++Parent topic: Server Monitoring+How Can I Create an Agency?
+++Scenarios
Create an agency so that the Agent can automatically obtain the AK and SK. This frees you from exposing the AK or SK in the configuration file.
++Procedure
- Log in to the management console.
- Click
in the upper left to select a region and project. - Click Service List in the upper left corner, and select Identity and Access Management.
- In the navigation pane on the left, choose Agencies. In the upper right corner, click Create Agency.
- Configure the parameters by referring to Table 1.
++
+Table 1 Creating an agency Parameter
+Description
+Agency Name
+Specifies the name of the agency.
+Example: CESAgentAutoConfigAgency
+Agency Type
+Select Cloud service.
+Cloud Service
+Select Elastic Cloud Server (ECS) and Bare Metal Server (BMS) from the drop-down list.
+Validity Period
+Select Unlimited.
+Description
+(Optional) Provides supplementary information about the agency.
+ - In the Permissions area, click Modify in the row where the current region is located.
- In the Available Policies area on the left, enter CES. In the search result, select CES and CES Administrator.
- Click OK.
+Agency Configuration
If no agency is configured for a server, perform the following operations to configure an agency:
+- Log in to the management console.
- Choose Service List > Computing > Elastic Cloud Server. +
If you purchase a BMS, choose Computing > Bare Metal Server.
+ - Click the name of the target ECS on which the Agent is installed.
- In the Management Information area, select the agency created in 5 for Agency and click the green tick to make the agency take effect.
++ diff --git a/docs/ces/umn/ces_faq_0030.html b/docs/ces/umn/ces_faq_0030.html new file mode 100644 index 00000000..81dc6cf7 --- /dev/null +++ b/docs/ces/umn/ces_faq_0030.html @@ -0,0 +1,11 @@ + + +++Parent topic: Server Monitoring+What Can I Do If Agency CESAgentAutoConfigAgency Is Invalid?
++An invalid agency is an agency that has expired. If you set the agency Validity Period to Unlimited, the agency will become valid again. For details, see How Can I Create an Agency?
+++ diff --git a/docs/ces/umn/ces_faq_0031.html b/docs/ces/umn/ces_faq_0031.html new file mode 100644 index 00000000..69957bb1 --- /dev/null +++ b/docs/ces/umn/ces_faq_0031.html @@ -0,0 +1,11 @@ + + +++Parent topic: Server Monitoring+What Should I Do If the IAM Account Permissions Are Abnormal?
++To use server monitoring, users in a user group must have the Security Administrator permissions. If they do not, a message indicating abnormal permissions is displayed. Contact the account administrator to change the permissions.
+++ diff --git a/docs/ces/umn/ces_faq_0032.html b/docs/ces/umn/ces_faq_0032.html new file mode 100644 index 00000000..b1a766f0 --- /dev/null +++ b/docs/ces/umn/ces_faq_0032.html @@ -0,0 +1,11 @@ + + +++Parent topic: User Permissions+What Can't I Create Another Agency?
++It may be that your quota is used up. If this is the case, you can delete unneeded agencies first or increase the agency quota. Then you can use the agency to restore the Agent configuration.
+++ diff --git a/docs/ces/umn/ces_faq_0033.html b/docs/ces/umn/ces_faq_0033.html new file mode 100644 index 00000000..608e0cf5 --- /dev/null +++ b/docs/ces/umn/ces_faq_0033.html @@ -0,0 +1,12 @@ + + +++Parent topic: Server Monitoring+What Should I Do If Agency CESAgentAutoConfigAgency Failed to Be Automatically Created?
++When the Agent configuration is being restored, agency CESAgentAutoConfigAgency will be automatically created, but if you have created such an agency but not for the ECS or BMS service, agency CESAgentAutoConfigAgency will fail to be automatically created.
+You can delete the agency you created and then restore the Agent configuration, or manually configure the agency based on How Can I Create an Agency?
+++ diff --git a/docs/ces/umn/ces_faq_0037.html b/docs/ces/umn/ces_faq_0037.html new file mode 100644 index 00000000..da7f2c4d --- /dev/null +++ b/docs/ces/umn/ces_faq_0037.html @@ -0,0 +1,21 @@ + + +++Parent topic: Server Monitoring+What Should I Do If the Service Port Is Used by the Agent?
++Cloud Eye Agent uses HTTP requests to report data. Any port in the range obtained from path /proc/sys/net/ipv4/ip_local_port_range may be occupied. If any service port is used by the Agent, you can modify path /proc/sys/net/ipv4/ip_local_port_range and restart the Agent to solve the problem.
++Procedure
- Log in an ECS or BMS as user root.
- Open the sysctl.conf file:
vim /etc/sysctl.conf
+ - (Permanent change) Add new ports to the sysctl.conf file:
net.ipv4.ip_local_port_range=49152 65536
+ - Make the modification take effect:
++
- The permanent change still takes effect after the ECS or BMS is restarted.
- For temporary modification (which expires after the ECS or BMS is restarted), run # echo 49152 65536 > /proc/sys/net/ipv4/ip_local_port_range.
- Run the following command to restart the Agent:
/usr/local/telescope/telescoped restart
++ For Windows, in the directory where the Agent installation package is stored, double-click the shutdown.bat script to stop the Agent, and execute the start.bat script to start the Agent.
+
++ diff --git a/docs/ces/umn/ces_faq_0045.html b/docs/ces/umn/ces_faq_0045.html index 87741126..eb73cee7 100644 --- a/docs/ces/umn/ces_faq_0045.html +++ b/docs/ces/umn/ces_faq_0045.html @@ -2,7 +2,7 @@++Parent topic: Server Monitoring+Why Is the Monitoring Data Not Displayed on the Cloud Eye Console?
Possible causes are as follows:
-- The service is not interconnected with Cloud Eye. To check whether a service has been interconnected with Cloud Eye, see Services Interconnected with Cloud Eye.
- The service has been interconnected with Cloud Eye. However, the collection and monitoring frequency for each service varies. The data may have just not been collected yet.
- The ECS has been stopped for more than 1 hour.
- The EVS disk has not been attached to an ECS.
- No backend server is bound to the elastic load balancer or all of the backend servers are shut down.
- It has been less than 10 minutes since the resource was created.
- The service is not interconnected with Cloud Eye. To check whether a service has been interconnected with Cloud Eye, see Services Interconnected with Cloud Eye.
- The service has been interconnected with Cloud Eye. However, the collection and monitoring frequency for each service varies. The data may have just not been collected yet.
- The ECS or BMS has been stopped for more than 1 hour.
- The EVS disk has not been attached to an ECS or BMS.
- No backend server is bound to the elastic load balancer or all of the backend servers are shut down.
- It has been less than 10 minutes since the resource was created.
diff --git a/docs/ces/umn/ces_faq_0053.html b/docs/ces/umn/ces_faq_0053.html new file mode 100644 index 00000000..e6eea276 --- /dev/null +++ b/docs/ces/umn/ces_faq_0053.html @@ -0,0 +1,17 @@ + + +diff --git a/docs/ces/umn/en-us_topic_0018121651.html b/docs/ces/umn/en-us_topic_0018121651.html index 996cc217..a9640163 100644 --- a/docs/ces/umn/en-us_topic_0018121651.html +++ b/docs/ces/umn/en-us_topic_0018121651.html @@ -4,11 +4,16 @@Why Is a BMS with the Agent Installed Displayed in the ECS List on the Server Monitoring Page?
+++Symptoms
The Agent was installed on a BMS, but the BMS is listed on the Server Monitoring > Elastic Cloud Server page on the Cloud Eye console.
++Possible Causes
The Agent determines whether a server is an ECS or BMS based on the services provided by IP address 169.254.169.254. If the route for this address is changed, the Agent will consider the server to be an ECS by default.
++Solution
Manually modify the Agent configuration file by adding BMS identifier BmsFlag and setting it to true.
+- Linux OS: See (Optional) Manually Configuring the Agent (Linux).
- Windows OS: See (Optional) Manually Configuring the Agent on a Windows Server.
++ diff --git a/docs/ces/umn/ces_faq_0059.html b/docs/ces/umn/ces_faq_0059.html new file mode 100644 index 00000000..bae2a580 --- /dev/null +++ b/docs/ces/umn/ces_faq_0059.html @@ -0,0 +1,35 @@ + + + +++Parent topic: Server Monitoring+Server Monitoring
+ +++ +++ diff --git a/docs/ces/umn/ces_faq_0064.html b/docs/ces/umn/ces_faq_0064.html new file mode 100644 index 00000000..5813b6af --- /dev/null +++ b/docs/ces/umn/ces_faq_0064.html @@ -0,0 +1,16 @@ + + +-
+
- How Can I Quickly Restore the Agent Configuration?
+
+ - Why Is a BMS with the Agent Installed Displayed in the ECS List on the Server Monitoring Page?
+
+ - What Should I Do If the Service Port Is Used by the Agent?
+
+ - How Can I Create an Agency?
+
+ - What Can't I Create Another Agency?
+
+ - What Should I Do If Agency CESAgentAutoConfigAgency Failed to Be Automatically Created?
+
+ - What Can I Do If Agency CESAgentAutoConfigAgency Is Invalid?
+
+ - Does the Server Monitoring Agent Affect the Server Performance?
+
+ - What Should I Do If the Agent Status Is Faulty?
+
+
++Parent topic: FAQs+User Permissions
++++ + ++ diff --git a/docs/ces/umn/ces_faq_0071.html b/docs/ces/umn/ces_faq_0071.html new file mode 100644 index 00000000..f06237a9 --- /dev/null +++ b/docs/ces/umn/ces_faq_0071.html @@ -0,0 +1,15 @@ + + +++Parent topic: FAQs+Does the Server Monitoring Agent Affect the Server Performance?
++The Agent uses very minimal system resources and it has almost no impact on the server performance.
+ + +++ diff --git a/docs/ces/umn/en-us_image_0000001081906243.png b/docs/ces/umn/en-us_image_0000001081906243.png new file mode 100644 index 00000000..4ce04a43 Binary files /dev/null and b/docs/ces/umn/en-us_image_0000001081906243.png differ diff --git a/docs/ces/umn/en-us_image_0000001136164665.png b/docs/ces/umn/en-us_image_0000001136164665.png new file mode 100644 index 00000000..e47ffb8f Binary files /dev/null and b/docs/ces/umn/en-us_image_0000001136164665.png differ diff --git a/docs/ces/umn/en-us_image_0000001200355919.png b/docs/ces/umn/en-us_image_0000001200355919.png new file mode 100644 index 00000000..31df5449 Binary files /dev/null and b/docs/ces/umn/en-us_image_0000001200355919.png differ diff --git a/docs/ces/umn/en-us_image_0000001220595446.png b/docs/ces/umn/en-us_image_0000001220595446.png new file mode 100644 index 00000000..9976b179 Binary files /dev/null and b/docs/ces/umn/en-us_image_0000001220595446.png differ diff --git a/docs/ces/umn/en-us_image_0000001264836141.png b/docs/ces/umn/en-us_image_0000001264836141.png new file mode 100644 index 00000000..b2ff978e Binary files /dev/null and b/docs/ces/umn/en-us_image_0000001264836141.png differ diff --git a/docs/ces/umn/en-us_image_0000001379012402.png b/docs/ces/umn/en-us_image_0000001379012402.png new file mode 100644 index 00000000..88b5fe20 Binary files /dev/null and b/docs/ces/umn/en-us_image_0000001379012402.png differ diff --git a/docs/ces/umn/en-us_image_0000001425588773.png b/docs/ces/umn/en-us_image_0000001425588773.png new file mode 100644 index 00000000..ac79d0f6 Binary files /dev/null and b/docs/ces/umn/en-us_image_0000001425588773.png differ diff --git a/docs/ces/umn/en-us_image_0000001425731481.png b/docs/ces/umn/en-us_image_0000001425731481.png new file mode 100644 index 00000000..e01c2b9d Binary files /dev/null and b/docs/ces/umn/en-us_image_0000001425731481.png differ diff --git a/docs/ces/umn/en-us_image_0110267213.png b/docs/ces/umn/en-us_image_0110267213.png new file mode 100644 index 00000000..1909444d Binary files /dev/null and b/docs/ces/umn/en-us_image_0110267213.png differ diff --git a/docs/ces/umn/en-us_image_0129738465.png b/docs/ces/umn/en-us_image_0129738465.png index c8178848..2befc80e 100644 Binary files a/docs/ces/umn/en-us_image_0129738465.png and b/docs/ces/umn/en-us_image_0129738465.png differ diff --git a/docs/ces/umn/en-us_image_0146378778.png b/docs/ces/umn/en-us_image_0146378778.png new file mode 100644 index 00000000..3072249e Binary files /dev/null and b/docs/ces/umn/en-us_image_0146378778.png differ diff --git a/docs/ces/umn/en-us_image_0167222995.png b/docs/ces/umn/en-us_image_0167222995.png new file mode 100644 index 00000000..69856628 Binary files /dev/null and b/docs/ces/umn/en-us_image_0167222995.png differ diff --git a/docs/ces/umn/en-us_image_0183510251.png b/docs/ces/umn/en-us_image_0183510251.png new file mode 100644 index 00000000..a2e2726b Binary files /dev/null and b/docs/ces/umn/en-us_image_0183510251.png differ diff --git a/docs/ces/umn/en-us_image_0184026531.png b/docs/ces/umn/en-us_image_0184026531.png new file mode 100644 index 00000000..1303a51c Binary files /dev/null and b/docs/ces/umn/en-us_image_0184026531.png differ diff --git a/docs/ces/umn/en-us_image_0239599900.png b/docs/ces/umn/en-us_image_0239599900.png new file mode 100644 index 00000000..9976b179 Binary files /dev/null and b/docs/ces/umn/en-us_image_0239599900.png differ diff --git a/docs/ces/umn/en-us_image_0239656150.png b/docs/ces/umn/en-us_image_0239656150.png new file mode 100644 index 00000000..9976b179 Binary files /dev/null and b/docs/ces/umn/en-us_image_0239656150.png differ diff --git a/docs/ces/umn/en-us_image_0291629699.png b/docs/ces/umn/en-us_image_0291629699.png new file mode 100644 index 00000000..88bee18a Binary files /dev/null and b/docs/ces/umn/en-us_image_0291629699.png differ diff --git a/docs/ces/umn/en-us_topic_0000001360217524.html b/docs/ces/umn/en-us_topic_0000001360217524.html new file mode 100644 index 00000000..1ecd1721 --- /dev/null +++ b/docs/ces/umn/en-us_topic_0000001360217524.html @@ -0,0 +1,22 @@ + + +++Parent topic: Server Monitoring+Region and AZ
+++Concept
A region and availability zone (AZ) identify the location of a data center. You can create resources in a specific region and AZ.
+- A region is a physical data center, which is completely isolated to improve fault tolerance and stability. The region that is selected during resource creation cannot be changed after the resource is created.
- An AZ is a physical location where resources use independent power supplies and networks. A region contains one or more AZs that are physically isolated but interconnected through internal networks. Because AZs are isolated from each other, any fault that occurs in one AZ will not affect others.
Figure 1 shows the relationship between regions and AZs.
+ ++Selecting a Region
Select a region closest to your target users for lower network latency and quick access.
++Selecting an AZ
When deploying resources, consider your applications' requirements on disaster recovery (DR) and network latency.
+- For high DR capability, deploy resources in different AZs within the same region.
- For lower network latency, deploy resources in the same AZ.
+Regions and Endpoints
Before you use an API to call resources, specify its region and endpoint. For more details, see Regions and Endpoints.
+++ diff --git a/docs/ces/umn/en-us_topic_0000001374986910.html b/docs/ces/umn/en-us_topic_0000001374986910.html new file mode 100644 index 00000000..2bc046a0 --- /dev/null +++ b/docs/ces/umn/en-us_topic_0000001374986910.html @@ -0,0 +1,104 @@ + + +++Parent topic: Product Introduction+Viewing Details of an Alarm Rule
+++Procedure
- Log in to the management console.
- In the upper left corner, select a region and project.
- Click Service List in the upper left corner, and select Cloud Eye.
- Choose Alarm Management > Alarm Rules.
- On the displayed page, click the name of the alarm rule to be viewed.Figure 1 Alarm rule details+ +
+ +
+Table 1 Basic parameters Parameter
+Description
+Name
+Specifies the alarm rule name. The system generates a random name, which you can modify.
+Status
+Specifies whether the alarm rule is enabled or disabled.
+Alarm Type
+Specifies the type of the alarm rule.
+Description
+(Optional) Provides supplementary information about the alarm rule.
+Resource Type
+Specifies the type of the resource the alarm rule is created for.
+Dimension
+Specifies the metric dimension of the selected resource type.
+Last Modified
+Specifies the time when the alarm rule was last modified.
++ +
+Table 2 Monitored objects Parameter
+Description
+Resource Name
+Specifies the resource name.
+ID
+Specifies the resource ID.
+Last Status Update
+Specifies the time when the a resource alarm is last generated or cleared.
++
+Table 3 Alarm policies Parameter
+Description
+Alarm Policy
+Specifies the policy for triggering an alarm.
+For example, an alarm is triggered if the average value of the monitored metric is 80% or more for three consecutive 5-minute periods.
+Alarm Severity
+Specifies the alarm severity, which can be Critical, Major, Minor, or Informational.
+
++ diff --git a/docs/ces/umn/en-us_topic_0015479882.html b/docs/ces/umn/en-us_topic_0015479882.html index 9d09f639..95fd32dd 100644 --- a/docs/ces/umn/en-us_topic_0015479882.html +++ b/docs/ces/umn/en-us_topic_0015479882.html @@ -6,9 +6,11 @@++Parent topic: Alarm Rule Management+Cloud Eye provides the following functions:
- Automatic monitoring
Monitoring starts automatically after you created resources such as Elastic Cloud Servers (ECSs). On the Cloud Eye console, you can view the service status and set alarm rules for these resources.
+ - Server monitoring
After you install the Agent (Telescope) on an ECS and Bare Metal Server (BMS), you can collect 60-second granularity ECS and BMS monitoring data in real-time. Cloud Eye provides 40 metrics, such as CPU, memory, and disk metrics. For details, see Introduction to Server Monitoring.
- Flexible alarm rule configuration
You can create alarm rules for multiple resources at the same time. After you create an alarm rule, you can modify, enable, disable, or delete it at any time. For more information, see Alarm Rule Management.
- Real-time notification
You can enable Alarm Notification when creating alarm rules. When the cloud service status changes and metrics reach the thresholds specified in alarm rules, Cloud Eye notifies you by text messages, emails, or by sending messages to server addresses, allowing you to monitor the cloud resource status and changes in real time.
- Monitoring panel
The panel enables you to view cross-service and cross-dimension monitoring data. It displays key metrics, providing an overview of the service status and monitoring details that you can use for troubleshooting. For more information, see Introduction to Monitoring Panels.
+ - Resource group
A resource group allows you to add and monitor correlated resources and provides a collective health status for all resources that it contains.
- Data dump
You can use the data dump function to query metrics on the DMS for Kafka console or on an open-source Kafka client. It helps you dump cloud service monitoring data to Kafka in real time.
Cloud Eye provides multiple built-in metrics based on the characteristics of each service. After you enable one cloud service on the cloud platform, Cloud Eye automatically associates its built-in metrics. You can track the cloud service status by monitoring these metrics.
This topic describes how to view monitoring data of a cloud service resource.
Procedure
- Log in to the management console.
- In the upper left corner, select a region and project.
- Click Service List in the upper left corner, and select Cloud Eye.
- In the navigation pane on the left, choose Cloud Service Monitoring, and select a cloud service.
The cloud service page is displayed.
- - Locate the row that contains the cloud service resource you want to monitor and click View Metric in the Operation column.
On the page displayed, you can view graphs based on raw data collected in the last 1h, 3h, 12h, 1d, and 7d. In the upper right corner of the graph, the maximum and minimum values of the metric in the corresponding time periods are dynamically displayed. You can also enable Auto Refresh to view the real-time data refreshed every minute.
- - Hover your mouse over a graph and click
in the upper right corner.An enlarged graph of the metric is displayed, on which you can view the metric monitoring details for longer time ranges. In the upper left corner, you can see six default monitoring periods: 1h, 3h, 12h, 1d, 7d, and 30d. You can also view historical monitoring data for any period during the last six months by customizing the monitoring period in the upper right corner of the graph.
- - If you select 1h, 3h, 12h, or 1d, raw data is displayed by default. Near the top left corner of the page, you can click Settings to change the rollup period of the monitoring data. For more details about the rollup period, see What Is Rollup?.
- If you select 7d or 30d, aggregated data is displayed by default. Near the top left corner of the page, you can click Settings to change the rollup period of the monitoring data.
- Locate the row that contains the cloud service resource you want to monitor and click View Metric in the Operation column.
The detailed monitoring page is displayed.
+You can view graphs based on raw data collected in the last 1h, 3h, 12h, 1d, and 7d. In the upper right corner of the graph, the maximum and minimum values of the metric in the corresponding time periods are dynamically displayed. You can also enable Auto Refresh to view the real-time data refreshed every minute.+- - Metric units can be changed between byte or byte/s and GB or GB/s on graphs. When you are changing the unit, if the maximum value of a metric is smaller than 10^ (-5), both the maximum value and the minimum value of this metric are 0. In addition, all data displayed on the graph is 0.
- If Auto Refresh is enabled, data is automatically refreshed every minute.
- You can search for a specific metric in the search box.
- Some cloud services allow you to view resource details. You can click View Resource Details in the upper part of the page to view details about monitored resources.
- In the upper right corner of the monitoring graph, click
to create alarm rules for the metric. For details about the parameters, see Creating an Alarm Rule for a Specific Metric.- To export data, click Export Data on the Cloud Service Monitoring page, configure parameters as prompted, and click Export. For details, see How Can I Export Collected Data?.
+- Near the top right corner of the page, click Select Metric.
The Select Metric dialog box is displayed.
+Select at least one metric. Drag and drop the selected metrics at desired locations to sort them. This helps you customize metrics to be viewed.
+- Hover your mouse over a graph and click
in the upper right corner.An enlarged graph of the metric is displayed, on which you can view the metric monitoring details for longer time ranges. In the upper left corner, you can see six default monitoring periods: 1h, 3h, 12h, 1d, 7d, and 30d. You can also view historical monitoring data for any period during the last six months by customizing the monitoring period in the upper right corner of the graph.
++ - If you select 1h, 3h, 12h, or 1d, raw data is displayed by default. Near the top left corner of the page, you can click Settings to change the rollup period of the monitoring data. For details about the rollup period, see What Is Rollup?.
- If you select 7d or 30d, aggregated data is displayed by default. Near the top left corner of the page, you can click Settings to change the rollup period of the monitoring data.
- In the upper right corner of the monitoring view, click
to create an alarm rule for a metric. For details about the parameters, see Creating an Alarm Rule for a Specific Metric. - To export data, click Export Data on the Cloud Service Monitoring page, configure parameters as prompted, and click Export. For details, see How Can I Export Collected Data?
diff --git a/docs/ces/umn/en-us_topic_0078721772.html b/docs/ces/umn/en-us_topic_0078721772.html new file mode 100644 index 00000000..1410284e --- /dev/null +++ b/docs/ces/umn/en-us_topic_0078721772.html @@ -0,0 +1,20 @@ + + +Introduction to Server Monitoring
++Server monitoring includes basic monitoring, process monitoring, and OS monitoring for servers.
+- Basic monitoring covers metrics automatically reported by ECSs. The data is collected every 5 minutes. For details, see Services Interconnected with Cloud Eye.
- OS monitoring provides proactive and fine-grained OS monitoring for ECSs or BMSs, and it requires the Agent to be installed on all servers that will be monitored. The data is collected every minute. OS monitoring supports metrics such as CPU usage and memory usage (Linux). For details, see Services Interconnected with Cloud Eye.
- Process monitoring provides monitoring of active processes on hosts. By default, Cloud Eye collects CPU usage, memory usage, and number of opened files of active processes.
+ - For the ECS specifications, use 2 vCPUs and 4 GB memory for a Linux ECS and 4 vCPUs and 8 GB memory or higher specifications for a Windows ECS.
- The Agent will use the system ports. For details, see descriptions of ClientPort and PortNum in (Optional) Manually Configuring the Agent (Linux). If the Agent port conflicts with a service port, see What Should I Do If the Service Port Is Used by the Agent?
- To install the Agent in a Linux server, you must have the root permissions. For a Windows server, you must have the administrator permissions.
+Scenarios
Whether you are using ECSs or BMSs, you can use server monitoring to track various OS metrics, monitor server resource usage, and query monitoring data when faults occur.
++Monitoring Capabilities
Server monitoring provides multiple metrics, such as metrics for CPU, memory, disk, and network usage, meeting the basic monitoring and O&M requirements for servers.
++Resource Usage
The Agent uses considerably less resources. When the Agent is installed on a server, it uses less than 5% of the CPU and less than 100 MB of memory.
+++ diff --git a/docs/ces/umn/en-us_topic_0079332017.html b/docs/ces/umn/en-us_topic_0079332017.html new file mode 100644 index 00000000..4c80f8bc --- /dev/null +++ b/docs/ces/umn/en-us_topic_0079332017.html @@ -0,0 +1,23 @@ + + +++Parent topic: Server Monitoring+Viewing Server Monitoring Metrics
+++Scenarios
This topic describes how to view server monitoring metrics, including fine-grained OS metrics collected by the Agent and basic ECS metrics.
+For details, see Services Interconnected with Cloud Eye.
++Prerequisites
You have installed the Agent. For details, see Installing and Configuring the Agent on a Linux ECS or BMS and Installing and Configuring the Agent on a Windows Server.
++Procedure
- Log in to the management console.
- Click Service List in the upper left corner, and select Cloud Eye.
- View ECS or BMS metrics.
- To view OS monitoring metrics of an ECS, in the left navigation pane, choose Server Monitoring > Elastic Cloud Server, locate the ECS, and click View Metric in the Operation column.
- To view basic monitoring metrics of an ECS, click the Basic Monitoring tab.
- To view OS monitoring metrics of a BMS, in the left navigation pane, choose Server Monitoring > Bare Metal Server, locate the BMS, and click View Metric in the Operation column.
- To view processing monitoring metrics, click the Process Monitoring tab.
- View metrics.
In the upper part of the OS Monitoring page, different metric types, such as CPU, memory, and disk metrics are displayed.
+View metric graphs based on raw data from the last 1 hour, last 3 hours, last 12 hours, last 1 day, last 7 days, or last 30 days. Cloud Eye provides the Auto Refresh function at 60-second intervals.
+ - Hover your mouse over a graph. In the upper right corner, click
to enlarge the graph for viewing detailed data.In the upper left corner, you can see six default monitoring periods: 1h, 3h, 12h, 1d, 7d, and 30d. To view historical monitoring data for any period during the last six months, customize the monitoring period by setting Select Range in the upper right corner.
+ - In the upper left corner of the graph, click Settings to configure the rollup method.
- If you select 1h, 3h, 12h, or 1d, raw data is displayed by default.
- If you select 7d or 30d, aggregated data is displayed by default.
- After clicking the zoom in icon in the upper right of an enlarged graph, you can drag the mouse to customize the time range.
++ diff --git a/docs/ces/umn/en-us_topic_0084572213.html b/docs/ces/umn/en-us_topic_0084572213.html index 41096141..aaee7deb 100644 --- a/docs/ces/umn/en-us_topic_0084572213.html +++ b/docs/ces/umn/en-us_topic_0084572213.html @@ -3,46 +3,48 @@++Parent topic: Server Monitoring+Creating an Alarm Rule by Using an Alarm Template
Cloud Eye allows you to use alarm templates to create alarm rules, making it easy and convenient to add or modify alarm rules for resources or cloud services, especially for a large number of resources and cloud services.
This topic describes how to use a default alarm template to create an alarm rule for a cloud service resource.
-Creating an Alarm Rule
- Log in to the management console.
- In the upper left corner, select a region and project.
- Click Service List in the upper left corner, and select Cloud Eye.
- In the navigation pane on the left, choose Alarm Management > Alarm Rules.
- Click Create Alarm Rule in the upper right corner.
- On the Create Alarm Rule page, follow the prompts to configure the parameters.
- Select an object and configure other parameters listed in Table 1. Click Next.-
Table 1 Parameters Parameter
+Creating an Alarm Rule
- Log in to the management console.
- In the upper left corner, select a region and project.
- Click Service List in the upper left corner, and select Cloud Eye.
- In the navigation pane on the left, choose Alarm Management > Alarm Rules.
- Click Create Alarm Rule in the upper right corner.
- On the Create Alarm Rule page, follow the prompts to configure the parameters.
- Select an object and configure other parameters listed in Table 1. Click Next.+
You can search for ECSs by name, ID, and IP address. For other cloud services, you can search only by ID.
++Table 1 Parameters Parameter
Description
+Description
Name
+Name
Specifies the alarm rule name. The system generates a random name, which you can modify.
-Example value: alarm-b6al
+Specifies the alarm rule name. The system generates a random name, which you can modify.
+Example value: alarm-b6al
Description
+Description
(Optional) Provides supplementary information about the alarm rule.
+(Optional) Provides supplementary information about the alarm rule.
Resource Type
+Resource Type
Specifies the type of the resource the alarm rule is created for.
+Specifies the type of the resource the alarm rule is created for.
Example value: Elastic Cloud Server
Dimension
+Dimension
Specifies the metric dimension of the selected resource type.
+Specifies the metric dimension of the selected resource type.
Example value: ECSs
Monitoring Scope
+Monitoring Scope
Specifies the monitoring scope the alarm rule applies to. You can select Resource groups or Specific resources.
+Specifies the monitoring scope the alarm rule applies to. You can select Resource groups or Specific resources.
NOTE:- If Resource groups is selected, an alarm is triggered when any resource in the group meets the alarm policy.
- If Resource groups is selected, alarm rules cannot be created using templates.
Monitored Object
+Monitored Object
Specifies the resource the alarm rule is created for. You can specify one or more resources.
+Specifies the resource the alarm rule is created for. You can specify one or more resources.
Notification Object
Specifies the object that receives alarm notifications. You can select the account contact or a topic.- Account contact is the mobile phone number and email address of the registered account.
- Topic: A topic is used to publish messages and subscribe to notifications. If the required topic is unavailable, create one first and add subscriptions to it. For details, see Creating a Topic and Adding Subscriptions.
Specifies the object that receives alarm notifications. You can select the account contact or a topic.- Account contact is the mobile phone number and email address of the registered account.
- Topic: A topic is used to publish messages and subscribe to notifications. If the required topic is unavailable, create one first and add subscriptions to it. For details, see Creating a Topic and Adding Subscriptions.
Validity Period
Cloud Eye sends notifications only within the validity period specified in the alarm rule.
-If Validity Period is set to 08:00-20:00, Cloud Eye sends notifications only within 08:00-20:00.
+If Validity Period is set to 08:00-20:00, Cloud Eye sends notifications only within 08:00-20:00.
Trigger Condition
@@ -93,7 +95,7 @@ -After the alarm rule is created, if the metric data reaches the specified threshold, Cloud Eye immediately informs you that an exception has occurred.
+After the alarm rule is created, if the metric data reaches the specified threshold, Cloud Eye immediately informs you that an exception has occurred.
To view monitoring graphs, click View Graph or View Resource in the Operation column, and click View Graph in the displayed View Resource dialog box.
diff --git a/docs/ces/umn/en-us_topic_0084572222.html b/docs/ces/umn/en-us_topic_0084572222.html index d2345a84..9c973e75 100644 --- a/docs/ces/umn/en-us_topic_0084572222.html +++ b/docs/ces/umn/en-us_topic_0084572222.html @@ -7,10 +7,14 @@- General Consulting
+ - Server Monitoring
+ - Alarm Notifications or False Alarms
- Monitored Data Exceptions
+ - User Permissions
+
Adding Subscriptions
A topic is a channel used by SMN to broadcast messages. Therefore, after you create a topic, add subscriptions. In this way, when the metric triggers an alarm, Cloud Eye sends the alarm information to subscription endpoints of the topic.
-Adding Subscriptions
- Log in to the management console.
- In the upper left corner, select a region and project.
- Under Application, select Simple Message Notification.
The SMN console is displayed.
+Adding Subscriptions
- Log in to the management console.
- In the upper left corner, select a region and project.
- Under Application, select Simple Message Notification.
The SMN console is displayed.
In the navigation pane on the left, choose Topics.
The Topics page is displayed.
- Locate the topic you want to add subscriptions to, click More under Operation, and select Add Subscription.
The Add Subscription dialog box is displayed.
-Figure 1 Adding Subscriptions+
Figure 1 Adding a subscription - Specify the subscription protocol and endpoints.
If you enter multiple endpoints, enter each endpoint on a separate line.
- Click OK.
The subscription you added is displayed in the subscription list.
+After the subscription is added, the corresponding subscription endpoint will receive a subscription notification. You need to confirm the subscription so that the endpoint can receive alarm notifications.
diff --git a/docs/ces/umn/en-us_topic_0085216039.html b/docs/ces/umn/en-us_topic_0085216039.html index 0d0bdb4a..b64f8eb6 100644 --- a/docs/ces/umn/en-us_topic_0085216039.html +++ b/docs/ces/umn/en-us_topic_0085216039.html @@ -8,7 +8,7 @@In the navigation pane on the left, choose Topics.
The Topics page is displayed.
- Click Create Topic.
The Create Topic dialog box is displayed.
-Figure 1 Create Topic+
Figure 1 Creating a topic
- Enter a topic name and display name (topic description).
Table 1 Parameters required for creating a topic Parameter
Tag
Tags identify cloud resources so that they can be categorized easily and searched quickly.
-- You can enter a maximum of 36 and 43 characters for Key and Value, respectively. Both Key and Value cannot start or end with a space and cannot contain any of the following special characters:=, *, <, >, \, ,, |, /
- Each topic supports up to 10 tags.
- For each resource, each tag key must be unique, and each tag key can have only one tag value.
- You can enter a maximum of 36 and 43 characters for a tag key and a tag value, respectively. Only digits, letters, hyphens (-), at signs (@), and underscores (_) are allowed.
- Each topic supports up to 20 tags.
Viewing Process Monitoring
++Process monitoring is used to monitor active processes on a host. By default, the Agent collects CPU usage, memory usage, and the number of opened files of the active processes. If you have customized process monitoring, the number of processes containing keywords is also monitored.
+The Agent collects process CPU usages once every minute and displays the top 5 processes, ranked by the CPU usage over the last 24 hours.
++ To view the process monitoring information, install the Agent.
++Querying the System Processes
After the Agent is installed, you can check system processes on Cloud Eye.
+To query the number of processes
+- Log in to the management console.
- Click Service List in the upper left corner, and select Cloud Eye.
- In the navigation pane on the left, choose Server Monitoring.
- On the Server Monitoring page, locate the row that contains the target ECS and click View Metric to go to the OS Monitoring page.
- Select the Process Monitoring tab.In the System Processes area, the process information is displayed. Table 1 describes the metrics of system processes. +++
+Table 1 System process metrics Metric
+Description
+Value Range
+Collection Mode (Linux)
+Collection Mode (Windows)
+Running Processes
+Number of processes that are running
+≥ 0
+Monitored object: ECS or BMS
+You can obtain the state of each process by checking the Status value in the /proc/pid/status file, and then collect the total number of processes in each state.
+Not supported
+Idle Processes
+Number of processes that are idle
+≥ 0
+Monitored object: ECS or BMS
+You can obtain the state of each process by checking the Status value in the /proc/pid/status file, and then collect the total number of processes in each state.
+Not supported
+Zombie Processes
+Number of zombie processes
+≥ 0
+Monitored object: ECS or BMS
+You can obtain the state of each process by checking the Status value in the /proc/pid/status file, and then collect the total number of processes in each state.
+Not supported
+Blocked Processes
+Number of processes that are blocked
+≥ 0
+Monitored object: ECS or BMS
+You can obtain the state of each process by checking the Status value in the /proc/pid/status file, and then collect the total number of processes in each state.
+Not supported
+Sleeping Processes
+Number of processes that are sleeping
+≥ 0
+Monitored object: ECS or BMS
+You can obtain the state of each process by checking the Status value in the /proc/pid/status file, and then collect the total number of processes in each state.
+Not supported
+Total Processes
+Total number of processes
+≥ 0
+Monitored object: ECS or BMS
+You can obtain the state of each process by checking the Status value in the /proc/pid/status file, and then collect the total number of processes in each state.
+Monitored object: ECS or BMS
+Obtain the total number of processes by using the system process status support module psapi.dll.
+
+Viewing the Running Data of Top CPU Processes
- The Agent collects process CPU usages once every minute and displays the top 5 processes, ranked by the CPU usage over the last 24 hours.
- Run the top command to query the CPU usage and memory usage of a process.
- Run the lsof or ls /proc/pid/fd |wc -l command to query the number of files opened by the current process. In the command, replace pid with the ID of the process to be queried.+
- If a process occupies multiple CPUs, the CPU usage may exceed 100% because the collection result is the total usage of multiple CPUs.
- The top 5 processes are not fixed. The process list displays the top 5 processes that have entered the statistical period of 1 minute in the last 24 hours.
- The CPU usage, memory usage, and number of opened files are collected only for the top 5 processes for which monitoring has been enabled in the last 24 hours. If such a process has been stopped, its data will not be displayed.
- The time in the list indicates the time when the process is created.
- If the system time on the client browser is different from that on the monitored ECS, the graph may have no metric data. In this case, synchronize the local time with the ECS time.
To query information about top 5 processes with the highest CPU usages
+- Log in to the management console.
- Click Service List in the upper left corner, and select Cloud Eye.
- In the navigation pane on the left, choose Server Monitoring.
- On the Server Monitoring page, locate the row that contains the target ECS and click View Metric to go to the OS Monitoring page.
- Select the Process Monitoring tab.
- In the Monitored Processes area, click
in the upper right corner to view Top 5 Processes with Highest CPU Usage. - In the displayed TOP 5 Processes with Highest CPU Usage window, enable process monitoring for target processes, and click OK.
In the Monitored Processes area, the system selects processes in the Running state by default and displays CPU usage curves of those processes in 1h. The displayed data is raw data.
+You can also select the process to be displayed and view its CPU usage curve in 1h.
+You can click CPU Usage, Memory Usage, or Open Files above the graph to view the curves of different metrics of the currently displayed process. Table 2 lists Process Monitoring metrics.
+ + ++
+Table 2 Process Monitoring metrics Metric
+Description
+Value Range
+Collection Mode (Linux)
+Collection Mode (Windows)
+CPU Usage
+Specifies the usage of CPU consumed by a process.
+pHashId (process name and process ID) is the value of md5.
+0–100%
+Monitored object: ECS or BMS
+Check the metric value changes in file /proc/pid/stat.
+Monitored object: ECS or BMS
+Call Windows API GetProcessTimes to obtain the CPU usage of the process.
+Memory Usage
+Specifies the memory consumed by a process. pHashId (process name and process ID) is the value of md5.
+0–100%
+Monitored object: ECS or BMS
+Memory Usage = RSS*PAGESIZE/MemTotal
+RSS: Obtain its value by checking the second column of file /proc/pid/statm.
+PAGESIZE: Obtain its value by running the getconf PAGESIZE command.
+MemTotal: Obtain its value by checking file /proc/meminfo.
+Monitored object: ECS or BMS
+Invoke Windows API procGlobalMemoryStatusEx to obtain the total memory size. Invoke GetProcessMemoryInfo to obtain the used memory size. Use the used memory size to divide the total memory size to get the memory usage.
+Open Files
+Specifies the number of opened files consumed by the process.
+pHashId (process name and process ID) is the value of md5.
+≥ 0
+Monitored object: ECS or BMS
+You can run the ls -l /proc/pid/fd command to view the number.
+Not supported
+ - Hover your mouse over a graph. In the upper right corner, click
to enlarge the graph for viewing detailed data.In the upper left corner, you can see six default monitoring periods: 1h, 3h, 12h, 1d, 7d, and 30d. To view historical monitoring data for any period during the last six months, customize the monitoring period by setting Select Range in the upper right corner.
+In the upper left corner of the graph, you can click Settings to configure the rollup method.
+
++ diff --git a/docs/ces/umn/en-us_topic_0094279601.html b/docs/ces/umn/en-us_topic_0094279601.html index 36488c9e..3a35c326 100644 --- a/docs/ces/umn/en-us_topic_0094279601.html +++ b/docs/ces/umn/en-us_topic_0094279601.html @@ -4,10 +4,10 @@++Parent topic: Process Monitoring+- diff --git a/docs/ces/umn/en-us_topic_0202622212.html b/docs/ces/umn/en-us_topic_0202622212.html index 3465539a..8c89bfca 100644 --- a/docs/ces/umn/en-us_topic_0202622212.html +++ b/docs/ces/umn/en-us_topic_0202622212.html @@ -6,7 +6,7 @@The Custom Monitoring page displays all custom metrics reported by users. You can use simple API requests to report collected monitoring data of those metrics to Cloud Eye for processing and display.
-Viewing Custom Monitoring
- Log in to the management console.
- Click Service List in the upper left corner, and select Cloud Eye.
- In the navigation pane on the left, choose Custom Monitoring.
- On the Custom Monitoring page, view the data reported by yourself through API requests, including custom services and metrics.-
- Only after you add monitoring data through APIs, will those data be displayed on the Cloud Eye console.
- For details about how to add monitoring data, see section "Adding Monitoring Data" in the Cloud Eye API Reference.
- Locate the row that contains the cloud service resource to be viewed, and click View Metric.
On the page displayed, you can view graphs based on raw data collected in 1h, 3h, 12h, 1d, and 7d. In the upper right corner of each graph, the maximum and minimum values of the metric in the corresponding time periods are dynamically displayed.
+ - Locate the row that contains the cloud service resource to be viewed, and click View Metric.
On the page displayed, you can view graphs based on raw data collected in 1h, 3h, 12h, 24h, and 7d. In the upper right corner of each graph, the maximum and minimum values of the metric in the corresponding time periods are dynamically displayed.
diff --git a/docs/ces/umn/en-us_topic_0102570567.html b/docs/ces/umn/en-us_topic_0102570567.html new file mode 100644 index 00000000..40f8cf1d --- /dev/null +++ b/docs/ces/umn/en-us_topic_0102570567.html @@ -0,0 +1,11 @@ + + +Creating an Alarm Rule
- Log in to the management console.
- Click Service List in the upper left corner, and select Cloud Eye.
- In the navigation pane on the left, choose Custom Monitoring.
- On the Custom Monitoring page, locate the target resource and click Create Alarm Rule in the Operation column.
- In the Create Alarm Rule dialog box, follow the prompts to configure the parameters. For details, see Table 2.
- Click Create.
Creating an Alarm Rule
- Log in to the management console.
- Click Service List in the upper left corner, and select Cloud Eye.
- In the navigation pane on the left, choose Custom Monitoring.
- On the Custom Monitoring page, locate the target resource and click Create Alarm Rule in the Operation column.
- In the Create Alarm Rule dialog box, follow the prompts to configure the parameters. For details, see Table 2.
- Click Create.
Introduction to Resource Groups
++A resource group allows you to add and monitor correlated resources and provides a collective health status for all resources that it contains.
+++ diff --git a/docs/ces/umn/en-us_topic_0109974074.html b/docs/ces/umn/en-us_topic_0109974074.html new file mode 100644 index 00000000..b2505fbe --- /dev/null +++ b/docs/ces/umn/en-us_topic_0109974074.html @@ -0,0 +1,14 @@ + + +++Parent topic: Resource Groups+Introduction to Event Monitoring
++In event monitoring, you can query system events that are automatically reported to Cloud Eye and custom events reported to Cloud Eye through the API. You can create alarm rules for both system events and custom events. When specific events occur, Cloud Eye generates alarms for you. Event monitoring does not depend on the Agent.
+Events are key operations on cloud service resources that are stored and monitored by Cloud Eye. You can view events to see operations performed by specific users on specific resources, such as deleting or rebooting an ECS.
+Event monitoring is enabled by default. For details, see Events Supported by Event Monitoring.
+Event monitoring provides an API for reporting custom events, which helps you collect and report abnormal events or important change events generated by services to Cloud Eye.
+++ diff --git a/docs/ces/umn/en-us_topic_0110258146.html b/docs/ces/umn/en-us_topic_0110258146.html new file mode 100644 index 00000000..85ff63e2 --- /dev/null +++ b/docs/ces/umn/en-us_topic_0110258146.html @@ -0,0 +1,42 @@ + + +++Parent topic: Event Monitoring+Installing and Configuring the Agent on a Windows Server
+++Scenarios
This topic describes how to install the Agent on a Windows ECS.
++Constraints
The Agent cannot be installed on Windows BMSs.
++Prerequisites
- You have performed operations described in Modifying the DNS Server Address and Adding Security Group Rules (Windows).
- Use an administrator account to install the Agent.
- Ensure that the Telescope process is not stopped by other processes after the installation.
- You have obtained the Agent installation package (Windows).
++
+Table 1 Installation package path Name
+Format
+Download Path
+Installation package for 64-bit Windows
+zip
+EU-DE: http://telescope-eu-de.obs.eu-de.otctest.t-systems.com/agent/telescope_windows_amd64.zip
+
+Procedure
- Log in to the Windows ECS as an administrator.
- Open a browser, and enter the address of the Agent installation package in the address box to download and save the installation package.
- Create a directory for storing the installation package (for example, D:\Agent) and decompress the package to this directory.
- Double-click the install.bat script to install and start the Agent.
If Install service success is displayed, the Agent is successfully installed and started.
++ After you configure the Agent, its status is still displayed as Uninstalled because no monitoring data is reported yet. Wait 3 to 5 minutes and refresh the page.
+ - On the Server Monitoring page, select the target ECS and click Restore Agent Configurations.
- In the displayed Restore Agent Configurations dialog box, click One-Click Restore.
The Agent configuration is completed.
+If the Agent is in the Running state, the Agent has been installed and has started to collect fine-grained metric data.
+
++ diff --git a/docs/ces/umn/en-us_topic_0135532770.html b/docs/ces/umn/en-us_topic_0135532770.html new file mode 100644 index 00000000..f7eb7425 --- /dev/null +++ b/docs/ces/umn/en-us_topic_0135532770.html @@ -0,0 +1,17 @@ + + +++Parent topic: Installing and Configuring the Agent on a Windows ECS+Resource Groups
+ ++ ++ diff --git a/docs/ces/umn/en-us_topic_0150354069.html b/docs/ces/umn/en-us_topic_0150354069.html new file mode 100644 index 00000000..715f64b5 --- /dev/null +++ b/docs/ces/umn/en-us_topic_0150354069.html @@ -0,0 +1,84 @@ + + +Modifying the DNS Server Address and Adding Security Group Rules (Linux)
+++Scenarios
This topic describes how to add the DNS server address and security group rules to a Linux ECS or BMS to ensure successful downloading of the Agent installation package and successful monitoring data collection. This topic takes an ECS as an example. The operations for BMSs are similar.
+You can modify the DNS server address of an ECS via command lines or the management console.
++ DNS and security group configuration are intended for the primary NIC.
++Modifying the DNS Server Address (Command Lines)
The following describes how to add the DNS server address to the resolv.conf file using command lines.
+To use the management console, see Modifying the DNS Server Address (Management Console).
+- Log in to an ECS as user root.
- Run the vi /etc/resolv.conf command to open the file.
- Add the DNS server address, for example, nameserver 100.125.4.25 to the file. Enter :wq and press Enter to save the change.Figure 1 Adding the DNS server address (Linux)+
+Modifying the DNS Server Address (Management Console)
The following describes how to modify the DNS server address of an ECS on the management console. This topic takes an ECS as an example. The operations for BMSs are similar.
+- In the upper left corner, select a region and project.
- Click Service List in the upper left corner. Under Compute, select Elastic Cloud Server.
On the ECS console, click the name of the target ECS to view its details.
+ - Click the VPC name on the right of VPC to go to the VPC console.
- Click the name of the target VPC.
- In the Networking Components area, click the number following Subnets.
The Subnets page is displayed.
+ - In the subnet list, click the name of target subnet.
- In the Gateway and DNS Information area, click
following DNS Server Address. - Change the DNS server address to 100.125.4.25.
- Click OK.+
The new DNS server address takes effect after the ECS or BMS is restarted.
+
+Modifying the ECS Security Group Rules (Management Console)
The following describes how to modify security group rules for an ECS on the management console. This topic takes an ECS as an example. The operations for BMSs are similar.
+- On the ECS details page, click the Security Groups tab.
The security group list is displayed.
+ - Click the security group name.
- Click Modify Security Group Rule.
The security group details page is displayed.
++ Procedure for BMS:
+- Click the security group ID on the upper left.
- Click Manage Rule in the Operation column of the security group.
- Click the Outbound Rules tab, and click Add Rule.
- Add rules based on Table 1.
++
+Table 1 Security group rules Protocol
+Port
+Type
+Destination
+Description
+TCP
+80
+IPv4
+100.125.0.0/16
+Used to download the Agent installation package from an OBS bucket to an ECS or BMS and obtain the ECS or BMS metadata and authentication information.
+TCP and UDP
+53
+IPv4
+100.125.0.0/16
+Used by DNS to resolve domain names, for example, resolve the OBS domain name when you are downloading the Agent installation package, and resolve the Cloud Eye endpoint when the Agent is sending monitoring data to Cloud Eye.
+TCP
+443
+IPv4
+100.125.0.0/16
+Used to collect monitoring data and send the data to Cloud Eye.
+
++ diff --git a/docs/ces/umn/en-us_topic_0150366044.html b/docs/ces/umn/en-us_topic_0150366044.html new file mode 100644 index 00000000..b7a05d19 --- /dev/null +++ b/docs/ces/umn/en-us_topic_0150366044.html @@ -0,0 +1,82 @@ + + ++ ++Modifying the DNS Server Address and Adding Security Group Rules (Windows)
+++Scenarios
This topic describes how to add the DNS server address and security group rules to a Windows ECS to ensure successful downloading of the Agent installation package and successful monitoring data collection.
+The DNS server address of an ECS can be modified in either of the following ways: Windows GUI or management console. Choose a method based on your habits.
++ DNS and security group configuration are intended for the primary NIC.
++Modifying the DNS Server Address (Windows GUI)
The following describes how to use the Windows GUI to add the DNS server address.
+- Click Service List in the upper left corner. Under Compute, select Elastic Cloud Server. Use VNC to log in to the Windows ECS.
- Choose Control Panel > Network and Sharing Center, and click Change adapter settings.
- Right-click the used network, choose Settings from the shortcut menu, and configure the DNS.
+Modifying the DNS Server Address (Management Console)
The following describes how to modify the DNS server address of an ECS on the management console. This topic takes an ECS as an example. The operations for BMSs are similar.
+- In the upper left corner, select a region and project.
- Click Service List in the upper left corner. Under Compute, select Elastic Cloud Server.
On the ECS console, click the name of the target ECS to view its details.
+ - Click the VPC name on the right of VPC to go to the VPC console.
- Click the name of the target VPC.
- In the Networking Components area, click the number following Subnets.
The Subnets page is displayed.
+ - In the subnet list, click the name of target subnet.
- In the Gateway and DNS Information area, click following DNS Server Address.
- Change the DNS server address to 100.125.4.25.
- Click OK.+
The new DNS server address takes effect after the ECS or BMS is restarted.
+
+Modifying the ECS Security Group Rules (Management Console)
The following describes how to modify security group rules for an ECS on the management console. This topic takes an ECS as an example. The operations for BMSs are similar.
+- On the ECS details page, click the Security Groups tab.
The security group list is displayed.
+ - Click the security group name.
- Click Modify Security Group Rule.
The security group details page is displayed.
++ Procedure for BMS:
+- Click the security group ID on the upper left.
- Click Manage Rule in the Operation column of the security group.
- Click the Outbound Rules tab, and click Add Rule.
- Add rules based on Table 1.
++
+Table 1 Security group rules Protocol
+Port
+Type
+Destination
+Description
+TCP
+80
+IPv4
+100.125.0.0/16
+Used to download the Agent installation package from an OBS bucket to an ECS or BMS and obtain the ECS or BMS metadata and authentication information.
+TCP and UDP
+53
+IPv4
+100.125.0.0/16
+Used by DNS to resolve domain names, for example, resolve the OBS domain name when you are downloading the Agent installation package, and resolve the Cloud Eye endpoint when the Agent is sending monitoring data to Cloud Eye.
+TCP
+443
+IPv4
+100.125.0.0/16
+Used to collect monitoring data and send the data to Cloud Eye.
+
++ diff --git a/docs/ces/umn/en-us_topic_0154940152.html b/docs/ces/umn/en-us_topic_0154940152.html index 67273a10..d75c2c6c 100644 --- a/docs/ces/umn/en-us_topic_0154940152.html +++ b/docs/ces/umn/en-us_topic_0154940152.html @@ -16,5 +16,4 @@++Parent topic: Installing and Configuring the Agent on a Windows ECS+Service
Namespace
+Namespace
Reference
Storage
+Storage
Elastic Volume Service (attached to an ECS or BMS)
Cloud Backup and Recovery
+SYS.CBR
++ +Network
Elastic IP and bandwidth
@@ -106,13 +113,15 @@Database
+Database
Relational Database Service
SYS.RDS
+ + + Document Database Service
@@ -122,6 +131,27 @@GaussDB NoSQL
+SYS.NoSQL
++ +GaussDB(for MySQL)
+SYS.GAUSSDB
++ +GaussDB(for openGauss)
+SYS.GAUSSDBV5
++ +Data analysis
Data Warehouse Service
@@ -142,4 +172,5 @@
- Select an object and configure other parameters listed in Table 1. Click Next.
- Select an object and configure other parameters listed in Table 1. Click Next.
Dimension
Specifies the metric dimension of the selected resource type.
-Example value: ECSs
+Example value: ECSs
Monitoring Scope
diff --git a/docs/ces/umn/ces_01_0076.html b/docs/ces/umn/ces_01_0076.html index a150d2f1..558a4afa 100644 --- a/docs/ces/umn/ces_01_0076.html +++ b/docs/ces/umn/ces_01_0076.html @@ -1,12 +1,12 @@ -Viewing Alarm Records
-The alarm records display the status changes of all alarm rules in the last 30 days.
+Viewing Alarm History
+The Alarm History page can display the status changes of all alarm rules in the last 30 days.
When an alarm is generated, you can view the alarm details about the cloud resource.
-