You must create a monitoring panel before you add graphs. You can create a maximum of 20 monitoring panels.
-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 Dashboard > Monitoring Panels and click Create Panel.
The Create Panel dialog box is displayed.
- - Set the panel name.
Enter a maximum of 128 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.
+Creating a Dashboard
+You must create a dashboard before you add graphs. You can create a maximum of 20 dashboards.
+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 Dashboard. Click Create Dashboard in the upper right corner.
The Create Dashboard dialog box is displayed.
+ - Set the dashboard name.
- Name: Enter a maximum of 128 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.
- (Optional) Enterprise Project: If you associate a dashboard with an enterprise project, only users who have the permissions of the enterprise project can manage the dashboard.+
The enterprise project feature is available only in some regions.
+
- Click OK.
diff --git a/docs/ces/umn/ces_01_0012.html b/docs/ces/umn/ces_01_0012.html index 87ba94ab..bdafca59 100644 --- a/docs/ces/umn/ces_01_0012.html +++ b/docs/ces/umn/ces_01_0012.html @@ -1,10 +1,10 @@-Parent topic: Monitoring Panels+Parent topic: DashboardsAdding a Graph
-After you create a panel, you can add graphs to the panel to monitor cloud services. Each panel supports up to 24 graphs.
-You can add up to 20 metrics to one graph. Monitoring comparison between different services, dimensions, and metrics is supported.
-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 Dashboard > Monitoring Panels, switch to the desired panel, and click Add Graph.
The Add Graph dialog box is displayed.
- - Set parameters based on Table 1.
+
After you create a dashboard, you can add graphs to the dashboard to monitor cloud services. Each dashboard supports up to 50 graphs.
+You can add up to 50 metrics to one graph. Monitoring comparison between different services, dimensions, and metrics is supported.
+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 Dashboard. Switch to the dashboard to which you want to add a graph, and click Add Graph.
The Add Graph dialog box is displayed.
+ - Configure parameters based on Table 1.
-
Table 1 Parameters Parameter
Description
@@ -17,6 +17,11 @@Example value: widget-axaj
(Optional) Enterprise Project
+Specifies the enterprise project associated with the graph. You can view the monitoring data on the graph only when you have the enterprise project permissions.
+Resource Type
Specifies the type of the resource to be monitored.
@@ -31,8 +36,8 @@Monitored Object
Specifies the monitored objects of the metric.
-You can select a maximum of 20 monitored objects at a time.
+Specifies the monitored object. You can add up to 50 monitored objects.
+You can select multiple monitored objects at a time.
Metric
@@ -44,13 +49,13 @@ - Click OK.
On the selected panel, you can view the trends of the new graph. If you hover your mouse on the graph and click
+
, you can view detailed metric data comparison. - Click OK.
On the selected dashboard, you can view the metric trends on the new graph. If you hover your mouse on the graph and click
, you can view detailed metric data comparison in an enlarged graph.
diff --git a/docs/ces/umn/ces_01_0013.html b/docs/ces/umn/ces_01_0013.html index 6a0dbb9e..cd7808ec 100644 --- a/docs/ces/umn/ces_01_0013.html +++ b/docs/ces/umn/ces_01_0013.html @@ -1,17 +1,32 @@-Parent topic: Monitoring Panels+Parent topic: DashboardsViewing a Graph
-After you add a graph, you can view the metric trends on the Monitoring Panels page. The system provides you both default and customizable time ranges to view trends from last month. This topic describes how to view trends for a longer time range.
-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 Dashboard > Monitoring Panels.You can view all monitoring graphs on the current monitoring panel.
- You can sort graphs by dragging them.
- You can click 1h, 3h, 12h, 1d, or 7d in the upper part of monitoring graphs to switch the monitoring periods of all graphs on the monitoring panel. By default, raw metric data is displayed for 1h, and the aggregated metric data is displayed for other periods.
After you add a graph, you can view the metric trends on the Dashboards page. The system provides you both default and customizable time ranges to view trends from last month. This topic describes how to view trends for a longer time range.
++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 Dashboard.You can view all graphs on the current dashboard.-
- You can sort graphs by dragging them.
- You can click 1h, 3h, 12h, 1d, or 7d in the upper part of the graphs to change the monitoring period of all graphs on the dashboard. By default, raw metric data is displayed for 1h and 3h, and the aggregated metric data is displayed for other periods. You can also customize a time range for all graphs.
- You can also go to the full screen to view the graphs. For details, see Using the Full Screen.
- 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, Cloud Eye displays raw data from the last hour by default; if you select any of the other time periods, Cloud Eye displays rolled-up data.
+ - Hover your mouse over a graph. In the upper right corner, click to view monitoring details on an enlarged graph. Select a time period or customize a time range to view the metric in a specific monitoring interval.
Raw metric data is displayed for 1h, 3h, 12h, and 1d by default. For 7d and 30d, rolled-up data is displayed by default.
+On the enlarged graph, you can Customizing a Period to View the Graph or Selecting Monitored Objects and Viewing Metrics.
+Figure 1 Viewing graphs
+Using the Full Screen
The full screen displays metric data more clearly.
+- To enter the full screen, click Full Screen in the upper right corner of the Dashboard page.
- To exit the full screen, click Exit Full Screen in the upper left corner of the page.
+Customizing a Period to View the Graph
By default, metrics in the last 1 hour, last 3 hours, last 12 hours, last 24 hours, and last 7 days are displayed. If you want to view metrics in the last 2 hours or a customized time period, you can drag the mouse to select the time range you want to view on the X axis.
+- To view metric details in a customized time period, click the first icon on the right. Drag the mouse to select a customized time range. The system automatically displays the monitoring data in the selected time range.Figure 2 Customizing a period+
- To go back to the default graph, click the third icon on the right.
Selecting Monitored Objects and Viewing Metrics
To compare the same metric of multiple resources, you can combine the metrics of the resources into a graph. When there are a large number of resources, you can drag to select monitored objects if you want to compare the metric data of only some of the resources.
+- To select a monitored object, click the second icon on the right. Drag the mouse on part of the curve of the monitored objects. Then, the system automatically displays the data of the selected monitored objects and hides the monitoring data of other monitored objects.Figure 3 Selecting the object to be monitored+
- To go back to the default graph, click the third icon on the right.+
In the lower part of an enlarged graph, you can select a monitored object as follows: Click a resource object to hide its trend chart, and click the monitored object again to display its trend chart.
+
diff --git a/docs/ces/umn/ces_01_0014.html b/docs/ces/umn/ces_01_0014.html index f247138c..3df59be0 100644 --- a/docs/ces/umn/ces_01_0014.html +++ b/docs/ces/umn/ces_01_0014.html @@ -2,15 +2,16 @@-Parent topic: Monitoring Panels+Parent topic: DashboardsConfiguring a Graph
This topic describes how to add, modify, and delete metrics on graphs.
-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 Dashboard > Monitoring Panels, select the target panel and graph, and click the configure icon.
On the displayed Configure Graph dialog box, you can edit the graph title and add new metrics. You can also delete or modify the current metrics.
- You can add up to 20 metrics to a single monitoring graph.
+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 Dashboard. Select the panel and graph, and click the configure icon.
On the displayed Configure Graph dialog box, you can edit the graph title and add new metrics. You can also delete or modify the current metrics.
+Figure 1 Configure Graph+
You can add up to 50 metrics to a graph.
diff --git a/docs/ces/umn/ces_01_0015.html b/docs/ces/umn/ces_01_0015.html index 968915ee..cb0c2439 100644 --- a/docs/ces/umn/ces_01_0015.html +++ b/docs/ces/umn/ces_01_0015.html @@ -1,11 +1,11 @@-Parent topic: Monitoring Panels+Parent topic: DashboardsDeleting a Graph
-- 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 Dashboard > Monitoring Panels.
- Select the monitoring panel from which you want to delete a graph.
- Hover your mouse on the target graph and click the trash icon in the upper right corner.
- In the displayed Delete Graph dialog box, click Yes.
- 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 Dashboard.
- Select the dashboard from which you want to delete a graph.
- Hover your mouse on the graph and click the trash icon in the upper right corner.
- In the displayed Delete Graph dialog box, click Yes.
diff --git a/docs/ces/umn/ces_01_0016.html b/docs/ces/umn/ces_01_0016.html index 6010d4d0..d5592a8a 100644 --- a/docs/ces/umn/ces_01_0016.html +++ b/docs/ces/umn/ces_01_0016.html @@ -1,13 +1,13 @@ --Parent topic: Monitoring Panels+Parent topic: DashboardsDeleting a Monitoring Panel
-To re-plan graphs on a panel, you can delete the existing panel. After you delete a panel, all graphs added to it will be deleted.
-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 Dashboard > Monitoring Panels.
- Select the monitoring panel on which the graph to be deleted is located.
- Click Delete.
- In the displayed Delete Monitoring Panel dialog box, click Yes.
Deleting a Dashboard
+To re-plan graphs on a dashboard, you can delete the dashboard. After that, all graphs on the dashboard will also be deleted.
+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 Dashboard.
- Select the dashboard.
- Click Delete.
- In the displayed Delete Dashboard dialog box, click Yes.
diff --git a/docs/ces/umn/ces_01_0017.html b/docs/ces/umn/ces_01_0017.html index 6ce4a700..5005b1a1 100644 --- a/docs/ces/umn/ces_01_0017.html +++ b/docs/ces/umn/ces_01_0017.html @@ -3,9 +3,11 @@-Parent topic: Monitoring Panels+Parent topic: DashboardsCreating 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.
-Restrictions
- Each user can create up to 1,000 resource groups.
- A resource group must contain 1 to 1,000 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. diff --git a/docs/ces/umn/ces_01_0019.html b/docs/ces/umn/ces_01_0019.html index c422c0dd..b64fc6a9 100644 --- a/docs/ces/umn/ces_01_0019.html +++ b/docs/ces/umn/ces_01_0019.html @@ -2,7 +2,7 @@
You can search for ECSs and BMSs by name, ID, and private IP address. For other cloud services, you can search only by name and 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.
- In the navigation pane on the left, choose Resource Groups.
- In the upper right corner, click Create Resource Group.Figure 1 Create Resource Group+
- Enter the group name.
- (Optional) Select cloud service resources and configure Associate Enterprise Project.You are advised to associate an enterprise project. After an enterprise project is associated, resources added to or deleted from the enterprise project are automatically added to or deleted from the resource group. If resources are frequently added or deleted, you can improve the efficiency of maintaining resource groups.Figure 2 Selecting cloud service resources+
You can search for ECSs and BMSs by name, ID, and private IP address. For other cloud services, you can search by name, ID, or tag.
- Click Create.
diff --git a/docs/ces/umn/ces_01_0018.html b/docs/ces/umn/ces_01_0018.html index 6b854179..325a023f 100644 --- a/docs/ces/umn/ces_01_0018.html +++ b/docs/ces/umn/ces_01_0018.html @@ -9,16 +9,12 @@-Parent topic: Resource Groups+Parent topic: Resource Groups- Resource Overview
-
- Unhealthy Resources
-- Alarm Rules
-
- Alarm History
--Parent topic: Resource Groups+Parent topic: Resource GroupsResource 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. +
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
@@ -16,24 +16,24 @@Health Status
+Status (Metric Monitoring)
- 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.
- OK: No alarms are generated for resources in the group.
- In alarm: An alarm is being generated for a resource in the group.
- No alarm rules set: No alarm rules have been created for any resource in the group.
Unhealthy Resources
+Resources (Alarm/Total)
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 number of resources that are generating alarms in a group/Total number of resources in the group.
Total Resources
+(Optional) Enterprise Project
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.
+Specifies the name of the enterprise project that has the resource group permission.
Resource Types
+Add Resources
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.
+Specifies how you add resources to a resource group. The value can be Manually or Automatically.
Created
@@ -41,9 +41,9 @@Specifies the time when the resource group was created.
Operation
+Operation
Specifies the operations that can be performed on a resource group. You can only modify or delete a resource group.
+You can create alarm rules 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).
-Figure 1 Resource overview-
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.
The Resource Overview page displays the resource types contained in the current group, as well as the total number of resources of each resource type, dimensions, and whether there are alarms generated for the resources.
+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.
On this page, you can change the resource group name and remove or add resources. There is also a link for you to quickly create alarm rules for those resources.
+Figure 1 Viewing details of a resource group+
diff --git a/docs/ces/umn/ces_01_0021.html b/docs/ces/umn/ces_01_0021.html deleted file mode 100644 index da384a42..00000000 --- a/docs/ces/umn/ces_01_0021.html +++ /dev/null @@ -1,13 +0,0 @@ - - -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.
-- diff --git a/docs/ces/umn/ces_01_0022.html b/docs/ces/umn/ces_01_0022.html index a7562060..2282fd46 100644 --- a/docs/ces/umn/ces_01_0022.html +++ b/docs/ces/umn/ces_01_0022.html @@ -1,8 +1,10 @@--Parent topic: Viewing Resource Groups-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.
The Alarm Rules page displays all alarm rules in a resource group. You can enable, disable, modify, or delete 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.
- 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.On the Alarm Rules page, you can quickly create alarm rules for resources in the resource group. For details, see Creating an Alarm Rule.+Figure 1 Managing alarm rules in a resource group+
diff --git a/docs/ces/umn/ces_01_0023.html b/docs/ces/umn/ces_01_0023.html deleted file mode 100644 index 77278a73..00000000 --- a/docs/ces/umn/ces_01_0023.html +++ /dev/null @@ -1,13 +0,0 @@ - - -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.
-- diff --git a/docs/ces/umn/ces_01_0024.html b/docs/ces/umn/ces_01_0024.html index 43a798ea..7560eabd 100644 --- a/docs/ces/umn/ces_01_0024.html +++ b/docs/ces/umn/ces_01_0024.html @@ -1,19 +1,19 @@--Parent topic: Viewing Resource Groups-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.
-diff --git a/docs/ces/umn/ces_01_0025.html b/docs/ces/umn/ces_01_0025.html index 234a7457..decf033a 100644 --- a/docs/ces/umn/ces_01_0025.html +++ b/docs/ces/umn/ces_01_0025.html @@ -1,8 +1,9 @@- Modifying a Resource Group
- Deleting a Resource Group
+ - Associating Resource Groups with Alarm Templates
+
-Parent topic: Resource Groups+Parent topic: Resource GroupsModifying 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.
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.
- Click a resource group name to go to the Resource Overview page
- Adding resources: Click to add resources and add resources as prompted.
- Removing resources: In the resource list, select the resource to be removed and click Remove in the Operation column.
diff --git a/docs/ces/umn/ces_01_0026.html b/docs/ces/umn/ces_01_0026.html index 00dcceac..32b1aebd 100644 --- a/docs/ces/umn/ces_01_0026.html +++ b/docs/ces/umn/ces_01_0026.html @@ -1,7 +1,8 @@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.
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 resource group and click Delete in the Operation column.Figure 1 Deleting a resource group+
- In the displayed Delete Resource Group dialog box, click OK.
diff --git a/docs/ces/umn/ces_01_0029.html b/docs/ces/umn/ces_01_0029.html index da93b897..a6ddd49d 100644 --- a/docs/ces/umn/ces_01_0029.html +++ b/docs/ces/umn/ces_01_0029.html @@ -5,10 +5,10 @@-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-
-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.otc.t-systems.com/scripts/agentInstall.sh && chmod 755 agentInstall.sh && ./agentInstall.sh
+If Telescope process starts successfully or Success to install telescope is displayed, the Agent is successfully installed.
+ - 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
diff --git a/docs/ces/umn/ces_01_0030.html b/docs/ces/umn/ces_01_0030.html index e84de226..c262943f 100644 --- a/docs/ces/umn/ces_01_0030.html +++ b/docs/ces/umn/ces_01_0030.html @@ -5,7 +5,7 @@ - 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.
diff --git a/docs/ces/umn/ces_01_0031.html b/docs/ces/umn/ces_01_0031.html index 8a95666a..7820bace 100644 --- a/docs/ces/umn/ces_01_0031.html +++ b/docs/ces/umn/ces_01_0031.html @@ -6,9 +6,12 @@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.
+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.
-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
+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
++
Storing plaintext AKs and SKs poses great security risks. You are advised to delegate all ECS or BMS Agents in the region. For details, see How Can I Create an Agency?
+{ "InstanceId":"XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX", "ProjectId": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX", @@ -30,60 +33,60 @@ "BmsFlag": true }-Table 1 Public parameters Parameter
+Table 1 Public parameters Parameter
Description
+Description
InstanceId
+InstanceId
(Optional) Specifies the ECS ID. You can log in to the management console and view the ECS ID in the ECS list.
+(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
+ProjectId
(Optional) Specifies the project ID.
+(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
+AccessKey/SecretKey
To obtain the AK and SK, perform the following operations:
+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.
- 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
+RegionId
Specifies the region ID. For example, if the ECS is located in region EU DE, RegionId is eu-de.
+Specifies the region ID. For example, if the ECS is located in region EU DE, RegionId is eu-de.
ClientPort
+ClientPort
Specifies the start port number used by the Agent.
+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
+PortNum
Specifies the number of ports configured for the Agent.
+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
+BmsFlag
Set this parameter to true for a BMS. This parameter is not required by an ECS.
+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.
-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.
{ +Procedure
- Log in to the ECS.
- Open the conf.json file in the telescope_windows_amd64\bin directory.
- Configure the following parameters. For details, see Table 1.+
Storing plaintext AKs and SKs poses great security risks. You are advised to delegate all ECS or BMS Agents in the region. For details, see How Can I Create an Agency?
+{ "InstanceId":"", "ProjectId": "", "AccessKey": "", @@ -16,6 +18,7 @@ "ClientPort": 0, "PortNum": 200 }+Table 1 Public parameters Parameter
@@ -27,36 +30,35 @@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:
+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:
+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.
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.
+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.
+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.
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.
- For servers running Windows OSs, Agents cannot be installed in batches.
-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:
@@ -14,8 +14,8 @@
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"
+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.otc.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.otc.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.diff --git a/docs/ces/umn/ces_01_0036.html b/docs/ces/umn/ces_01_0036.html index b5cd3635..ecbb5f0e 100644 --- a/docs/ces/umn/ces_01_0036.html +++ b/docs/ces/umn/ces_01_0036.html @@ -14,7 +14,7 @@
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.
Stopping the Agent
Log in to an ECS or BMS and run the following command to stop the Agent:
service telescoped stop
- diff --git a/docs/ces/umn/ces_01_0042-A.html b/docs/ces/umn/ces_01_0042-A.html new file mode 100644 index 00000000..0715992b --- /dev/null +++ b/docs/ces/umn/ces_01_0042-A.html @@ -0,0 +1,52 @@ + + +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:
+ If the Agent installation fails, it may be impossible to stop the Agent. In this case, run the following command to stop the Agent:
/usr/local/telescope/telescoped stop
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, and click Create Alarm Rule in the Operation column. When you create an alarm rule, related metric parameters will be preset.
- On the Create Alarm Rule page, configure the parameters.
For details about the parameters, see Table 1 to Table 4.
+Some parameters have been preset. For details, see Table 1.
+ ++
+Table 1 Preset parameters for server monitoring alarms Parameter
+Description
+Alarm Type
+Alarm type that the alarm rule applies to. The default value is Metric.
+Resource Type
+Specifies the name of the monitored service.
+Dimension
+Specifies the metric dimension.
+Monitoring Scope
+Specifies the monitoring scope the alarm rule applies to.
+Monitored Object
+Specifies the monitored object, that is, the name of the selected resource.
+
After the alarm rule is created, if the metric data reaches the specified threshold, Cloud Eye immediately informs you that an exception has occurred.
+++ diff --git a/docs/ces/umn/ces_01_0042.html b/docs/ces/umn/ces_01_0042.html deleted file mode 100644 index 36329dea..00000000 --- a/docs/ces/umn/ces_01_0042.html +++ /dev/null @@ -1,117 +0,0 @@ - - -++Parent topic: Server 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.
--- diff --git a/docs/ces/umn/ces_01_0050.html b/docs/ces/umn/ces_01_0050.html index 69f64fd6..88570f68 100644 --- a/docs/ces/umn/ces_01_0050.html +++ b/docs/ces/umn/ces_01_0050.html @@ -9,7 +9,7 @@--Parent topic: Server Monitoring-- Viewing Event Monitoring Data
-
- Creating an Alarm Rule to Monitor an Event
+- Creating an Alarm Rule to Monitor an Event
- Events Supported by Event Monitoring
diff --git a/docs/ces/umn/ces_01_0051.html b/docs/ces/umn/ces_01_0051.html index 7400d298..70ef67d0 100644 --- a/docs/ces/umn/ces_01_0051.html +++ b/docs/ces/umn/ces_01_0051.html @@ -3,10 +3,13 @@
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.
+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 view events in the last 1 hour, last 3 hours, last 12 hours, last 24 hours, last 7 days, or last 30 days. Alternatively, you can set a custom time range to view events triggered within that period.
+Figure 1 Event Monitoring-
- Expand an event, and click View Event in the Operation column to view details about a specific event.
- Expand an event and click View Event in the Operation column to view its details.
Figure 2 Viewing event details+
- In the row containing the target event, click View Graph in the Operation column. Then, you can view the monitoring data of last 24 hours.
You can view monitoring data of a specified event in the last 1 hour, last 3 hours, last 12 hours, last 24 hours, last 7 days, or last 30 days. Alternatively, you can set a custom time range by specifying the start time and end time to view monitoring data of a specified event within that period.
+- In the upper right corner of the event list, select an event type and enter an event name to filter the desired event.
- To view events of a specific time period, click on the corresponding bar chart.
diff --git a/docs/ces/umn/ces_01_0052-A.html b/docs/ces/umn/ces_01_0052-A.html new file mode 100644 index 00000000..0861cdd6 --- /dev/null +++ b/docs/ces/umn/ces_01_0052-A.html @@ -0,0 +1,42 @@ + + +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.
- On the event list page, click Create Alarm Rule in the upper right corner.
You can also click Create Alarm Rule in the Operation column of the target event. When you create an alarm rule, related event parameters will be preset.
+ - On the Create Alarm Rule page, configure the parameters.
For details about the parameters, see Table 1 to Table 4.
+Some parameters have been preset. For details, see Table 1. + ++
++ diff --git a/docs/ces/umn/ces_01_0052.html b/docs/ces/umn/ces_01_0052.html deleted file mode 100644 index 896b8c83..00000000 --- a/docs/ces/umn/ces_01_0052.html +++ /dev/null @@ -1,117 +0,0 @@ - - -++Parent topic: Event Monitoring+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.
-
-- diff --git a/docs/ces/umn/ces_01_0054.html b/docs/ces/umn/ces_01_0054.html index f1b72508..b66cbfca 100644 --- a/docs/ces/umn/ces_01_0054.html +++ b/docs/ces/umn/ces_01_0054.html @@ -4,7 +4,7 @@--Parent topic: Event Monitoring-- Events in Event Monitoring come from operations on cloud service resources and are not collected by the Agent in Server Monitoring.
Table 1 ECS Event Source
+Table 1 Elastic Cloud Server (ECS) Event Source
Event Name
Services are interrupted.
Start auto recovery
+Restart triggered due to system faults
startAutoRecovery
Services may be interrupted.
Stop auto recovery
+Restart completed due to system faults
endAutoRecovery
Major
The ECS was restored to be normal after the automatic migration.
+The ECS was recovered after the automatic migration.
This event indicates that the ECS has been recovered and been working properly.
+This event indicates that the ECS has recovered and been working properly.
None
Critical
The processes of the host accommodating the ECS were abnormal.
+The host where the ECS resides is faulty. The system will automatically try to start the ECS.
Contact O&M personnel.
+After the ECS is started, check whether this ECS and services on it can run properly.
The ECS is faulty.
- 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.
Table 2 Advanced Anti-DDoS (AAD) Event Source
+-Table 2 Advanced Anti-DDoS (AAD) Event Source
Event Name
+Namespace
Event ID
+Event Name
Event Severity
+Event ID
Description
+Event Severity
Solution
+Description
Impact
+Solution
+Impact
AAD
+AAD
+DDoS Attack Events
+SYS.DDOS
ddosAttackEvents
+DDoS Attack Events
Major
+ddosAttackEvents
A DDoS attack occurs in the AAD protected lines.
+Major
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.
+A DDoS attack occurs in the AAD protected lines.
Services may be interrupted.
+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.
+Domain name scheduling event
+domainNameDispatchEvents
+Major
+The high-defense CNAME corresponding to the domain name is scheduled, and the domain name is resolved to another high-defense IP address.
+Pay attention to the workloads involving the domain name.
+Services are not affected.
+Blackhole event
+blackHoleEvents
+Major
+The attack traffic exceeds the purchased AAD protection threshold.
+A blackhole is canceled after 30 minutes by default. The actual blackhole duration is related to the blackhole triggering times and peak attack traffic on the current day. The maximum duration is 24 hours. If you need to permit access before a blackhole becomes ineffective, contact technical support.
+Services may be interrupted.
+Cancel Blackhole
+cancelBlackHole
+Informational
+The customer's AAD instance recovers from the black hole state.
+This is only a prompt and no action is required.
+Customer services recover.
+IP address scheduling triggered
+ipDispatchEvents
+Major
+IP route changed
+Check the workloads of the IP address.
+Services are not affected.
Table 3 CBR Event Source
+-Table 3 Elastic Load Balance (ELB) Event Source
Event Name
+Namespace
Event ID
+Event Name
Event Severity
+Event ID
Description
+Event Severity
Solution
+Description
Impact
+Solution
+Impact
CBR
+ELB
Failed to create the backup.
+SYS.ELB
backupFailed
+The backend servers are unhealthy.
Critical
+healthCheckUnhealthy
The backup failed to be created.
+Major
Manually create a backup or contact customer service.
+Generally, this problem occurs because backend server services are offline. This event will not be reported after it is reported for several times.
Data loss may occur.
+Ensure that the backend servers are running properly.
+ELB does not forward requests to unhealthy backend servers. If all backend servers in the backend server group are detected unhealthy, services will be interrupted.
Failed to restore the resource using a backup.
+The backend server is detected healthy.
restorationFailed
+healthCheckRecovery
Critical
+Minor
The resource failed to be restored using a backup.
+The backend server is detected healthy.
Restore the resource using another backup or contact customer service.
+No further action is required.
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
+The load balancer can properly route requests to the backend server.
Table 4 RDS — resource exception Event Source
+-Table 4 Cloud Backup and Recovery (CBR) Event Source
Event Name
+Event Name
Event ID
+Event ID
Event Severity
+Event Severity
Description
+Description
Solution
+Solution
Impact
+Impact
RDS
+CBR
Full backup failure
+Failed to create the backup.
fullBackupFailed
+backupFailed
Major
+Critical
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).
+The backup failed to be created.
Create a manual backup again.
+Manually create a backup or contact customer service.
Backup failed.
+Data loss may occur.
Primary/standby switchover or failover
+Failed to restore the resource using a backup.
PrimaryStandbySwitched
+restorationFailed
Major
+Critical
This event is reported when a primary/standby switchover or a failover is triggered.
+The resource failed to be restored using a backup.
- After the switchover or failover is complete, check whether workloads are restored. If workloads are not restored, contact SRE engineers.
- Ignore the event if you have performed a switchover.
- If the failover is triggered by a node fault, contact the SRE engineers.
Restore the resource using another backup or contact customer service.
Downtime occurs during the switchover.
+Data loss may occur.
Replication status abnormal
+Failed to delete the backup.
abnormalReplicationStatus
+backupDeleteFailed
Major
+Critical
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.
+The backup failed to be deleted.
Submit a service ticket.
+Try again later or contact customer service.
Your applications are not affected because this event does not interrupt data read and write.
+Charging may be abnormal.
Replication status recovered
+Failed to delete the vault.
replicationStatusRecovered
+vaultDeleteFailed
Major
+Critical
The replication delay between the primary and standby instances is within the normal range, or the network connection between them has restored.
+The vault failed to be deleted.
No action is required.
+Try again later or contact technical support.
None
+Charging may be abnormal.
DB instance faulty
+Replication failure
faultyDBInstance
+replicationFailed
Major
+Critical
A single or primary DB instance was faulty due to a disaster or a server failure.
+The backup failed to be replicated.
Check whether an automated backup policy has been configured for the DB instance and submit a service ticket.
+Try again later or contact technical support.
The database service may be unavailable.
+Data loss may occur.
DB instance recovered
+The backup is created successfully.
DBInstanceRecovered
+backupSucceeded
Major
+Major
RDS rebuilds the standby DB instance with its high availability. After the instance is rebuilt, this event will be reported.
+The backup was created.
No action is required.
+None
None
+None
Failure of changing single DB instance to primary/standby
+Resource restoration using a backup succeeded.
singleToHaFailed
+restorationSucceeded
Major
+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.
+The resource was restored using a backup.
Submit a service ticket.
+Check whether the data is successfully restored.
Your applications are not affected because this event does not interrupt data read and write of the DB instance.
+None
Database process restarted
+The backup is deleted successfully.
DatabaseProcessRestarted
+backupDeletionSucceeded
Major
+Major
The database process is stopped due to insufficient memory or high load.
+The backup was deleted.
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.
+None
Downtime occurs. When this happens, RDS automatically restarts the database process and attempts to recover the workloads.
+None
Instance storage full
+The vault is deleted successfully.
instanceDiskFull
+vaultDeletionSucceeded
Major
+Major
Generally, the cause is that the data space usage is too high.
+The vault was deleted.
Scale up the instance.
+None
The DB instance becomes read-only because the storage space is full, and data cannot be written to the database.
+None
Instance storage full recovered
+Replication success
instanceDiskFullRecovered
+replicationSucceeded
Major
+Major
The instance disk is recovered.
+The backup was replicated successfully.
No action is required.
+None
Cancel the read-only state of the instance and resume write operations.
+None
Read replica promotion failure
+Client offline
activeStandBySwitchFailed
+agentOffline
Major
+Critical
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.
+The backup client was offline.
Submit a service ticket.
+Ensure that the Agent status is normal and the backup client can be connected to .
The read replica fails to be promoted to the primary DB instance.
+Backup tasks may fail.
+Client online
+agentOnline
+Major
+The backup client was online.
+None
+None
Table 5 GaussDB(for MySQL) Event Source
+-Table 5 Relational Database Service (RDS) — resource exception Event Source
Event Name
+Namespace
Event ID
+Event Name
Event Severity
+Event ID
Description
+Event Severity
Solution
+Description
Impact
+Solution
+Impact
GaussDB(for MySQL)
+RDS
Incremental backup failure
+SYS.RDS
TaurusIncrementalBackupInstanceFailed
+DB instance creation failure
Major
+createInstanceFailed
The network between the instance and the management plane (or the OBS) is disconnected, or the backup environment created for the instance is abnormal.
+Major
Submit a service ticket.
+Generally, the cause is that the number of disks is insufficient due to quota limits, or underlying resources are exhausted.
Backup jobs fail.
+The selected resource specifications are insufficient. Select other available specifications and try again.
+DB instances cannot be created.
Read replica creation failure
+Full backup failure
addReadonlyNodesFailed
+fullBackupFailed
Major
+Major
The quota is insufficient or underlying resources are exhausted.
+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).
Check the read replica quota. Release resources and create read replicas again.
+Try again.
Read replicas fail to be created.
+Restoration using backups will be affected.
DB instance creation failure
+Read replica promotion failure
createInstanceFailed
+activeStandBySwitchFailed
Major
+Major
The instance quota or underlying resources are insufficient.
+The standby DB instance does not take over workloads from the primary DB instance due to network or server failures. The original primary DB instance continues to provide services within a short time.
Check the instance quota. Release resources and create instances again.
+Perform the operation again during off-peak hours.
DB instances fail to be created.
+Read replica promotion failed.
Read replica promotion failure
+Replication status abnormal
activeStandBySwitchFailed
+abnormalReplicationStatus
Major
+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.
+The possible causes are as follows:
+The replication delay between the primary instance and the standby instance or a read replica is too long, which usually occurs when a large amount of data is being written to databases or a large transaction is being processed. During peak hours, data may be blocked.
+The network between the primary instance and the standby instance or a read replica is disconnected.
Submit a service ticket.
+The issue is being fixed. Please wait for our notifications.
The read replica fails to be promoted to the primary node.
+The replication status is abnormal.
Instance specifications change failure
+Replication status recovered
flavorAlterationFailed
+replicationStatusRecovered
Major
+Major
The quota is insufficient or underlying resources are exhausted.
+The replication delay between the primary and standby instances is within the normal range, or the network connection between them has restored.
Submit a service ticket.
+Check whether services are running properly.
Instance specifications fail to be changed.
+Replication status is recovered.
Faulty DB instance
+DB instance faulty
TaurusInstanceRunningStatusAbnormal
+faultyDBInstance
Major
+Major
The instance process is faulty or the communications between the instance and the DFV storage are abnormal.
+A single or primary DB instance was faulty due to a catastrophic failure, for example, server failure.
Submit a service ticket.
+The issue is being fixed. Please wait for our notifications.
Services may be affected.
+The instance status is abnormal.
DB instance recovered
+DB instance recovered
TaurusInstanceRunningStatusRecovered
+DBInstanceRecovered
Major
+Major
The instance is recovered.
+RDS rebuilds the standby DB instance with its high availability. After the instance is rebuilt, this event will be reported.
Observe the service running status.
+The DB instance status is normal. Check whether services are running properly.
None
+The instance is recovered.
Faulty node
+Failure of changing single DB instance to primary/standby
TaurusNodeRunningStatusAbnormal
+singleToHaFailed
Major
+Major
The node process is faulty or the communications between the node and the DFV storage are abnormal.
+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.
Observe the instance and service running statuses.
+Automatic retry is in progress.
A read replica may be promoted to the primary node.
+Changing a single DB instance to primary/standby failed.
Node recovered
+Database process restarted
TaurusNodeRunningStatusRecovered
+DatabaseProcessRestarted
Major
+Major
The node is recovered.
+The database process is stopped due to insufficient memory or high load.
Observe the service running status.
+Check whether services are running properly.
None
+The primary instance is restarted. Services are interrupted for a short period of time.
Read replica deletion failure
+Instance storage full
TaurusDeleteReadOnlyNodeFailed
+instanceDiskFull
Major
+Major
The communications between the management plane and the read replica are abnormal or the VM fails to be deleted from IaaS.
+Generally, the cause is that the data space usage is too high.
Submit a service ticket.
+Scale up the storage.
Read replicas fail to be deleted.
+The instance storage is used up. No data can be written into databases.
Password reset failure
+Instance storage full recovered
TaurusResetInstancePasswordFailed
+instanceDiskFullRecovered
Major
+Major
The communications between the management plane and the instance are abnormal or the instance is abnormal.
+The instance disk is recovered.
Check the instance status and try again. If the fault persists, submit a service ticket.
+Check whether services are running properly.
Passwords fail to be reset for instances.
+The instance has available storage.
DB instance reboot failure
+Kafka connection failed
TaurusRestartInstanceFailed
+kafkaConnectionFailed
Major
+Major
The network between the management plane and the instance is abnormal or the instance is abnormal.
+The network is unstable or the Kafka server does not work properly.
Check the instance status and try again. If the fault persists, submit a service ticket.
+Check whether services are affected.
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.
-- Check whether the service is running properly.
- Check whether an alarm is generated, indicating that the read replica failed to be promoted to primary.
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.
+None
Table 6 GaussDB(for openGauss) Event Source
++ +
+Table 6 Document Database Service (DDS) Event Source
Event Name
+Namespace
Event ID
+Event Name
Event Severity
+Event ID
Description
+Event Severity
Solution
+Description
Impact
+Solution
+Impact
GaussDB(for openGauss)
+DDS
Process status alarm
+SYS.DDS
ProcessStatusAlarm
+DB instance creation failure
Major
+DDSCreateInstanceFailed
Key processes exit, including: CMS/CMA, ETCD, GTM, CN, or DN process.
+Major
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.
+A DDS instance fails to be created due to insufficient disks, quotas, and underlying resources.
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.
+Check the number and quota of disks. Release resources and create DDS instances again.
+DDS instances cannot be created.
Component status alarm
+Replication failed
ComponentStatusAlarm
+DDSAbnormalReplicationStatus
Major
+Major
Key components do not respond, including: CMA, ETCD, GTM, CN, or DN component.
+The possible causes are as follows:
+The replication delay between the primary instance and the standby instance or a read replica is too long, which usually occurs when a large amount of data is being written to databases or a large transaction is being processed. During peak hours, data may be blocked.
+The network between the primary instance and the standby instance or a read replica is disconnected.
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.
+Submit a service ticket.
If processes on primary nodes do not respond, neither do the services. If processes on standby nodes are faulty, services are not affected.
+Your applications are not affected because this event does not interrupt data read and write.
Cluster status alarm
+Replication recovered
ClusterStatusAlarm
+DDSReplicationStatusRecovered
Major
+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.
+The replication delay between the primary and standby instances is within the normal range, or the network connection between them has restored.
Contact SRE engineers.
+No action is required.
If the cluster status is read-only, only read services are processed.
+None
+DB instance failed
+DDSFaultyDBInstance
+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
+DDSDBInstanceRecovered
+Major
+If a disaster occurs, NoSQL provides an HA tool to automatically or manually rectify the fault. After the fault is rectified, this event is reported.
+No action is required.
+None
+Faulty node
+DDSFaultyDBNode
+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.
+Node recovered
+DDSDBNodeRecovered
+Major
+If a disaster occurs, NoSQL provides an HA tool to automatically or manually rectify the fault. After the fault is rectified, this event is reported.
+No action is required.
+None
+Primary/standby switchover or failover
+DDSPrimaryStandbySwitched
+Major
+A primary/standby switchover is performed or a failover is triggered.
+No action is required.
+None
+Insufficient storage space
+DDSRiskyDataDiskUsage
+Major
+The storage space is insufficient.
+Scale up storage space. For details, see section "Scaling Up Storage Space" in the corresponding user guide.
+The instance is set to read-only and data cannot be written to the instance.
+Data disk expanded and being writable
+DDSDataDiskUsageRecovered
+Major
+The capacity of a data disk has been expanded and the data disk becomes writable.
+No further action is required.
+No adverse impact.
+Schedule for deleting a KMS key
+DDSplanDeleteKmsKey
+Major
+A request to schedule deletion of a KMS key was submitted.
+After the KMS key is scheduled to be deleted, either decrypt the data encrypted by KMS key in a timely manner or cancel the key deletion.
+After the KMS key is deleted, users cannot encrypt disks.
++ +
+Table 7 GaussDB(for MySQL) Event Source
+Namespace
+Event Name
+Event ID
+Event Severity
+Description
+Solution
+Impact
+GaussDB(for MySQL)
+SYS.GAUSSDB
+ +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.
+- Check whether the service is running properly.
- Check whether an alarm is generated, indicating that the read replica failed to be promoted to primary.
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.
+Submit a service ticket.
+After the database becomes read-only, write operations cannot be processed.
+Database read/write
+NodeReadWriteMode
+Major
+The database supports both write and read operations.
+Submit a service ticket.
+None.
+Instance DR switchover
+DisasterSwitchOver
+Major
+If an instance is faulty and unavailable, a switchover is performed to ensure that the instance continues to provide services.
+Contact technical support.
+The database connection is intermittently interrupted. The HA service switches workloads from the primary node to a read replica and continues to provide services.
+Database process restarted
+TaurusDatabaseProcessRestarted
+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 or the CPU usage is too high for a long time. You can increase the specifications or optimize the service logic.
+When the database process is suspended, workloads on the node are interrupted. In this case, the HA service automatically restarts the database process and attempts to recover the workloads.
++ +
+Table 8 GaussDB Event Source
+Namespace
+Event Name
+Event ID
+Event Severity
+Description
+Solution
+Impact
+GaussDB
+ +SYS.GAUSSDBV5
+Process status alarm
+ProcessStatusAlarm
+Major
+Key processes exit, including CMS/CMA, ETCD, GTM, CN, and DN processes.
+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, and DN components.
+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
+Hardware resource alarm
HardwareResourceAlarm
+HardwareResourceAlarm
Major
+Major
A major hardware fault occurs in the instance, such as disk damage or GTM network fault.
+A major hardware fault occurs in the instance, such as disk damage or GTM network fault.
Contact SRE engineers.
+Contact SRE engineers.
Some or all services are affected.
+Some or all services are affected.
Status transition alarm
+Status transition alarm
StateTransitionAlarm
+StateTransitionAlarm
Major
+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.
+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.
+Wait until the fault is automatically rectified and check whether services are recovered. If no, contact SRE engineers.
Some services are interrupted.
+Some services are interrupted.
Other abnormal alarm
+Other abnormal alarm
OtherAbnormalAlarm
+OtherAbnormalAlarm
Major
+Major
Disk usage threshold alarm
+Disk usage threshold alarm
Focus on service changes and scale up storage space as needed.
+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.
+If the used storage space exceeds the threshold, storage space cannot be scaled up.
Faulty DB instance
+Faulty DB instance
TaurusInstanceRunningStatusAbnormal
+TaurusInstanceRunningStatusAbnormal
Major
+Major
This event is a key alarm event and is reported when an instance is faulty due to a disaster or a server failure.
+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.
+Submit a service ticket.
The database service may be unavailable.
+The database service may be unavailable.
DB instance recovered
+DB instance recovered
TaurusInstanceRunningStatusRecovered
+TaurusInstanceRunningStatusRecovered
Major
+Major
GaussDB(for openGauss) provides an HA tool for automated or manual rectification of faults. After the fault is rectified, this event is reported.
+GaussDB(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.
+No further action is required.
None
+None
Faulty DB node
+Faulty DB node
TaurusNodeRunningStatusAbnormal
+TaurusNodeRunningStatusAbnormal
Major
+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.
+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.
+Check whether the database service is available and submit a service ticket.
The database service may be unavailable.
+The database service may be unavailable.
DB node recovered
+DB node recovered
TaurusNodeRunningStatusRecovered
+TaurusNodeRunningStatusRecovered
Major
+Major
GaussDB(for openGauss) provides an HA tool for automated or manual rectification of faults. After the fault is rectified, this event is reported.
+GaussDB(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.
+No further action is required.
None
+None
DB instance creation failure
+DB instance creation failure
GaussDBV5CreateInstanceFailed
+GaussDBV5CreateInstanceFailed
Major
+Major
Instances fail to be created because the quota is insufficient or underlying resources are exhausted.
+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.
+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.
+DB instances cannot be created.
Node adding failure
+Node adding failure
GaussDBV5ExpandClusterFailed
+GaussDBV5ExpandClusterFailed
Major
+Major
The underlying resources are insufficient.
+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.
+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
+None
Storage scale-up failure
+Storage scale-up failure
GaussDBV5EnlargeVolumeFailed
+GaussDBV5EnlargeVolumeFailed
Major
+Major
The underlying resources are insufficient.
+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.
+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.
+Services may be interrupted.
Reboot failure
+Reboot failure
GaussDBV5RestartInstanceFailed
+GaussDBV5RestartInstanceFailed
Major
+Major
The network is abnormal.
+The network is abnormal.
Retry the reboot operation or submit a service ticket to the O&M personnel.
+Retry the reboot operation or submit a service ticket to the O&M personnel.
The database service may be unavailable.
+The database service may be unavailable.
Full backup failure
+Full backup failure
GaussDBV5FullBackupFailed
+GaussDBV5FullBackupFailed
Major
+Major
The backup files fail to be exported or uploaded.
+The backup files fail to be exported or uploaded.
Submit a service ticket to the O&M personnel.
+Submit a service ticket to the O&M personnel.
Data cannot be backed up.
+Data cannot be backed up.
Differential backup failure
+Differential backup failure
GaussDBV5DifferentialBackupFailed
+GaussDBV5DifferentialBackupFailed
Major
+Major
The backup files fail to be exported or uploaded.
+The backup files fail to be exported or uploaded.
Submit a service ticket to the O&M personnel.
+Submit a service ticket to the O&M personnel.
Data cannot be backed up.
+Data cannot be backed up.
Backup deletion failure
+Backup deletion failure
GaussDBV5DeleteBackupFailed
+GaussDBV5DeleteBackupFailed
Major
+Major
This function does not need to be implemented.
+This function does not need to be implemented.
N/A
+N/A
N/A
+N/A
EIP binding failure
+EIP binding failure
GaussDBV5BindEIPFailed
+GaussDBV5BindEIPFailed
Major
+Major
The EIP is bound to another resource.
+The EIP is bound to another resource.
Submit a service ticket to the O&M personnel.
+Submit a service ticket to the O&M personnel.
The instance cannot be accessed from the Internet.
+The instance cannot be accessed from the Internet.
EIP unbinding failure
+EIP unbinding failure
GaussDBV5UnbindEIPFailed
+GaussDBV5UnbindEIPFailed
Major
+Major
The network is faulty or EIP is abnormal.
+The network is faulty or EIP is abnormal.
Unbind the IP address again or submit a service ticket to the O&M personnel.
+Unbind the IP address again or submit a service ticket to the O&M personnel.
IP addresses may be residual.
+IP addresses may be residual.
Parameter template application failure
+Parameter template application failure
GaussDBV5ApplyParamFailed
+GaussDBV5ApplyParamFailed
Major
+Major
Modifying a parameter template times out.
+Modifying a parameter template times out.
Modify the parameter template again.
+Modify the parameter template again.
None
+None
Parameter modification failure
+Parameter modification failure
GaussDBV5UpdateInstanceParamGroupFailed
+GaussDBV5UpdateInstanceParamGroupFailed
Major
+Major
Modifying a parameter template times out.
+Modifying a parameter template times out.
Modify the parameter template again.
+Modify the parameter template again.
None
+None
Backup and restoration failure
+Backup and restoration failure
GaussDBV5RestoreFromBcakupFailed
+GaussDBV5RestoreFromBcakupFailed
Major
+Major
The underlying resources are insufficient or backup files fail to be downloaded.
+The underlying resources are insufficient or backup files fail to be downloaded.
Submit a service ticket.
+Submit a service ticket.
The database service may be unavailable during the restoration failure.
+The database service may be unavailable during the restoration failure.
+Failed to upgrade the hot patch
+GaussDBV5UpgradeHotfixFailed
+Major
+Generally, this fault is caused by an error reported during kernel upgrade.
+View the error information about the workflow and redo or skip the job.
+None
++ +
+Table 9 Distributed Database Middleware (DDM) Event Source
+Namespace
+Event Name
+Event ID
+Event Severity
+Description
+Solution
+Impact
+DDM
+SYS.DDM
+Failed to create a DDM instance
+createDdmInstanceFailed
+Major
+The underlying resources are insufficient.
+Release resources and create the instance again.
+DDM instances cannot be created.
+Failed to change class of a DDM instance
+resizeFlavorFailed
+Major
+The underlying resources are insufficient.
+Submit a service ticket to the O&M personnel to coordinate resources and try again.
+Services on some nodes are interrupted.
+Failed to scale out a DDM instance
+enlargeNodeFailed
+Major
+The underlying resources are insufficient.
+Submit a service ticket to the O&M personnel to coordinate resources, delete the node that fails to be added, and add a node again.
+The instance fails to be scaled out.
+Failed to scale in a DDM instance
+reduceNodeFailed
+Major
+The underlying resources fail to be released.
+Submit a service ticket to the O&M personnel to release resources.
+The instance fails to be scaled in.
+Failed to restart a DDM instance
+restartInstanceFailed
+Major
+The DB instances associated are abnormal.
+Check whether DB instances associated are normal. If the instances are normal, submit a service ticket to the O&M personnel.
+Services on some nodes are interrupted.
+Failed to create a schema
+createLogicDbFailed
+Major
+The possible causes are as follows:
+- The password for the DB instance account is incorrect.
- The security group of the DDM instance and the associated DB instance are incorrectly configured. As a result, the DDM instance cannot communicate with the associated DB instance.
Check whether
+- The username and password of the DB instance are correct.
- The security groups associated with the DDM instance and underlying database instance are correctly configured.
Services cannot run properly.
+Failed to bind an EIP
+bindEipFailed
+Major
+The EIP is abnormal.
+Try again later. In case of emergency, contact O&M personnel to rectify the fault.
+The DDM instance cannot be accessed from the Internet.
+Failed to scale out a schema
+migrateLogicDbFailed
+Major
+The underlying resources fail to be processed.
+Submit a service ticket to the O&M personnel.
+The schema cannot be scaled out.
+Failed to re-scale out a schema
+retryMigrateLogicDbFailed
+Major
+The underlying resources fail to be processed.
+Submit a service ticket to the O&M personnel.
+The schema cannot be scaled out.
++ +
+Table 10 Elastic Volume Service (EVS) Event Source
+Namespace
+Event Name
+Event ID
+Event Severity
+Description
+Solution
+Impact
+EVS
+SYS.EVS
+Update disk
+updateVolume
+Minor
+Update the name and description of an EVS disk.
+No further action is required.
+None
+Expand disk
+extendVolume
+Minor
+Expand an EVS disk.
+No further action is required.
+None
+Delete disk
+deleteVolume
+Major
+Delete an EVS disk.
+No further action is required.
+Deleted disks cannot be recovered.
+QoS upper limit reached
+reachQoS
+Major
+The I/O latency increases as the QoS upper limits of the disk are frequently reached and flow control triggered.
+Change the disk type to one with a higher specification.
+The current disk may fail to meet service requirements.
++ +
+Table 11 Key Management Service (KMS) Event Source
+Namespace
+Event Name
+Event ID
+Event Severity
+KMS
+SYS.KMS
+Key disabled
+disableKey
+Major
+Key deletion scheduled
+scheduleKeyDeletion
+Minor
+Grant retired
+retireGrant
+Major
+Grant revoked
+revokeGrant
+Major
++ +
+Table 12 Cloud Eye Event Source
+Event Name
+Event ID
+Event Severity
+Description
+Solution
+Cloud Eye
+Agent heartbeat interruption
+agentHeartbeatInterrupted
+Major
+The Agent sends a heartbeat message to Cloud Eye every minute. If Cloud Eye cannot receive a heartbeat for 3 minutes, Agent Status is displayed as Faulty.
+- Confirm that the Agent domain name cannot be resolved.
- Check whether your account is in arrears.
- The Agent process is faulty. Restart the Agent. If the Agent process is still faulty after the restart, the Agent files may be damaged. In this case, reinstall the Agent.
- Confirm that the server time is inconsistent with the local standard time.
- Update the Agent to the latest version.
+ +
+Table 13 Distributed Cache Service (DCS) Event Source
+Namespace
+Event Name
+Event ID
+Event Severity
+Description
+Solution
+Impact
+DCS
+SYS.DCS
+Full sync retry during online migration
+migrationFullResync
+Minor
+If online migration fails, full synchronization will be triggered because incremental synchronization cannot be performed.
+Check whether full sync retries are triggered repeatedly. Check whether the source instance is connected and whether it is overloaded. If full sync retries are triggered repeatedly, contact O&M personnel.
+The migration task is disconnected from the source instance, triggering another full sync. As a result, the CPU usage of the source instance may increase sharply.
+masterStandbyFailover
+Minor
+The master node was abnormal, promoting a replica to master.
+Memcached master/standby switchover
+memcachedMasterStandbyFailover
+Minor
+The master node was abnormal, promoting the standby node to master.
+Check whether services can recover by themselves. If applications cannot recover, restart them.
+Persistent connections to the instance are interrupted.
+Redis server abnormal
+redisNodeStatusAbnormal
+Major
+The Redis server status was abnormal.
+Check whether services are affected. If yes, contact O&M personnel.
+If the master node is abnormal, an automatic failover is performed. If a standby node is abnormal and the client directly connects to the standby node for read/write splitting, no data can be read.
+Redis server recovered
+redisNodeStatusNormal
+Major
+The Redis server status recovered.
+Check whether services can recover. If the applications are not reconnected, restart them.
+Recover from an exception.
+Sync failure in data migration
+migrateSyncDataFail
+Major
+Online migration failed.
+Reconfigure the migration task and migrate data again. If the fault persists, contact O&M personnel.
+Data migration fails.
+Memcached instance abnormal
+memcachedInstanceStatusAbnormal
+Major
+The Memcached node status was abnormal.
+Check whether services are affected. If yes, contact O&M personnel.
+The Memcached instance is abnormal and may not be accessed.
+Memcached instance recovered
+memcachedInstanceStatusNormal
+Major
+The Memcached node status recovered.
+Check whether services can recover. If the applications are not reconnected, restart them.
+Recover from an exception.
+Instance backup failure
+instanceBackupFailure
+Major
+The DCS instance fails to be backed up due to an OBS access failure.
+Retry backup manually.
+Automated backup fails.
+Instance node abnormal restart
+instanceNodeAbnormalRestart
+Major
+DCS nodes restarted unexpectedly when they became faulty.
+Check whether services can recover. If the applications are not reconnected, restart them.
+Persistent connections to the instance are interrupted.
+Long-running Lua scripts stopped
+scriptsStopped
+Informational
+Lua scripts that had timed out automatically stopped running.
+Optimize Lua scrips to prevent execution timeout.
+If Lua scripts take a long time to execute, they will be forcibly stopped to avoid blocking the entire instance.
+Node restarted
+nodeRestarted
+Informational
+After write operations had been performed, the node automatically restarted to stop Lua scripts that had timed out.
+Check whether services can recover by themselves. If applications cannot recover, restart them.
+Persistent connections to the instance are interrupted.
++ +
+Table 14 Config Event Source
+Event Name
+Event ID
+Event Severity
+Description
+Solution
+Impact
+RMS
+Configuration noncompliance notification
+configurationNoncomplianceNotification
+Major
+The assignment evaluation result is Non-compliant.
+Modify the noncompliant configuration items of the resource.
+None
+Configuration compliance notification
+configurationComplianceNotification
+Informational
+The assignment evaluation result changed to be Compliant.
+None
+None
++ +
+Table 15 Host Security Service Event Source
+Namespace
+Event Name
+Event ID
+Event Severity
+Description
+Solution
+Impact
+HSS
+SYS.HSS
+HSS agent disconnected
+hssAgentAbnormalOffline
+Major
+The communication between the agent and the server is abnormal, or the agent process on the server is abnormal.
+Fix your network connection. If the agent is still offline for a long time after the network recovers, the agent process may be abnormal. In this case, log in to the server and restart the agent process.
+Services are interrupted.
+Abnormal HSS agent status
+hssAgentAbnormalProtection
+Major
+The agent is abnormal probably because it does not have sufficient resources.
+Log in to the server and check your resources. If the usage of memory or other system resources is too high, increase their capacity first. If the resources are sufficient but the fault persists after the agent process is restarted, submit a service ticket to the O&M personnel.
+Services are interrupted.
++ +
+Table 16 Image Management Service Event Source
+Namespace
+Event Name
+Event ID
+Event Severity
+Description
+Solution
+Impact
+IMS
+SYS.IMS
+Create Image
+createImage
+Major
+An image was created.
+None
+You can use this image to create cloud servers.
+Update Image
+updateImage
+Major
+Metadata of an image was modified.
+None
+Cloud servers may fail to be created from this image.
+Delete Image
+deleteImage
+Major
+An image was deleted.
+None
+This image will be unavailable on the management console.
++ +
+Table 17 Bare Metal Server (BMS) Event Source
+Event Name
+Event ID
+Event Severity
+Description
+Solution
+Impact
+BMS
+ECC uncorrectable errors generated on GPU SRAM
+SRAMUncorrectableEccError
+Major
+There are ECC uncorrectable errors generated on GPU SRAM.
+If services are affected, submit a service ticket.
+The GPU hardware may be faulty. As a result, the GPU memory is faulty, and services exit abnormally.
+osShutdown
+osShutdown
+Major
+The BMS was stopped
+- on the management console.
- by calling APIs.
- Deploy service applications in HA mode.
- After the BMS is started, check whether services recover.
Services are interrupted.
+Abnormal shutdown
+serverShutdown
+Major
+The BMS was stopped unexpectedly, which may be caused by
+- unexpected power-off.
- hardware faults.
- Deploy service applications in HA mode.
- After the BMS is started, check whether services recover.
Services are interrupted.
+Abnormal reboot
+serverReboot
+Major
+The BMS restarted unexpectedly, which may be caused by
+- OS faults.
- hardware faults.
- Deploy service applications in HA mode.
- After the BMS is restarted, check whether services recover.
Services are interrupted.
+Network interruption
+linkDown
+Major
+The BMS network was disconnected. Possible causes are as follows:
+- The BMS was unexpectedly stopped or restarted.
- The switch was faulty.
- The gateway was faulty.
- Deploy service applications in HA mode.
- After the BMS is started, check whether services recover.
Services are interrupted.
+PCIE error
+pcieError
+Major
+The PCIe devices or main board of the BMS was faulty.
+- Deploy service applications in HA mode.
- After the BMS is started, check whether services recover.
The network or disk read/write services are affected.
+Disk error
+diskError
+Major
+The disk backplane or disks of the BMS were faulty.
+- Deploy service applications in HA mode.
- After the fault is rectified, check whether services recover.
Data read/write services are affected, or the BMS cannot be started.
+Storage error
+storageError
+Major
+The BMS failed to connect to EVS disks. Possible causes are as follows:
+- The SDI card was faulty.
- Remote storage devices were faulty.
- Deploy service applications in HA mode.
- After the fault is rectified, check whether services recover.
Data read/write services are affected, or the BMS cannot be started.
+OS reboot
+osReboot
+Major
+The BMS was restarted
+- on the management console.
- by calling APIs.
- Deploy service applications in HA mode.
- After the BMS is restarted, check whether services recover.
Services are interrupted.
+Inforom alarm generated on GPU
+gpuInfoROMAlarm
+Major
+The driver failed to read inforom information due to GPU faults.
+Non-critical services can continue to use the GPU card. For critical services, submit a service ticket to resolve this issue.
+Services will not be affected if inforom information cannot be read. If error correction code (ECC) errors are reported on GPU, faulty pages may not be automatically retired and services are affected.
+Double-bit ECC alarm generated on GPU
+doubleBitEccError
+Major
+A double-bit ECC error occurred on GPU.
+- If services are interrupted, restart the services to restore.
- If services cannot be restarted, restart the VM where services are running.
- If services still cannot be restored, submit a service ticket.
Services may be interrupted. After faulty pages are retired, the GPU card can continue to be used.
+Too many retired pages
+gpuTooManyRetiredPagesAlarm
+Major
+An ECC page retirement error occurred on GPU.
+If services are affected, submit a service ticket.
+Services may be affected.
+ECC alarm generated on GPU A100
+gpuA100EccAlarm
+Major
+An ECC error occurred on GPU.
+- If services are interrupted, restart the services to restore.
- If services cannot be restarted, restart the VM where services are running.
- If services still cannot be restored, submit a service ticket.
Services may be interrupted. After faulty pages are retired, the GPU card can continue to be used.
+GPU ECC memory page retirement failure
+eccPageRetirementRecordingFailure
+Major
+Automatic page retirement failed due to ECC errors.
+- If services are interrupted, restart the services to restore.
- If services cannot be restarted, restart the VM where services are running.
- If services still cannot be restored, submit a service ticket.
Services may be interrupted, and memory page retirement fails. As a result, services cannot no longer use the GPU card.
+GPU ECC page retirement alarm generated
+eccPageRetirementRecordingEvent
+Minor
+Memory pages are automatically retired due to ECC errors.
+- If services are interrupted, restart the services to restore.
- If services cannot be restarted, restart the VM where services are running.
- If services still cannot be restored, submit a service ticket.
Generally, this alarm is generated together with the ECC error alarm. If this alarm is generated independently, services are not affected.
+Too many single-bit ECC errors on GPU
+highSingleBitEccErrorRate
+Major
+There are too many single-bit ECC errors.
+- If services are interrupted, restart the services to restore.
- If services cannot be restarted, restart the VM where services are running.
- If services still cannot be restored, submit a service ticket.
Single-bit errors can be automatically rectified and do not affect GPU-related applications.
+GPU card not found
+gpuDriverLinkFailureAlarm
+Major
+A GPU link is normal, but the NVIDIA driver cannot find the GPU card.
+- Restart the VM to restore services.
- If services still cannot be restored, submit a service ticket.
The GPU card cannot be found.
+GPU link faulty
+gpuPcieLinkFailureAlarm
+Major
+GPU hardware information cannot be queried through lspci due to a GPU link fault.
+If services are affected, submit a service ticket.
+The driver cannot use GPU.
+GPU card lost
+vmLostGpuAlarm
+Major
+The number of GPU cards on the VM is less than the number specified in the specifications.
+If services are affected, submit a service ticket.
+GPU cards get lost.
+GPU memory page faulty
+gpuMemoryPageFault
+Major
+The GPU memory page is faulty, which may be caused by applications, drivers, or hardware.
+If services are affected, submit a service ticket.
+The GPU hardware may be faulty. As a result, the GPU memory is faulty, and services exit abnormally.
+GPU image engine faulty
+graphicsEngineException
+Major
+The GPU image engine is faulty, which may be caused by applications, drivers, or hardware.
+If services are affected, submit a service ticket.
+The GPU hardware may be faulty. As a result, the image engine is faulty, and services exit abnormally.
+GPU temperature too high
+highTemperatureEvent
+Major
+GPU temperature too high
+If services are affected, submit a service ticket.
+If the GPU temperature exceeds the threshold, the GPU performance may deteriorate.
+GPU NVLink faulty
+nvlinkError
+Major
+A hardware fault occurs on the NVLink.
+If services are affected, submit a service ticket.
+The NVLink link is faulty and unavailable.
+nvidia-smi suspended
+nvidiaSmiHangEvent
+Major
+nvidia-smi timed out.
+If services are affected, submit a service ticket.
+The driver may report an error during service running.
++ +
+Table 18 Virtual Private Cloud Event Source
+Event Name
+Event ID
+Event Severity
+Elastic IP and bandwidth
+Delete VPC
+deleteVpc
+Major
+Modify VPC
+modifyVpc
+Minor
+Delete subnet
+deleteSubnet
+Minor
+Modify subnet
+modifySubnet
+Minor
+Modify bandwidth
+modifyBandwidth
+Minor
+Delete VPN
+deleteVpn
+Major
+Modify VPN
+modifyVpn
+Minor
++ +
+Table 19 Object Storage Service (OBS) Event Source
+Event Name
+Event ID
+Event Severity
+OBS
+Delete bucket
+deleteBucket
+Major
+Delete bucket policy
+deleteBucketPolicy
+Major
+Set bucket ACL
+setBucketAcl
+Minor
+Set bucket policy
+setBucketPolicy
+Minor
+Table 20 Elastic IP (EIP) Event Source
+Event Name
+Event ID
+Event Severity
+Description
+Solution
+Impact
+EIP
+EIP bandwidth overflow
+EIPBandwidthOverflow
+Major
+The used bandwidth exceeded the purchased one, which may slow down the network or cause packet loss. The value of this event is the maximum value in a monitoring period, and the value of the EIP inbound and outbound bandwidth is the value at a specific time point in the period.
+The metrics are described as follows:
+egressDropBandwidth: dropped outbound packets (bytes)
+egressAcceptBandwidth: accepted outbound packets (bytes)
+egressMaxBandwidthPerSec: peak outbound bandwidth (byte/s)
+ingressAcceptBandwidth: accepted inbound packets (bytes)
+ingressMaxBandwidthPerSec: peak inbound bandwidth (byte/s)
+ingressDropBandwidth: dropped inbound packets (bytes)
+Check whether the EIP bandwidth keeps increasing and whether services are normal. Increase bandwidth if necessary.
+The network becomes slow or packets are lost.
+Delete EIP
+deleteEip
+Minor
+The EIP was released.
+Check whether the EIP was release by mistake.
+The server that has the EIP bound cannot access the Internet.
+EIP blocked
+blockEIP
+Critical
+The used bandwidth of an EIP exceeded 5 Gbit/s, the EIP were blocked and packets were discarded. Such an event may be caused by DDoS attacks.
+Replace the EIP to prevent services from being affected.
+Locate and deal with the fault.
+Services are impacted.
+EIP unblocked
+unblockEIP
+Critical
+The EIP was unblocked.
+Use the previous EIP again.
+None
+Start DDoS traffic scrubbing
+ddosCleanEIP
+Major
+Traffic scrubbing on the EIP was started to prevent DDoS attacks.
+Check whether the EIP was attacked.
+Services may be interrupted.
+Stop DDoS traffic scrubbing
+ddosEndCleanEip
+Major
+Traffic scrubbing on the EIP to prevent DDoS attacks was ended.
+Check whether the EIP was attacked.
+Services may be interrupted.
+Enterprise-class QoS bandwidth limit exceeded
+EIPBandwidthRuleOverflow
+Major
+The used QoS bandwidth exceeded the allocated one, which may slow down the network or cause packet loss. The value of this event is the maximum value in a monitoring period, and the value of the EIP inbound and outbound bandwidth is the value at a specific time point in the period.
+egressDropBandwidth: dropped outbound packets (bytes)
+egressAcceptBandwidth: accepted outbound packets (bytes)
+egressMaxBandwidthPerSec: peak outbound bandwidth (byte/s)
+ingressAcceptBandwidth: accepted inbound packets (bytes)
+ingressMaxBandwidthPerSec: peak inbound bandwidth (byte/s)
+ingressDropBandwidth: dropped inbound packets (bytes)
+Check whether the EIP bandwidth keeps increasing and whether services are normal. Increase bandwidth if necessary.
+The network becomes slow or packets are lost.
- Adding a Dump Task
- - Modifying, Deleting, Enabling, or Disabling a Dump Task
+ - Modifying, Deleting, Enabling, or Disabling Dump Tasks
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.
+Scenarios
You can dump cloud service monitoring data to DMS for Kafka in real time and query the metrics on the DMS for Kafka console or using 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
+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 Data Dump.
- Click Add Dump Task.
- In the Add Dump Task dialog box, configure parameters.Figure 1 Adding a dump task+ +
-Table 1 Dump task parameters Parameter
Description
+Description
Name
+Name
Specifies the dump task 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
+Resource Type
Specifies the type of resources monitored by Cloud Eye.
+Specifies the type of resources monitored by Cloud Eye.
Example value: Elastic Cloud Server
Dimension
+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.
+Specifies the dimension of the monitored object.
+For details about the dimensions of each monitored object, see Services Interconnected with Cloud Eye.
+If you select All all monitored objects of the selected resource type will be dumped to Kafka.
+If you select a specific dimension, only metrics of this dimension will be dumped to Kafka.
Example value: All
Monitoring Scope
+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.
+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
+Resource Type
The type can only be Distributed Message Service for Kafka.
+The type can only be Distributed Message Service for Kafka.
Destination
+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.
+Specifies the Kafka instance and topic where the data is to be dumped.
+If no Kafka instance or topic is available, see Creating an Instance and Creating a Topic.
- Click Add. diff --git a/docs/ces/umn/ces_01_0057.html b/docs/ces/umn/ces_01_0057.html index bd395f14..0c6bd404 100644 --- a/docs/ces/umn/ces_01_0057.html +++ b/docs/ces/umn/ces_01_0057.html @@ -1,16 +1,18 @@ -
You can query the dumped data in Kafka.
+- Click Add after the configuration is complete.
Modifying, Deleting, Enabling, or Disabling a Dump Task
-Scenarios
This topic describes how to modify, disable, enable, or delete dump tasks.
+Modifying, Deleting, Enabling, or Disabling Dump Tasks
+-Scenarios
This topic describes how to modify, disable, enable, or delete a dump task.
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.
+-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.
- Locate a dump task and 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.
+-Disabling Dump Tasks
- Disabling a single dump task: On the Data Dump page, locate the dump task and click Disable in the Operation column. In the displayed Disable Dump Task dialog box, click Yes. After you disable a dump task, collected monitoring data will not be dumped but existing data is still saved.
- Batch disabling dump tasks: On the Data Dump page, select the check boxes in front of the data dump tasks to be disabled and click Disable above the list. In the displayed Disable Dump Task dialog box, click Yes. After you disable a dump task, collected monitoring data will not be dumped but existing data is still saved.
Enabling a Dump Task
Locate a dump task whose status is Disabled and click Enable in the Operation column.
+-Enabling Dump Tasks
- Enabling a single dump task: On the Data Dump page, locate a dump task whose status is Disabled and click Enable in the Operation column. In the displayed Enable Dump Task dialog box, click Yes. After you enable the dump task, collected monitoring data will be dumped.
- Batch enabling dump tasks: On the Data Dump page, select the check boxes in front of the data dump tasks to be enabled and click Enable above the list. In the displayed Enable Dump Task dialog box, click Yes. After you enable the dump task, collected monitoring data will be dumped.
Deleting a Dump Task
Locate the dump task and click Delete in the Operation column.
+Deleting a Dump Task
+
After you delete a dump task, collected monitoring data will not be dumped but existing data is still saved.
+Locate the dump task and click Delete in the Operation column. In the displayed Delete Data Dump dialog box, click Yes.
diff --git a/docs/ces/umn/ces_01_0067.html b/docs/ces/umn/ces_01_0067.html index 927a6444..7d47f8bb 100644 --- a/docs/ces/umn/ces_01_0067.html +++ b/docs/ces/umn/ces_01_0067.html @@ -10,7 +10,7 @@- Creating Alarm Rules
-
- Viewing Alarm History
+- Viewing Alarm Records
- Alarm Rule Management
diff --git a/docs/ces/umn/ces_01_0068.html b/docs/ces/umn/ces_01_0068.html index 48241561..3c646fd1 100644 --- a/docs/ces/umn/ces_01_0068.html +++ b/docs/ces/umn/ces_01_0068.html @@ -1,10 +1,11 @@
Introduction to the Alarm Function
-You can set 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.
+You can set alarm rules for key metrics of cloud services. When the conditions in the alarm rule are met, Cloud Eye sends emails, or SMS messages, or sends HTTP/HTTPS requests, enabling you to quickly respond to resource changes.
Cloud Eye invokes SMN APIs to send notifications. This requires you to create a topic and add subscriptions to this topic on the SMN console. Then, when you create alarm rules on Cloud Eye, you can enable the alarm notification function and select the topic. When alarm rule conditions are met, Cloud Eye sends the alarm information to subscription endpoints in real time.
- If no alarm notification topic is created, alarm notifications will be sent to the default email address of the login account.
++ If no alarm notification topic is created, alarm notifications will be sent to the default email address of the account contact.
The Alarm Rules function supports enterprise projects. If an alarm rule is associated with an enterprise project, only users who have the permission of the enterprise project can view and manage the alarm rule.
diff --git a/docs/ces/umn/ces_01_0073.html b/docs/ces/umn/ces_01_0073.html index b9db1bf7..b8b2ca86 100644 --- a/docs/ces/umn/ces_01_0073.html +++ b/docs/ces/umn/ces_01_0073.html @@ -7,9 +7,7 @@- Introduction to Alarm Rules
- - Creating an Alarm Rule by Using an Alarm Template
-
- - Creating an Alarm Rule for a Specific Metric
+ - Creating an Alarm Rule
Creating an Alarm Rule for a Specific Metric
--Cloud Eye enables you to create alarm rules for a metric of one or multiple cloud services, making it convenient for you to monitor the metric of your resources.
--Adding a Custom 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, and click Create Alarm Rule in the upper right corner.
- In the Create Alarm Rule dialog box, configure the parameters.
- Select an object and configure other parameters listed in Table 1.
--
-Table 1 Parameters 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.
-Resource Type
-Specifies the type of the resource the alarm rule is created for.
-Example value: Elastic Cloud Server
-Dimension
-Specifies the metric dimension of the selected resource type.
-Example value: ECSs
-Monitoring Scope
-Specifies the monitoring scope the alarm rule applies to. You can select Resource groups or Specific resources.
-NOTE:-- If Resource groups is selected and any resource in the group meets the alarm policy, an alarm is triggered.
- If Resource groups is selected, alarm rules cannot be created using templates.
Monitored Object
-Specifies the resource the alarm rule is created for. You can specify one or more resources.
- - 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.
-Configure manually
-Metric
-For example:
- - -CPU Usage
-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.
-Enable
-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.
N/A
-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.
-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
-
- Select an object and configure other parameters listed in Table 1.
-
-- diff --git a/docs/ces/umn/ces_01_0076.html b/docs/ces/umn/ces_01_0076.html index 558a4afa..c7dd49c7 100644 --- a/docs/ces/umn/ces_01_0076.html +++ b/docs/ces/umn/ces_01_0076.html @@ -1,14 +1,11 @@ ---Parent topic: Creating Alarm Rules-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.
-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.
Viewing Alarm Records
+diff --git a/docs/ces/umn/ces_01_0077.html b/docs/ces/umn/ces_01_0077.html index 6bb869b5..6fac818c 100644 --- a/docs/ces/umn/ces_01_0077.html +++ b/docs/ces/umn/ces_01_0077.html @@ -15,6 +15,8 @@The Alarm Records page displays the status changes of all alarm rules so that you can trace and view alarm records in a unified and convenient manner. By default, alarm records of the last seven days are displayed. You can customize the time range to display alarm records of the last 180 days.
+When an alarm is generated, you can view the alarm records about the cloud 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.
- Choose Alarm Management > Alarm Records.
On the Alarm Records page, you can view the status changes of all alarm rules in the last 7 days.
+ - Click View Details in the Operation column. On the displayed drawer, view the basic information about the resource, and view the data that triggered the latest alarm status change.-
- You can select a time range within the past 180 days to view alarm records.
- In the search bar of the Alarm Records page, you can search for alarm records by status, alarm severity, alarm rule name, resource type, resource ID, or alarm rule ID.
- In the upper left of the alarm record list, you can click Export to export alarm records.
- 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.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.
- Deleting Alarm Rules
+
- Copying an Alarm Rule
+diff --git a/docs/ces/umn/ces_01_0078.html b/docs/ces/umn/ces_01_0078.html index 511ffdfd..797e75f4 100644 --- a/docs/ces/umn/ces_01_0078.html +++ b/docs/ces/umn/ces_01_0078.html @@ -1,74 +1,289 @@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.
-
Table 1 Parameters Parameter
+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 Modify in the Operation column.
- 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.
+-
Table 1 Configuring metric alarm parameters Parameter
Description
+Description
Example Value
+Example Value
Name
+Name
Specifies the alarm rule name. The system generates a random name, which you can modify.
+Specifies the alarm rule name.
alarm-b6al
+alarm-b6al
Description
+Description
(Optional) Provides supplementary information about the alarm rule.
+(Optional) Provides supplementary information about the alarm rule.
N/A
+N/A
Monitored Object
+Alarm Type
Specifies the resource the alarm rule is created for. You can specify one or more resources.
+Specifies the alarm type to which the alarm rule applies.
N/A
+Metric
Metric
+Resource Type
For example:
-Dimension
+Specifies the metric dimension of the selected resource type.
+ECSs
+Monitoring Scope
+Specifies the monitoring scope the alarm rule applies to.
+Resource Groups
+Group
+This parameter is only available if Monitoring Scope is set to Resource groups.
+N/A
+Method
+The only option is Configure manually.
+Configure manually
+Metric
+For example:
+ -N/A
+CPU Usage
Alarm Policy
+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.
+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
+N/A
Alarm Severity
+Alarm Severity
Specifies the alarm severity, which can be Critical, Major, Minor, or Informational.
+Specifies the alarm severity, which can be Critical, Major, Minor, or Informational.
Major
+Major
Alarm Notification
+Mount Point or Disk
Specifies whether to notify users when alarms are triggered. Notifications can be sent by email, text message, or HTTP/HTTPS message.
+This parameter is displayed on the console and can be configured only when the following conditions are met:
+- Monitoring Scope: Specific resources
- Resource Type: ECSs or BMSs
- Method: Configure manually.
- Metric Name in an alarm policy: disk metric whose name is prefixed with Agent
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.
N/A
+/dev
+Alarm Notification
+Specifies whether to notify users by sending emails or SMS messages, or by sending HTTP/HTTPS messages to servers.
+N/A
+Notification Object
+Specifies the object to which alarm notifications will be sent. You can select the account contact or a topic.
+- The account contact is the tenant owner. If a user registers both a mobile number and an email address, they will receive alarm information through both channels. However, if only one of these contact methods is registered, the alarm information will be sent exclusively to that registered one.
- A topic is a specific event type for publishing messages or subscribing to notifications. If the required topic is not available, create one first and add subscriptions to it. For details, 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 00:00-08:00, Cloud Eye sends notifications only from 00:00 to 08:00.
+N/A
+Trigger Condition
+Specifies the condition for triggering an alarm notification. You can select Generated alarm (when an alarm is generated), Cleared alarm (when an alarm is cleared), or both.
+If you set Alarm Type to Event, Trigger Condition can only be Generated alarm.
+N/A
+(Optional) Enterprise Project
+Specifies the enterprise project that the alarm rule belongs to. Only users with the enterprise project permissions can view and manage the alarm rule.
+default
- Click OK.
+ +
+Table 2 Configuring event alarm parameters Parameter
+Description
+Example Value
+Name
+Specifies the alarm rule name.
+alarm-b6al
+Description
+(Optional) Provides supplementary information about the alarm rule.
+N/A
+Alarm Type
+Specifies the alarm type to which the alarm rule applies.
+Event
+Event Type
+Specifies the event type, which can be System event or Custom event.
+Custom event
+Event Source
+Specifies the service the event is generated for.
+Elastic Cloud Server
+Monitoring Scope
+Specifies the monitoring scope the alarm rule applies to.
+All resources
+Alarm Policy
+Specifies the policy for triggering an alarm.
+If Alarm Type is set to Event and a specific event occurs, Cloud Eye triggers an alarm. For example, if the event Reboot ECS occurs, an alarm will be triggered.
+NOTE:+A maximum of 50 alarm policies can be added to an alarm rule. If any one of these alarm policies is met, an alarm will be triggered.
+N/A
+Event Name
+Specifies the event name.
+For events supported by event monitoring, see Events Supported by Event Monitoring.
+ECS deleted
+Trigger Mode
+You can select Immediate trigger or Accumulative trigger based on the operation severity.
+- Immediate trigger: An alarm is triggered once an event occurs.
- Accumulative trigger: An alarm is only triggered when the number of times an event occurs meets the preset value.
Immediate trigger
+Alarm Policy
+Specifies the policy for triggering an alarm.
+NOTE:+This parameter is mandatory when Trigger Mode is set to Accumulative trigger.
+An alarm is triggered if the event occurred for three consecutive periods of 5 minutes.
+Alarm Severity
+Specifies the alarm severity, which can be Critical, Major, Minor, or Informational.
+Major
+Operation
+You can click Delete to delete an alarm policy.
+Delete
+Alarm Notification
+Specifies whether to notify users when alarms are triggered. Notifications can be sent by email, SMS message, or HTTP/HTTPS message.
+N/A
+Notification Object
+Specifies the object to which alarm notifications will be sent. You can select the account contact or a topic.
+- The account contact is the tenant owner. If a user registers both a mobile number and an email address, they will receive alarm information through both channels. However, if only one of these contact methods is registered, the alarm information will be sent exclusively to that registered one.
- A topic is a specific event type for publishing messages or subscribing to notifications. If the required topic is not available, create one first and add subscriptions to it. For details, 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 00:00-08:00, Cloud Eye sends notifications only from 00:00 to 08:00.
+N/A
+Trigger Condition
+Specifies the condition for triggering an alarm notification. You can select Generated alarm (when an alarm is generated), Cleared alarm (when an alarm is cleared), or both.
+If you set Alarm Type to Event, Trigger Condition can only be Generated alarm.
+N/A
+(Optional) Enterprise Project
+Specifies the enterprise project that the alarm rule belongs to. Only users with the enterprise project permissions can view and manage the alarm rule.
+default
+- Click Modify.
diff --git a/docs/ces/umn/ces_01_0079.html b/docs/ces/umn/ces_01_0079.html index ae5864f3..19faa248 100644 --- a/docs/ces/umn/ces_01_0079.html +++ b/docs/ces/umn/ces_01_0079.html @@ -1,8 +1,11 @@Disabling Alarm Rules
-To disable a single alarm rule, go to the Alarm Rules page, locate the row containing the alarm rule you want to disable, and click Disable in the Operation column. In the displayed Disable Alarm Rule dialog box, click Yes.
-To disable multiple alarm rules, go to the Alarm Rules page, select multiple alarm rules, and click Disable in the upper left of the alarm rule list. In the displayed Disable Alarm Rule dialog box, click Yes.
++Scenarios
If you don't need to monitor the metrics or events of a resource, you can disable the alarm rule created for the resource. Once the alarm rule is disabled, the monitoring metrics or events configured in it will no longer trigger any alarms.
+Procedure
You can disable an alarm rule in any of the following ways:
+- To disable multiple alarm rules, go to the Alarm Rules page, select multiple alarm rules, and click Disable in the upper left of the alarm rule list. In the displayed Disable Alarm Rule dialog box, click OK.
- To disable an alarm rule, go to the Alarm Rules page, locate the alarm rule you want to disable, click More, and choose Disable in the Operation column. In the displayed Disable Alarm Rule dialog box, click OK.
- On the Alarm Rules page, click the name of the alarm rule to be disabled. On the details page, click Disable in the upper right corner. In the displayed dialog box, click OK.
diff --git a/docs/ces/umn/ces_01_0080.html b/docs/ces/umn/ces_01_0080.html index 8e8985cc..e842f54b 100644 --- a/docs/ces/umn/ces_01_0080.html +++ b/docs/ces/umn/ces_01_0080.html @@ -1,8 +1,11 @@Enabling Alarm Rules
-To enable a single alarm rule, go to the Alarm Rules page, locate the row containing the alarm rule you want to enable, and click Enable in the Operation column. In the displayed Enable Alarm Rule dialog box, click Yes.
-To enable multiple alarm rules, go to the Alarm Rules page, select multiple alarm rules, and click Enable in the upper left of the alarm rule list. In the displayed Enable Alarm Rule dialog box, click Yes.
++Scenarios
If an alarm rule has been created for a resource but is currently disabled, you can enable it to keep track of the metrics or events configured in it. This allows you to promptly identify any abnormal metric data and quickly rectify the fault.
+Procedure
You can enable an alarm rule in any of the following ways:
+- To enable multiple alarm rules, go to the Alarm Rules page, select multiple alarm rules, and click Enable in the upper left of the alarm rule list. In the displayed Enable Alarm Rule dialog box, click OK.
- To enable a single alarm rule, go to the Alarm Rules page, locate the alarm rule you want to enable, and choose More > Enable in the Operation column. In the displayed Enable Alarm Rule dialog box, click OK.
- On the Alarm Rules page, click the name of the alarm rule to be enabled. On the details page, click Enable in the upper right corner. In the displayed dialog box, click OK.
diff --git a/docs/ces/umn/ces_01_0081.html b/docs/ces/umn/ces_01_0081.html index b0a8a51c..e8b6ae25 100644 --- a/docs/ces/umn/ces_01_0081.html +++ b/docs/ces/umn/ces_01_0081.html @@ -1,8 +1,10 @@Deleting Alarm Rules
-To delete a single alarm rule, go to the Alarm Rules page, locate the row containing the alarm rule you want to delete, click More in the Operation column, and choose Delete. In the displayed Delete Alarm Rule dialog box, click Yes.
-To delete multiple alarm rules, go to the Alarm Rules page, select multiple alarm rules, and click Delete in the upper left of the alarm rule list. In the displayed Delete Alarm Rule dialog box, click Yes.
++ Deleted alarm rules cannot be restored. Exercise caution when performing this operation.
+To delete a single alarm rule, go to the Alarm Rules page, locate the row containing the alarm rule you want to delete, click More in the Operation column, and choose Delete. In the displayed Delete Alarm Rule dialog box, click OK.
+To delete multiple alarm rules, go to the Alarm Rules page, select multiple alarm rules, and click Delete in the upper left of the alarm rule list. In the displayed Delete Alarm Rule dialog box, click OK.
diff --git a/docs/ces/umn/ces_01_0082.html b/docs/ces/umn/ces_01_0082.html index 75de80b1..ed62344b 100644 --- a/docs/ces/umn/ces_01_0082.html +++ b/docs/ces/umn/ces_01_0082.html @@ -1,7 +1,7 @@Alarm Templates
-+An alarm template contains a group of alarm rules for a specific service. You can use it to quickly create alarm rules for multiple resources of a cloud service. Cloud Eye recommends alarm templates based on the attributes of each cloud service. It also allows you to create custom templates as needed.
-
@@ -11,7 +11,11 @@
- Modifying a Custom Template
- - Deleting a custom alarm template
+ - Deleting a Custom Template
+
+ - Importing and Exporting Custom Templates
+
+ - Copying an Alarm Template
Creating a Custom Template
-- On the Alarm Templates page, click Create Custom Template.
- In the Configure Template step, specify the parameters listed in Table 1.-
Table 1 Parameters Parameter
+-- 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 Templates.
- Click Create Custom Template.
- On the Create Custom Template page, configure parameters by referring to Table 1.Figure 1 Create Custom Template+ +
-Table 1 Parameters Parameter
Description
+Description
Resource Type
+Name
Specifies the type of the resource the alarm rule is created for.
-Example value: Elastic Cloud Server
+Specifies the alarm rule name. The system generates a random name, which you can modify.
+Example value: alarmTemplate-c6ft
Dimension
+Description
Specifies the metric dimension of the selected resource type.
-Example value: ECSs
+(Optional) Provides supplementary information about the custom template.
Import Template
+Alarm Type
+ You can select Metric or Event.
+Method
+You can select Using existing template or Configure manually.
+- Using existing template: Select an existing template for Template. The alarm rules in the template are automatically added.
- Configure manually: You can customize alarm policies as required.
Add Resource Type
+Specifies the type of the resource the alarm rule is created for.
+Example value: Elastic Cloud Server
+NOTE:A maximum of 50 resource types can be added for each service.
+
- 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.
---
-Table 2 Parameters Parameter
-Description
-Metric
-For example:
- - -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.
-Operation
-When the number of the alarm policies is two or more, you can delete alarm policies.
-- Click Next to go to the Specify Template Details step. Specify parameters listed in Table 3. - -
- Click Finish.
+- Click Create.
diff --git a/docs/ces/umn/ces_01_0084.html b/docs/ces/umn/ces_01_0084.html index c78b0d6c..0aab4c4d 100644 --- a/docs/ces/umn/ces_01_0084.html +++ b/docs/ces/umn/ces_01_0084.html @@ -1,7 +1,8 @@Modifying a Custom Template
-- In the navigation pane on the left, choose Alarm Management > Alarm Templates and click Custom Templates. Locate the template you want to modify and click Modify in the Operation column.
- In the displayed Modify Custom Template dialog box, modify the parameter settings based on Table 2 and click Next.
- Modify the template name and description based on Table 3, and click OK.
- 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 Templates.
- Click Custom Templates.
- Locate the row containing the alarm template to be modified, and click Modify in the Operation column.
- On the Modify Custom Template page, modify the configured parameters by referring to Table 1.Figure 1 Modify Custom Template+
- Click Modify.
diff --git a/docs/ces/umn/ces_01_0085.html b/docs/ces/umn/ces_01_0085.html index 991654d3..3bf101d3 100644 --- a/docs/ces/umn/ces_01_0085.html +++ b/docs/ces/umn/ces_01_0085.html @@ -1,7 +1,12 @@ -Deleting a custom alarm template
-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.
+Deleting a Custom Template
++ Deleted custom templates cannot be restored. Exercise caution when performing this operation.
+- 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 Templates.
- +
- Locate the alarm template to be deleted and click Delete in the Operation column.
In the confirmation dialog box, click OK.
+
Figure 1 Delete Custom Template
diff --git a/docs/ces/umn/ces_01_0086.html b/docs/ces/umn/ces_01_0086.html new file mode 100644 index 00000000..4da65bdc --- /dev/null +++ b/docs/ces/umn/ces_01_0086.html @@ -0,0 +1,14 @@ + + +Auditing Operation Records on Cloud Eye
++Cloud Trace Service (CTS) records Cloud Eye operation requests initiated from the cloud service management console or open APIs and responses to the requests. You can query, audit, and trace back the operation records.
++ ++ diff --git a/docs/ces/umn/ces_01_0087.html b/docs/ces/umn/ces_01_0087.html new file mode 100644 index 00000000..79814d79 --- /dev/null +++ b/docs/ces/umn/ces_01_0087.html @@ -0,0 +1,127 @@ + + +Key Cloud Eye Operations
++++
+Table 1 Cloud Eye operations that can be recorded by CTS Operation
+Resource Type
+Trace Name
+Creating an alarm rule
+alarm_rule
+createAlarmRule
+Deleting an alarm rule
+alarm_rule
+deleteAlarmRule
+Disabling an alarm rule
+alarm_rule
+disableAlarmRule
+Enabling an alarm rule
+alarm_rule
+enableAlarmRule
+Modifying an alarm rule
+alarm_rule
+updateAlarmRule
+Updating the alarm status to Alarm
+alarm_rule
+alarmStatusChangeToAlarm
+Updating the alarm status to Insufficient data
+alarm_rule
+alarmStatusChangeToInsufficientData
+Updating the alarm status to OK
+alarm_rule
+alarmStatusChangeToOk
+Creating a custom template
+alarm_template
+createAlarmTemplate
+Deleting a custom template
+alarm_template
+deleteAlarmTemplate
+Modifying a custom template
+alarm_template
+updateAlarmTemplate
+Creating a dashboard
+dashboard
+createDashboard
+Deleting a dashboard
+dashboard
+deleteDashboard
+Modifying a dashboard
+dashboard
+updateDashboard
+Exporting monitoring data
+metric
+downloadMetricsReport
+++ diff --git a/docs/ces/umn/ces_01_0088.html b/docs/ces/umn/ces_01_0088.html new file mode 100644 index 00000000..481cf477 --- /dev/null +++ b/docs/ces/umn/ces_01_0088.html @@ -0,0 +1,22 @@ + + +++Parent topic: Auditing Operation Records on Cloud Eye+Viewing Cloud Eye Logs
+++Scenarios
After CTS is enabled, CTS starts recording operations on cloud resources. The CTS management console stores the operation records of the last 7 days.
+This section describes how to query or export the last seven days of operation records on the management console.
++Procedure
- Log in to the management console.
- In the upper left corner, select a region and project.
- Click
in the upper left corner and choose Management & Deployment > Cloud Trace Service. The CTS console is displayed. - Choose Trace List in the navigation pane on the left.
- Set filters to search for your desired traces, as shown in Figure 1. The following filters are available:
++
- Trace Type, Trace Source, Resource Type, and Search By: Select a filter from the drop-down list.
- If you select Resource ID for Search By, specify a resource ID.
- If you select Trace name for Search By, specify a trace name.
- If you select Resource name for Search By, specify a resource name.
- Operator: Select a user.
- Trace Status: Select All trace statuses, Normal, Warning, or Incident.
- Time range: You can query traces generated during any time range in the last seven days.
- Click Export to export all traces in the query result as a CSV file. The file can contain up to 5000 records.
- Trace Type, Trace Source, Resource Type, and Search By: Select a filter from the drop-down list.
- Click Query.
- On the Trace List page, you can also export and refresh the trace list.
- Click Export to export all traces in the query result as a CSV file. The file can contain up to 5000 records.
- Click
to view the latest information about traces.
- Click
on the left of a trace to expand its details.Figure 2 Expanding trace details+
- Click View Trace in the Operation column. On the displayed View Trace dialog box, view details of the trace.Figure 3 View Trace+
++ diff --git a/docs/ces/umn/ces_01_0089.html b/docs/ces/umn/ces_01_0089.html new file mode 100644 index 00000000..70fc317d --- /dev/null +++ b/docs/ces/umn/ces_01_0089.html @@ -0,0 +1,14 @@ + + +++Parent topic: Auditing Operation Records on Cloud Eye+Permissions Management
+++ + diff --git a/docs/ces/umn/ces_01_0090.html b/docs/ces/umn/ces_01_0090.html new file mode 100644 index 00000000..f11f5b65 --- /dev/null +++ b/docs/ces/umn/ces_01_0090.html @@ -0,0 +1,26 @@ + + +Creating a User and Granting Permissions
++You can use IAM for fine-grained permissions control for your Cloud Eye resources. With IAM, you can:
+- Create IAM users for employees based on your enterprise's organizational structure. Each IAM user will have their own security credentials for accessing Cloud Eye resources.
- Grant different permissions to IAM users based on their job responsibilities.
- Entrust an account or a cloud service to perform efficient O&M on your Cloud Eye resources.
If your account does not require individual IAM users, skip this topic.
+This topic describes the procedure for granting permissions (see Figure 1).
++ +Prerequisites
You have learned about the system policies of Cloud Eye before assigning the preset Cloud Eye permissions to user groups (if needed). To grant custom permissions to a user group, ensure that you have created a custom Cloud Eye policy.
+For details about the system policies supported by Cloud Eye and the comparison between these policies, see Permissions.
+- Create a user group and assign permissions.
Create a user group on the IAM console, and attach the CES Administrator, Tenant Guest, and Server Administrator policies to the group.
+ ++ - Cloud Eye is a region-specific service and must be deployed in specific physical regions. Cloud Eye permissions can be assigned and take effect only in specific regions. If you want a permission to take effect for all regions, assign it in all these regions. The global permission does not take effect.
- The preceding permissions are all Cloud Eye permissions. For more refined Cloud Eye permissions, see Permissions.
- Create a user and add it to a user group. Create a user on the IAM console and add the user to the group created in 1.
- Log in and verify permissions.
Log in to the Cloud Eye console as the created user, and verify that the user only has the CES Administrator permissions. After you log in to the Cloud Eye console and use related functions, if no authentication failure message is displayed, the authorization is successful.
+
++ diff --git a/docs/ces/umn/ces_01_0091.html b/docs/ces/umn/ces_01_0091.html new file mode 100644 index 00000000..76cea99d --- /dev/null +++ b/docs/ces/umn/ces_01_0091.html @@ -0,0 +1,57 @@ + + +++Parent topic: Permissions Management+Cloud Eye Custom Policies
++Custom policies can be created to supplement the system-defined policies of Cloud Eye. For the actions that can be added to custom policies, see Permissions Policies and Supported Actions.
+You can create custom policies in either of the following two ways:
+- Visual editor: Select cloud services, actions, resources, and request conditions. This does not require knowledge of policy syntax.
- JSON: Edit JSON policies from scratch or based on an existing policy.
For details, see Creating a Custom Policy. This topic contains examples of common Cloud Eye custom policies.
++Example Custom Policies
- Example 1: allowing users to modify alarm rules
{ + "Version": "1.1", + "Statement": [ + { + "Action": [ + "ces:alarms:put" + ], + "Effect": "Allow" + } + ] +}+
- Example 2: denying alarm rule deletion
A policy with only "Deny" permissions must be used in conjunction with other policies to take effect. If the permissions assigned to a user contain both "Allow" and "Deny", the "Deny" permissions take precedence over the "Allow" permissions.
+The following method can be used if you need to assign permissions of the CES FullAccess policy to a user but you want to prevent the user from deleting alarm rules. Create a custom policy for denying alarm rule deletion, and attach both policies to the group the user belongs. Then the user can perform all operations on alarm rules except deleting alarm rules. The following is an example of a deny policy:+{ + "Version": "1.1", + "Statement": [ + { + "Action": [ + "ces:alarms:delete" + ], + "Effect": "Deny" + } + ] +}+
- Example 3: allowing users to create, modify, query, and delete alarm rulesA custom policy can contain the actions of multiple services that are of the global or project-level type. The following is a policy with multiple actions:+
{ + "Version": "1.1", + "Statement": [ + { + "Action": [ + "ces:alarms:put", + "ces:alarms:create", + "ces:alarms:delete" + ], + "Effect": "Allow" + } + ] +}+
++ diff --git a/docs/ces/umn/ces_01_0097.html b/docs/ces/umn/ces_01_0097.html index 29d2d471..7526bb3c 100644 --- a/docs/ces/umn/ces_01_0097.html +++ b/docs/ces/umn/ces_01_0097.html @@ -8,7 +8,25 @@++Parent topic: Permissions Management+2022-10-10
+2024-09-13
+- Added Copying an Alarm Template.
- Updated Using Resource Groups.
- Updated Creating an Alarm Rule.
- Updated Creating a Resource Group.
- Updated Resource Group List.
- Updated Modifying a Resource Group.
- Updated Creating a Topic.
- Updated Adding Subscriptions.
- Update Creating an Alarm Rule.
- Updated Viewing Alarm Records.
- Updated Modifying an Alarm Rule.
- Updated Modifying a Custom Template.
- Updated Enabling Alarm Rules.
- Updated Viewing Alarm Templates.
- Updated Creating a Custom Template.
- Updated Modifying a Custom Template.
- Updated Deleting a Custom Template.
- Updated Creating an Alarm Rule to Monitor a Server.
- Updated Creating an Alarm Rule to Monitor an Event.
- Updated Services Interconnected with Cloud Eye.
2024-01-30
+This release incorporates the following changes:
+- Added Importing and Exporting Custom Templates.
- Added events of the following services: Document Database Service (DDS), Bare Metal Server (BMS), Cloud Eye, Distributed Cache Service (DCS), Distributed Database Middleware (DDM), Virtual Private Cloud (VPC), Config, Object Storage Service (OBS), Elastic IP (EIP), Elastic Load Balance (ELB), Elastic Volume Service (EVS), Host Security Service (HSS), Image Management Service (IMS), Key Management Service (KMS) in Events Supported by Event Monitoring.
- Added descriptions of Direct Connect, Object Storage Service (OBS), and Data Ingestion Service (DIS) metrics in Services Interconnected with Cloud Eye.
- Removed section "Alarm Records".
2023-08-31
+This release incorporates the following changes:
+- Added Viewing the Overview Page.
- Added Using Resource Groups.
- Added section "Creating an Alarm Rule."
- Updated Dashboards.
- Updated the procedure in Creating an Alarm Rule.
- Updated Viewing Alarm Records.
- Added section "One-Click Monitoring."
- Added section "Alarm Masking."
- Added section "Task Center."
- Added Auditing Operation Records on Cloud Eye.
- Bring section "Unhealthy Resources" offline.
- Removed section "Modifying a Resource Group".
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.
+Added Resource Groups.
2019-11-18
@@ -28,7 +46,7 @@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 unit minute for ECS and BMS OS monitoring metrics.
- Added the metric IDs for Scalable File Service (SFS) metrics.
- Deleted example values in Creating an Alarm Rule.
- Added unit minute for ECS and BMS OS monitoring metrics.
2019-11-22
@@ -65,7 +83,7 @@2018-09-30
This release incorporates the following changes:
-Optimized the Create Alarm Rule window in Creating an Alarm Rule by Using an Alarm Template.
+Optimized the Create Alarm Rule window in Creating an Alarm Rule.
Interconnected with NAT Gateway.
Glossary
-- - diff --git a/docs/ces/umn/ces_01_0109.html b/docs/ces/umn/ces_01_0109.html index 24aa9be2..d00e0d03 100644 --- a/docs/ces/umn/ces_01_0109.html +++ b/docs/ces/umn/ces_01_0109.html @@ -3,7 +3,7 @@For details about the terms involved in this document, see Glossary.
-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.
What You Can Do with Cloud Service Monitoring
- Viewing metrics: You can view the graphs of raw data collected in the last 1 hour, 3 hours, 12 hours, 1 day, and 7 days. 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, SMS messages, or HTTP/HTTPS requests, 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 index 4b6a4754..be7b1f68 100644 --- a/docs/ces/umn/ces_01_0110.html +++ b/docs/ces/umn/ces_01_0110.html @@ -1,13 +1,13 @@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?.
- 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 cloud service resource and click View Metric in the Operation column.
- 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.
- 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. You can set Period and Statistic to change the rollup period of monitoring data. For details about rollup periods, see What Is Rollup?
- If you select 7d or 30d, aggregated data is displayed by default. You can set Period and Statistic to change the rollup period of 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.- 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.-diff --git a/docs/ces/umn/ces_01_0112.html b/docs/ces/umn/ces_01_0112.html new file mode 100644 index 00000000..b59b32f5 --- /dev/null +++ b/docs/ces/umn/ces_01_0112.html @@ -0,0 +1,12 @@ + + +diff --git a/docs/ces/umn/ces_01_0123.html b/docs/ces/umn/ces_01_0123.html new file mode 100644 index 00000000..96c86bdd --- /dev/null +++ b/docs/ces/umn/ces_01_0123.html @@ -0,0 +1,12 @@ + + +Copying an Alarm Template
++- 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 Templates.
- On the Default Templates tab, locate the desired alarm template and click Copy in the Operation column.
- Click the Custom Templates tab, locate the desired alarm template, and choose More > Copy in the Operation column.
- In the Copy Template dialog box, set parameters and click OK.
++ diff --git a/docs/ces/umn/ces_01_0120.html b/docs/ces/umn/ces_01_0120.html index a40e1f00..d5181d4e 100644 --- a/docs/ces/umn/ces_01_0120.html +++ b/docs/ces/umn/ces_01_0120.html @@ -21,7 +21,7 @@++Parent topic: Alarm Templates+- Viewing Server Monitoring Metrics
-
- Creating an Alarm Rule to Monitor a Server
+- Creating an Alarm Rule to Monitor a Server
Copying 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 Alarm Rules page, locate the alarm rule you want to copy, and choose More > Copy in the Operation column.
++ diff --git a/docs/ces/umn/ces_01_0185.html b/docs/ces/umn/ces_01_0185.html new file mode 100644 index 00000000..228c76bd --- /dev/null +++ b/docs/ces/umn/ces_01_0185.html @@ -0,0 +1,17 @@ + + +++Parent topic: Alarm Rule Management+Importing and Exporting Custom Templates
+++Importing a Custom Template
- 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 Templates.
- Click the Custom Templates tab.
- Click Import.
- Upload a JSON file, enter a template name, and click OK.Figure 1 Import Template+
+ The template name must be different from that of a default template.
++Exporting a Custom Template
- 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 Templates.
- Click the Custom Templates tab.
- Locate the custom template and choose More > Export in the Operation column.
++ diff --git a/docs/ces/umn/en-us_topic_0135532770.html b/docs/ces/umn/ces_01_0205.html similarity index 88% rename from docs/ces/umn/en-us_topic_0135532770.html rename to docs/ces/umn/ces_01_0205.html index f7eb7425..b0262869 100644 --- a/docs/ces/umn/en-us_topic_0135532770.html +++ b/docs/ces/umn/ces_01_0205.html @@ -1,4 +1,4 @@ - +++Parent topic: Alarm Templates+Resource Groups
diff --git a/docs/ces/umn/en-us_topic_0135551322.html b/docs/ces/umn/ces_01_0207.html similarity index 65% rename from docs/ces/umn/en-us_topic_0135551322.html rename to docs/ces/umn/ces_01_0207.html index ef333997..a661ce52 100644 --- a/docs/ces/umn/en-us_topic_0135551322.html +++ b/docs/ces/umn/ces_01_0207.html @@ -1,13 +1,12 @@ - + -Monitoring Panels
--+Dashboards
+diff --git a/docs/ces/umn/ces_01_0235.html b/docs/ces/umn/ces_01_0235.html new file mode 100644 index 00000000..4236a9a9 --- /dev/null +++ b/docs/ces/umn/ces_01_0235.html @@ -0,0 +1,48 @@ + + +Associating Resource Groups with Alarm Templates
+++Scenarios
You can create resource groups and associate them with alarm templates to create alarm rules in batches, improving alarm rule configuration efficiency.
++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.
- On the Resource Groups page, locate the resource group and click Associate Alarm Template in the Operation column.
- In the Associate Alarm Template dialog box, select an alarm template.Figure 1 Associate Alarm Template+
- Configure the alarm notification.Figure 2 Alarm Notification+ +
+
+Table 1 Alarm Notification Parameter
+Description
+Alarm Notification
+Specifies whether to notify users when alarms are triggered. Notifications can be sent by email, SMS message, or HTTP/HTTPS message.
+Notification Object
+Specifies the object to which the alarm notification is to be sent. You can select a topic name.
+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 notification window specified in the alarm rule.
+If you set Validity Period to 08:00-20:00, Cloud Eye sends notifications only from 08:00 to 20:00.
+Trigger Condition
+Specifies the condition for triggering an alarm notification. You can select Generated alarm (when an alarm is generated), Cleared alarm (when an alarm is cleared), or both.
+ - Click OK.
++ diff --git a/docs/ces/umn/ces_06_0001.html b/docs/ces/umn/ces_06_0001.html index c0cc2866..cac771dd 100644 --- a/docs/ces/umn/ces_06_0001.html +++ b/docs/ces/umn/ces_06_0001.html @@ -1,11 +1,10 @@++Parent topic: Managing Resource Groups+Getting Started
--+diff --git a/docs/ces/umn/ces_06_0002.html b/docs/ces/umn/ces_06_0002.html deleted file mode 100644 index d0d38cb8..00000000 --- a/docs/ces/umn/ces_06_0002.html +++ /dev/null @@ -1,17 +0,0 @@ - - -Checking the Status of a Cloud Platform
--On the Monitoring Overview page, you can view information about Monitored Object Statistics, Alarm Rule Statistics, and Resource Monitoring Preview (in the Alarm State) to quickly track the overall status of the cloud platform.
--Viewing Monitored Object Statistics
- 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 Dashboard > Monitoring Overview, and you can view the service resource quantity in the Monitored Object Statistics area.
-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 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 index e4c9b807..8e606f49 100644 --- a/docs/ces/umn/ces_06_0003.html +++ b/docs/ces/umn/ces_06_0003.html @@ -10,8 +10,8 @@--Parent topic: Getting Started-- 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.
+diff --git a/docs/ces/umn/ces_06_0005.html b/docs/ces/umn/ces_06_0005.html index 0874291d..9d4b1642 100644 --- a/docs/ces/umn/ces_06_0005.html +++ b/docs/ces/umn/ces_06_0005.html @@ -3,12 +3,12 @@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 ECS or BMS and install the Agent on it.
- Change the DNS server address of and add security group rules to the 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.
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.
+-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 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.
diff --git a/docs/ces/umn/ces_06_0006.html b/docs/ces/umn/ces_06_0006.html index 5280c069..d992e89c 100644 --- a/docs/ces/umn/ces_06_0006.html +++ b/docs/ces/umn/ces_06_0006.html @@ -4,11 +4,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.
- 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.
+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 cloud service resource and click Create Alarm Rule in the Operation column.
- Configure the alarm rule name, alarm policy, and alarm notification.
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.
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.
-diff --git a/docs/ces/umn/ces_07_0002.html b/docs/ces/umn/ces_07_0002.html index 6d40ce15..9454a061 100644 --- a/docs/ces/umn/ces_07_0002.html +++ b/docs/ces/umn/ces_07_0002.html @@ -6,11 +6,11 @@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.
+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.
diff --git a/docs/ces/umn/ces_06_0007.html b/docs/ces/umn/ces_06_0007.html new file mode 100644 index 00000000..e39cb6ae --- /dev/null +++ b/docs/ces/umn/ces_06_0007.html @@ -0,0 +1,20 @@ + + +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.
+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.
Using Resource Groups
+++Scenarios
- Resource Management
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.
+ - Routine Inspection and Quick Fault Locating
Each resource group provides two pages: Resource Overview and Alarm Rules. This feature helps you view cloud resource usage and quickly locate faulty resources.
+
+Functions
- Resource groups enable you to manage your cloud resources across products.
- The unhealthy resource list enables you to quickly locate faults.
- The Alarm Rules page displays all alarm rules in a resource group. You can enable, disable, modify, or delete an alarm rule.
+Using Resource Groups
- 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 Resource Groups.
- In the upper right corner, click Create Resource Group. On the page displayed, enter a group name as prompted.
- Select cloud service resources.
- Click Create.
For details about how to create and manage resource groups, see Introduction to Resource Groups.
+For details about how to create and manage resource groups, see Resource Groups.
+
++ diff --git a/docs/ces/umn/ces_06_0008-A.html b/docs/ces/umn/ces_06_0008-A.html new file mode 100644 index 00000000..cfd687d0 --- /dev/null +++ b/docs/ces/umn/ces_06_0008-A.html @@ -0,0 +1,18 @@ + + +++Parent topic: Getting Started+Creating an Alarm Rule
+++Scenarios
The alarm function provides the alarm service for monitoring data. By creating alarm rules, you define how the alarm system checks monitoring data and sends alarm notifications when metric data meets alarm policies.
+After creating alarm rules for important metrics or events, you can promptly identify metric data exceptions or events and quickly rectify the faults.
++Functions
- Alarm rules can be created for all monitoring items on Cloud Eye.
- Alarm rules can be created for all resources, resource groups, log monitoring, custom monitoring, event monitoring, and website monitoring.
- You can set validity periods of alarm rules, that is, customize the time when alarm rules take effect.
- Notifications can be sent by email, SMS message, or HTTP/HTTPS message.
+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.
- Click Service List in the upper left corner and select Cloud Eye.
- In the navigation pane, choose Alarm Management > Alarm Rules. Click Create Alarm Rule in the upper right corner.
- On the Create Alarm Rule page, configure the parameters by referring to Table 1 to Table 4.
After the alarm rule is created, if the metric data reaches the specified threshold, Cloud Eye immediately informs you that an exception has occurred.
+++ diff --git a/docs/ces/umn/ces_07_0001.html b/docs/ces/umn/ces_07_0001.html index 0ac9419f..9ab55ed9 100644 --- a/docs/ces/umn/ces_07_0001.html +++ b/docs/ces/umn/ces_07_0001.html @@ -12,10 +12,12 @@++Parent topic: Getting Started+ - Basic Concepts
- - Constraints
+ - Notes and Constraints
- Region and AZ
+ - Permissions
+
-Reliable Real-time Monitoring
Raw data is reported to Cloud Eye in real time for monitoring of cloud services.
Alarms are generated and notifications are sent to you in real time.
Visualized Monitoring
You can create monitoring panels and graphs to compare multiple metrics. The graphs automatically refresh to display the latest data.
+-Visualized Monitoring
You can create dashboards and graphs to compare multiple metrics. The graphs are refreshed automatically to always display the latest data.
Multiple Notification Types
You can enable Alarm Notification when creating alarm rules. When the metric reaches the threshold specified in an alarm rule, Cloud Eye notifies you by emails or text messages, or by sending HTTP/HTTPS messages to an IP address of your choice, allowing you to keep track of the statuses of cloud services and enabling you to build smart alarm handling programs.
+-Multiple Notification Types
You can enable Alarm Notification when creating alarm rules. When a metric reaches the threshold specified in an alarm rule, Cloud Eye notifies you by emails or SMS messages, or by sending HTTP/HTTPS messages to an IP address of your choice, allowing you to keep track of the statuses of cloud services and enabling you to build smart alarm handling programs.
Batch Creation of Alarm Rules
Alarm templates allow you to create alarm rules in batches for multiple cloud services.
+Batch Creation of Alarm Rules
You can use alarm templates to create alarm rules in batches for multiple cloud services.
diff --git a/docs/ces/umn/ces_07_0003.html b/docs/ces/umn/ces_07_0003.html index db9b7f17..3f70243d 100644 --- a/docs/ces/umn/ces_07_0003.html +++ b/docs/ces/umn/ces_07_0003.html @@ -1,19 +1,17 @@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.
+-Cloud Service Monitoring
After enabling a cloud service supported by Cloud Eye, you can view the status and metric data of the cloud service, 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.
+-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 runs 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.
+-Performance Issues
When an alarm rule's conditions are met, Cloud Eye generates an alarm and invokes the Simple Message Notification (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.
+-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 workload increases, Cloud Eye sends you an alarm notification. After receiving the notification, you can choose to manually expand the capacity or configure AS policies to automatically increase the 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.
+-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 displays 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 collected by Log Tank Service (LTS), thus to reduce your O&M cost for log monitoring and simplify the log monitoring process.
-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
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.
diff --git a/docs/ces/umn/ces_07_0006.html b/docs/ces/umn/ces_07_0006.html index c462a522..1567428e 100644 --- a/docs/ces/umn/ces_07_0006.html +++ b/docs/ces/umn/ces_07_0006.html @@ -2,20 +2,20 @@Basic Concepts
The following concepts are central to your understanding and use of Cloud Eye:
- -Metrics
A metric refers to a quantized value of a resource dimension on the cloud platform, such as the ECS CPU usage and memory usage. A metric is a time-dependent variable that generates a certain amount of monitoring data over time. It helps you understand the changes over a specific period of time.
+ +Metrics
A metric refers to a quantized value of a resource dimension on the cloud platform, such as the ECS CPU usage and memory usage. A metric is a time-dependent variable that generates a certain amount of monitoring data over time. It helps you understand the changes over a specific period.
-Rollup
Rollup is the process in which Cloud Eye calculates the average, maximum, minimum, sum, or variance value based on sample raw data reported by each cloud service in specific periods. The calculation period is called rollup period. Cloud Eye supports the following rollup periods: 5 minutes, 20 minutes, 1 hour, 4 hours, and 24 hours.
Monitoring Panels
Monitoring panels allow you to view monitoring data of metrics of different services and dimensions. You can use monitoring panels to display metrics of key services in a centralized way, get an overview of the service status, and use monitoring data for troubleshooting.
+-Dashboards
Dashboards allow you to view monitoring data of metrics of different services and dimensions. You can use dashboards to display metrics of key services in a centralized way, get an overview of the service statuses, and use monitoring data for troubleshooting.
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.
+-Topics
A topic is used to publish messages and subscribe to notifications in SMN. 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 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, SMS messages, or HTTP/HTTPS messages to an IP address of your choice.
-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.
User Permission
By default, the public cloud system provides two types of user permissions by default: user management and resource management. User management permissions can manage users, user groups, and user group permissions. Resource management permissions can control users' operations on cloud service resources.
+User Permission
By default, the system provides two types of user permissions by default: user management and resource management. User management permissions can manage users, user groups, and user group permissions. Resource management permissions can control users' operations on cloud service resources.
For details about Cloud Eye user permissions, see Permissions.
Projects
A project is used to group and isolate OpenStack resources, such as the compute, storage, and network resources. A project can either be a department or a project team. You can use an account to create multiple projects.
diff --git a/docs/ces/umn/ces_07_0007.html b/docs/ces/umn/ces_07_0007.html index 5e850960..679dbd1a 100644 --- a/docs/ces/umn/ces_07_0007.html +++ b/docs/ces/umn/ces_07_0007.html @@ -1,72 +1,71 @@ -Constraints
-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.
+Notes and Constraints
+Table 1 lists Cloud Eye resource limits for a user. The alarm rule quota can be increased. For details about how to adjust the quota, see Quota Adjustment.
-Table 1 User resource limits Item
+Table 1 Resources and their default quotas Resource
Maximum Number Allowed
+Default Quota
Alarm rules that can be created
+Alarm rules that can be created
100
+1,000
Custom alarm templates that can be created
+Custom alarm templates that can be created
50
+200
Alarm rules that can be added to an alarm template
+Alarm rules that can be added to an alarm template
20
+20
Monitoring panels that can be created
+Dashboards that can be created
20
+20
Graphs that can be added to a monitoring panel
+Graphs that can be added to a dashboard
24
+50
Time that the alarm history can be kept
+Time that the alarm history can be kept
720 hours
+7 days
Instances that can be selected for single alarm rule creation
+Objects that can be selected for monitoring when creating an alarm rule
50
+5,000
Alarm rules that can be created at a time
+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.
+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
+Topics that can be selected for receiving notifications
5
+5
Monitoring data records that can be exported at a time
+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.
+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
+Resource groups that can be created
10
+1,000
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/ces_07_0009.html b/docs/ces/umn/ces_07_0009.html new file mode 100644 index 00000000..519f7ab7 --- /dev/null +++ b/docs/ces/umn/ces_07_0009.html @@ -0,0 +1,725 @@ + + +--Parent topic: Product Introduction-Permissions
++If you need to assign different permissions to employees in your enterprise to access your Cloud Eye resources, you can use IAM to manage fine-grained permissions. IAM provides identity authentication, permissions management, and access control, helping you secure access to your cloud service resources.
+With IAM, you can use your account to create IAM users, and assign permissions to the users to control their access to specific resources. For example, some software developers in your enterprise need to use Cloud Eye resources but should not be allowed to delete the resources or perform any other high-risk operations. In this scenario, you can create IAM users for the software developers and grant them only the permissions required for using Cloud Eye resources.
+If your account does not require individual IAM users for permissions management, skip this section.
+IAM is a free service. You pay only for the resources in your account. For more information about IAM, see IAM Service Overview.
++Cloud Eye Permissions
By default, IAM users do not have permissions. To assign permissions to IAM users, add them to one or more groups, and attach policies or roles to these groups. The users then inherit permissions from the groups to which the users belong, and can perform specific operations on cloud services.
+Cloud Eye is a project-level service deployed and accessed in specific physical regions. Therefore, Cloud Eye permissions are assigned to users in specific regions and only take effect in these regions. If you want the permissions to take effect in all regions, you need to assign the permissions to users in each region. When users access Cloud Eye, they need to switch to a region where they have been authorized to use this service.
+You can grant users permissions by using roles and policies.
+- Roles: A type of coarse-grained authorization mechanism that defines permissions related to user responsibilities. This mechanism provides only a limited number of service-level roles for authorization. When using roles to grant permissions, you also need to assign other roles on which the permissions depend to take effect. However, roles are not an ideal choice for fine-grained authorization and secure access control.
- Policies: A type of fine-grained authorization mechanism that defines permissions required to perform operations on specific cloud resources under certain conditions. This mechanism allows for more flexible policy-based authorization, meeting requirements for secure access control. For example, you can grant Cloud Eye users only the permissions for managing a certain type of Cloud Eye resources.
Most policies define permissions based on APIs. For the API actions supported by Cloud Eye, see section ''Permissions Policies and Supported Actions'' in Cloud Eye API Reference.
+
Table 1 lists the system-defined policies supported by Cloud Eye.
+ ++
+Table 1 System policies Policy Name
+Description
+Dependency
+Type
+CES Administrator
+Administrator permissions for Cloud Eye
+Depend on the Tenant Guest policy.
+Tenant Guest: a global policy, which must be assigned in the Global project
+System-defined role
+CES FullAccess
+Administrator permissions for Cloud Eye. Users granted these permissions can perform all operations on Cloud Eye.
+The Cloud Eye monitoring function involves querying resources of other cloud services, which requires the cloud services to support fine-grained authorization.
+System-defined policy
+CES ReadOnlyAccess
+Read-only permissions for Cloud Eye. Users granted these permissions can only view Cloud Eye data.
+The Cloud Eye monitoring function involves querying resources of other cloud services, which requires the cloud services to support fine-grained authorization.
+System-defined policy
+Table 2 lists common operations supported by the Cloud Eye system policies.
+ ++
+Table 2 Common operations supported by the Cloud Eye system policies Feature
+Operation
+CES Administrator
+(The Tenant Guest policy must be added at the same time.)
+Tenant Guest
+CES FullAccess
+CES ReadOnlyAccess
+Monitoring Overview
+Viewing monitoring overview
+√
+√
+√
+√
+Viewing full screen monitoring
+√
+√
+√
+√
+Dashboards
+Creating a dashboard
+√
+×
+√
+×
+Viewing full screen monitoring
+√
+√
+√
+√
+Querying a dashboard
+√
+√
+√
+√
+Deleting a dashboard
+√
+×
+√
+×
+Adding a graph
+√
+×
+√
+×
+Viewing a graph
+√
+√
+√
+√
+Modifying a graph
+√
+×
+√
+×
+Deleting a graph
+√
+×
+√
+×
+Adjusting the position of a graph
+√
+×
+√
+×
+Resource Groups
+Creating a resource group
+√
+×
+√
+×
+Viewing the resource group list
+√
+√
+√
+√
+Viewing resource groups (Resource Overview)
+√
+√
+√
+√
+Viewing resource groups (Alarm Rules)
+√
+√
+√
+√
+Viewing resource groups (Alarm Records)
+√
+√
+√
+√
+Modifying a resource group
+√
+×
+√
+×
+Deleting a resource group
+√
+×
+√
+×
+Alarm Rules
+Creating an alarm rule
+√
+×
+√
+×
+Modifying an alarm rule
+√
+×
+√
+×
+Enabling an alarm rule
+√
+×
+√
+×
+Disabling an alarm rule
+√
+×
+√
+×
+Deleting an alarm rule
+√
+×
+√
+×
+Querying the alarm rule list
+√
+√
+√
+√
+Viewing details of an alarm rule
+√
+√
+√
+√
+Alarm Records
+Viewing a graph
+√
+√
+√
+√
+Viewing alarm records
+√
+√
+√
+√
+Alarm Templates
+Viewing a default template
+√
+√
+√
+√
+Viewing a custom template
+√
+√
+√
+√
+Creating a custom template
+√
+×
+√
+×
+Modifying a custom template
+√
+×
+√
+×
+Deleting a custom template
+√
+×
+√
+×
+Server Monitoring
+Viewing the server list
+√
+√
+√
+√
+Viewing server monitoring metrics
+√
+√
+√
+√
+Installing the Agent
+√ (You must have the ECS FullAccess permission.)
+×
+√ (You must have the ECS FullAccess permission.)
+×
+Restoring the Agent configurations
+√ (You must have the Security Administrator and ECS FullAccess permissions.)
+×
+√ (You must have the Security Administrator and ECS FullAccess permissions.)
+×
+Uninstalling the Agent
+√ (You must have the ECS FullAccess permission.)
+×
+√ (You must have the ECS FullAccess permission.)
+×
+Configuring process monitoring
+√
+×
+√
+×
+Configuring monitoring for a process
+√
+×
+√
+×
+Cloud Service Monitoring
+Viewing the cloud service list
+√
+√
+√ (Cloud services need to support fine-grained authorization.)
+√ (Cloud services need to support fine-grained authorization.)
+Querying cloud service metrics
+√
+√
+√
+√
+Custom Monitoring
+Adding custom monitoring data
+√
+×
+√
+×
+Viewing the custom monitoring list
+√
+√
+√
+√
+Viewing custom monitoring data
+√
+√
+√
+√
+Event Monitoring
+Adding a custom event
+√
+×
+√
+×
+Viewing the event list
+√
+√
+√
+√
+Viewing details of an event
+√
+√
+√
+√
+Data Dumping to DMS Kafka
+Creating a dump task
+√
+×
+√
+×
+Querying data dumping tasks
+√
+√
+√
+√
+Querying a specified data dump task
+√
+√
+√
+√
+Modifying a data dump task
+√
+×
+√
+×
+Starting a data dump task
+√
+×
+√
+×
+Stopping a data dump task
+√
+×
+√
+×
+Deleting a data dump task
+√
+×
+√
+×
+Others
+Exporting monitoring data
+√
+×
+√
+×
+Sending an alarm notification
+√
+×
+√
+×
++Helpful Links
- IAM Service Overview
- Creating a User and Granting Permissions
- For the actions supported by fine-grained policies, see section "Permissions Policies and Supported Actions" in Cloud Eye API Reference.
++ diff --git a/docs/ces/umn/ces_faq_0004.html b/docs/ces/umn/ces_faq_0004.html index 9395f0b8..2ae652d8 100644 --- a/docs/ces/umn/ces_faq_0004.html +++ b/docs/ces/umn/ces_faq_0004.html @@ -1,8 +1,8 @@++Parent topic: Product Introduction+What Alarm Status Does Cloud Eye Support?
-There are three Cloud Eye alarm statuses: Alarm, OK, and Insufficient data. If an alarm rule is disabled, its status is considered as invalid, and Disabled is displayed.
-- Alarm: The monitoring data meets the preset alarm policy.
- OK: The monitoring data is reported but does not meet the preset alarm policy.
- Insufficient data: No monitoring data has been reported for three consecutive hours, and this is generally because the instance has been deleted or is abnormal.
Alarm, Resolved, Insufficient data, Triggered, and Expired are supported.
+- Alarm: The metric value reached the alarm threshold, and an alarm has been triggered but not cleared for the resource.
- Resolved: The metric value went back to the normal range, and the resource alarm was cleared.
- Insufficient data: No monitoring data has been reported for three consecutive hours, and this is generally because the instance has been deleted or is abnormal.
- Triggered: An event configured in the alarm policy triggered an alarm.
- Expired: The monitored resources or alarm policies in the alarm rule were adjusted, so the original alarm record status expired.
diff --git a/docs/ces/umn/ces_faq_0006.html b/docs/ces/umn/ces_faq_0006.html index e407fadd..74927944 100644 --- a/docs/ces/umn/ces_faq_0006.html +++ b/docs/ces/umn/ces_faq_0006.html @@ -1,10 +1,10 @@ -What Is an Alarm Notification? How Many Types of Alarm Notifications Are There? How Can I Configure an Alarm Notification?
+What Is an Alarm Notification? How Many Types of Alarm Notifications Are There?
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 notifications.
- Work with Auto Scaling to trigger the system to automatically add or remove servers.
- Send emails or SMS messages to you, or send HTTP/HTTPS messages to servers.
- 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 1b4655a9..1a1c51eb 100644 --- a/docs/ces/umn/ces_faq_0010.html +++ b/docs/ces/umn/ces_faq_0010.html @@ -11,7 +11,7 @@5 minutes
10 days
+6 days
20 minutes
diff --git a/docs/ces/umn/ces_faq_0011.html b/docs/ces/umn/ces_faq_0011.html index 143f6487..1c4e5f51 100644 --- a/docs/ces/umn/ces_faq_0011.html +++ b/docs/ces/umn/ces_faq_0011.html @@ -1,7 +1,7 @@ -What Are the Impacts on ECS Metrics If OTC Tools Is Not Installed on ECSs?
-If OTC tools are not installed on your ECSs, Cloud Eye can still monitor the outband incoming rate and outband outgoing rate. However, it cannot monitor memory usage, disk usage, inband incoming rate, or inband outgoing rate, which reduces the CPU monitoring accuracy.
+What Are the Impacts on ECS Metrics If OTC Tools Are Not Installed on ECSs?
+If OTC tools are not installed on your ECSs, Cloud Eye can still monitor the outband incoming rate and outband outgoing rate. However, it cannot monitor memory usage, disk usage, inband incoming rate, or inband outgoing rate, which lowers the CPU monitoring accuracy.
To learn more about ECS metrics supported by Cloud Eye, see Basic ECS Metrics.
diff --git a/docs/ces/umn/ces_faq_0012.html b/docs/ces/umn/ces_faq_0012.html index 3e10095d..e5c93521 100644 --- a/docs/ces/umn/ces_faq_0012.html +++ b/docs/ces/umn/ces_faq_0012.html @@ -4,8 +4,8 @@- 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.
- The first row in the exported CSV file 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:
diff --git a/docs/ces/umn/ces_faq_0025.html b/docs/ces/umn/ces_faq_0025.html index a06923a7..11c0185f 100644 --- a/docs/ces/umn/ces_faq_0025.html +++ b/docs/ces/umn/ces_faq_0025.html @@ -1,9 +1,10 @@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.
+diff --git a/docs/ces/umn/ces_faq_0027.html b/docs/ces/umn/ces_faq_0027.html index 33871de3..fbdfa825 100644 --- a/docs/ces/umn/ces_faq_0027.html +++ b/docs/ces/umn/ces_faq_0027.html @@ -2,7 +2,7 @@The OS monitoring Agent sends a heartbeat message to Cloud Eye every minute. If Cloud Eye does not receive any heartbeat messages for three consecutive 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.
- Your 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 accidentally. In this case, reinstall the Agent.
- The server time is inconsistent with the local standard time.
- The Agent plug-in logs are stored in the following directories:
- Linux: /usr/local/telescope/log/ces.log
- Windows: C:\Program Files\telescope\log\ces.log
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.
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.
+If you are in a region that does not support one-click configuration restoration of the Agent, on the Server Monitoring page, select the 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 index a22cfcb4..1e363bb1 100644 --- a/docs/ces/umn/ces_faq_0028.html +++ b/docs/ces/umn/ces_faq_0028.html @@ -3,7 +3,7 @@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
- Run the following command to open conf.json:
- Run the following command to open conf.json:
