diff --git a/docs/ces/umn/ALL_META.TXT.json b/docs/ces/umn/ALL_META.TXT.json index 9ce61b7ad..dc3422f1d 100644 --- a/docs/ces/umn/ALL_META.TXT.json +++ b/docs/ces/umn/ALL_META.TXT.json @@ -87,7 +87,7 @@ "node_id":"ces_07_0006.xml", "product_code":"ces", "code":"5", - "des":"The following concepts are central to your understanding and use of Cloud Eye:MetricsAggregationDashboardsTopicsAlarm RulesAlarm TemplatesUser PermissionProjectsA metric ", + "des":"The following concepts are central to your understanding and use of Cloud Eye:A metric refers to a quantized value of a resource dimension on the cloud platform, such as ", "doc_type":"usermanual", "kw":"Basic Concepts,Product Introduction,User Guide", "search_title":"", @@ -107,9 +107,9 @@ "node_id":"ces_07_0007.xml", "product_code":"ces", "code":"6", - "des":"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.", + "des":"Table 1 lists the default Cloud Eye resource quotas per user. For details about how to adjust the quotas, see Quota Adjustment. You can contact the Cloud Eye owner to ob", "doc_type":"usermanual", - "kw":"Notes and Constraints,Product Introduction,User Guide", + "kw":"Constraints,Product Introduction,User Guide", "search_title":"", "metedata":[ { @@ -119,7 +119,7 @@ "IsBot":"Yes" } ], - "title":"Notes and Constraints", + "title":"Constraints", "githuburl":"" }, { @@ -147,7 +147,7 @@ "node_id":"ces_07_0009.xml", "product_code":"ces", "code":"8", - "des":"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 pr", + "des":"If you need to grant your enterprise personnel permission to access your Cloud Eye resources, use Identity and Access Management (IAM). IAM provides identity authenticati", "doc_type":"usermanual", "kw":"Permissions,Product Introduction,User Guide", "search_title":"", @@ -187,9 +187,9 @@ "node_id":"en-us_topic_0015479891.xml", "product_code":"ces", "code":"10", - "des":"The Overview page provides different modules, helping you track the resource usage and alarms in real time.This module displays the total number of monitored cloud servic", + "des":"The Overview page provides resource overview, alarm statistics, server monitoring, network monitoring, and storage monitoring. You can view Monitoring Overview to learn t", "doc_type":"usermanual", - "kw":"Viewing the Overview Page,Getting Started,User Guide", + "kw":"Viewing Overview,Getting Started,User Guide", "search_title":"", "metedata":[ { @@ -199,7 +199,7 @@ "IsBot":"Yes" } ], - "title":"Viewing the Overview Page", + "title":"Viewing Overview", "githuburl":"" }, { @@ -323,13 +323,13 @@ "githuburl":"" }, { - "uri":"ces_01_0207.html", - "node_id":"ces_01_0207.xml", + "uri":"en-us_topic_0000001835759456.html", + "node_id":"en-us_topic_0000001835759456.xml", "product_code":"ces", "code":"17", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"Dashboards", + "kw":"My Dashboards", "search_title":"", "metedata":[ { @@ -339,17 +339,17 @@ "IsBot":"Yes" } ], - "title":"Dashboards", + "title":"My Dashboards", "githuburl":"" }, { - "uri":"en-us_topic_0015479901.html", - "node_id":"en-us_topic_0015479901.xml", + "uri":"en-us_topic_0015479901-A.html", + "node_id":"en-us_topic_0015479901-a.xml", "product_code":"ces", "code":"18", - "des":"Dashboards serve as custom monitoring platforms and allow you to view core metrics and compare the performance data of different services.", + "des":"You can use dashboards to view core metrics and compare the performance data of different services.You can create or delete a dashboard, and add graphs to the dashboard t", "doc_type":"usermanual", - "kw":"Introduction to Dashboards,Dashboards,User Guide", + "kw":"Overview,My Dashboards,User Guide", "search_title":"", "metedata":[ { @@ -359,17 +359,17 @@ "IsBot":"Yes" } ], - "title":"Introduction to Dashboards", + "title":"Overview", "githuburl":"" }, { - "uri":"ces_01_0011.html", - "node_id":"ces_01_0011.xml", + "uri":"ces_01_0011-A.html", + "node_id":"ces_01_0011-a.xml", "product_code":"ces", "code":"19", - "des":"You must create a dashboard before you add graphs. You can create a maximum of 20 dashboards.Log in to the management console.In the upper left corner, select a region an", + "des":"You can create a dashboard to monitor metrics. Before adding graphs, you need to create a dashboard first.You can create a maximum of 10 dashboards.Log in to the manageme", "doc_type":"usermanual", - "kw":"Creating a Dashboard,Dashboards,User Guide", + "kw":"Creating a Dashboard,My Dashboards,User Guide", "search_title":"", "metedata":[ { @@ -383,13 +383,33 @@ "githuburl":"" }, { - "uri":"ces_01_0012.html", - "node_id":"ces_01_0012.xml", + "uri":"ces_01_0255.html", + "node_id":"ces_01_0255.xml", "product_code":"ces", "code":"20", - "des":"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 g", + "des":"After creating dashboards, you can view all of them in your account on the My Dashboards page.Log in to the management console.In the upper left corner, select a region a", "doc_type":"usermanual", - "kw":"Adding a Graph,Dashboards,User Guide", + "kw":"Viewing My Dashboards,My Dashboards,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"ces", + "documenttype":"usermanual", + "IsMulti":"Yes", + "IsBot":"Yes" + } + ], + "title":"Viewing My Dashboards", + "githuburl":"" + }, + { + "uri":"ces_01_0012-A.html", + "node_id":"ces_01_0012-a.xml", + "product_code":"ces", + "code":"21", + "des":"If you are using multiple cloud services, you can add their metrics to the same dashboard by creating graphs. This way, you can view global monitoring data of these cloud", + "doc_type":"usermanual", + "kw":"Adding a Graph,My Dashboards,User Guide", "search_title":"", "metedata":[ { @@ -403,13 +423,13 @@ "githuburl":"" }, { - "uri":"ces_01_0013.html", - "node_id":"ces_01_0013.xml", + "uri":"ces_01_0230.html", + "node_id":"ces_01_0230.xml", "product_code":"ces", - "code":"21", - "des":"After you add a graph, you can view the metric trends on the Dashboards page. The system provides you both default and custom time ranges to view trends from last month. ", + "code":"22", + "des":"After adding a graph, you can view monitoring data in a default or custom time range.Log in to the management console.In the upper left corner, select a region and projec", "doc_type":"usermanual", - "kw":"Viewing a Graph,Dashboards,User Guide", + "kw":"Viewing a Graph,My Dashboards,User Guide", "search_title":"", "metedata":[ { @@ -423,13 +443,13 @@ "githuburl":"" }, { - "uri":"ces_01_0014.html", - "node_id":"ces_01_0014.xml", + "uri":"ces_01_0014-A.html", + "node_id":"ces_01_0014-a.xml", "product_code":"ces", - "code":"22", - "des":"This topic describes how to add, modify, and delete metrics on graphs.Log in to the management console.In the upper left corner, select a region and project.Click Service", + "code":"23", + "des":"If the existing metrics do not meet your requirements, you can add, modify, and delete metrics on a line chart and a bar chart.Log in to the management console.In the upp", "doc_type":"usermanual", - "kw":"Configure Graph,Dashboards,User Guide", + "kw":"Configuring a Graph,My Dashboards,User Guide", "search_title":"", "metedata":[ { @@ -439,17 +459,17 @@ "IsBot":"Yes" } ], - "title":"Configure Graph", + "title":"Configuring a Graph", "githuburl":"" }, { - "uri":"ces_01_0015.html", - "node_id":"ces_01_0015.xml", + "uri":"ces_01_0232.html", + "node_id":"ces_01_0232.xml", "product_code":"ces", - "code":"23", - "des":"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 ", + "code":"24", + "des":"If there are service changes or you need to replan parameters for a graph, you can delete the graph.Log in to the management console.In the upper left corner, select a re", "doc_type":"usermanual", - "kw":"Deleting a Graph,Dashboards,User Guide", + "kw":"Deleting a Graph,My Dashboards,User Guide", "search_title":"", "metedata":[ { @@ -463,13 +483,33 @@ "githuburl":"" }, { - "uri":"ces_01_0016.html", - "node_id":"ces_01_0016.xml", + "uri":"ces_01_0248.html", + "node_id":"ces_01_0248.xml", "product_code":"ces", - "code":"24", - "des":"To re-plan graphs on a dashboard, you can delete the dashboard. After that, all graphs on the dashboard will also be deleted.Log in to the management console.In the upper", + "code":"25", + "des":"You can copy a dashboard. If you need to create a dashboard with the same configurations and graphs as an existing one, you can simply copy the dashboard. The following ", "doc_type":"usermanual", - "kw":"Deleting a Dashboard,Dashboards,User Guide", + "kw":"Copying a Dashboard,My Dashboards,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"ces", + "documenttype":"usermanual", + "IsMulti":"Yes", + "IsBot":"Yes" + } + ], + "title":"Copying a Dashboard", + "githuburl":"" + }, + { + "uri":"ces_01_0233.html", + "node_id":"ces_01_0233.xml", + "product_code":"ces", + "code":"26", + "des":"If an existing dashboard cannot meet your requirements, you can delete it and replan graphs on a new dashboard. After you delete a dashboard, all graphs added to it will ", + "doc_type":"usermanual", + "kw":"Deleting a Dashboard,My Dashboards,User Guide", "search_title":"", "metedata":[ { @@ -486,7 +526,7 @@ "uri":"ces_01_0205.html", "node_id":"ces_01_0205.xml", "product_code":"ces", - "code":"25", + "code":"27", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Resource Groups", @@ -506,7 +546,7 @@ "uri":"en-us_topic_0102570567.html", "node_id":"en-us_topic_0102570567.xml", "product_code":"ces", - "code":"26", + "code":"28", "des":"A resource group allows you to add and monitor correlated resources and provides a collective health status for all resources that it contains.Resource Groups supports en", "doc_type":"usermanual", "kw":"Introduction to Resource Groups,Resource Groups,User Guide", @@ -526,8 +566,8 @@ "uri":"ces_01_0017.html", "node_id":"ces_01_0017.xml", "product_code":"ces", - "code":"27", - "des":"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", + "code":"29", + "des":"If you use multiple cloud services, you can add all related resources, such as ECSs, BMSs, EVS disks, EIPs, bandwidths, and databases to the same resource group for easie", "doc_type":"usermanual", "kw":"Creating a Resource Group,Resource Groups,User Guide", "search_title":"", @@ -546,7 +586,7 @@ "uri":"ces_01_0018.html", "node_id":"ces_01_0018.xml", "product_code":"ces", - "code":"28", + "code":"30", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Viewing Resource Groups", @@ -566,7 +606,7 @@ "uri":"ces_01_0019.html", "node_id":"ces_01_0019.xml", "product_code":"ces", - "code":"29", + "code":"31", "des":"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.Log in to the managem", "doc_type":"usermanual", "kw":"Resource Group List,Viewing Resource Groups,User Guide", @@ -586,7 +626,7 @@ "uri":"ces_01_0020.html", "node_id":"ces_01_0020.xml", "product_code":"ces", - "code":"30", + "code":"32", "des":"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 whe", "doc_type":"usermanual", "kw":"Resource Overview,Viewing Resource Groups,User Guide", @@ -606,7 +646,7 @@ "uri":"ces_01_0022.html", "node_id":"ces_01_0022.xml", "product_code":"ces", - "code":"31", + "code":"33", "des":"The Alarm Rules page displays all alarm rules in a resource group. You can enable, disable, modify, or delete an alarm rule.Log in to the management console.In the upper ", "doc_type":"usermanual", "kw":"Alarm Rules,Viewing Resource Groups,User Guide", @@ -626,7 +666,7 @@ "uri":"ces_01_0024.html", "node_id":"ces_01_0024.xml", "product_code":"ces", - "code":"32", + "code":"34", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Managing Resource Groups", @@ -646,7 +686,7 @@ "uri":"ces_01_0025.html", "node_id":"ces_01_0025.xml", "product_code":"ces", - "code":"33", + "code":"35", "des":"When you need to add resources to or delete resources from a resource group, modify the resource group.Log in to the management console.In the upper left corner, select a", "doc_type":"usermanual", "kw":"Modifying a Resource Group,Managing Resource Groups,User Guide", @@ -666,8 +706,8 @@ "uri":"ces_01_0026.html", "node_id":"ces_01_0026.xml", "product_code":"ces", - "code":"34", - "des":"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 ", + "code":"36", + "des":"Log in to the management console.In the upper left corner, select a region and project.Choose Service List > Cloud Eye.In the navigation pane on the left, choose Resource", "doc_type":"usermanual", "kw":"Deleting a Resource Group,Managing Resource Groups,User Guide", "search_title":"", @@ -686,7 +726,7 @@ "uri":"ces_01_0067.html", "node_id":"ces_01_0067.xml", "product_code":"ces", - "code":"35", + "code":"37", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Using the Alarm Function", @@ -706,8 +746,8 @@ "uri":"ces_01_0068.html", "node_id":"ces_01_0068.xml", "product_code":"ces", - "code":"36", - "des":"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 req", + "code":"38", + "des":"You can set alarm rules for key metrics of cloud services. When the conditions in an alarm rule are met, Cloud Eye notifies you of faults via emails, or SMS messages, or ", "doc_type":"usermanual", "kw":"Introduction to the Alarm Function,Using the Alarm Function,User Guide", "search_title":"", @@ -726,7 +766,7 @@ "uri":"ces_01_0069.html", "node_id":"ces_01_0069.xml", "product_code":"ces", - "code":"37", + "code":"39", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Creating Alarm Notification Topics", @@ -746,7 +786,7 @@ "uri":"en-us_topic_0085216039.html", "node_id":"en-us_topic_0085216039.xml", "product_code":"ces", - "code":"38", + "code":"40", "des":"A topic is used to publish messages and subscribe to notifications. It serves as a message transmission channel between publishers and subscribers.For details about how t", "doc_type":"usermanual", "kw":"Creating a Topic,Creating Alarm Notification Topics,User Guide", @@ -766,7 +806,7 @@ "uri":"en-us_topic_0084572343.html", "node_id":"en-us_topic_0084572343.xml", "product_code":"ces", - "code":"39", + "code":"41", "des":"A topic is a channel used by SMN to publish messages. After you create a topic, add subscriptions. When the metric data reaches the specified threshold or an event occurs", "doc_type":"usermanual", "kw":"Adding Subscriptions,Creating Alarm Notification Topics,User Guide", @@ -786,7 +826,7 @@ "uri":"ces_01_0073.html", "node_id":"ces_01_0073.xml", "product_code":"ces", - "code":"40", + "code":"42", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Creating Alarm Rules", @@ -806,8 +846,8 @@ "uri":"en-us_topic_0015479880.html", "node_id":"en-us_topic_0015479880.xml", "product_code":"ces", - "code":"41", - "des":"You can flexibly create alarm rules on the Cloud Eye console. You can create an alarm rule for a specific metric or use the alarm template to create alarm rules in batche", + "code":"43", + "des":"You can flexibly create alarm rules on Cloud Eye. You can create an alarm rule for a specific metric or use the alarm template to create alarm rules in batches for multip", "doc_type":"usermanual", "kw":"Introduction to Alarm Rules,Creating Alarm Rules,User Guide", "search_title":"", @@ -826,7 +866,7 @@ "uri":"en-us_topic_0084572213.html", "node_id":"en-us_topic_0084572213.xml", "product_code":"ces", - "code":"42", + "code":"44", "des":"Cloud Eye allows you to use alarm templates to create alarm rules, making it easy and convenient to add or modify alarm rules for resources or cloud services, especially ", "doc_type":"usermanual", "kw":"Creating an Alarm Rule,Creating Alarm Rules,User Guide", @@ -846,8 +886,8 @@ "uri":"ces_01_0076.html", "node_id":"ces_01_0076.xml", "product_code":"ces", - "code":"43", - "des":"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 r", + "code":"45", + "des":"The Alarm Records page displays the status changes for all alarm rules, making it easy to track and review them in one place. By default, alarm records of the last seven ", "doc_type":"usermanual", "kw":"Viewing Alarm Records,Using the Alarm Function,User Guide", "search_title":"", @@ -862,11 +902,31 @@ "title":"Viewing Alarm Records", "githuburl":"" }, + { + "uri":"en-us_topic_0171694487.html", + "node_id":"en-us_topic_0171694487.xml", + "product_code":"ces", + "code":"46", + "des":"One-click monitoring allows you to quickly enable alarm reporting for all resources. This helps you quickly establish a monitoring and alarm system and receive notificati", + "doc_type":"usermanual", + "kw":"One-Click Monitoring,Using the Alarm Function,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"ces", + "documenttype":"usermanual", + "IsMulti":"Yes", + "IsBot":"Yes" + } + ], + "title":"One-Click Monitoring", + "githuburl":"" + }, { "uri":"ces_01_0077.html", "node_id":"ces_01_0077.xml", "product_code":"ces", - "code":"44", + "code":"47", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Alarm Rule Management", @@ -886,8 +946,8 @@ "uri":"en-us_topic_0000001374986910.html", "node_id":"en-us_topic_0000001374986910.xml", "product_code":"ces", - "code":"45", - "des":"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 Manag", + "code":"48", + "des":"Log in to the management console.In the upper left corner, select a region and project.Choose Service List > Cloud Eye.Choose Alarm Management > Alarm Rules.On the displa", "doc_type":"usermanual", "kw":"Viewing Details of an Alarm Rule,Alarm Rule Management,User Guide", "search_title":"", @@ -906,8 +966,8 @@ "uri":"ces_01_0078.html", "node_id":"ces_01_0078.xml", "product_code":"ces", - "code":"46", - "des":"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 Manag", + "code":"49", + "des":"If there are service changes or you need to replan an alarm rule, you can modify the alarm rule.Log in to the management console.In the upper left corner, select a region", "doc_type":"usermanual", "kw":"Modifying an Alarm Rule,Alarm Rule Management,User Guide", "search_title":"", @@ -926,7 +986,7 @@ "uri":"ces_01_0079.html", "node_id":"ces_01_0079.xml", "product_code":"ces", - "code":"47", + "code":"50", "des":"If you do not 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 monitorin", "doc_type":"usermanual", "kw":"Disabling Alarm Rules,Alarm Rule Management,User Guide", @@ -946,7 +1006,7 @@ "uri":"ces_01_0080.html", "node_id":"ces_01_0080.xml", "product_code":"ces", - "code":"48", + "code":"51", "des":"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 ", "doc_type":"usermanual", "kw":"Enabling Alarm Rules,Alarm Rule Management,User Guide", @@ -966,7 +1026,7 @@ "uri":"ces_01_0081.html", "node_id":"ces_01_0081.xml", "product_code":"ces", - "code":"49", + "code":"52", "des":"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 containi", "doc_type":"usermanual", "kw":"Deleting Alarm Rules,Alarm Rule Management,User Guide", @@ -986,8 +1046,8 @@ "uri":"ces_01_0123.html", "node_id":"ces_01_0123.xml", "product_code":"ces", - "code":"50", - "des":"That it will be available only in the next version.Log in to the management console.In the upper left corner, select a region and project.Click Service List in the upper ", + "code":"53", + "des":"Log in to the management console.In the upper left corner, select a region and project.Choose Service List > Cloud Eye.Choose Alarm Management > Alarm Rules.On the Alarm ", "doc_type":"usermanual", "kw":"Copying an Alarm Rule,Alarm Rule Management,User Guide", "search_title":"", @@ -1006,7 +1066,7 @@ "uri":"ces_01_0082.html", "node_id":"ces_01_0082.xml", "product_code":"ces", - "code":"51", + "code":"54", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Alarm Templates", @@ -1026,8 +1086,8 @@ "uri":"en-us_topic_0077185772.html", "node_id":"en-us_topic_0077185772.xml", "product_code":"ces", - "code":"52", - "des":"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 Manag", + "code":"55", + "des":"Log in to the management console.In the upper left corner, select a region and project.Choose Service List > Cloud Eye.Choose Alarm Management > Alarm Templates.On the Al", "doc_type":"usermanual", "kw":"Viewing Alarm Templates,Alarm Templates,User Guide", "search_title":"", @@ -1046,10 +1106,10 @@ "uri":"ces_01_0083.html", "node_id":"ces_01_0083.xml", "product_code":"ces", - "code":"53", - "des":"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 Manag", + "code":"56", + "des":"Log in to the management console.In the upper left corner, select a region and project.Choose Service List > Cloud Eye.Choose Alarm Management > Alarm Templates.Click Cre", "doc_type":"usermanual", - "kw":"Creating a Custom Alarm Template,Alarm Templates,User Guide", + "kw":"Creating a Custom Metric or Event Template,Alarm Templates,User Guide", "search_title":"", "metedata":[ { @@ -1059,17 +1119,17 @@ "IsBot":"Yes" } ], - "title":"Creating a Custom Alarm Template", + "title":"Creating a Custom Metric or Event Template", "githuburl":"" }, { "uri":"ces_01_0084.html", "node_id":"ces_01_0084.xml", "product_code":"ces", - "code":"54", - "des":"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 Manag", + "code":"57", + "des":"Log in to the management console.In the upper left corner, select a region and project.Choose Service List > Cloud Eye.Choose Alarm Management > Alarm Templates.Click the", "doc_type":"usermanual", - "kw":"Modifying a Custom Alarm Template,Alarm Templates,User Guide", + "kw":"Modifying a Custom Metric or Event Template,Alarm Templates,User Guide", "search_title":"", "metedata":[ { @@ -1079,17 +1139,17 @@ "IsBot":"Yes" } ], - "title":"Modifying a Custom Alarm Template", + "title":"Modifying a Custom Metric or Event Template", "githuburl":"" }, { "uri":"ces_01_0085.html", "node_id":"ces_01_0085.xml", "product_code":"ces", - "code":"55", + "code":"58", "des":"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 an", "doc_type":"usermanual", - "kw":"Deleting a Custom Alarm Template,Alarm Templates,User Guide", + "kw":"Deleting a Custom Metric or Event Template,Alarm Templates,User Guide", "search_title":"", "metedata":[ { @@ -1099,17 +1159,17 @@ "IsBot":"Yes" } ], - "title":"Deleting a Custom Alarm Template", + "title":"Deleting a Custom Metric or Event Template", "githuburl":"" }, { "uri":"ces_01_0185.html", "node_id":"ces_01_0185.xml", "product_code":"ces", - "code":"56", - "des":"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 ", + "code":"59", + "des":"If you want to quickly create a metric or event template using an existing custom template, you can export the target template, modify the content as needed, and then imp", "doc_type":"usermanual", - "kw":"Importing and Exporting Custom Alarm Templates,Alarm Templates,User Guide", + "kw":"Importing and Exporting Custom Metric or Event Templates,Alarm Templates,User Guide", "search_title":"", "metedata":[ { @@ -1119,15 +1179,15 @@ "IsBot":"Yes" } ], - "title":"Importing and Exporting Custom Alarm Templates", + "title":"Importing and Exporting Custom Metric or Event Templates", "githuburl":"" }, { "uri":"ces_01_0112.html", "node_id":"ces_01_0112.xml", "product_code":"ces", - "code":"57", - "des":"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 Manag", + "code":"60", + "des":"Log in to the management console.In the upper left corner, select a region and project.Choose Service List > Cloud Eye.Choose Alarm Management > Alarm Templates.On the De", "doc_type":"usermanual", "kw":"Copying an Alarm Template,Alarm Templates,User Guide", "search_title":"", @@ -1146,7 +1206,7 @@ "uri":"ces_01_0120.html", "node_id":"ces_01_0120.xml", "product_code":"ces", - "code":"58", + "code":"61", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Server Monitoring", @@ -1166,7 +1226,7 @@ "uri":"en-us_topic_0078721772.html", "node_id":"en-us_topic_0078721772.xml", "product_code":"ces", - "code":"59", + "code":"62", "des":"Server monitoring includes basic monitoring, process monitoring, and OS monitoring for servers.Basic monitoring covers metrics automatically reported by ECSs. The data is", "doc_type":"usermanual", "kw":"Introduction to Server Monitoring,Server Monitoring,User Guide", @@ -1182,14 +1242,34 @@ "title":"Introduction to Server Monitoring", "githuburl":"" }, + { + "uri":"en-us_topic_0000002452369417.html", + "node_id":"en-us_topic_0000002452369417.xml", + "product_code":"ces", + "code":"63", + "des":"To enable you to monitor servers more securely and efficiently, Cloud Eye provides the latest Agent permission-granting method. That is, before installing Agents, you onl", + "doc_type":"usermanual", + "kw":"Configuring an Agency by One Click,Server Monitoring,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"ces", + "documenttype":"usermanual", + "IsMulti":"Yes", + "IsBot":"Yes" + } + ], + "title":"Configuring an Agency by One Click", + "githuburl":"" + }, { "uri":"ces_01_0027.html", "node_id":"ces_01_0027.xml", "product_code":"ces", - "code":"60", - "des":"Based on the OS you are going to use, server quantity, and personal habits, install the Agent by choosing one or more of the following scenarios:Agent installation and co", + "code":"64", + "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"Agent Installation and Configuration,Server Monitoring,User Guide", + "kw":"Agent Installation and Configuration", "search_title":"", "metedata":[ { @@ -1206,7 +1286,7 @@ "uri":"ces_01_0004.html", "node_id":"ces_01_0004.xml", "product_code":"ces", - "code":"61", + "code":"65", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Installing and Configuring the Agent on a Linux ECS or BMS", @@ -1226,7 +1306,7 @@ "uri":"en-us_topic_0150354069.html", "node_id":"en-us_topic_0150354069.xml", "product_code":"ces", - "code":"62", + "code":"66", "des":"This topic describes how to add the DNS server address and security group rules to a Linux ECS or BMS to ensure successful downloading of the Agent installation package a", "doc_type":"usermanual", "kw":"Modifying the DNS Server Address and Adding Security Group Rules (Linux),Installing and Configuring ", @@ -1246,8 +1326,8 @@ "uri":"ces_01_0029.html", "node_id":"ces_01_0029.xml", "product_code":"ces", - "code":"63", - "des":"This section describes how to manually install the Agent on a Linux ECS or BMS.You have the read and write permissions for the installation directories in Procedure. The ", + "code":"67", + "des":"This topic describes how to manually install the Agent on a Linux ECS or BMS.Some OSs are not supported. For details about which Linux OSs are supported, see What OSs Doe", "doc_type":"usermanual", "kw":"Installing the Agent on a Linux Server,Installing and Configuring the Agent on a Linux ECS or BMS,Us", "search_title":"", @@ -1262,34 +1342,14 @@ "title":"Installing the Agent on a Linux Server", "githuburl":"" }, - { - "uri":"ces_01_0030.html", - "node_id":"ces_01_0030.xml", - "product_code":"ces", - "code":"64", - "des":"This topic describes how to restore the Agent configurations on the Cloud Eye console (recommended).The Restore Agent Configurations option is unavailable for BMSs. For d", - "doc_type":"usermanual", - "kw":"Restoring the Agent Configurations on a Linux Server,Installing and Configuring the Agent on a Linux", - "search_title":"", - "metedata":[ - { - "prodname":"ces", - "documenttype":"usermanual", - "IsMulti":"Yes", - "IsBot":"Yes" - } - ], - "title":"Restoring the Agent Configurations on a Linux Server", - "githuburl":"" - }, { "uri":"ces_01_0031.html", "node_id":"ces_01_0031.xml", "product_code":"ces", - "code":"65", - "des":"After you install the Agent, configure it by clicking Restore Agent Configurations on the Cloud Eye console. If the Agent fails to be configured by clicking Restore Agent", + "code":"68", + "des":"The Configure feature allows you to configure the AK/SK, region ID, and project ID If the Agent fails to be configured by clicking Configure or due to other reasons, manu", "doc_type":"usermanual", - "kw":"(Optional) Manually Configuring the Agent (Linux),Installing and Configuring the Agent on a Linux EC", + "kw":"(Optional) Manually Configuring the Agent on a Linux Server,Installing and Configuring the Agent on ", "search_title":"", "metedata":[ { @@ -1299,14 +1359,14 @@ "IsBot":"Yes" } ], - "title":"(Optional) Manually Configuring the Agent (Linux)", + "title":"(Optional) Manually Configuring the Agent on a Linux Server", "githuburl":"" }, { "uri":"ces_01_0005.html", "node_id":"ces_01_0005.xml", "product_code":"ces", - "code":"66", + "code":"69", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Installing and Configuring the Agent on a Windows ECS", @@ -1326,7 +1386,7 @@ "uri":"en-us_topic_0150366044.html", "node_id":"en-us_topic_0150366044.xml", "product_code":"ces", - "code":"67", + "code":"70", "des":"This topic describes how to add the DNS server address and security group rules to a Windows ECS to ensure successful downloading of the Agent installation package and su", "doc_type":"usermanual", "kw":"Modifying the DNS Server Address and Adding Security Group Rules (Windows),Installing and Configurin", @@ -1346,10 +1406,10 @@ "uri":"en-us_topic_0110258146.html", "node_id":"en-us_topic_0110258146.xml", "product_code":"ces", - "code":"68", - "des":"This topic describes how to install the Agent on a Windows ECS.The Agent cannot be installed on Windows BMSs.You have performed operations described in Modifying the DNS ", + "code":"71", + "des":"This topic describes how to install the Agent on a Windows ECS.The Agent cannot be installed on Windows BMSs.Some OSs are not supported. For details about which Windows O", "doc_type":"usermanual", - "kw":"Installing and Configuring the Agent on a Windows Server,Installing and Configuring the Agent on a W", + "kw":"Installing the Agent on a Windows server,Installing and Configuring the Agent on a Windows ECS,User ", "search_title":"", "metedata":[ { @@ -1359,15 +1419,15 @@ "IsBot":"Yes" } ], - "title":"Installing and Configuring the Agent on a Windows Server", + "title":"Installing the Agent on a Windows server", "githuburl":"" }, { "uri":"ces_01_0032.html", "node_id":"ces_01_0032.xml", "product_code":"ces", - "code":"69", - "des":"After you install the Agent, configure it by clicking Restore Agent Configurations on the Cloud Eye console. If the Agent fails to be configured by clicking Restore Agent", + "code":"72", + "des":"The Configure feature allows you to configure the AK/SK, region ID, and project ID in one-click mode. If the Agent fails to be configured by clicking Configure or due to ", "doc_type":"usermanual", "kw":"(Optional) Manually Configuring the Agent on a Windows Server,Installing and Configuring the Agent o", "search_title":"", @@ -1386,10 +1446,10 @@ "uri":"ces_01_0033.html", "node_id":"ces_01_0033.xml", "product_code":"ces", - "code":"70", - "des":"This topic describes how to install Agents in batches on Linux ECSs.After binding an elastic IP address to an ECS, install and configure the Agent by following instructio", + "code":"73", + "des":"This topic describes how to batch install the Agents on Linux ECSs.After binding an elastic IP address to an ECS, install and configure the Agent by following instruction", "doc_type":"usermanual", - "kw":"Installing the Agents in Batches on Linux ECSs,Server Monitoring,User Guide", + "kw":"Installing the Agents in Batches on Linux ECSs,Agent Installation and Configuration,User Guide", "search_title":"", "metedata":[ { @@ -1406,7 +1466,7 @@ "uri":"ces_01_0035.html", "node_id":"ces_01_0035.xml", "product_code":"ces", - "code":"71", + "code":"74", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Managing the Agent", @@ -1426,8 +1486,8 @@ "uri":"ces_01_0036.html", "node_id":"ces_01_0036.xml", "product_code":"ces", - "code":"72", - "des":"To view, start, stop, update, and uninstall the Agent, you must log in as user root.Log in to an ECS or BMS as user root and run the following command to check the Agent ", + "code":"75", + "des":"This section describes how to view, start, stop, restart, uninstall, or upgrade the Agent on the Linux platform.To view, start, stop, restart, or uninstall the Agent, you", "doc_type":"usermanual", "kw":"Managing the Agent (Linux),Managing the Agent,User Guide", "search_title":"", @@ -1446,8 +1506,8 @@ "uri":"ces_01_0037.html", "node_id":"ces_01_0037.xml", "product_code":"ces", - "code":"73", - "des":"The default installation path of the Agent is C:\\Program Files\\telescope.In the task manager, check the status of the telescope process.In the directory where the Agent ", + "code":"76", + "des":"This section describes how to view, start, stop, uninstall, restart, or upgrade the Agent on the Windows platform.Earlier version: The Agent is installed in the directory", "doc_type":"usermanual", "kw":"Managing the Agent (Windows),Managing the Agent,User Guide", "search_title":"", @@ -1466,10 +1526,10 @@ "uri":"ces_01_0040.html", "node_id":"ces_01_0040.xml", "product_code":"ces", - "code":"74", + "code":"77", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", - "kw":"Process Monitoring", + "kw":"Viewing Metrics", "search_title":"", "metedata":[ { @@ -1479,17 +1539,17 @@ "IsBot":"Yes" } ], - "title":"Process Monitoring", + "title":"Viewing Metrics", "githuburl":"" }, { "uri":"en-us_topic_0092358859.html", "node_id":"en-us_topic_0092358859.xml", "product_code":"ces", - "code":"75", + "code":"78", "des":"Process monitoring is used to monitor active processes on a host. By default, the Agent collects CPU usage, memory usage, and the number of opened files of the active pro", "doc_type":"usermanual", - "kw":"Viewing Process Monitoring,Process Monitoring,User Guide", + "kw":"Viewing Process Monitoring Metrics,Viewing Metrics,User Guide", "search_title":"", "metedata":[ { @@ -1499,17 +1559,17 @@ "IsBot":"Yes" } ], - "title":"Viewing Process Monitoring", + "title":"Viewing Process Monitoring Metrics", "githuburl":"" }, { "uri":"en-us_topic_0079332017.html", "node_id":"en-us_topic_0079332017.xml", "product_code":"ces", - "code":"76", + "code":"79", "des":"This topic describes how to view server monitoring metrics, including fine-grained OS metrics collected by the Agent and basic ECS metrics.For details, see Services Inter", "doc_type":"usermanual", - "kw":"Viewing Server Monitoring Metrics,Server Monitoring,User Guide", + "kw":"Viewing Server Monitoring Metrics,Viewing Metrics,User Guide", "search_title":"", "metedata":[ { @@ -1526,8 +1586,8 @@ "uri":"ces_01_0042.html", "node_id":"ces_01_0042.xml", "product_code":"ces", - "code":"77", - "des":"This topic describes how to create an alarm rule for an ECS or BMS.Log in to the management console.In the upper left corner, select a region and project.Click Service Li", + "code":"80", + "des":"This topic describes how to create an alarm rule for an ECS or BMS.Log in to the management console.In the upper left corner, select a region and project.Choose Service L", "doc_type":"usermanual", "kw":"Creating an Alarm Rule to Monitor a Server,Server Monitoring,User Guide", "search_title":"", @@ -1546,7 +1606,7 @@ "uri":"en-us_topic_0094279601.html", "node_id":"en-us_topic_0094279601.xml", "product_code":"ces", - "code":"78", + "code":"81", "des":"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 Ey", "doc_type":"usermanual", "kw":"Custom Monitoring,User Guide", @@ -1566,7 +1626,7 @@ "uri":"ces_01_0050.html", "node_id":"ces_01_0050.xml", "product_code":"ces", - "code":"79", + "code":"82", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Event Monitoring", @@ -1586,7 +1646,7 @@ "uri":"en-us_topic_0109974074.html", "node_id":"en-us_topic_0109974074.xml", "product_code":"ces", - "code":"80", + "code":"83", "des":"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 alar", "doc_type":"usermanual", "kw":"Introduction to Event Monitoring,Event Monitoring,User Guide", @@ -1606,8 +1666,8 @@ "uri":"ces_01_0051.html", "node_id":"ces_01_0051.xml", "product_code":"ces", - "code":"81", - "des":"This topic describes how to view the event monitoring data.Log in to the management console.Click Service List in the upper left corner and select Cloud Eye.In the naviga", + "code":"84", + "des":"This topic describes how to view the event monitoring data.Log in to the management console.Choose Service List > Cloud Eye.In the navigation pane on the left, choose Eve", "doc_type":"usermanual", "kw":"Viewing Event Monitoring Data,Event Monitoring,User Guide", "search_title":"", @@ -1626,8 +1686,8 @@ "uri":"ces_01_0052.html", "node_id":"ces_01_0052.xml", "product_code":"ces", - "code":"82", - "des":"This topic describes how to create an alarm rule to monitor an event.Log in to the management console.Click Service List in the upper left corner and select Cloud Eye.In ", + "code":"85", + "des":"This topic describes how to create an alarm rule to monitor an event.Log in to the management console.Choose Service List > Cloud Eye.In the navigation pane on the left, ", "doc_type":"usermanual", "kw":"Creating an Alarm Rule to Monitor an Event,Event Monitoring,User Guide", "search_title":"", @@ -1646,8 +1706,8 @@ "uri":"ces_01_0054.html", "node_id":"ces_01_0054.xml", "product_code":"ces", - "code":"83", - "des":"Events in Event Monitoring come from operations on cloud service resources and are not collected by the Agent in Server Monitoring.Once a physical host running ECSs break", + "code":"86", + "des":"Events in Event Monitoring come from operations on cloud service resources and are not collected by the Agent in Server Monitoring.The name of a resource that supports ev", "doc_type":"usermanual", "kw":"Events Supported by Event Monitoring,Event Monitoring,User Guide", "search_title":"", @@ -1662,11 +1722,31 @@ "title":"Events Supported by Event Monitoring", "githuburl":"" }, + { + "uri":"ces_01_0108.html", + "node_id":"ces_01_0108.xml", + "product_code":"ces", + "code":"87", + "des":"On the Task Center page, you can export data including monitoring data and alarm records. You can go to the Alarm Records and Server Monitoring (Elastic Cloud Server) pag", + "doc_type":"usermanual", + "kw":"Task Center,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"ces", + "documenttype":"usermanual", + "IsMulti":"Yes", + "IsBot":"Yes" + } + ], + "title":"Task Center", + "githuburl":"" + }, { "uri":"ces_01_0055.html", "node_id":"ces_01_0055.xml", "product_code":"ces", - "code":"84", + "code":"88", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Data Dump", @@ -1686,7 +1766,7 @@ "uri":"ces_01_0056.html", "node_id":"ces_01_0056.xml", "product_code":"ces", - "code":"85", + "code":"89", "des":"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 accoun", "doc_type":"usermanual", "kw":"Adding a Dump Task,Data Dump,User Guide", @@ -1706,8 +1786,8 @@ "uri":"ces_01_0057.html", "node_id":"ces_01_0057.xml", "product_code":"ces", - "code":"86", - "des":"This topic describes how to modify, disable, enable, or delete a dump task.Log in to the management console.Click Service List in the upper left corner and select Cloud E", + "code":"90", + "des":"This topic describes how to modify, disable, enable, or delete a dump task.Log in to the management console.Choose Service List > Cloud Eye.In the navigation pane, choose", "doc_type":"usermanual", "kw":"Modifying, Deleting, Enabling, or Disabling Dump Tasks,Data Dump,User Guide", "search_title":"", @@ -1726,7 +1806,7 @@ "uri":"ces_01_0064.html", "node_id":"ces_01_0064.xml", "product_code":"ces", - "code":"87", + "code":"91", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Cloud Service Monitoring", @@ -1746,7 +1826,7 @@ "uri":"ces_01_0109.html", "node_id":"ces_01_0109.xml", "product_code":"ces", - "code":"88", + "code":"92", "des":"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 Cl", "doc_type":"usermanual", "kw":"Introduction to Cloud Service Monitoring,Cloud Service Monitoring,User Guide", @@ -1766,8 +1846,8 @@ "uri":"ces_01_0110.html", "node_id":"ces_01_0110.xml", "product_code":"ces", - "code":"89", - "des":"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 ", + "code":"93", + "des":"Log in to the management console.In the upper left corner, select a region and project.Choose Service List > Cloud Eye.In the navigation pane on the left, choose Cloud Se", "doc_type":"usermanual", "kw":"Viewing Metrics,Cloud Service Monitoring,User Guide", "search_title":"", @@ -1783,13 +1863,13 @@ "githuburl":"" }, { - "uri":"ces_01_0086.html", - "node_id":"ces_01_0086.xml", + "uri":"ces_01_0160.html", + "node_id":"ces_01_0160.xml", "product_code":"ces", - "code":"90", - "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "code":"94", + "des":"Some connected cloud services may not appear in the monitoring list. If no monitoring data is reported for all instances of a cloud service for a certain period of time, ", "doc_type":"usermanual", - "kw":"Auditing Operation Records on Cloud Eye", + "kw":"Cloud Services Displayed in the Cloud Service Monitoring List,Cloud Service Monitoring,User Guide", "search_title":"", "metedata":[ { @@ -1799,17 +1879,17 @@ "IsBot":"Yes" } ], - "title":"Auditing Operation Records on Cloud Eye", + "title":"Cloud Services Displayed in the Cloud Service Monitoring List", "githuburl":"" }, { "uri":"ces_01_0087.html", "node_id":"ces_01_0087.xml", "product_code":"ces", - "code":"91", - "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "code":"95", + "des":"With CTS, you can record operations associated with Cloud Eye for future query, audit, and backtracking.CTS has been enabled.For details, see Querying Real-Time Traces.", "doc_type":"usermanual", - "kw":"Key Cloud Eye Operations,Auditing Operation Records on Cloud Eye,User Guide", + "kw":"Key Cloud Eye Operations Supported by CTS,User Guide", "search_title":"", "metedata":[ { @@ -1819,34 +1899,14 @@ "IsBot":"Yes" } ], - "title":"Key Cloud Eye Operations", - "githuburl":"" - }, - { - "uri":"ces_01_0088.html", - "node_id":"ces_01_0088.xml", - "product_code":"ces", - "code":"92", - "des":"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 describe", - "doc_type":"usermanual", - "kw":"Viewing Cloud Eye Logs,Auditing Operation Records on Cloud Eye,User Guide", - "search_title":"", - "metedata":[ - { - "prodname":"ces", - "documenttype":"usermanual", - "IsMulti":"Yes", - "IsBot":"Yes" - } - ], - "title":"Viewing Cloud Eye Logs", + "title":"Key Cloud Eye Operations Supported by CTS", "githuburl":"" }, { "uri":"ces_01_0089.html", "node_id":"ces_01_0089.xml", "product_code":"ces", - "code":"93", + "code":"96", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Permissions Management", @@ -1866,7 +1926,7 @@ "uri":"ces_01_0090.html", "node_id":"ces_01_0090.xml", "product_code":"ces", - "code":"94", + "code":"97", "des":"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 organizatio", "doc_type":"usermanual", "kw":"Creating a User and Granting Permissions,Permissions Management,User Guide", @@ -1886,7 +1946,7 @@ "uri":"ces_01_0091.html", "node_id":"ces_01_0091.xml", "product_code":"ces", - "code":"95", + "code":"98", "des":"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 Table 3 in .You can creat", "doc_type":"usermanual", "kw":"Cloud Eye Custom Policies,Permissions Management,User Guide", @@ -1906,7 +1966,7 @@ "uri":"en-us_topic_0154940152.html", "node_id":"en-us_topic_0154940152.xml", "product_code":"ces", - "code":"96", + "code":"99", "des":"Quotas can limit the number or amount of resources available to users, such as the maximum number of ECS or EVS disks that can be created.If the existing resource quota c", "doc_type":"usermanual", "kw":"Quota Adjustment,User Guide", @@ -1926,8 +1986,8 @@ "uri":"en-us_topic_0202622212.html", "node_id":"en-us_topic_0202622212.xml", "product_code":"ces", - "code":"97", - "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "code":"100", + "des":"In addition to the preceding cloud services, the following cloud services also support event monitoring. For details about monitored events, see Events Supported by Event", "doc_type":"usermanual", "kw":"Services Interconnected with Cloud Eye,User Guide", "search_title":"", @@ -1946,7 +2006,7 @@ "uri":"en-us_topic_0084572222.html", "node_id":"en-us_topic_0084572222.xml", "product_code":"ces", - "code":"98", + "code":"101", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"FAQs", @@ -1966,7 +2026,7 @@ "uri":"index.html", "node_id":"index.xml", "product_code":"ces", - "code":"99", + "code":"102", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"General Consulting", @@ -1986,10 +2046,10 @@ "uri":"ces_faq_0009.html", "node_id":"ces_faq_0009.xml", "product_code":"ces", - "code":"100", - "des":"Aggregation is a process where Cloud Eye calculates the maximum, minimum, average, sum, or variance value of raw data sampled for different periods and repeats the proces", + "code":"103", + "des":"Rollup is a process where Cloud Eye calculates the maximum, minimum, average, sum, or variance value of raw data sampled for different periods and repeats the process for", "doc_type":"usermanual", - "kw":"What Is Aggregation?,General Consulting,User Guide", + "kw":"What Is Rollup?,General Consulting,User Guide", "search_title":"", "metedata":[ { @@ -1999,14 +2059,14 @@ "IsBot":"Yes" } ], - "title":"What Is Aggregation?", + "title":"What Is Rollup?", "githuburl":"" }, { "uri":"ces_faq_0010.html", "node_id":"ces_faq_0010.xml", "product_code":"ces", - "code":"101", + "code":"104", "des":"Metric data includes raw data and rolled-up data.Raw data is retained for two days.Rolled-up data is data aggregated based on raw data. The retention period for rolled-up", "doc_type":"usermanual", "kw":"How Long Is Metric Data Retained?,General Consulting,User Guide", @@ -2026,8 +2086,8 @@ "uri":"ces_faq_0013.html", "node_id":"ces_faq_0013.xml", "product_code":"ces", - "code":"102", - "des":"Cloud Eye supports the following rollup methods:AverageIf Avg. is selected for Statistic, Cloud Eye calculates the average value of metrics collected within a rollup peri", + "code":"105", + "des":"Cloud Eye supports the following five rollup methods, among which variance has been disabled and will be removed in later versions:AverageIf Statistic is set to Avg., Clo", "doc_type":"usermanual", "kw":"How Many Rollup Methods Does Cloud Eye Support?,General Consulting,User Guide", "search_title":"", @@ -2042,31 +2102,11 @@ "title":"How Many Rollup Methods Does Cloud Eye Support?", "githuburl":"" }, - { - "uri":"ces_faq_0012.html", - "node_id":"ces_faq_0012.xml", - "product_code":"ces", - "code":"103", - "des":"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", - "doc_type":"usermanual", - "kw":"How Can I Export Collected Data?,General Consulting,User Guide", - "search_title":"", - "metedata":[ - { - "prodname":"ces", - "documenttype":"usermanual", - "IsMulti":"Yes", - "IsBot":"Yes" - } - ], - "title":"How Can I Export Collected Data?", - "githuburl":"" - }, { "uri":"ces_faq_0059.html", "node_id":"ces_faq_0059.xml", "product_code":"ces", - "code":"104", + "code":"106", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Server Monitoring", @@ -2082,31 +2122,11 @@ "title":"Server Monitoring", "githuburl":"" }, - { - "uri":"ces_faq_0027.html", - "node_id":"ces_faq_0027.xml", - "product_code":"ces", - "code":"105", - "des":"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", - "doc_type":"usermanual", - "kw":"How Can I Quickly Restore the Agent Configuration?,Server Monitoring,User Guide", - "search_title":"", - "metedata":[ - { - "prodname":"ces", - "documenttype":"usermanual", - "IsMulti":"Yes", - "IsBot":"Yes" - } - ], - "title":"How Can I Quickly Restore the Agent Configuration?", - "githuburl":"" - }, { "uri":"ces_faq_0053.html", "node_id":"ces_faq_0053.xml", "product_code":"ces", - "code":"106", + "code":"107", "des":"The Agent was installed on a BMS, but the BMS is listed on the Server Monitoring > Elastic Cloud Server page on the Cloud Eye console.The Agent determines whether a serve", "doc_type":"usermanual", "kw":"Why Is a BMS with the Agent Installed Displayed in the ECS List on the Server Monitoring Page?,Serve", @@ -2122,11 +2142,31 @@ "title":"Why Is a BMS with the Agent Installed Displayed in the ECS List on the Server Monitoring Page?", "githuburl":"" }, + { + "uri":"ces_faq_0024.html", + "node_id":"ces_faq_0024.xml", + "product_code":"ces", + "code":"108", + "des":"The following table lists OSs compatible with the Agent. More OSs will be supported soon.Using the OSs or versions that have not been verified may adversely affect your s", + "doc_type":"usermanual", + "kw":"What OSs Does the Agent Support?,Server Monitoring,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"ces", + "documenttype":"usermanual", + "IsMulti":"Yes", + "IsBot":"Yes" + } + ], + "title":"What OSs Does the Agent Support?", + "githuburl":"" + }, { "uri":"ces_faq_0037.html", "node_id":"ces_faq_0037.xml", "product_code":"ces", - "code":"107", + "code":"109", "des":"Cloud Eye Agent uses HTTP requests to report data. Any port in the range obtained from path /proc/sys/net/ipv4/ip_local_port_range may be occupied. If any service port is", "doc_type":"usermanual", "kw":"What Should I Do If the Service Port Is Used by the Agent?,Server Monitoring,User Guide", @@ -2142,11 +2182,31 @@ "title":"What Should I Do If the Service Port Is Used by the Agent?", "githuburl":"" }, + { + "uri":"ces_faq_2502.html", + "node_id":"ces_faq_2502.xml", + "product_code":"ces", + "code":"110", + "des":"To enable you to monitor servers more securely and efficiently, Cloud Eye provides the latest Agent permission-granting method. That is, before installing Agents, you onl", + "doc_type":"usermanual", + "kw":"How Do I Configure an Agency?,Server Monitoring,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"ces", + "documenttype":"usermanual", + "IsMulti":"Yes", + "IsBot":"Yes" + } + ], + "title":"How Do I Configure an Agency?", + "githuburl":"" + }, { "uri":"ces_faq_0028.html", "node_id":"ces_faq_0028.xml", "product_code":"ces", - "code":"108", + "code":"111", "des":"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.Log in to the management co", "doc_type":"usermanual", "kw":"How Can I Create an Agency?,Server Monitoring,User Guide", @@ -2166,10 +2226,10 @@ "uri":"ces_faq_0032.html", "node_id":"ces_faq_0032.xml", "product_code":"ces", - "code":"109", - "des":"It may be that your quota is used up. If this is the case, you can delete unneeded agencies first or increase the agency quota. Then you can use the agency to restore the", + "code":"112", + "des":"Your quota may be used up. In this case, you can delete unneeded agencies first or request a higher agency quota. Then you can use the agency to restore the Agent configu", "doc_type":"usermanual", - "kw":"What Can't I Create Another Agency?,Server Monitoring,User Guide", + "kw":"Why Can't I Create Another Agency?,Server Monitoring,User Guide", "search_title":"", "metedata":[ { @@ -2179,14 +2239,14 @@ "IsBot":"Yes" } ], - "title":"What Can't I Create Another Agency?", + "title":"Why Can't I Create Another Agency?", "githuburl":"" }, { "uri":"ces_faq_0033.html", "node_id":"ces_faq_0033.xml", "product_code":"ces", - "code":"110", + "code":"113", "des":"When the Agent configuration is being restored, agency CESAgentAutoConfigAgency will be automatically created, but if you have created such an agency but not for the ECS ", "doc_type":"usermanual", "kw":"What Should I Do If Agency CESAgentAutoConfigAgency Failed to Be Automatically Created?,Server Monit", @@ -2206,7 +2266,7 @@ "uri":"ces_faq_0030.html", "node_id":"ces_faq_0030.xml", "product_code":"ces", - "code":"111", + "code":"114", "des":"An invalid agency is an agency that has expired. If you set the agencyValidity Period to Unlimited, the agency will become valid again. For details, see How Can I Create ", "doc_type":"usermanual", "kw":"What Can I Do If Agency CESAgentAutoConfigAgency Is Invalid?,Server Monitoring,User Guide", @@ -2226,7 +2286,7 @@ "uri":"ces_faq_0071.html", "node_id":"ces_faq_0071.xml", "product_code":"ces", - "code":"112", + "code":"115", "des":"The Agent uses very minimal system resources and it has almost no impact on the server performance.On an ECS, the Agent uses less than 5% of the CPU capacity and less tha", "doc_type":"usermanual", "kw":"Will the Agent Affect the Server Performance?,Server Monitoring,User Guide", @@ -2246,7 +2306,7 @@ "uri":"ces_faq_0025.html", "node_id":"ces_faq_0025.xml", "product_code":"ces", - "code":"113", + "code":"116", "des":"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 Sta", "doc_type":"usermanual", "kw":"What Should I Do If the Agent Status Is Faulty?,Server Monitoring,User Guide", @@ -2262,11 +2322,111 @@ "title":"What Should I Do If the Agent Status Is Faulty?", "githuburl":"" }, + { + "uri":"ces_faq_0126.html", + "node_id":"ces_faq_0126.xml", + "product_code":"ces", + "code":"117", + "des":"This following describes how to enable or disable metric collection by modifying the configuration file.This operation applies only to Agent 2.7.2 or later.Log in to a se", + "doc_type":"usermanual", + "kw":"How Do I Enable or Disable Metric Collection by Modifying the Configuration File?,Server Monitoring,", + "search_title":"", + "metedata":[ + { + "prodname":"ces", + "documenttype":"usermanual", + "IsMulti":"Yes", + "IsBot":"Yes" + } + ], + "title":"How Do I Enable or Disable Metric Collection by Modifying the Configuration File?", + "githuburl":"" + }, + { + "uri":"ces_faq_0127.html", + "node_id":"ces_faq_0127.xml", + "product_code":"ces", + "code":"118", + "des":"This section describes how to modify the configuration file to change the Agent resource usage threshold.This operation applies only to Agent 2.7.2 or later.ProcedureUse ", + "doc_type":"usermanual", + "kw":"How Do I Change the Agent Resource Usage Threshold by Modifying the Configuration File?,Server Monit", + "search_title":"", + "metedata":[ + { + "prodname":"ces", + "documenttype":"usermanual", + "IsMulti":"Yes", + "IsBot":"Yes" + } + ], + "title":"How Do I Change the Agent Resource Usage Threshold by Modifying the Configuration File?", + "githuburl":"" + }, + { + "uri":"ces_faq_0128.html", + "node_id":"ces_faq_0128.xml", + "product_code":"ces", + "code":"119", + "des":"The following describes how to modify the configuration file to change the process collection frequency.This operation applies only to Agent 2.7.2 or later.Enter the foll", + "doc_type":"usermanual", + "kw":"How Do I Change the Process Collection Frequency by Modifying the Configuration File?,Server Monitor", + "search_title":"", + "metedata":[ + { + "prodname":"ces", + "documenttype":"usermanual", + "IsMulti":"Yes", + "IsBot":"Yes" + } + ], + "title":"How Do I Change the Process Collection Frequency by Modifying the Configuration File?", + "githuburl":"" + }, + { + "uri":"ces_faq_2513.html", + "node_id":"ces_faq_2513.xml", + "product_code":"ces", + "code":"120", + "des":"The Monitoring Period (Raw Data) of the agent metrics is 1 minute.Currently, CES Agent can collect only physical disk metrics and does not support disks mounted using the", + "doc_type":"usermanual", + "kw":"What Metrics Are Supported by the Agent?,Server Monitoring,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"ces", + "documenttype":"usermanual", + "IsMulti":"Yes", + "IsBot":"Yes" + } + ], + "title":"What Metrics Are Supported by the Agent?", + "githuburl":"" + }, + { + "uri":"ces_faq_2514.html", + "node_id":"ces_faq_2514.xml", + "product_code":"ces", + "code":"121", + "des":"When the Agent installation command provided by the Cloud Eye console is used to batch install the Agent, the error message \"SSH dial error\" was displayed. As a result, t", + "doc_type":"usermanual", + "kw":"How Can I Fix the \"SSH dial error\" During Batch Agent Installation?,Server Monitoring,User Guide", + "search_title":"", + "metedata":[ + { + "prodname":"ces", + "documenttype":"usermanual", + "IsMulti":"Yes", + "IsBot":"Yes" + } + ], + "title":"How Can I Fix the \"SSH dial error\" During Batch Agent Installation?", + "githuburl":"" + }, { "uri":"ces_faq_0060.html", "node_id":"ces_faq_0060.xml", "product_code":"ces", - "code":"114", + "code":"122", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Alarm Notifications or False Alarms", @@ -2286,7 +2446,7 @@ "uri":"ces_faq_0006.html", "node_id":"ces_faq_0006.xml", "product_code":"ces", - "code":"115", + "code":"123", "des":"Alarm notifications are emails, SMS messages, or HTTP/HTTPS messages that are sent out when an alarm status is Alarm, OK, or both.You can configure Cloud Eye to send or n", "doc_type":"usermanual", "kw":"What Is an Alarm Notification? How Many Types of Alarm Notifications Are There?,Alarm Notifications ", @@ -2306,7 +2466,7 @@ "uri":"ces_faq_0004.html", "node_id":"ces_faq_0004.xml", "product_code":"ces", - "code":"116", + "code":"124", "des":"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 clea", "doc_type":"usermanual", "kw":"What Alarm Status Does Cloud Eye Support?,Alarm Notifications or False Alarms,User Guide", @@ -2326,7 +2486,7 @@ "uri":"ces_faq_0043.html", "node_id":"ces_faq_0043.xml", "product_code":"ces", - "code":"117", + "code":"125", "des":"There are four levels of alarm severity: critical, major, minor, and informational.Critical: An emergency fault has occurred and services are affected.Major: A relatively", "doc_type":"usermanual", "kw":"What Alarm Severities Does Cloud Eye Support?,Alarm Notifications or False Alarms,User Guide", @@ -2346,7 +2506,7 @@ "uri":"ces_faq_0017.html", "node_id":"ces_faq_0017.xml", "product_code":"ces", - "code":"118", + "code":"126", "des":"When monitoring data of a metric is not reported to Cloud Eye for three consecutive hours, the alarm rule status changes to Insufficient data.In special cases, if monitor", "doc_type":"usermanual", "kw":"When Will an \"Insufficient data\" Alarm Be Triggered?,Alarm Notifications or False Alarms,User Guide", @@ -2366,7 +2526,7 @@ "uri":"ces_faq_0062.html", "node_id":"ces_faq_0062.xml", "product_code":"ces", - "code":"119", + "code":"127", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Monitored Data Exceptions", @@ -2386,7 +2546,7 @@ "uri":"ces_faq_0045.html", "node_id":"ces_faq_0045.xml", "product_code":"ces", - "code":"120", + "code":"128", "des":"Possible causes are as follows:The cloud service is not interconnected with Cloud Eye. To check whether a cloud service has been interconnected with Cloud Eye, see Servic", "doc_type":"usermanual", "kw":"Why Is the Monitoring Data Not Displayed on the Cloud Eye Console?,Monitored Data Exceptions,User Gu", @@ -2406,7 +2566,7 @@ "uri":"ces_faq_0008.html", "node_id":"ces_faq_0008.xml", "product_code":"ces", - "code":"121", + "code":"129", "des":"Because the sampling period in Cloud Eye is different from that of the metric monitoring tool in ECS.Cloud Eye collects ECS and EVS disk data every 4 minutes (5 minutes f", "doc_type":"usermanual", "kw":"Why Are the Network Traffic Metric Values in Cloud Eye Different from Those Detected in ECS?,Monitor", @@ -2422,31 +2582,11 @@ "title":"Why Are the Network Traffic Metric Values in Cloud Eye Different from Those Detected in ECS?", "githuburl":"" }, - { - "uri":"ces_faq_0011.html", - "node_id":"ces_faq_0011.xml", - "product_code":"ces", - "code":"122", - "des":"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, dis", - "doc_type":"usermanual", - "kw":"What Are the Impacts on ECS Metrics If OTC Tools Are Not Installed on ECSs?,Monitored Data Exception", - "search_title":"", - "metedata":[ - { - "prodname":"ces", - "documenttype":"usermanual", - "IsMulti":"Yes", - "IsBot":"Yes" - } - ], - "title":"What Are the Impacts on ECS Metrics If OTC Tools Are Not Installed on ECSs?", - "githuburl":"" - }, { "uri":"ces_faq_0064.html", "node_id":"ces_faq_0064.xml", "product_code":"ces", - "code":"123", + "code":"130", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"User Permissions", @@ -2466,7 +2606,7 @@ "uri":"ces_faq_0031.html", "node_id":"ces_faq_0031.xml", "product_code":"ces", - "code":"124", + "code":"131", "des":"To use server monitoring, IAM users in a user group must have the Security Administrator permissions. If they do not have the permissions, a message indicating abnormal p", "doc_type":"usermanual", "kw":"What Should I Do If the IAM User Permissions Are Abnormal?,User Permissions,User Guide", @@ -2482,11 +2622,31 @@ "title":"What Should I Do If the IAM User Permissions Are Abnormal?", "githuburl":"" }, + { + "uri":"ces_faq_0072.html", + "node_id":"ces_faq_0072.xml", + "product_code":"ces", + "code":"132", + "des":"When an IAM user clicked Configure on the Server Monitoring page, a message indicating insufficient permissions was displayed.The IAM agency permissions are not configure", + "doc_type":"usermanual", + "kw":"What Can I Do If the System Displays a Message Indicating Insufficient Permissions When I Click Conf", + "search_title":"", + "metedata":[ + { + "prodname":"ces", + "documenttype":"usermanual", + "IsMulti":"Yes", + "IsBot":"Yes" + } + ], + "title":"What Can I Do If the System Displays a Message Indicating Insufficient Permissions When I Click Configure on the Server Monitoring Page?", + "githuburl":"" + }, { "uri":"ces_01_0097.html", "node_id":"ces_01_0097.xml", "product_code":"ces", - "code":"125", + "code":"133", "des":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "doc_type":"usermanual", "kw":"Change History,User Guide", diff --git a/docs/ces/umn/CLASS.TXT.json b/docs/ces/umn/CLASS.TXT.json index 6c5142613..66c337775 100644 --- a/docs/ces/umn/CLASS.TXT.json +++ b/docs/ces/umn/CLASS.TXT.json @@ -36,7 +36,7 @@ "code":"4" }, { - "desc":"The following concepts are central to your understanding and use of Cloud Eye:MetricsAggregationDashboardsTopicsAlarm RulesAlarm TemplatesUser PermissionProjectsA metric ", + "desc":"The following concepts are central to your understanding and use of Cloud Eye:A metric refers to a quantized value of a resource dimension on the cloud platform, such as ", "product_code":"ces", "title":"Basic Concepts", "uri":"ces_07_0006.html", @@ -45,9 +45,9 @@ "code":"5" }, { - "desc":"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.", + "desc":"Table 1 lists the default Cloud Eye resource quotas per user. For details about how to adjust the quotas, see Quota Adjustment. You can contact the Cloud Eye owner to ob", "product_code":"ces", - "title":"Notes and Constraints", + "title":"Constraints", "uri":"ces_07_0007.html", "doc_type":"usermanual", "p_code":"1", @@ -63,7 +63,7 @@ "code":"7" }, { - "desc":"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 pr", + "desc":"If you need to grant your enterprise personnel permission to access your Cloud Eye resources, use Identity and Access Management (IAM). IAM provides identity authenticati", "product_code":"ces", "title":"Permissions", "uri":"ces_07_0009.html", @@ -81,9 +81,9 @@ "code":"9" }, { - "desc":"The Overview page provides different modules, helping you track the resource usage and alarms in real time.This module displays the total number of monitored cloud servic", + "desc":"The Overview page provides resource overview, alarm statistics, server monitoring, network monitoring, and storage monitoring. You can view Monitoring Overview to learn t", "product_code":"ces", - "title":"Viewing the Overview Page", + "title":"Viewing Overview", "uri":"en-us_topic_0015479891.html", "doc_type":"usermanual", "p_code":"9", @@ -146,75 +146,93 @@ { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"ces", - "title":"Dashboards", - "uri":"ces_01_0207.html", + "title":"My Dashboards", + "uri":"en-us_topic_0000001835759456.html", "doc_type":"usermanual", "p_code":"", "code":"17" }, { - "desc":"Dashboards serve as custom monitoring platforms and allow you to view core metrics and compare the performance data of different services.", + "desc":"You can use dashboards to view core metrics and compare the performance data of different services.You can create or delete a dashboard, and add graphs to the dashboard t", "product_code":"ces", - "title":"Introduction to Dashboards", - "uri":"en-us_topic_0015479901.html", + "title":"Overview", + "uri":"en-us_topic_0015479901-A.html", "doc_type":"usermanual", "p_code":"17", "code":"18" }, { - "desc":"You must create a dashboard before you add graphs. You can create a maximum of 20 dashboards.Log in to the management console.In the upper left corner, select a region an", + "desc":"You can create a dashboard to monitor metrics. Before adding graphs, you need to create a dashboard first.You can create a maximum of 10 dashboards.Log in to the manageme", "product_code":"ces", "title":"Creating a Dashboard", - "uri":"ces_01_0011.html", + "uri":"ces_01_0011-A.html", "doc_type":"usermanual", "p_code":"17", "code":"19" }, { - "desc":"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 g", + "desc":"After creating dashboards, you can view all of them in your account on the My Dashboards page.Log in to the management console.In the upper left corner, select a region a", "product_code":"ces", - "title":"Adding a Graph", - "uri":"ces_01_0012.html", + "title":"Viewing My Dashboards", + "uri":"ces_01_0255.html", "doc_type":"usermanual", "p_code":"17", "code":"20" }, { - "desc":"After you add a graph, you can view the metric trends on the Dashboards page. The system provides you both default and custom time ranges to view trends from last month. ", + "desc":"If you are using multiple cloud services, you can add their metrics to the same dashboard by creating graphs. This way, you can view global monitoring data of these cloud", "product_code":"ces", - "title":"Viewing a Graph", - "uri":"ces_01_0013.html", + "title":"Adding a Graph", + "uri":"ces_01_0012-A.html", "doc_type":"usermanual", "p_code":"17", "code":"21" }, { - "desc":"This topic describes how to add, modify, and delete metrics on graphs.Log in to the management console.In the upper left corner, select a region and project.Click Service", + "desc":"After adding a graph, you can view monitoring data in a default or custom time range.Log in to the management console.In the upper left corner, select a region and projec", "product_code":"ces", - "title":"Configure Graph", - "uri":"ces_01_0014.html", + "title":"Viewing a Graph", + "uri":"ces_01_0230.html", "doc_type":"usermanual", "p_code":"17", "code":"22" }, { - "desc":"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 ", + "desc":"If the existing metrics do not meet your requirements, you can add, modify, and delete metrics on a line chart and a bar chart.Log in to the management console.In the upp", "product_code":"ces", - "title":"Deleting a Graph", - "uri":"ces_01_0015.html", + "title":"Configuring a Graph", + "uri":"ces_01_0014-A.html", "doc_type":"usermanual", "p_code":"17", "code":"23" }, { - "desc":"To re-plan graphs on a dashboard, you can delete the dashboard. After that, all graphs on the dashboard will also be deleted.Log in to the management console.In the upper", + "desc":"If there are service changes or you need to replan parameters for a graph, you can delete the graph.Log in to the management console.In the upper left corner, select a re", "product_code":"ces", - "title":"Deleting a Dashboard", - "uri":"ces_01_0016.html", + "title":"Deleting a Graph", + "uri":"ces_01_0232.html", "doc_type":"usermanual", "p_code":"17", "code":"24" }, + { + "desc":"You can copy a dashboard. If you need to create a dashboard with the same configurations and graphs as an existing one, you can simply copy the dashboard. The following ", + "product_code":"ces", + "title":"Copying a Dashboard", + "uri":"ces_01_0248.html", + "doc_type":"usermanual", + "p_code":"17", + "code":"25" + }, + { + "desc":"If an existing dashboard cannot meet your requirements, you can delete it and replan graphs on a new dashboard. After you delete a dashboard, all graphs added to it will ", + "product_code":"ces", + "title":"Deleting a Dashboard", + "uri":"ces_01_0233.html", + "doc_type":"usermanual", + "p_code":"17", + "code":"26" + }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"ces", @@ -222,7 +240,7 @@ "uri":"ces_01_0205.html", "doc_type":"usermanual", "p_code":"", - "code":"25" + "code":"27" }, { "desc":"A resource group allows you to add and monitor correlated resources and provides a collective health status for all resources that it contains.Resource Groups supports en", @@ -230,17 +248,17 @@ "title":"Introduction to Resource Groups", "uri":"en-us_topic_0102570567.html", "doc_type":"usermanual", - "p_code":"25", - "code":"26" + "p_code":"27", + "code":"28" }, { - "desc":"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", + "desc":"If you use multiple cloud services, you can add all related resources, such as ECSs, BMSs, EVS disks, EIPs, bandwidths, and databases to the same resource group for easie", "product_code":"ces", "title":"Creating a Resource Group", "uri":"ces_01_0017.html", "doc_type":"usermanual", - "p_code":"25", - "code":"27" + "p_code":"27", + "code":"29" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -248,8 +266,8 @@ "title":"Viewing Resource Groups", "uri":"ces_01_0018.html", "doc_type":"usermanual", - "p_code":"25", - "code":"28" + "p_code":"27", + "code":"30" }, { "desc":"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.Log in to the managem", @@ -257,8 +275,8 @@ "title":"Resource Group List", "uri":"ces_01_0019.html", "doc_type":"usermanual", - "p_code":"28", - "code":"29" + "p_code":"30", + "code":"31" }, { "desc":"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 whe", @@ -266,8 +284,8 @@ "title":"Resource Overview", "uri":"ces_01_0020.html", "doc_type":"usermanual", - "p_code":"28", - "code":"30" + "p_code":"30", + "code":"32" }, { "desc":"The Alarm Rules page displays all alarm rules in a resource group. You can enable, disable, modify, or delete an alarm rule.Log in to the management console.In the upper ", @@ -275,8 +293,8 @@ "title":"Alarm Rules", "uri":"ces_01_0022.html", "doc_type":"usermanual", - "p_code":"28", - "code":"31" + "p_code":"30", + "code":"33" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -284,8 +302,8 @@ "title":"Managing Resource Groups", "uri":"ces_01_0024.html", "doc_type":"usermanual", - "p_code":"25", - "code":"32" + "p_code":"27", + "code":"34" }, { "desc":"When you need to add resources to or delete resources from a resource group, modify the resource group.Log in to the management console.In the upper left corner, select a", @@ -293,17 +311,17 @@ "title":"Modifying a Resource Group", "uri":"ces_01_0025.html", "doc_type":"usermanual", - "p_code":"32", - "code":"33" + "p_code":"34", + "code":"35" }, { - "desc":"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 ", + "desc":"Log in to the management console.In the upper left corner, select a region and project.Choose Service List > Cloud Eye.In the navigation pane on the left, choose Resource", "product_code":"ces", "title":"Deleting a Resource Group", "uri":"ces_01_0026.html", "doc_type":"usermanual", - "p_code":"32", - "code":"34" + "p_code":"34", + "code":"36" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -312,16 +330,16 @@ "uri":"ces_01_0067.html", "doc_type":"usermanual", "p_code":"", - "code":"35" + "code":"37" }, { - "desc":"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 req", + "desc":"You can set alarm rules for key metrics of cloud services. When the conditions in an alarm rule are met, Cloud Eye notifies you of faults via emails, or SMS messages, or ", "product_code":"ces", "title":"Introduction to the Alarm Function", "uri":"ces_01_0068.html", "doc_type":"usermanual", - "p_code":"35", - "code":"36" + "p_code":"37", + "code":"38" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -329,8 +347,8 @@ "title":"Creating Alarm Notification Topics", "uri":"ces_01_0069.html", "doc_type":"usermanual", - "p_code":"35", - "code":"37" + "p_code":"37", + "code":"39" }, { "desc":"A topic is used to publish messages and subscribe to notifications. It serves as a message transmission channel between publishers and subscribers.For details about how t", @@ -338,8 +356,8 @@ "title":"Creating a Topic", "uri":"en-us_topic_0085216039.html", "doc_type":"usermanual", - "p_code":"37", - "code":"38" + "p_code":"39", + "code":"40" }, { "desc":"A topic is a channel used by SMN to publish messages. After you create a topic, add subscriptions. When the metric data reaches the specified threshold or an event occurs", @@ -347,8 +365,8 @@ "title":"Adding Subscriptions", "uri":"en-us_topic_0084572343.html", "doc_type":"usermanual", - "p_code":"37", - "code":"39" + "p_code":"39", + "code":"41" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -356,17 +374,17 @@ "title":"Creating Alarm Rules", "uri":"ces_01_0073.html", "doc_type":"usermanual", - "p_code":"35", - "code":"40" + "p_code":"37", + "code":"42" }, { - "desc":"You can flexibly create alarm rules on the Cloud Eye console. You can create an alarm rule for a specific metric or use the alarm template to create alarm rules in batche", + "desc":"You can flexibly create alarm rules on Cloud Eye. You can create an alarm rule for a specific metric or use the alarm template to create alarm rules in batches for multip", "product_code":"ces", "title":"Introduction to Alarm Rules", "uri":"en-us_topic_0015479880.html", "doc_type":"usermanual", - "p_code":"40", - "code":"41" + "p_code":"42", + "code":"43" }, { "desc":"Cloud Eye allows you to use alarm templates to create alarm rules, making it easy and convenient to add or modify alarm rules for resources or cloud services, especially ", @@ -374,17 +392,26 @@ "title":"Creating an Alarm Rule", "uri":"en-us_topic_0084572213.html", "doc_type":"usermanual", - "p_code":"40", - "code":"42" + "p_code":"42", + "code":"44" }, { - "desc":"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 r", + "desc":"The Alarm Records page displays the status changes for all alarm rules, making it easy to track and review them in one place. By default, alarm records of the last seven ", "product_code":"ces", "title":"Viewing Alarm Records", "uri":"ces_01_0076.html", "doc_type":"usermanual", - "p_code":"35", - "code":"43" + "p_code":"37", + "code":"45" + }, + { + "desc":"One-click monitoring allows you to quickly enable alarm reporting for all resources. This helps you quickly establish a monitoring and alarm system and receive notificati", + "product_code":"ces", + "title":"One-Click Monitoring", + "uri":"en-us_topic_0171694487.html", + "doc_type":"usermanual", + "p_code":"37", + "code":"46" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -392,26 +419,26 @@ "title":"Alarm Rule Management", "uri":"ces_01_0077.html", "doc_type":"usermanual", - "p_code":"35", - "code":"44" + "p_code":"37", + "code":"47" }, { - "desc":"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 Manag", + "desc":"Log in to the management console.In the upper left corner, select a region and project.Choose Service List > Cloud Eye.Choose Alarm Management > Alarm Rules.On the displa", "product_code":"ces", "title":"Viewing Details of an Alarm Rule", "uri":"en-us_topic_0000001374986910.html", "doc_type":"usermanual", - "p_code":"44", - "code":"45" + "p_code":"47", + "code":"48" }, { - "desc":"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 Manag", + "desc":"If there are service changes or you need to replan an alarm rule, you can modify the alarm rule.Log in to the management console.In the upper left corner, select a region", "product_code":"ces", "title":"Modifying an Alarm Rule", "uri":"ces_01_0078.html", "doc_type":"usermanual", - "p_code":"44", - "code":"46" + "p_code":"47", + "code":"49" }, { "desc":"If you do not 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 monitorin", @@ -419,8 +446,8 @@ "title":"Disabling Alarm Rules", "uri":"ces_01_0079.html", "doc_type":"usermanual", - "p_code":"44", - "code":"47" + "p_code":"47", + "code":"50" }, { "desc":"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 ", @@ -428,8 +455,8 @@ "title":"Enabling Alarm Rules", "uri":"ces_01_0080.html", "doc_type":"usermanual", - "p_code":"44", - "code":"48" + "p_code":"47", + "code":"51" }, { "desc":"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 containi", @@ -437,17 +464,17 @@ "title":"Deleting Alarm Rules", "uri":"ces_01_0081.html", "doc_type":"usermanual", - "p_code":"44", - "code":"49" + "p_code":"47", + "code":"52" }, { - "desc":"That it will be available only in the next version.Log in to the management console.In the upper left corner, select a region and project.Click Service List in the upper ", + "desc":"Log in to the management console.In the upper left corner, select a region and project.Choose Service List > Cloud Eye.Choose Alarm Management > Alarm Rules.On the Alarm ", "product_code":"ces", "title":"Copying an Alarm Rule", "uri":"ces_01_0123.html", "doc_type":"usermanual", - "p_code":"44", - "code":"50" + "p_code":"47", + "code":"53" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -455,62 +482,62 @@ "title":"Alarm Templates", "uri":"ces_01_0082.html", "doc_type":"usermanual", - "p_code":"35", - "code":"51" + "p_code":"37", + "code":"54" }, { - "desc":"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 Manag", + "desc":"Log in to the management console.In the upper left corner, select a region and project.Choose Service List > Cloud Eye.Choose Alarm Management > Alarm Templates.On the Al", "product_code":"ces", "title":"Viewing Alarm Templates", "uri":"en-us_topic_0077185772.html", "doc_type":"usermanual", - "p_code":"51", - "code":"52" + "p_code":"54", + "code":"55" }, { - "desc":"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 Manag", + "desc":"Log in to the management console.In the upper left corner, select a region and project.Choose Service List > Cloud Eye.Choose Alarm Management > Alarm Templates.Click Cre", "product_code":"ces", - "title":"Creating a Custom Alarm Template", + "title":"Creating a Custom Metric or Event Template", "uri":"ces_01_0083.html", "doc_type":"usermanual", - "p_code":"51", - "code":"53" + "p_code":"54", + "code":"56" }, { - "desc":"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 Manag", + "desc":"Log in to the management console.In the upper left corner, select a region and project.Choose Service List > Cloud Eye.Choose Alarm Management > Alarm Templates.Click the", "product_code":"ces", - "title":"Modifying a Custom Alarm Template", + "title":"Modifying a Custom Metric or Event Template", "uri":"ces_01_0084.html", "doc_type":"usermanual", - "p_code":"51", - "code":"54" + "p_code":"54", + "code":"57" }, { "desc":"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 an", "product_code":"ces", - "title":"Deleting a Custom Alarm Template", + "title":"Deleting a Custom Metric or Event Template", "uri":"ces_01_0085.html", "doc_type":"usermanual", - "p_code":"51", - "code":"55" + "p_code":"54", + "code":"58" }, { - "desc":"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 ", + "desc":"If you want to quickly create a metric or event template using an existing custom template, you can export the target template, modify the content as needed, and then imp", "product_code":"ces", - "title":"Importing and Exporting Custom Alarm Templates", + "title":"Importing and Exporting Custom Metric or Event Templates", "uri":"ces_01_0185.html", "doc_type":"usermanual", - "p_code":"51", - "code":"56" + "p_code":"54", + "code":"59" }, { - "desc":"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 Manag", + "desc":"Log in to the management console.In the upper left corner, select a region and project.Choose Service List > Cloud Eye.Choose Alarm Management > Alarm Templates.On the De", "product_code":"ces", "title":"Copying an Alarm Template", "uri":"ces_01_0112.html", "doc_type":"usermanual", - "p_code":"51", - "code":"57" + "p_code":"54", + "code":"60" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -519,7 +546,7 @@ "uri":"ces_01_0120.html", "doc_type":"usermanual", "p_code":"", - "code":"58" + "code":"61" }, { "desc":"Server monitoring includes basic monitoring, process monitoring, and OS monitoring for servers.Basic monitoring covers metrics automatically reported by ECSs. The data is", @@ -527,17 +554,26 @@ "title":"Introduction to Server Monitoring", "uri":"en-us_topic_0078721772.html", "doc_type":"usermanual", - "p_code":"58", - "code":"59" + "p_code":"61", + "code":"62" }, { - "desc":"Based on the OS you are going to use, server quantity, and personal habits, install the Agent by choosing one or more of the following scenarios:Agent installation and co", + "desc":"To enable you to monitor servers more securely and efficiently, Cloud Eye provides the latest Agent permission-granting method. That is, before installing Agents, you onl", + "product_code":"ces", + "title":"Configuring an Agency by One Click", + "uri":"en-us_topic_0000002452369417.html", + "doc_type":"usermanual", + "p_code":"61", + "code":"63" + }, + { + "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"ces", "title":"Agent Installation and Configuration", "uri":"ces_01_0027.html", "doc_type":"usermanual", - "p_code":"58", - "code":"60" + "p_code":"61", + "code":"64" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -545,8 +581,8 @@ "title":"Installing and Configuring the Agent on a Linux ECS or BMS", "uri":"ces_01_0004.html", "doc_type":"usermanual", - "p_code":"58", - "code":"61" + "p_code":"64", + "code":"65" }, { "desc":"This topic describes how to add the DNS server address and security group rules to a Linux ECS or BMS to ensure successful downloading of the Agent installation package a", @@ -554,35 +590,26 @@ "title":"Modifying the DNS Server Address and Adding Security Group Rules (Linux)", "uri":"en-us_topic_0150354069.html", "doc_type":"usermanual", - "p_code":"61", - "code":"62" + "p_code":"65", + "code":"66" }, { - "desc":"This section describes how to manually install the Agent on a Linux ECS or BMS.You have the read and write permissions for the installation directories in Procedure. The ", + "desc":"This topic describes how to manually install the Agent on a Linux ECS or BMS.Some OSs are not supported. For details about which Linux OSs are supported, see What OSs Doe", "product_code":"ces", "title":"Installing the Agent on a Linux Server", "uri":"ces_01_0029.html", "doc_type":"usermanual", - "p_code":"61", - "code":"63" + "p_code":"65", + "code":"67" }, { - "desc":"This topic describes how to restore the Agent configurations on the Cloud Eye console (recommended).The Restore Agent Configurations option is unavailable for BMSs. For d", + "desc":"The Configure feature allows you to configure the AK/SK, region ID, and project ID If the Agent fails to be configured by clicking Configure or due to other reasons, manu", "product_code":"ces", - "title":"Restoring the Agent Configurations on a Linux Server", - "uri":"ces_01_0030.html", - "doc_type":"usermanual", - "p_code":"61", - "code":"64" - }, - { - "desc":"After you install the Agent, configure it by clicking Restore Agent Configurations on the Cloud Eye console. If the Agent fails to be configured by clicking Restore Agent", - "product_code":"ces", - "title":"(Optional) Manually Configuring the Agent (Linux)", + "title":"(Optional) Manually Configuring the Agent on a Linux Server", "uri":"ces_01_0031.html", "doc_type":"usermanual", - "p_code":"61", - "code":"65" + "p_code":"65", + "code":"68" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -590,8 +617,8 @@ "title":"Installing and Configuring the Agent on a Windows ECS", "uri":"ces_01_0005.html", "doc_type":"usermanual", - "p_code":"58", - "code":"66" + "p_code":"64", + "code":"69" }, { "desc":"This topic describes how to add the DNS server address and security group rules to a Windows ECS to ensure successful downloading of the Agent installation package and su", @@ -599,35 +626,35 @@ "title":"Modifying the DNS Server Address and Adding Security Group Rules (Windows)", "uri":"en-us_topic_0150366044.html", "doc_type":"usermanual", - "p_code":"66", - "code":"67" + "p_code":"69", + "code":"70" }, { - "desc":"This topic describes how to install the Agent on a Windows ECS.The Agent cannot be installed on Windows BMSs.You have performed operations described in Modifying the DNS ", + "desc":"This topic describes how to install the Agent on a Windows ECS.The Agent cannot be installed on Windows BMSs.Some OSs are not supported. For details about which Windows O", "product_code":"ces", - "title":"Installing and Configuring the Agent on a Windows Server", + "title":"Installing the Agent on a Windows server", "uri":"en-us_topic_0110258146.html", "doc_type":"usermanual", - "p_code":"66", - "code":"68" + "p_code":"69", + "code":"71" }, { - "desc":"After you install the Agent, configure it by clicking Restore Agent Configurations on the Cloud Eye console. If the Agent fails to be configured by clicking Restore Agent", + "desc":"The Configure feature allows you to configure the AK/SK, region ID, and project ID in one-click mode. If the Agent fails to be configured by clicking Configure or due to ", "product_code":"ces", "title":"(Optional) Manually Configuring the Agent on a Windows Server", "uri":"ces_01_0032.html", "doc_type":"usermanual", - "p_code":"66", - "code":"69" + "p_code":"69", + "code":"72" }, { - "desc":"This topic describes how to install Agents in batches on Linux ECSs.After binding an elastic IP address to an ECS, install and configure the Agent by following instructio", + "desc":"This topic describes how to batch install the Agents on Linux ECSs.After binding an elastic IP address to an ECS, install and configure the Agent by following instruction", "product_code":"ces", "title":"Installing the Agents in Batches on Linux ECSs", "uri":"ces_01_0033.html", "doc_type":"usermanual", - "p_code":"58", - "code":"70" + "p_code":"64", + "code":"73" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -635,44 +662,44 @@ "title":"Managing the Agent", "uri":"ces_01_0035.html", "doc_type":"usermanual", - "p_code":"58", - "code":"71" + "p_code":"61", + "code":"74" }, { - "desc":"To view, start, stop, update, and uninstall the Agent, you must log in as user root.Log in to an ECS or BMS as user root and run the following command to check the Agent ", + "desc":"This section describes how to view, start, stop, restart, uninstall, or upgrade the Agent on the Linux platform.To view, start, stop, restart, or uninstall the Agent, you", "product_code":"ces", "title":"Managing the Agent (Linux)", "uri":"ces_01_0036.html", "doc_type":"usermanual", - "p_code":"71", - "code":"72" + "p_code":"74", + "code":"75" }, { - "desc":"The default installation path of the Agent is C:\\Program Files\\telescope.In the task manager, check the status of the telescope process.In the directory where the Agent ", + "desc":"This section describes how to view, start, stop, uninstall, restart, or upgrade the Agent on the Windows platform.Earlier version: The Agent is installed in the directory", "product_code":"ces", "title":"Managing the Agent (Windows)", "uri":"ces_01_0037.html", "doc_type":"usermanual", - "p_code":"71", - "code":"73" + "p_code":"74", + "code":"76" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", "product_code":"ces", - "title":"Process Monitoring", + "title":"Viewing Metrics", "uri":"ces_01_0040.html", "doc_type":"usermanual", - "p_code":"58", - "code":"74" + "p_code":"61", + "code":"77" }, { "desc":"Process monitoring is used to monitor active processes on a host. By default, the Agent collects CPU usage, memory usage, and the number of opened files of the active pro", "product_code":"ces", - "title":"Viewing Process Monitoring", + "title":"Viewing Process Monitoring Metrics", "uri":"en-us_topic_0092358859.html", "doc_type":"usermanual", - "p_code":"74", - "code":"75" + "p_code":"77", + "code":"78" }, { "desc":"This topic describes how to view server monitoring metrics, including fine-grained OS metrics collected by the Agent and basic ECS metrics.For details, see Services Inter", @@ -680,17 +707,17 @@ "title":"Viewing Server Monitoring Metrics", "uri":"en-us_topic_0079332017.html", "doc_type":"usermanual", - "p_code":"58", - "code":"76" + "p_code":"77", + "code":"79" }, { - "desc":"This topic describes how to create an alarm rule for an ECS or BMS.Log in to the management console.In the upper left corner, select a region and project.Click Service Li", + "desc":"This topic describes how to create an alarm rule for an ECS or BMS.Log in to the management console.In the upper left corner, select a region and project.Choose Service L", "product_code":"ces", "title":"Creating an Alarm Rule to Monitor a Server", "uri":"ces_01_0042.html", "doc_type":"usermanual", - "p_code":"58", - "code":"77" + "p_code":"61", + "code":"80" }, { "desc":"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 Ey", @@ -699,7 +726,7 @@ "uri":"en-us_topic_0094279601.html", "doc_type":"usermanual", "p_code":"", - "code":"78" + "code":"81" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -708,7 +735,7 @@ "uri":"ces_01_0050.html", "doc_type":"usermanual", "p_code":"", - "code":"79" + "code":"82" }, { "desc":"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 alar", @@ -716,35 +743,44 @@ "title":"Introduction to Event Monitoring", "uri":"en-us_topic_0109974074.html", "doc_type":"usermanual", - "p_code":"79", - "code":"80" + "p_code":"82", + "code":"83" }, { - "desc":"This topic describes how to view the event monitoring data.Log in to the management console.Click Service List in the upper left corner and select Cloud Eye.In the naviga", + "desc":"This topic describes how to view the event monitoring data.Log in to the management console.Choose Service List > Cloud Eye.In the navigation pane on the left, choose Eve", "product_code":"ces", "title":"Viewing Event Monitoring Data", "uri":"ces_01_0051.html", "doc_type":"usermanual", - "p_code":"79", - "code":"81" + "p_code":"82", + "code":"84" }, { - "desc":"This topic describes how to create an alarm rule to monitor an event.Log in to the management console.Click Service List in the upper left corner and select Cloud Eye.In ", + "desc":"This topic describes how to create an alarm rule to monitor an event.Log in to the management console.Choose Service List > Cloud Eye.In the navigation pane on the left, ", "product_code":"ces", "title":"Creating an Alarm Rule to Monitor an Event", "uri":"ces_01_0052.html", "doc_type":"usermanual", - "p_code":"79", - "code":"82" + "p_code":"82", + "code":"85" }, { - "desc":"Events in Event Monitoring come from operations on cloud service resources and are not collected by the Agent in Server Monitoring.Once a physical host running ECSs break", + "desc":"Events in Event Monitoring come from operations on cloud service resources and are not collected by the Agent in Server Monitoring.The name of a resource that supports ev", "product_code":"ces", "title":"Events Supported by Event Monitoring", "uri":"ces_01_0054.html", "doc_type":"usermanual", - "p_code":"79", - "code":"83" + "p_code":"82", + "code":"86" + }, + { + "desc":"On the Task Center page, you can export data including monitoring data and alarm records. You can go to the Alarm Records and Server Monitoring (Elastic Cloud Server) pag", + "product_code":"ces", + "title":"Task Center", + "uri":"ces_01_0108.html", + "doc_type":"usermanual", + "p_code":"", + "code":"87" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -753,7 +789,7 @@ "uri":"ces_01_0055.html", "doc_type":"usermanual", "p_code":"", - "code":"84" + "code":"88" }, { "desc":"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 accoun", @@ -761,17 +797,17 @@ "title":"Adding a Dump Task", "uri":"ces_01_0056.html", "doc_type":"usermanual", - "p_code":"84", - "code":"85" + "p_code":"88", + "code":"89" }, { - "desc":"This topic describes how to modify, disable, enable, or delete a dump task.Log in to the management console.Click Service List in the upper left corner and select Cloud E", + "desc":"This topic describes how to modify, disable, enable, or delete a dump task.Log in to the management console.Choose Service List > Cloud Eye.In the navigation pane, choose", "product_code":"ces", "title":"Modifying, Deleting, Enabling, or Disabling Dump Tasks", "uri":"ces_01_0057.html", "doc_type":"usermanual", - "p_code":"84", - "code":"86" + "p_code":"88", + "code":"90" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -780,7 +816,7 @@ "uri":"ces_01_0064.html", "doc_type":"usermanual", "p_code":"", - "code":"87" + "code":"91" }, { "desc":"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 Cl", @@ -788,44 +824,35 @@ "title":"Introduction to Cloud Service Monitoring", "uri":"ces_01_0109.html", "doc_type":"usermanual", - "p_code":"87", - "code":"88" + "p_code":"91", + "code":"92" }, { - "desc":"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 ", + "desc":"Log in to the management console.In the upper left corner, select a region and project.Choose Service List > Cloud Eye.In the navigation pane on the left, choose Cloud Se", "product_code":"ces", "title":"Viewing Metrics", "uri":"ces_01_0110.html", "doc_type":"usermanual", - "p_code":"87", - "code":"89" + "p_code":"91", + "code":"93" }, { - "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "desc":"Some connected cloud services may not appear in the monitoring list. If no monitoring data is reported for all instances of a cloud service for a certain period of time, ", "product_code":"ces", - "title":"Auditing Operation Records on Cloud Eye", - "uri":"ces_01_0086.html", + "title":"Cloud Services Displayed in the Cloud Service Monitoring List", + "uri":"ces_01_0160.html", "doc_type":"usermanual", - "p_code":"", - "code":"90" + "p_code":"91", + "code":"94" }, { - "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "desc":"With CTS, you can record operations associated with Cloud Eye for future query, audit, and backtracking.CTS has been enabled.For details, see Querying Real-Time Traces.", "product_code":"ces", - "title":"Key Cloud Eye Operations", + "title":"Key Cloud Eye Operations Supported by CTS", "uri":"ces_01_0087.html", "doc_type":"usermanual", - "p_code":"90", - "code":"91" - }, - { - "desc":"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 describe", - "product_code":"ces", - "title":"Viewing Cloud Eye Logs", - "uri":"ces_01_0088.html", - "doc_type":"usermanual", - "p_code":"90", - "code":"92" + "p_code":"", + "code":"95" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -834,7 +861,7 @@ "uri":"ces_01_0089.html", "doc_type":"usermanual", "p_code":"", - "code":"93" + "code":"96" }, { "desc":"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 organizatio", @@ -842,8 +869,8 @@ "title":"Creating a User and Granting Permissions", "uri":"ces_01_0090.html", "doc_type":"usermanual", - "p_code":"93", - "code":"94" + "p_code":"96", + "code":"97" }, { "desc":"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 Table 3 in .You can creat", @@ -851,8 +878,8 @@ "title":"Cloud Eye Custom Policies", "uri":"ces_01_0091.html", "doc_type":"usermanual", - "p_code":"93", - "code":"95" + "p_code":"96", + "code":"98" }, { "desc":"Quotas can limit the number or amount of resources available to users, such as the maximum number of ECS or EVS disks that can be created.If the existing resource quota c", @@ -861,16 +888,16 @@ "uri":"en-us_topic_0154940152.html", "doc_type":"usermanual", "p_code":"", - "code":"96" + "code":"99" }, { - "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", + "desc":"In addition to the preceding cloud services, the following cloud services also support event monitoring. For details about monitored events, see Events Supported by Event", "product_code":"ces", "title":"Services Interconnected with Cloud Eye", "uri":"en-us_topic_0202622212.html", "doc_type":"usermanual", "p_code":"", - "code":"97" + "code":"100" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -879,7 +906,7 @@ "uri":"en-us_topic_0084572222.html", "doc_type":"usermanual", "p_code":"", - "code":"98" + "code":"101" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -887,17 +914,17 @@ "title":"General Consulting", "uri":"index.html", "doc_type":"usermanual", - "p_code":"98", - "code":"99" + "p_code":"101", + "code":"102" }, { - "desc":"Aggregation is a process where Cloud Eye calculates the maximum, minimum, average, sum, or variance value of raw data sampled for different periods and repeats the proces", + "desc":"Rollup is a process where Cloud Eye calculates the maximum, minimum, average, sum, or variance value of raw data sampled for different periods and repeats the process for", "product_code":"ces", - "title":"What Is Aggregation?", + "title":"What Is Rollup?", "uri":"ces_faq_0009.html", "doc_type":"usermanual", - "p_code":"99", - "code":"100" + "p_code":"102", + "code":"103" }, { "desc":"Metric data includes raw data and rolled-up data.Raw data is retained for two days.Rolled-up data is data aggregated based on raw data. The retention period for rolled-up", @@ -905,26 +932,17 @@ "title":"How Long Is Metric Data Retained?", "uri":"ces_faq_0010.html", "doc_type":"usermanual", - "p_code":"99", - "code":"101" + "p_code":"102", + "code":"104" }, { - "desc":"Cloud Eye supports the following rollup methods:AverageIf Avg. is selected for Statistic, Cloud Eye calculates the average value of metrics collected within a rollup peri", + "desc":"Cloud Eye supports the following five rollup methods, among which variance has been disabled and will be removed in later versions:AverageIf Statistic is set to Avg., Clo", "product_code":"ces", "title":"How Many Rollup Methods Does Cloud Eye Support?", "uri":"ces_faq_0013.html", "doc_type":"usermanual", - "p_code":"99", - "code":"102" - }, - { - "desc":"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", - "product_code":"ces", - "title":"How Can I Export Collected Data?", - "uri":"ces_faq_0012.html", - "doc_type":"usermanual", - "p_code":"99", - "code":"103" + "p_code":"102", + "code":"105" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -932,17 +950,8 @@ "title":"Server Monitoring", "uri":"ces_faq_0059.html", "doc_type":"usermanual", - "p_code":"98", - "code":"104" - }, - { - "desc":"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", - "product_code":"ces", - "title":"How Can I Quickly Restore the Agent Configuration?", - "uri":"ces_faq_0027.html", - "doc_type":"usermanual", - "p_code":"104", - "code":"105" + "p_code":"101", + "code":"106" }, { "desc":"The Agent was installed on a BMS, but the BMS is listed on the Server Monitoring > Elastic Cloud Server page on the Cloud Eye console.The Agent determines whether a serve", @@ -950,8 +959,17 @@ "title":"Why Is a BMS with the Agent Installed Displayed in the ECS List on the Server Monitoring Page?", "uri":"ces_faq_0053.html", "doc_type":"usermanual", - "p_code":"104", - "code":"106" + "p_code":"106", + "code":"107" + }, + { + "desc":"The following table lists OSs compatible with the Agent. More OSs will be supported soon.Using the OSs or versions that have not been verified may adversely affect your s", + "product_code":"ces", + "title":"What OSs Does the Agent Support?", + "uri":"ces_faq_0024.html", + "doc_type":"usermanual", + "p_code":"106", + "code":"108" }, { "desc":"Cloud Eye Agent uses HTTP requests to report data. Any port in the range obtained from path /proc/sys/net/ipv4/ip_local_port_range may be occupied. If any service port is", @@ -959,8 +977,17 @@ "title":"What Should I Do If the Service Port Is Used by the Agent?", "uri":"ces_faq_0037.html", "doc_type":"usermanual", - "p_code":"104", - "code":"107" + "p_code":"106", + "code":"109" + }, + { + "desc":"To enable you to monitor servers more securely and efficiently, Cloud Eye provides the latest Agent permission-granting method. That is, before installing Agents, you onl", + "product_code":"ces", + "title":"How Do I Configure an Agency?", + "uri":"ces_faq_2502.html", + "doc_type":"usermanual", + "p_code":"106", + "code":"110" }, { "desc":"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.Log in to the management co", @@ -968,17 +995,17 @@ "title":"How Can I Create an Agency?", "uri":"ces_faq_0028.html", "doc_type":"usermanual", - "p_code":"104", - "code":"108" + "p_code":"106", + "code":"111" }, { - "desc":"It may be that your quota is used up. If this is the case, you can delete unneeded agencies first or increase the agency quota. Then you can use the agency to restore the", + "desc":"Your quota may be used up. In this case, you can delete unneeded agencies first or request a higher agency quota. Then you can use the agency to restore the Agent configu", "product_code":"ces", - "title":"What Can't I Create Another Agency?", + "title":"Why Can't I Create Another Agency?", "uri":"ces_faq_0032.html", "doc_type":"usermanual", - "p_code":"104", - "code":"109" + "p_code":"106", + "code":"112" }, { "desc":"When the Agent configuration is being restored, agency CESAgentAutoConfigAgency will be automatically created, but if you have created such an agency but not for the ECS ", @@ -986,8 +1013,8 @@ "title":"What Should I Do If Agency CESAgentAutoConfigAgency Failed to Be Automatically Created?", "uri":"ces_faq_0033.html", "doc_type":"usermanual", - "p_code":"104", - "code":"110" + "p_code":"106", + "code":"113" }, { "desc":"An invalid agency is an agency that has expired. If you set the agencyValidity Period to Unlimited, the agency will become valid again. For details, see How Can I Create ", @@ -995,8 +1022,8 @@ "title":"What Can I Do If Agency CESAgentAutoConfigAgency Is Invalid?", "uri":"ces_faq_0030.html", "doc_type":"usermanual", - "p_code":"104", - "code":"111" + "p_code":"106", + "code":"114" }, { "desc":"The Agent uses very minimal system resources and it has almost no impact on the server performance.On an ECS, the Agent uses less than 5% of the CPU capacity and less tha", @@ -1004,8 +1031,8 @@ "title":"Will the Agent Affect the Server Performance?", "uri":"ces_faq_0071.html", "doc_type":"usermanual", - "p_code":"104", - "code":"112" + "p_code":"106", + "code":"115" }, { "desc":"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 Sta", @@ -1013,8 +1040,53 @@ "title":"What Should I Do If the Agent Status Is Faulty?", "uri":"ces_faq_0025.html", "doc_type":"usermanual", - "p_code":"104", - "code":"113" + "p_code":"106", + "code":"116" + }, + { + "desc":"This following describes how to enable or disable metric collection by modifying the configuration file.This operation applies only to Agent 2.7.2 or later.Log in to a se", + "product_code":"ces", + "title":"How Do I Enable or Disable Metric Collection by Modifying the Configuration File?", + "uri":"ces_faq_0126.html", + "doc_type":"usermanual", + "p_code":"106", + "code":"117" + }, + { + "desc":"This section describes how to modify the configuration file to change the Agent resource usage threshold.This operation applies only to Agent 2.7.2 or later.ProcedureUse ", + "product_code":"ces", + "title":"How Do I Change the Agent Resource Usage Threshold by Modifying the Configuration File?", + "uri":"ces_faq_0127.html", + "doc_type":"usermanual", + "p_code":"106", + "code":"118" + }, + { + "desc":"The following describes how to modify the configuration file to change the process collection frequency.This operation applies only to Agent 2.7.2 or later.Enter the foll", + "product_code":"ces", + "title":"How Do I Change the Process Collection Frequency by Modifying the Configuration File?", + "uri":"ces_faq_0128.html", + "doc_type":"usermanual", + "p_code":"106", + "code":"119" + }, + { + "desc":"The Monitoring Period (Raw Data) of the agent metrics is 1 minute.Currently, CES Agent can collect only physical disk metrics and does not support disks mounted using the", + "product_code":"ces", + "title":"What Metrics Are Supported by the Agent?", + "uri":"ces_faq_2513.html", + "doc_type":"usermanual", + "p_code":"106", + "code":"120" + }, + { + "desc":"When the Agent installation command provided by the Cloud Eye console is used to batch install the Agent, the error message \"SSH dial error\" was displayed. As a result, t", + "product_code":"ces", + "title":"How Can I Fix the \"SSH dial error\" During Batch Agent Installation?", + "uri":"ces_faq_2514.html", + "doc_type":"usermanual", + "p_code":"106", + "code":"121" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1022,8 +1094,8 @@ "title":"Alarm Notifications or False Alarms", "uri":"ces_faq_0060.html", "doc_type":"usermanual", - "p_code":"98", - "code":"114" + "p_code":"101", + "code":"122" }, { "desc":"Alarm notifications are emails, SMS messages, or HTTP/HTTPS messages that are sent out when an alarm status is Alarm, OK, or both.You can configure Cloud Eye to send or n", @@ -1031,8 +1103,8 @@ "title":"What Is an Alarm Notification? How Many Types of Alarm Notifications Are There?", "uri":"ces_faq_0006.html", "doc_type":"usermanual", - "p_code":"114", - "code":"115" + "p_code":"122", + "code":"123" }, { "desc":"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 clea", @@ -1040,8 +1112,8 @@ "title":"What Alarm Status Does Cloud Eye Support?", "uri":"ces_faq_0004.html", "doc_type":"usermanual", - "p_code":"114", - "code":"116" + "p_code":"122", + "code":"124" }, { "desc":"There are four levels of alarm severity: critical, major, minor, and informational.Critical: An emergency fault has occurred and services are affected.Major: A relatively", @@ -1049,8 +1121,8 @@ "title":"What Alarm Severities Does Cloud Eye Support?", "uri":"ces_faq_0043.html", "doc_type":"usermanual", - "p_code":"114", - "code":"117" + "p_code":"122", + "code":"125" }, { "desc":"When monitoring data of a metric is not reported to Cloud Eye for three consecutive hours, the alarm rule status changes to Insufficient data.In special cases, if monitor", @@ -1058,8 +1130,8 @@ "title":"When Will an \"Insufficient data\" Alarm Be Triggered?", "uri":"ces_faq_0017.html", "doc_type":"usermanual", - "p_code":"114", - "code":"118" + "p_code":"122", + "code":"126" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1067,8 +1139,8 @@ "title":"Monitored Data Exceptions", "uri":"ces_faq_0062.html", "doc_type":"usermanual", - "p_code":"98", - "code":"119" + "p_code":"101", + "code":"127" }, { "desc":"Possible causes are as follows:The cloud service is not interconnected with Cloud Eye. To check whether a cloud service has been interconnected with Cloud Eye, see Servic", @@ -1076,8 +1148,8 @@ "title":"Why Is the Monitoring Data Not Displayed on the Cloud Eye Console?", "uri":"ces_faq_0045.html", "doc_type":"usermanual", - "p_code":"119", - "code":"120" + "p_code":"127", + "code":"128" }, { "desc":"Because the sampling period in Cloud Eye is different from that of the metric monitoring tool in ECS.Cloud Eye collects ECS and EVS disk data every 4 minutes (5 minutes f", @@ -1085,17 +1157,8 @@ "title":"Why Are the Network Traffic Metric Values in Cloud Eye Different from Those Detected in ECS?", "uri":"ces_faq_0008.html", "doc_type":"usermanual", - "p_code":"119", - "code":"121" - }, - { - "desc":"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, dis", - "product_code":"ces", - "title":"What Are the Impacts on ECS Metrics If OTC Tools Are Not Installed on ECSs?", - "uri":"ces_faq_0011.html", - "doc_type":"usermanual", - "p_code":"119", - "code":"122" + "p_code":"127", + "code":"129" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1103,8 +1166,8 @@ "title":"User Permissions", "uri":"ces_faq_0064.html", "doc_type":"usermanual", - "p_code":"98", - "code":"123" + "p_code":"101", + "code":"130" }, { "desc":"To use server monitoring, IAM users in a user group must have the Security Administrator permissions. If they do not have the permissions, a message indicating abnormal p", @@ -1112,8 +1175,17 @@ "title":"What Should I Do If the IAM User Permissions Are Abnormal?", "uri":"ces_faq_0031.html", "doc_type":"usermanual", - "p_code":"123", - "code":"124" + "p_code":"130", + "code":"131" + }, + { + "desc":"When an IAM user clicked Configure on the Server Monitoring page, a message indicating insufficient permissions was displayed.The IAM agency permissions are not configure", + "product_code":"ces", + "title":"What Can I Do If the System Displays a Message Indicating Insufficient Permissions When I Click Configure on the Server Monitoring Page?", + "uri":"ces_faq_0072.html", + "doc_type":"usermanual", + "p_code":"130", + "code":"132" }, { "desc":"HUAWEI CLOUD Help Center presents technical documents to help you quickly get started with HUAWEI CLOUD services. The technical documents include Service Overview, Price Details, Purchase Guide, User Guide, API Reference, Best Practices, FAQs, and Videos.", @@ -1122,6 +1194,6 @@ "uri":"ces_01_0097.html", "doc_type":"usermanual", "p_code":"", - "code":"125" + "code":"133" } ] \ No newline at end of file diff --git a/docs/ces/umn/ces_01_0004.html b/docs/ces/umn/ces_01_0004.html index 0795b8235..af6edeb39 100644 --- a/docs/ces/umn/ces_01_0004.html +++ b/docs/ces/umn/ces_01_0004.html @@ -9,14 +9,12 @@
  • Installing the Agent on a Linux Server
    • -
  • Restoring the Agent Configurations on a Linux Server
    -
    • -
  • (Optional) Manually Configuring the Agent (Linux)
    +
  • (Optional) Manually Configuring the Agent on a Linux Server
    • -
    Parent topic: Server Monitoring
    +
    Parent topic: Agent Installation and Configuration
    diff --git a/docs/ces/umn/ces_01_0005.html b/docs/ces/umn/ces_01_0005.html index 40f4a1e18..13d03da78 100644 --- a/docs/ces/umn/ces_01_0005.html +++ b/docs/ces/umn/ces_01_0005.html @@ -7,14 +7,14 @@
    -
    Parent topic: Server Monitoring
    +
    Parent topic: Agent Installation and Configuration
    diff --git a/docs/ces/umn/ces_01_0011-A.html b/docs/ces/umn/ces_01_0011-A.html new file mode 100644 index 000000000..b637953fd --- /dev/null +++ b/docs/ces/umn/ces_01_0011-A.html @@ -0,0 +1,19 @@ + + +

    Creating a Dashboard

    +

    You can create a dashboard to monitor metrics. Before adding graphs, you need to create a dashboard first.

    +

    Constraints

    You can create a maximum of 10 dashboards.

    +
    +

    Procedure

    1. Log in to the management console.
    2. In the upper left corner, select a region and project.
    3. Choose Service List > Cloud Eye.
    1. Choose My Dashboards and click Create Dashboard.

      The Create Dashboard dialog box is displayed.

      +
    2. Configure the following parameters:
      • Name: Enter a maximum of 128 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.
      • Enterprise Project: Select an enterprise project to be associated with the dashboard. Only users who have all permissions for the selected enterprise project can manage the dashboard.

        Enterprise Project is available only in certain regions.

        +
        +
      +
    3. Click OK.
    +
    +
    +
    +
    +
    Parent topic: My Dashboards
    +
    +
    + diff --git a/docs/ces/umn/ces_01_0011.html b/docs/ces/umn/ces_01_0011.html deleted file mode 100644 index 0e8759e9e..000000000 --- a/docs/ces/umn/ces_01_0011.html +++ /dev/null @@ -1,17 +0,0 @@ - - -

    Creating a Dashboard

    -

    You must create a dashboard before you add graphs. You can create a maximum of 20 dashboards.

    -

    Procedure

    1. Log in to the management console.
    2. In the upper left corner, select a region and project.
    3. Click Service List in the upper left corner and select Cloud Eye.
    4. In the navigation pane on the left, choose Dashboard. Click Create Dashboard in the upper right corner.

      The Create Dashboard dialog box is displayed.

      -
    5. 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.

        -
        -
      -
    6. Click OK.
    -
    -
    -
    -
    -
    Parent topic: Dashboards
    -
    -
    - diff --git a/docs/ces/umn/ces_01_0012-A.html b/docs/ces/umn/ces_01_0012-A.html new file mode 100644 index 000000000..c089c36b7 --- /dev/null +++ b/docs/ces/umn/ces_01_0012-A.html @@ -0,0 +1,52 @@ + + +

    Adding a Graph

    +

    If you are using multiple cloud services, you can add their metrics to the same dashboard by creating graphs. This way, you can view global monitoring data of these cloud services.

    +

    In the same graph, you can compare data across services, dimensions, and metrics.

    +

    Constraints

    +
    +

    Prerequisites

    You have created a dashboard by referring to Creating a Dashboard.

    +
    +

    Procedure

    1. Log in to the management console.
    2. In the upper left corner, select a region and project.
    3. Choose Service List > Cloud Eye.
    1. Choose My Dashboards and click the name of the dashboard to which you want to add a graph. On the displayed page, click Add Graph. You can select Line Chart or Bar Chart to display the graph.
      • Line Chart: The chart visualizes changes and peak values of metrics over time.
      • Bar Chart: The chart visualizes the metric data of top-ranked resources of the same type.
      +
      +
    2. On the Add Graph page, set parameters as prompted. +
      + + + + + + + + + + + + + + + + +
      Table 1 Parameters for adding a graph

      Parameter

      +

      Description

      +

      Metric Display

      +
      • For a line graph, you can select One graph for a single metric or One graph for multiple metrics.
      • For a bar chart, only One graph for a single metric is available.
      +

      Monitoring Scope

      +

      Select the target resources and metrics. If you selected a bar chart, all resources are selected by default.

      +
      NOTE:

      If an instance does not report monitoring data for a specified period, the instance will not appear in the resource list. For details about the data retention period, see Cloud Services Displayed in the Cloud Service Monitoring List.

      +
      +

      Quantity

      +

      When creating a bar chart, you can configure how many resources to show (3 ≤ N ≤ 10). Metric data of those resources is displayed, in an ascending or descending order.

      +

      Advanced Settings

      +

      You can configure the name, threshold, and legend name of a graph.

      +
      +
      +
    3. Click Save.
    +
    +
    +
    +
    +
    Parent topic: My Dashboards
    +
    +
    + diff --git a/docs/ces/umn/ces_01_0012.html b/docs/ces/umn/ces_01_0012.html deleted file mode 100644 index eb12c5d8c..000000000 --- a/docs/ces/umn/ces_01_0012.html +++ /dev/null @@ -1,61 +0,0 @@ - - -

    Adding a Graph

    -

    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

    1. Log in to the management console.
    2. In the upper left corner, select a region and project.
    3. Click Service List in the upper left corner and select Cloud Eye.
    1. 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.

      -
    2. Configure parameters based on Table 1. -
      - - - - - - - - - - - - - - - - - - - - - - -
      Table 1 Parameters

      Parameter

      -

      Description

      -

      Title

      -

      Specifies the title of the graph to be added. Only letters, digits, underscores (_), and hyphens (-) are allowed. Enter a maximum of 128 characters.

      -

      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.

      -

      Example value: Elastic Cloud Server

      -

      Dimension

      -

      Specifies the metric dimension.

      -

      Example value: ECSs

      -

      Monitored Object

      -

      Specifies the monitored object. You can add up to 50 monitored objects.

      -

      You can select multiple monitored objects at a time.

      -

      Metric

      -

      Specifies the metric name.

      -

      Example value: CPU Usage

      -
      -
      -
    3. 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.

      -
    -
    -
    -
    -
    -
    Parent topic: Dashboards
    -
    -
    - diff --git a/docs/ces/umn/ces_01_0013.html b/docs/ces/umn/ces_01_0013.html deleted file mode 100644 index 7f50212a0..000000000 --- a/docs/ces/umn/ces_01_0013.html +++ /dev/null @@ -1,32 +0,0 @@ - - -

    Viewing a Graph

    -

    After you add a graph, you can view the metric trends on the Dashboards page. The system provides you both default and custom time ranges to view trends from last month. This topic describes how to view trends for a longer time range.

    -

    Procedure

    1. Log in to the management console.
    2. In the upper left corner, select a region and project.
    3. Click Service List in the upper left corner and select Cloud Eye.
    4. In the navigation pane, 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.
      -
      -
      -
    5. 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.

    - -
    -

    Customizing a Period to View the Graph

    By default, metrics in the last 1 hour, last 3 hours, last 12 hours, last 1 day, last 7 days, and last 30 days are displayed. If you want to view metrics in the last 2 hours or a customized time range, you can drag the mouse to select the time range you want to view on the X axis.

    - -
    -

    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.

    - -
    -
    -
    -
    -
    Parent topic: Dashboards
    -
    -
    - diff --git a/docs/ces/umn/ces_01_0014-A.html b/docs/ces/umn/ces_01_0014-A.html new file mode 100644 index 000000000..a4a55dd9e --- /dev/null +++ b/docs/ces/umn/ces_01_0014-A.html @@ -0,0 +1,25 @@ + + +

    Configuring a Graph

    +

    If the existing metrics do not meet your requirements, you can add, modify, and delete metrics on a line chart and a bar chart.

    +

    Procedure for Configuring Line Charts

    1. Log in to the management console.
    2. In the upper left corner, select a region and project.
    3. Choose Service List > Cloud Eye.
    1. In the navigation pane, choose My Dashboards.
    2. Locate the dashboard for which you want to configure a graph and click its name.
    3. Click to copy, delete, or edit, the graph, or change its legend name.
      1. To copy a graph, locate the graph and click Copy. In the displayed dialog box, set parameters.
        • Copying a graph to the current dashboard: Set From to Current Dashboard, set Graph Name, and click OK.
        • Copying a graph to another dashboard: Set From to Other dashboards. Set Enterprise Project, Target Dashboard, and Graph Name. Then, click OK.
        +
      2. To edit a graph, locate the graph and click Edit. On the displayed page, modify Monitoring Scope and Advanced Settings.
      3. To change the legend name, click Change Legend Name. In the displayed dialog box, enter a legend name in the Legend column and click OK.
      +

      +
      Figure 1 Managing a graph
      +

      +
    +
    +

    Procedure for Configuring Bar Charts

    1. Log in to the management console.
    2. In the upper left corner, select a region and project.
    3. Choose Service List > Cloud Eye.
    1. In the navigation pane, choose My Dashboards.
    2. Locate the dashboard for which you want to configure a graph and click its name.
    1. Click to configure Quantity and Sorting Order.

      +
      Figure 2 Sorting metrics
      +
    1. Click to copy, edit, or delete the graph.
      1. To copy a graph, locate the graph and click Copy. In the displayed dialog box, set parameters.
        • Copying a graph to the current dashboard: Set From to Current Dashboard, set Graph Name, and click OK.
        • Copying a graph to another dashboard: Set From to Other dashboards. Set Enterprise Project, Target Dashboard, and Graph Name. Then, click OK.
        +
      2. To edit a graph, locate the graph and click Edit. On the displayed page, modify Monitoring Scope, Quantity, and Advanced Settings.
      +

      +
    +
    +
    +
    +
    +
    Parent topic: My Dashboards
    +
    +
    + diff --git a/docs/ces/umn/ces_01_0014.html b/docs/ces/umn/ces_01_0014.html deleted file mode 100644 index 84d3f7698..000000000 --- a/docs/ces/umn/ces_01_0014.html +++ /dev/null @@ -1,17 +0,0 @@ - - -

    Configure Graph

    -

    This topic describes how to add, modify, and delete metrics on graphs.

    -

    Procedure

    1. Log in to the management console.
    2. In the upper left corner, select a region and project.
    3. Click Service List in the upper left corner and select Cloud Eye.
    4. 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.

      -
      -
    -
    -
    -
    -
    -
    Parent topic: Dashboards
    -
    -
    - diff --git a/docs/ces/umn/ces_01_0015.html b/docs/ces/umn/ces_01_0015.html deleted file mode 100644 index cb0c24397..000000000 --- a/docs/ces/umn/ces_01_0015.html +++ /dev/null @@ -1,11 +0,0 @@ - - -

    Deleting a Graph

    -
    1. Log in to the management console.
    2. In the upper left corner, select a region and project.
    3. Click Service List in the upper left corner and select Cloud Eye.
    4. In the navigation pane on the left, choose Dashboard.
    5. Select the dashboard from which you want to delete a graph.
    6. Hover your mouse on the graph and click the trash icon in the upper right corner.
    7. In the displayed Delete Graph dialog box, click Yes.
    -
    -
    -
    -
    Parent topic: Dashboards
    -
    -
    - diff --git a/docs/ces/umn/ces_01_0016.html b/docs/ces/umn/ces_01_0016.html deleted file mode 100644 index d5592a8a3..000000000 --- a/docs/ces/umn/ces_01_0016.html +++ /dev/null @@ -1,13 +0,0 @@ - - -

    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

    1. Log in to the management console.
    2. In the upper left corner, select a region and project.
    3. Click Service List in the upper left corner and select Cloud Eye.
    4. In the navigation pane on the left, choose Dashboard.
    5. Select the dashboard.
    6. Click Delete.
    7. In the displayed Delete Dashboard dialog box, click Yes.
    -
    -
    -
    -
    -
    Parent topic: Dashboards
    -
    -
    - diff --git a/docs/ces/umn/ces_01_0017.html b/docs/ces/umn/ces_01_0017.html index 8fb4fbf93..6e8da1024 100644 --- a/docs/ces/umn/ces_01_0017.html +++ b/docs/ces/umn/ces_01_0017.html @@ -1,13 +1,13 @@

    Creating a Resource Group

    -

    Scenarios

    If you use multiple cloud services, you can add all related resources, such as ECSs, BMSs, EVS disks, elastic IP addresses, bandwidths, and databases to the same resource group for easier management and O&M.

    +

    Scenarios

    If you use multiple cloud services, you can add all related resources, such as ECSs, BMSs, EVS disks, EIPs, bandwidths, and databases to the same resource group for easier management and O&M.

    -

    Restrictions

    • Each user can create up to 1,000 resource groups.
    • A resource group can 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.
    +

    Constraints

    • Each user can create up to 1,000 resource groups.
    • A resource group can 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

    1. Log in to the management console.
    2. In the upper left corner, select a region and project.
    3. Click Service List in the upper left corner and select Cloud Eye.
    4. In the navigation pane on the left, choose Resource Groups.
    5. In the upper right corner, click Create Resource Group.
      Figure 1 Creating a resource group
      -
    6. Enter a group name, select the cloud service resources to be added, and optionally set 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 resources, you can search by name, ID, or tag.

      +

      Procedure

      1. Log in to the management console.
      1. In the upper left corner, select a region and project.
      2. Choose Service List > Cloud Eye.
      3. In the navigation pane on the left, choose Resource Groups.
      4. In the upper right corner, click Create Resource Group.
        Figure 1 Creating a resource group
        +
      1. Enter a group name, select the cloud service resources to be added, and optionally set Enterprise Project.
        You are advised to associate an enterprise project. After an enterprise project is associated, adding or removing resources from the enterprise project will automatically update the resource group. This setup streamlines maintenance if you often add or delete resources.
        Figure 2 Selecting cloud service resources
        +

        You can search for ECSs and BMSs by name, ID, or private IP address. For other cloud resources, you can search by name, ID, or tag.

      2. Click Create.
      diff --git a/docs/ces/umn/ces_01_0019.html b/docs/ces/umn/ces_01_0019.html index f0b44fd97..7627aee08 100644 --- a/docs/ces/umn/ces_01_0019.html +++ b/docs/ces/umn/ces_01_0019.html @@ -2,59 +2,63 @@

      Resource Group List

      The resource group list displays all resource groups you have on Cloud Eye, the resources they contain, and the health status of each resource group.

      -

      Procedure

      1. Log in to the management console.
      2. In the upper left corner, select a region and project.
      3. Click Service List in the upper left corner and select Cloud Eye.
      4. 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

        +

        Procedure

        1. Log in to the management console.
        1. In the upper left corner, select a region and project.
        2. Choose Service List > Cloud Eye.
        3. In the navigation pane, choose Resource Groups.
        4. 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

          +

          Description

          Name/ID

          +

          Name/ID

          Specifies the resource group name and ID.

          +

          Specifies the resource group name and ID.

          NOTE:

          The group name can contain a maximum of 128 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.

          Alarm Status

          +

          Status (Metric Monitoring)

          • 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.
          +
          • 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.

          Resources (Alarm/Total)

          +

          Resources (Alarm/Total)

          Total number of resources that are generating alarms in a group/Total number of resources in the group.

          +

          Total number of resources that are generating alarms in a group/Total number of resources in the group.

          Resource Types

          +

          Resource Types

          Specifies the number of different resource types in a group. For example, if there are two ECSs and one EVS disk in a resource group, then there are two types of resources and Resource Types is 2.

          +

          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.

          (Optional) Enterprise Project

          +

          (Optional) Enterprise Project

          Specifies the name of the enterprise project that has the resource group permission.

          +

          Specifies the name of the enterprise project that has the resource group permission.

          Add Resources

          +

          Add Resources

          Specifies how you add resources to a resource group. Only Manually is supported.

          +

          Specifies how you add resources to a resource group. Only Manually is supported.

          Created

          +

          Synchronize Resources

          Specifies the time when the resource group was created.

          +

          You can add all resources in an enterprise project or resources with the same tags to a resource group. If Add Resources is set to Manually, this parameter is not required.

          Operation

          +

          Created

          You can create alarm rules or delete a resource group.

          +

          Specifies the time when the resource group was created.

          +

          Operation

          +

          You can create alarm rules or delete a resource group.
          -
        diff --git a/docs/ces/umn/ces_01_0020.html b/docs/ces/umn/ces_01_0020.html index 859e345a5..b248eea0c 100644 --- a/docs/ces/umn/ces_01_0020.html +++ b/docs/ces/umn/ces_01_0020.html @@ -2,9 +2,9 @@

        Resource Overview

        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

        1. Log in to the management console.
        2. In the upper left corner, select a region and project.
        3. Click Service List in the upper left corner and select Cloud Eye.
        4. In the navigation pane on the left, choose Resource Groups.
        5. 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.

          +

          Procedure

          1. Log in to the management console.
          1. In the upper left corner, select a region and project.
          2. Choose Service List > Cloud Eye.
          3. In the navigation pane on the left, choose Resource Groups.
          4. 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_0022.html b/docs/ces/umn/ces_01_0022.html index 2282fd46b..dd3bf649f 100644 --- a/docs/ces/umn/ces_01_0022.html +++ b/docs/ces/umn/ces_01_0022.html @@ -2,9 +2,12 @@

        Alarm Rules

        The Alarm Rules page displays all alarm rules in a resource group. You can enable, disable, modify, or delete an alarm rule.

        -

        Procedure

        1. Log in to the management console.
        2. In the upper left corner, select a region and project.
        3. Click Service List in the upper left corner and select Cloud Eye.
        4. In the navigation pane on the left, choose Resource Groups.
        5. Click a resource group name to go to the Resource Overview page.
        6. 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
          +

          Procedure

          1. Log in to the management console.
          1. In the upper left corner, select a region and project.
          2. Choose Service List > Cloud Eye.
          3. In the navigation pane on the left, choose Resource Groups.
          4. Click a resource group name to go to the Resource Overview page.
          5. In the navigation pane, 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.

          +

          For event alarm rules, you can set the monitoring scope to Resource groups only when the event source is DDS, RDS, or DCS.

          +
          +
          Figure 1 Managing alarm rules in a resource group
          -
        diff --git a/docs/ces/umn/ces_01_0025.html b/docs/ces/umn/ces_01_0025.html index aaf9cb5a5..ce40d0e16 100644 --- a/docs/ces/umn/ces_01_0025.html +++ b/docs/ces/umn/ces_01_0025.html @@ -2,7 +2,7 @@

        Modifying a Resource Group

        When you need to add resources to or delete resources from a resource group, modify the resource group.

        -

        Procedure

        1. Log in to the management console.
        2. In the upper left corner, select a region and project.
        3. Click Service List in the upper left corner and select Cloud Eye.
        4. In the navigation pane on the left, choose Resource Groups.
        5. Click a resource group name to go to the Resource Overview page
          • Adding resources: Click to add resources.
          • Removing resources: In the resource list, select the resource to be removed and click Remove in the Operation column.
          +

          Procedure

          1. Log in to the management console.
          2. In the upper left corner, select a region and project.
          3. Choose Service List > Cloud Eye.
          4. In the navigation pane on the left, choose Resource Groups.
          5. Click a resource group name to go to the Resource Overview page
            • Adding resources: Click Add Resources to 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 32b1aebd2..c6588b737 100644 --- a/docs/ces/umn/ces_01_0026.html +++ b/docs/ces/umn/ces_01_0026.html @@ -1,8 +1,8 @@

        Deleting a Resource Group

        -

        Procedure

        1. Log in to the management console.
        2. In the upper left corner, select a region and project.
        3. Click Service List in the upper left corner and select Cloud Eye.
        4. In the navigation pane on the left, choose Resource Groups.
        5. Locate the resource group and click Delete in the Operation column.
          Figure 1 Deleting a resource group
          -
        6. In the displayed Delete Resource Group dialog box, click OK.
        +

        Procedure

        1. Log in to the management console.
        1. In the upper left corner, select a region and project.
        2. Choose Service List > Cloud Eye.
        3. In the navigation pane on the left, choose Resource Groups.
        4. Locate the resource group and click Delete in the Operation column.
          Figure 1 Deleting a resource group
          +
        5. In the displayed Delete Resource Group dialog box, click OK.
        diff --git a/docs/ces/umn/ces_01_0027.html b/docs/ces/umn/ces_01_0027.html index 26701ecfe..c0e63d922 100644 --- a/docs/ces/umn/ces_01_0027.html +++ b/docs/ces/umn/ces_01_0027.html @@ -36,9 +36,18 @@

        Agent installation and configuration description:

        -
        • To successfully install the Agent, ensure that both DNS and security group rules are correctly configured.
        • After you install the Agent, you can click Restore Agent Configurations on the Cloud Eye console to complete the agency and Agent configuration.
        • If the Agent fails to be configured by clicking Restore Agent Configurations or due to other reasons, manually configure it.
        +
        • To successfully install the Agent, ensure that both DNS and security group rules are correctly configured.
        • Before installing the Agent, you only need to click Configure on the Server Monitoring page of the Cloud Eye console, or select cesgency for Agency in Advanced Options when buying an ECS. Cloud Eye automatically performs a temporary AK/SK authorization for the Agent installed on the ECS or BMS in the region. And in the future, the newly created servers in this region will automatically get this authorization. After the configuration is completed, the Agent configurations of all servers in these regions are restored by default.
        • If the Agent fails to be configured by clicking Configure or due to other reasons, manually configure it. For details, see (Optional) Manually Configuring the Agent on a Linux Server or (Optional) Manually Configuring the Agent on a Windows Server.
        • Not every Operating System is supported. For details about which Windows and Linux OSs are supported, see What OSs Does the Agent Support?
        + +
        Parent topic: Server Monitoring
        diff --git a/docs/ces/umn/ces_01_0029.html b/docs/ces/umn/ces_01_0029.html index 4f899e712..97f908a83 100644 --- a/docs/ces/umn/ces_01_0029.html +++ b/docs/ces/umn/ces_01_0029.html @@ -1,23 +1,20 @@

        Installing the Agent on a Linux Server

        -

        Scenarios

        This section describes how to manually install the Agent on a Linux ECS or BMS.

        +

        Scenarios

        This topic describes how to manually install the Agent on a Linux ECS or BMS.

        -

        Prerequisites

        +

        Constraints

        Some OSs are not supported. For details about which Linux OSs are supported, see What OSs Does the Agent Support?

        -

        Procedure

        1. Log in to the ECS or BMS as user root.
        2. Install the Agent.
          EU DE:
          • x86_64
            cd /usr/local && wget --no-check-certificate https://telescope-eu-de.obs.eu-de.otc.t-systems.com/scripts/agentInstall.sh && chmod 755 agentInstall.sh && ./agentInstall.sh
            -
          • Arm 64
            cd /usr/local && wget --no-check-certificate https://telescope-eu-de.obs.eu-de.otc.t-systems.com/scripts/agentInstallARM.sh && chmod 755 agentInstallARM.sh && ./agentInstallARM.sh
            -
          +

          Prerequisites

          -
          EU NL:
          • x86_64
            cd /usr/local && wget --no-check-certificate https://telescope-eu-nl.obs.eu-nl.otc.t-systems.com/scripts/agentInstall.sh && chmod 755 agentInstall.sh && ./agentInstall.sh
            -
          • Arm 64
            cd /usr/local && wget --no-check-certificate https://telescope-eu-nl.obs.eu-nl.otc.t-systems.com/scripts/agentInstallARM.sh && chmod 755 agentInstallARM.sh && ./agentInstallARM.sh
            -
          +

          Procedure

          1. Log in to the ECS or BMS as user root.
          2. Install the Agent.
            EU DE:
            cd /usr/local && curl -k -O https://uniagent-eu-de.obs.eu-de.otc.t-systems.com/package/agent_install.sh && bash agent_install.sh -r eu-de -u 0.1.9 -t 2.7.2 -o otc.t-systems.com -d agent.ces.otc.t-systems.com
            -

            If Telescope process starts successfully or Success to install telescope is displayed, the Agent is successfully installed.

            -

            -
          3. Configure the Agent by referring to Restoring the Agent Configurations on a Linux Server or (Optional) Manually Configuring the Agent (Linux).
            +
            EU NL:
            cd /usr/local && curl -k -O https://uniagent-eu-nl.obs.eu-nl.otc.t-systems.com/package/agent_install.sh && bash agent_install.sh -r eu-nl -u 0.1.9 -t 2.7.2 -o otc.t-systems.com -d agent.ces.otc.t-systems.com
            +
            +
            If the message "Telescope process starts successfully." is displayed, the installation is successful. Wait for 3 to 5 minutes until the Agent starts collecting monitoring data.
            • After you configure the Agent, its status is still displayed as Not installed on the Server Monitoring page because no monitoring data is reported yet. Wait 3 to 5 minutes and refresh the page.
            • If the Agent status is Running and monitoring is enabled, the Agent has been recognized by Cloud Eye and has started to report fine-grained metric data.
            -
          4. 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 deleted file mode 100644 index c262943f2..000000000 --- a/docs/ces/umn/ces_01_0030.html +++ /dev/null @@ -1,17 +0,0 @@ - - -

        Restoring the Agent Configurations on a Linux Server

        -

        Scenarios

        This topic describes how to restore the Agent configurations on the Cloud Eye console (recommended).

        -
        • The Restore Agent Configurations option is unavailable for BMSs. For details, see (Optional) Manually Configuring the Agent (Linux).
        • After you configure the Agent, its status is still displayed as Not installed because no monitoring data is reported yet. Wait 3 to 5 minutes and refresh the page.
        • If the Agent is in the Running state, the Agent has been installed and has started to collect fine-grained metric data.
        -
        -
        -

        Restoring the Agent Configurations

        1. Log in to the management console.
        2. Click Service List in the upper left corner and select Cloud Eye. In the navigation pane on the left, choose Server Monitoring.
        3. On the Server Monitoring page, select a server that has the Agent installed.
        4. Click Restore Agent Configurations.
        5. 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.

          -
        -
        -
        - - diff --git a/docs/ces/umn/ces_01_0031.html b/docs/ces/umn/ces_01_0031.html index 8468ae0b8..cdb777080 100644 --- a/docs/ces/umn/ces_01_0031.html +++ b/docs/ces/umn/ces_01_0031.html @@ -1,14 +1,25 @@ -

        (Optional) Manually Configuring the Agent (Linux)

        -

        Scenarios

        After you install the Agent, configure it by clicking Restore Agent Configurations on the Cloud Eye console. If the Agent fails to be configured by clicking Restore Agent Configurations or due to other reasons, manually configure it by following the instructions provided in this topic.

        +

        (Optional) Manually Configuring the Agent on a Linux Server

        +

        Scenarios

        The Configure feature allows you to configure the AK/SK, region ID, and project ID If the Agent fails to be configured by clicking Configure or due to other reasons, manually configure it by following the instructions provided in this section.

        This section takes an ECS as an example. The operations for BMSs are similar.

        +

        Constraints

        Not every Operating System is supported. For details about which Linux OSs are supported, see What OSs Does the Agent Support?

        +

        Prerequisites

        The Agent has been installed.

        -

        Procedure

        1. Log in to an ECS as user root.
        2. Run the following command to go to the Agent installation path bin:

          cd /usr/local/telescope/bin

          -
        3. Modify configuration file conf.json.
          1. Run the following command to open conf.json:

            vi conf.json

            -
          2. Modify the parameters in the file. For details, see Table 1.

            ECS parameters

            +

            Checking the Version of the Agent In Use

            1. Log in to an ECS as user root.
            2. Run the following command to check the Agent version:

              if [[ -f /usr/local/uniagent/extension/install/telescope/bin/telescope ]]; then /usr/local/uniagent/extension/install/telescope/bin/telescope -v; elif [[ -f /usr/local/telescope/bin/telescope ]]; then echo "old agent"; else echo 0; fi

              +
              • If old agent is displayed, the earlier version of the Agent is used.
              • If a version is returned, the new version of the Agent is in use.
              • If 0 is returned, the Agent is not installed.
              +
            +
            +

            Procedure

            1. Log in to an ECS as user root.
            2. Run the following command to go to the Agent installation path bin:

              Earlier version:

              +
              cd /usr/local/telescope/bin
              +
              New version:
              cd /usr/local/uniagent/extension/install/telescope/bin
              +
              +
            3. Modify configuration file conf.json.
              1. Run the following command to open conf.json:

                vi conf.json

                +
              2. Modify the parameters in the file. For details, see Table 1.

                To avoid major security risks from storing plaintext AKs and SKs, it is advised to delegate all ECS or BMS Agents in the region. For details, see How Do I Configure an Agency?

                +
                +

                ECS parameters

                {
     "InstanceId":"XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX",
     "ProjectId": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
@@ -30,60 +41,57 @@
     "BmsFlag": true
 }
                -
                Table 1 Public parameters

                Parameter

                +
                - - - - - - - - - - - - - - - @@ -92,25 +100,31 @@
              3. Modify configuration file conf_ces.json for the Cloud Eye metric collection module.
                1. Run the following command to open public configuration file conf_ces.json:

                  vi conf_ces.json

                  -
                2. Modify the endpoint in conf_ces.json, and save the conf_ces.json file. For details, see Table 2.
                  {
+
                3. Modify the endpoint in conf_ces.json, and save the conf_ces.json file. For details, see Table 2.
                  EU DE:
                  {
   "Endpoint": "https://ces.eu-de.otc.t-systems.com"
 }
                  +
                  +
                  EU NL:
                  {
+  "Endpoint": "https://ces.eu-nl.otc.t-systems.com"
+}
                  +
                  -
                4. 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.

                -
                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.
                +

                Specifies the instance ID. This parameter is left blank by default, indicating that the instance ID of the current server is specified. Retain the default value. If you need to change the value, log in to the management console and view the instance ID in the ECS list.

                +
                NOTE:

                When configuring the instance ID, comply with the following rules:

                +
                • The instance ID must be unique at all sites, that is, in the same region, InstanceId used by the Agent cannot be the same, or 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.

                -

                If you do not configure ProjectId, retain "ProjectId": "".

                -

                If you configure it, perform the following operations:

                -
                1. Log in to the Cloud Eye console, click the username in the upper right corner, and choose My Credentials.
                2. Under Projects, obtain the project ID for the region where the ECS or BMS is located.
                +

                Specifies the project ID. This parameter is left blank by default, indicating that the project ID of the current server is specified. Retain the default value. If you need to configure it, obtain the project ID as follows:

                +
                1. Log in to the Cloud Eye console, click the username in the upper right corner, and choose My Credentials.
                2. 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:

                -

                Log in to Cloud Eye, click the username in the upper right corner, and choose My Credentials > Access Keys.

                +

                To obtain the AK and SK, perform the following operations:

                +

                Log in to Cloud Eye, click the username in the upper right corner, and choose My Credentials > 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

                +

                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.
                Table 2 Parameter setting of the metric collection module

                Parameter

                +
                - - -
                Table 2 Parameter setting of the metric collection module

                Parameter

                Description

                +

                Description

                Endpoint

                +

                Endpoint

                Specifies the Cloud Eye endpoint URL in the region of the ECS or BMS. For example, if the ECS or BMS is located in region EU-DE, Endpoint is ces.eu-de.otc.t-systems.com.

                +

                Specifies the Cloud Eye endpoint URL in the region that the ECS or BMS belongs to.

                +
                • If the ECS or BMS is in the EU-DE region, ces.eu-de.otc.t-systems.com is used.
                • If the ECS or BMS is in the EU-NL region, ces.eu-nl.otc.t-systems.com is used.
                -
                • After you configure the Agent, its status is still displayed as Uninstalled because no monitoring data is reported yet. Wait 3 to 5 minutes and refresh the page.
                • If the Agent is in the Running state, the Agent has been installed and has started to collect fine-grained metric data.
                +
                • 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 status is Running, the Agent has been recognized by Cloud Eye and has started to report fine-grained metric data.
                diff --git a/docs/ces/umn/ces_01_0032.html b/docs/ces/umn/ces_01_0032.html index d4797b0fe..2ebfc900e 100644 --- a/docs/ces/umn/ces_01_0032.html +++ b/docs/ces/umn/ces_01_0032.html @@ -1,13 +1,18 @@

                (Optional) Manually Configuring the Agent on a Windows Server

                -

                Scenarios

                After you install the Agent, configure it by clicking Restore Agent Configurations on the Cloud Eye console. If the Agent fails to be configured by clicking Restore Agent Configurations or due to other reasons, manually configure it by following the instructions provided in this topic.

                +

                Scenarios

                The Configure feature allows you to configure the AK/SK, region ID, and project ID in one-click mode. If the Agent fails to be configured by clicking Configure or due to other reasons, manually configure it by following the instructions provided in this topic.

                -

                Constraints

                The Agent cannot be installed on Windows BMSs.

                +

                Constraints

                Some OSs are not supported. For details about which Windows OSs are supported, see What OSs Does the Agent Support?

                Prerequisites

                The Agent has been installed.

                -

                Procedure

                1. Log in to the ECS.
                2. Open the conf.json file in the telescope_windows_amd64\bin directory.
                3. 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?

                  +

                  Checking the Version of the Agent In Use

                  1. Log in to an ECS as an administrator.
                  2. Check the installation path and the Agent version.
                    • Earlier version: The Agent is installed in the directory where the Agent installation package is decompressed, for example, if the package is decompressed in D:\Agent, the installation path would be D:\Agent\telescope_windows_amd64.
                    • New version: C:\Program Files\uniagent\extension\install\telescope
                    +
                  +
                  +

                  Procedure

                  1. Log in to the ECS.
                  2. Go to the bin directory in the Agent installation path.

                    Earlier version: The Agent is installed in the directory of the decompressed Agent installation package, for example, if the package is decompressed in D:\Agent, the installation path would be D:\Agent\telescope_windows_amd64.

                    +

                    New version: C:\Program Files\uniagent\extension\install\telescope

                    +
                  3. Modify the conf.json file. For details about the parameters, see Table 1.

                    To avoid major security risks from storing plaintext AKs and SKs, it is advised to delegate all ECS Agents in the region. For details, see How Do I Configure an Agency?

                    {
     "InstanceId":"",
@@ -20,50 +25,50 @@
 }

                    -
                    Table 1 Public parameters

                    Parameter

                    +
                    - - - - - - - - - - - - - @@ -71,7 +76,9 @@
                    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.

                    -
                    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.
                    +

                    Specifies the instance ID. This parameter is left blank by default, indicating that the instance ID of the current server is specified. Retain the default value. If you need to change the value, log in to the management console and view the instance ID in the ECS list.

                    +
                    NOTE:

                    When configuring the instance ID, comply with the following rules:

                    +
                    • The instance ID must be unique at all sites, that is, in the same region, InstanceId used by the Agent cannot be the same, or errors may occur.
                    • The InstanceId value must be consistent with the actual ECS ID, or you cannot see the OS monitoring data on Cloud Eye.

                    ProjectId

                    +

                    ProjectId

                    Specifies the project ID. You do not need to configure ProjectId. Retain "ProjectId": "". If you wish to configure it, perform the following operations:

                    -
                    1. Log in to the Cloud Eye console, click the username in the upper right corner, and choose My Credentials.
                    2. Under Projects, obtain the project ID for the region where the ECS or BMS is located.
                    +

                    Specifies the project ID. This parameter is left blank by default, indicating that the project ID of the current server is specified. Retain the default value. If you need to configure it, obtain the project ID as follows:

                    +
                    1. Log in to the Cloud Eye console, click the username in the upper right corner, and choose My Credentials.
                    2. Under Projects, obtain the project ID for the region where the ECS is located.

                    AccessKey/SecretKey

                    +

                    AccessKey/SecretKey

                    To obtain the AK and SK, perform the following operations:

                    -

                    Log in to Cloud Eye, click the username in the upper right corner, and choose My Credentials > 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.
                      +

                    To obtain the AK and SK, perform the following operations:

                    +

                    Log in to Cloud Eye, click the username in the upper right corner, and choose My Credentials > 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

                    +

                    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.

                    -
                    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.

                    +

                    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.
                    -
                  4. Wait for a few minutes. If Agent Status is Running, the Agent has been installed and starts to collect fine-grained metric data.
                    5. +
                    • 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 status is Running and monitoring is enabled, the Agent has been recognized by Cloud Eye and has started to report fine-grained metric data.
                    +
                    +
                    diff --git a/docs/ces/umn/ces_01_0033.html b/docs/ces/umn/ces_01_0033.html index c14360d67..39175c4f6 100644 --- a/docs/ces/umn/ces_01_0033.html +++ b/docs/ces/umn/ces_01_0033.html @@ -1,40 +1,37 @@

                    Installing the Agents in Batches on Linux ECSs

                    -

                    Scenarios

                    This topic describes how to install Agents in batches on Linux ECSs.

                    +

                    Scenarios

                    This topic describes how to batch install the Agents on Linux ECSs.

                    Operation

                    After binding an elastic IP address to an ECS, install and configure the Agent by following instructions in Installing and Configuring the Agent on a Linux ECS or BMS to ensure that data collection is normal. Use the ECS as a jump server and run scripts in batches to copy, decompress, and install the Agent package and configuration file to other ECSs.

                    • The ECSs where the Agent is to be installed in batches must belong to the same VPC.
                    • Agents cannot be installed on Windows servers in batches.
                    -

                    Prerequisites

                    • The IP addresses and password of user root of all ECSs for which the Agent is to be installed have been collected, sorted in the iplist.txt format, and uploaded to the /usr/local directory on the first ECS.

                      In the iplist.txt file, each line contains only one IP address in the "IP address,Password of user root" format.

                      +

                      Constraints

                      Some OSs are not supported. For details about which Linux OSs are supported, see What OSs Does the Agent Support?

                      +
                      +

                      Prerequisites

                      • You have configured an agency by referring to Configuring an Agency by One Click.
                      • The IP addresses and password of user root of all ECSs for which the Agent is to be installed have been collected, sorted in the iplist.txt format, and uploaded to the /usr/local directory on the first ECS.

                        In the iplist.txt file, each line contains only one IP address in the "IP address,Password of user root" format.

                        In the following example, abcd is the password.

                        192.168.1.1,abcd
 192.168.1.2,abcd
                      -

                      Procedure

                      1. Use PuTTY to log in to the ECS on which the Agent has been installed as user root.
                      2. Run the following command to download and run the batch installation script:
                        eu-de:
                        • x86_64
                          cd /usr/local && wget --no-check-certificate https://telescope-eu-de.obs.eu-de.otc.t-systems.com/scripts/agentBatchPackage.sh && chmod 755 agentBatchPackage.sh && ./agentBatchPackage.sh
                          -
                        • Arm 64
                          cd /usr/local && wget --no-check-certificate https://telescope-eu-de.obs.eu-de.otc.t-systems.com/scripts/agentBatchPackageARM.sh && chmod 755 agentBatchPackageARM.sh && ./agentBatchPackageARM.sh
                          -
                        +

                        Procedure

                        1. Log in to the ECS on which the Agent has been installed as user root.
                        2. Run the following command to download and run the batch installation script:
                          EU DE:
                          cd /usr/local && curl -k -O https://uniagent-eu-de.obs.eu-de.otc.t-systems.com/package/batch_agent_install.sh && bash batch_agent_install.sh -r eu-de -u 0.1.9 -t 2.7.2 -d agent.ces.otc.t-systems.com -o otc.t-systems.com
                          -

                          eu-nl:

                          -
                          • x86_64
                            cd /usr/local && wget --no-check-certificate https://telescope-eu-nl.obs.eu-nl.otc.t-systems.com/scripts/agentBatchPackage.sh && chmod 755 agentBatchPackage.sh && ./agentBatchPackage.sh
                            -
                          • Arm 64
                            cd /usr/local && wget --no-check-certificate https://telescope-eu-nl.obs.eu-nl.otc.t-systems.com/scripts/agentBatchPackageARM.sh && chmod 755 agentBatchPackageARM.sh && ./agentBatchPackageARM.sh
                            -
                          -
                        3. Run the following command to run the script and enter the password (the passwords of multiple ECSs are the same):

                          cd /usr/local && ./batchInstall.sh $password

                          -
                          • If multiple passwords are involved in the configured iplist.txt, enter the preceding commands and passwords for multiple times. If the password of an ECS is incorrect, the Agent installation on the ECS will fail.
                          • If the passwords of multiple ECSs are different, run the cd /usr/local && ./batchInstall.sh command.
                          • Ensure that the ECSs are running during script execution.
                          -
                          -
                        4. After the installation is complete, log in to the Cloud Eye console and choose Server Monitoring in the navigation pane on the left.
                          View the list of ECSs on which the Agent has been installed.

                          After you configure the Agent, its status is still displayed as Uninstalled because no monitoring data is reported yet. Wait 3 to 5 minutes and refresh the page.

                          -
                          +
                          EU NL:
                          cd /usr/local && curl -k -O https://uniagent-eu-nl.obs.eu-nl.otc.t-systems.com/package/batch_agent_install.sh && bash batch_agent_install.sh -r eu-nl -u 0.1.9 -t 2.7.2 -d agent.ces.otc.t-systems.com -o otc.t-systems.com
                          -
                        5. On the Server Monitoring page, select all ECSs and click Restore Agent Configurations.
                        6. On the page that is displayed, click One-Click Restore.
                        +
                      3. Check whether Telescope process starts successfully. is displayed. If so, the installation is successful. Wait for 3 to 5 minutes until the Agent starts collecting monitoring data.
                        • After you configure the Agent, its status is still displayed as Not installed on the Server Monitoring page because no monitoring data is reported yet. Wait 3 to 5 minutes and refresh the page.
                        • If the Agent status is Running and monitoring is enabled, the Agent has been recognized by Cloud Eye and has started to report fine-grained metric data.
                        +
                        +
                        Figure 1 Successful installation
                        +
                      +
                      +

                      Helpful Links

                      If the error message "SSH dial error" is displayed during batch installation, rectify the fault by referring to How Can I Fix the "SSH dial error" During Batch Agent Installation?.

                      diff --git a/docs/ces/umn/ces_01_0035.html b/docs/ces/umn/ces_01_0035.html index c994b3540..f77a241d6 100644 --- a/docs/ces/umn/ces_01_0035.html +++ b/docs/ces/umn/ces_01_0035.html @@ -1,8 +1,7 @@

                      Managing the Agent

                      -

                      This topic describes how to manage the Agent, including how to view, start, stop, and uninstall the Agent.

                      -
                      +
                      • Managing the Agent (Linux)
                        diff --git a/docs/ces/umn/ces_01_0036.html b/docs/ces/umn/ces_01_0036.html index 9a523ee3f..181ff2759 100644 --- a/docs/ces/umn/ces_01_0036.html +++ b/docs/ces/umn/ces_01_0036.html @@ -1,27 +1,72 @@

                        Managing the Agent (Linux)

                        -

                        To view, start, stop, update, and uninstall the Agent, you must log in as user root.

                        +

                        This section describes how to view, start, stop, restart, uninstall, or upgrade the Agent on the Linux platform.

                        +

                        To view, start, stop, restart, or uninstall the Agent, you need to log in to the server as user root.

                        -

                        Checking the Agent Status

                        Log in to an ECS or BMS as user root and run the following command to check the Agent status:

                        +

                        Viewing the Agent Version

                        1. Log in to an ECS as user root.
                        2. Run the following command to check the Agent version:

                          if [[ -f /usr/local/uniagent/extension/install/telescope/bin/telescope ]]; then /usr/local/uniagent/extension/install/telescope/bin/telescope -v; elif [[ -f /usr/local/telescope/bin/telescope ]]; then echo "old agent"; else echo 0; fi

                          +
                          • If old agent is returned, the earlier version of the Agent is used. Manage the Agent based on its version.
                          • If a version is returned, the new version of the Agent is used. Manage the Agent based on its version.
                          • If 0 is returned, the Agent is not installed.

                            The new version of the Agent consists of two processes: Telescope and UniAgent. The Telescope process is used to collect and report metrics, and the UniAgent process is used to manage the Telescope lifecycle.

                            +
                            +
                          +
                        +
                        +

                        Checking the Agent Status (New Version)

                        Log in to an ECS or BMS as user root and check the Agent status.

                        +

                        service ces-uniagent status

                        +
                        • If the command output contains active (running), the UniAgent is running properly and can manage the Telescope lifecycle.
                        • If the command output contains inactive (dead), the UniAgent is not running and cannot manage the Telescope lifecycle.
                        +
                        +

                        /usr/local/uniagent/extension/install/telescope/telescoped status

                        +
                        • If the following information is displayed, the Telescope is running properly and can collect and report metrics.
                          Telescope process is running well.
                          +
                        • If the following information is displayed, the Telescope stops working and cannot collect or report metrics.
                          Telescope process is not running.
                          +
                        +
                        +
                        +

                        Starting the Agent (New Version)

                        Start the Agent.

                        +

                        service ces-uniagent start

                        +

                        /usr/local/uniagent/extension/install/telescope/telescoped start

                        +
                        +

                        Restarting the Agent (New Version)

                        Restart the Agent.

                        +

                        service ces-uniagent stop

                        +

                        service ces-uniagent start

                        +

                        /usr/local/uniagent/extension/install/telescope/telescoped restart

                        +
                        +

                        Stopping the Agent (New Version)

                        Log in to an ECS or BMS and stop the Agent.

                        +

                        service ces-uniagent stop

                        +

                        /usr/local/uniagent/extension/install/telescope/telescoped stop

                        +
                        +

                        Uninstalling the Agent (New Version)

                        You can manually uninstall the Agent. After the uninstallation, Cloud Eye does not support monitoring by seconds for ECSs or BMSs. To use the Agent again, reinstall it by referring to Installing and Configuring the Agent on a Linux ECS or BMS.

                        +

                        Uninstall the Agent.

                        +

                        cd /usr/local/uniagent/script/

                        +

                        ./uninstall.sh

                        +
                        Before reinstalling the Agent, run the following command to manually remove the original Agent installation package:
                        rm /usr/local/uniagent_install_amd64.sh
                        +
                        +
                        +
                        +

                        Checking the Agent Status (Earlier Version)

                        Log in to an ECS or BMS as user root and check the Agent status.

                        service telescoped status

                        The following message indicates that the Agent is running properly:

                        "Active (running) or "Telescope process is running well."
                        -

                        Starting the Agent

                        /usr/local/telescope/telescoped start

                        +

                        Starting the Agent (Earlier Version)

                        Start the Agent.

                        +

                        /usr/local/telescope/telescoped start

                        -

                        Restarting the Agent

                        /usr/local/telescope/telescoped restart

                        +

                        Restarting the Agent (Earlier Version)

                        Restart the Agent.

                        +

                        /usr/local/telescope/telescoped restart

                        -

                        Stopping the Agent

                        Log in to an ECS or BMS and run the following command to stop the Agent:

                        +

                        Stopping the Agent (Earlier Version)

                        Log in to an ECS or BMS and run the following command to stop the Agent:

                        service telescoped stop

                        If the Agent installation fails, it may be impossible to stop the Agent. In this case, run the following command to stop the Agent:

                        /usr/local/telescope/telescoped stop

                        -

                        Uninstalling the Agent

                        Run the following command to uninstall the Agent:

                        +

                        Uninstalling the Agent (Earlier Version)

                        Uninstall the Agent.

                        /usr/local/telescope/uninstall.sh

                        You can manually uninstall the Agent. After the uninstallation, Cloud Eye does not support monitoring by seconds (60s by default) for ECSs or BMSs. To use the Agent again, reinstall it by referring to Installing and Configuring the Agent on a Linux ECS or BMS. Before reinstalling the Agent, manually delete the previous Agent installation package.

                        +

                        +
                        +

                        Upgrading the Agent

                        If the current Agent version is not the desired one, you can upgrade the Agent. The Cloud Eye Agent will be continuously upgraded to provide you with a better monitoring experience.

                        +
                        1. Uninstall the Agent of the current version. +
                        2. Install the Agent of the latest version by running the command in Installing the Agent on a Linux Server.
                        diff --git a/docs/ces/umn/ces_01_0037.html b/docs/ces/umn/ces_01_0037.html index 8beaba508..89ca5553e 100644 --- a/docs/ces/umn/ces_01_0037.html +++ b/docs/ces/umn/ces_01_0037.html @@ -1,17 +1,24 @@

                        Managing the Agent (Windows)

                        -

                        The default installation path of the Agent is C:\Program Files\telescope.

                        +

                        This section describes how to view, start, stop, uninstall, restart, or upgrade the Agent on the Windows platform.

                        +

                        Earlier version: The Agent is installed in the directory where the Agent installation package is decompressed, for example, if the package is decompressed in D:\Agent, the installation path would be D:\Agent\telescope_windows_amd64.

                        +

                        New version: The default Agent installation path is C:\Program Files\uniagent\extension\install\telescope.

                        Checking the Agent Status

                        In the task manager, check the status of the telescope process.

                        Starting the Agent

                        In the directory where the Agent installation package is stored, double-click the start.bat script.

                        -

                        Stopping the Agent

                        In the directory where the Agent installation package is stored, double-click the shutdown.bat script.

                        +

                        Stopping the Agent

                        In the directory where the Agent installation package is stored, double-click the shutdown.bat script.

                        -

                        Uninstalling the Agent

                        In the directory where the Agent installation package is stored, double-click the uninstall.bat script.

                        +

                        Uninstalling the Agent

                        In the directory where the Agent installation package is stored, double-click the uninstall.bat script.

                        Before reinstalling the Agent, manually delete the previous Agent installation package.

                        +

                        Restarting the Agent

                        1. In the Agent installation directory, double-click the shutdown.bat script to stop the Agent.
                        2. Double-click the start.bat script to start the Agent.
                        +
                        +

                        Upgrading the Agent

                        If the current Agent version is not the desired one, you can upgrade the Agent. The Cloud Eye Agent will be continuously upgraded to provide you with a better monitoring experience.

                        +
                        1. Uninstall the Agent of the current version. For details, see Uninstalling the Agent.
                        2. Install the Agent of the latest version. For details, see Installing the Agent on a Windows server.
                        +
                        diff --git a/docs/ces/umn/ces_01_0040.html b/docs/ces/umn/ces_01_0040.html index 6f27020a8..a7b592829 100644 --- a/docs/ces/umn/ces_01_0040.html +++ b/docs/ces/umn/ces_01_0040.html @@ -1,11 +1,13 @@ -

                        Process Monitoring

                        +

                        Viewing Metrics

                        diff --git a/docs/ces/umn/ces_01_0042.html b/docs/ces/umn/ces_01_0042.html index afea7ebed..08c27e944 100644 --- a/docs/ces/umn/ces_01_0042.html +++ b/docs/ces/umn/ces_01_0042.html @@ -3,7 +3,7 @@

                        Creating an Alarm Rule to Monitor a Server

                        Scenarios

                        This topic describes how to create an alarm rule for an ECS or BMS.

                        -

                        Procedure

                        1. Log in to the management console.
                        2. In the upper left corner, select a region and project.
                        3. Click Service List in the upper left corner and select Cloud Eye.
                        4. In the navigation pane on the left, choose Server Monitoring.
                        5. 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.
                        6. On the Create Alarm Rule page, configure the parameters.

                          For details about the parameters, see Table 1 to Table 4.

                          +

                          Procedure

                          1. Log in to the management console.
                          2. In the upper left corner, select a region and project.
                          3. Choose Service List > Cloud Eye.
                          4. In the navigation pane on the left, choose Server Monitoring.
                          5. 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.
                          6. 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

                            diff --git a/docs/ces/umn/ces_01_0051.html b/docs/ces/umn/ces_01_0051.html index 024c22726..aafcfe109 100644 --- a/docs/ces/umn/ces_01_0051.html +++ b/docs/ces/umn/ces_01_0051.html @@ -3,13 +3,14 @@

                            Viewing Event Monitoring Data

                            Scenarios

                            This topic describes how to view the event monitoring data.

                            -

                            Procedure

                            1. Log in to the management console.
                            2. Click Service List in the upper left corner and select Cloud Eye.
                            3. 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.

                              +

                              Procedure

                              1. Log in to the management console.
                              2. Choose Service List > Cloud Eye.
                              3. 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

                                -
                              4. Expand an event and click View Event in the Operation column to view its details.
                                Figure 2 Viewing event details
                                -
                              5. 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.

                                -
                              6. In the upper right corner of the event list, select an event type and enter an event name to filter the desired event.
                              7. To view events of a specific time period, click the corresponding bar chart.
                              +
                            4. 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 1 day, 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.

                              +
                              Figure 2 Viewing graphs
                              +
                            5. Click View Event in the Operation column to view details about a specific event.
                            6. Above the event list, select a property type and enter a key word to filter the desired event.
                            7. To view events of a specific time period, click the corresponding bar chart.
                            8. In the event list, select multiple events and click the arrow in the lower right corner to view their monitoring details.
                              Figure 3 Viewing event monitoring details in batches
                              +
                            diff --git a/docs/ces/umn/ces_01_0052.html b/docs/ces/umn/ces_01_0052.html index bbe847580..0414cdb43 100644 --- a/docs/ces/umn/ces_01_0052.html +++ b/docs/ces/umn/ces_01_0052.html @@ -3,7 +3,7 @@

                            Creating an Alarm Rule to Monitor an Event

                            Scenarios

                            This topic describes how to create an alarm rule to monitor an event.

                            -

                            Procedure

                            1. Log in to the management console.
                            2. Click Service List in the upper left corner and select Cloud Eye.
                            3. In the navigation pane on the left, choose Event Monitoring.
                            4. 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.

                              +

                              Procedure

                              1. Log in to the management console.
                              2. Choose Service List > Cloud Eye.
                              3. In the navigation pane on the left, choose Event Monitoring.
                              4. 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.

                              5. 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 event monitoring alarms

                                Parameter

                                diff --git a/docs/ces/umn/ces_01_0054.html b/docs/ces/umn/ces_01_0054.html index 67a31fd46..530721994 100644 --- a/docs/ces/umn/ces_01_0054.html +++ b/docs/ces/umn/ces_01_0054.html @@ -1,2715 +1,4263 @@

                                Events Supported by Event Monitoring

                                -

                                Events in Event Monitoring come from operations on cloud service resources and are not collected by the Agent in Server Monitoring.

                                +
                                • Events in Event Monitoring come from operations on cloud service resources and are not collected by the Agent in Server Monitoring.
                                • The name of a resource that supports event reporting can contain a maximum of 128 characters, including letters, digits, underscores (_), hyphens (-), and periods (.). If it contains other characters, the event may fail to be reported to Cloud Eye.
                                -
                                Table 1 Elastic Cloud Server (ECS)

                                Event Source

                                +
                                - - - - - - + - - - - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                                Table 1 Elastic Cloud Server (ECS)

                                Event Source

                                Event Name

                                +

                                Namespace

                                Event ID

                                +

                                Event Name

                                Event Severity

                                +

                                Event ID

                                Description

                                +

                                Event Severity

                                Solution

                                +

                                Description

                                Impact

                                +

                                Solution

                                +

                                Impact

                                ECS

                                +

                                ECS

                                Delete ECS

                                +

                                SYS.ECS

                                deleteServer

                                +

                                Restart triggered due to hardware fault

                                Major

                                +

                                startAutoRecovery

                                The ECS was deleted

                                -
                                • on the management console.
                                • by calling APIs.
                                +

                                Major

                                Check whether the deletion was performed intentionally by a user.

                                +

                                ECSs on a faulty host would be automatically migrated to another properly-running host. During the migration, the ECSs was restarted.

                                Services are interrupted.

                                +

                                Wait for the event to end and check whether services are affected.

                                +

                                Services may be interrupted.

                                Reboot ECS

                                +

                                Restart completed due to hardware failure

                                rebootServer

                                +

                                endAutoRecovery

                                Minor

                                +

                                Major

                                The ECS was restarted

                                -
                                • on the management console.
                                • by calling APIs.
                                +

                                The ECS was recovered after the automatic migration.

                                Check whether the restart was performed intentionally by a user.

                                -
                                • Deploy service applications in HA mode.
                                • After the ECS starts up, check whether services recover.
                                +

                                This event indicates that the ECS has recovered and been working properly.

                                Services are interrupted.

                                +

                                None

                                Resize ECS

                                +

                                Auto recovery timeout (being processed on the backend)

                                resizeServer

                                +

                                faultAutoRecovery

                                Minor

                                +

                                Major

                                The ECS was resized

                                -
                                • on the management console.
                                • by calling APIs.
                                +

                                Migrating the ECS to a normal host timed out.

                                • Check whether the operation was performed by a user.
                                • Deploy service applications in HA mode.
                                • After the ECS is resized, check whether services have recovered.
                                +

                                Migrate services to other ECSs.

                                Services are interrupted.

                                +

                                Services are interrupted.

                                Restart triggered due to system faults

                                +

                                ECS deleted

                                startAutoRecovery

                                +

                                deleteServer

                                Major

                                +

                                Major

                                ECSs on a faulty host would be automatically migrated to another properly-running host. During the migration, the ECSs was restarted.

                                +

                                The ECS was deleted

                                +
                                • on the management console.
                                • by calling APIs.

                                Wait for the event to end and check whether services are affected.

                                +

                                Check whether the deletion was performed intentionally by a user.

                                Services may be interrupted.

                                +

                                Services are interrupted.

                                Restart completed due to system faults

                                +

                                ECS restarted

                                endAutoRecovery

                                +

                                rebootServer

                                Major

                                +

                                Minor

                                The ECS was recovered after the automatic migration.

                                +

                                The ECS was restarted

                                +
                                • on the management console.
                                • by calling APIs.

                                This event indicates that the ECS has recovered and been working properly.

                                +

                                Check whether the restart was performed intentionally by a user.

                                +
                                • Deploy service applications in HA mode.
                                • After the ECS starts up, check whether services recover.

                                None

                                +

                                Services are interrupted.

                                Auto recovery timeout (being processed on the backend)

                                +

                                ECS stopped

                                faultAutoRecovery

                                +

                                stopServer

                                Major

                                +

                                Minor

                                Migrating the ECS to a normal host timed out.

                                +

                                The ECS was stopped

                                +
                                • on the management console.
                                • by calling APIs.

                                Migrate services to other ECSs.

                                +
                                • Check whether the operation was intentionally performed by a user.
                                • Deploy service applications in HA mode.
                                • After the ECS starts up, check whether services recover.

                                Services are interrupted.

                                +

                                Services are interrupted.

                                Improper ECS running

                                +

                                NIC deleted

                                vmIsRunningImproperly

                                +

                                deleteNic

                                Major

                                +

                                Major

                                The ECS was faulty or the ECS NIC was abnormal.

                                +

                                The ECS NIC was deleted

                                +
                                • on the management console.
                                • by calling APIs.

                                Deploy service applications in HA mode.

                                -

                                After the fault is rectified, check whether services recover.

                                +
                                • Check whether the deletion was performed intentionally by a user.
                                • Deploy service applications in HA mode.
                                • After the NIC is deleted, check whether services recover.

                                Services are interrupted.

                                +

                                Services may be interrupted.

                                Improper ECS running recovered

                                +

                                ECS resized

                                vmIsRunningImproperlyRecovery

                                +

                                resizeServer

                                Major

                                +

                                Minor

                                The ECS was restored to the normal status.

                                +

                                The ECS specifications were resized

                                +
                                • on the management console.
                                • by calling APIs.

                                Wait for the ECS status to become normal and check whether services are affected.

                                +
                                • Check whether the operation was performed by a user.
                                • Deploy service applications in HA mode.
                                • After the ECS is resized, check whether services have recovered.

                                None

                                +

                                Services are interrupted.

                                VM faults caused by host process exceptions

                                +

                                GuestOS restarted

                                VMFaultsByHostProcessExceptions

                                +

                                RestartGuestOS

                                Critical

                                +

                                Minor

                                The host where the ECS resides is faulty. The system will automatically try to start the ECS.

                                +

                                The guest OS was restarted.

                                After the ECS is started, check whether this ECS and services on it can run properly.

                                +

                                Contact O&M personnel.

                                The ECS is faulty.

                                +

                                Services may be interrupted.

                                Restarted GuestOS

                                +

                                ECS failure caused by system faults

                                RestartGuestOS

                                +

                                VMFaultsByHostProcessExceptions

                                Minor

                                +

                                Critical

                                The guest OS was restarted.

                                +

                                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.

                                Services may be interrupted.

                                +

                                The ECS is faulty.

                                +

                                Startup failure

                                +

                                faultPowerOn

                                +

                                Major

                                +

                                The ECS failed to start.

                                +

                                Start the ECS again. If the problem persists, contact O&M personnel.

                                +

                                The ECS cannot start.

                                +

                                Host breakdown risk

                                +

                                hostMayCrash

                                +

                                Major

                                +

                                The host where the ECS resides may break down, and the risk cannot be prevented through live migration due to some reasons.

                                +

                                Migrate services running on the ECS first and delete or stop the ECS. Start the ECS only after the O&M personnel eliminate the risk.

                                +

                                The host may break down, causing service interruption.

                                +

                                Scheduled migration completed

                                +

                                instance_migrate_completed

                                +

                                Major

                                +

                                Scheduled ECS migration is completed.

                                +

                                Wait until the ECSs become available and check whether services are affected.

                                +

                                Services may be interrupted.

                                +

                                Scheduled migration being executed

                                +

                                instance_migrate_executing

                                +

                                Major

                                +

                                ECSs are being migrated as scheduled.

                                +

                                Wait until the event is complete and check whether services are affected.

                                +

                                Services may be interrupted.

                                +

                                Scheduled migration canceled

                                +

                                instance_migrate_canceled

                                +

                                Major

                                +

                                Scheduled ECS migration is canceled.

                                +

                                None

                                +

                                None

                                +

                                Scheduled migration failed

                                +

                                instance_migrate_failed

                                +

                                Major

                                +

                                ECSs failed to be migrated as scheduled.

                                +

                                Contact O&M personnel.

                                +

                                Services are interrupted.

                                +

                                Scheduled migration to be executed

                                +

                                instance_migrate_scheduled

                                +

                                Major

                                +

                                ECSs will be migrated as scheduled.

                                +

                                Clarify the impact on services during the execution window.

                                +

                                None

                                +

                                Scheduled specification modification failed

                                +

                                instance_resize_failed

                                +

                                Major

                                +

                                Specifications failed to be modified as scheduled.

                                +

                                Contact O&M personnel.

                                +

                                Services are interrupted.

                                +

                                Scheduled specification modification completed

                                +

                                instance_resize_completed

                                +

                                Major

                                +

                                Scheduled specifications modification is completed.

                                +

                                None

                                +

                                None

                                +

                                Scheduled specification modification being executed

                                +

                                instance_resize_executing

                                +

                                Major

                                +

                                Specifications are being modified as scheduled.

                                +

                                Wait until the event is completed and check whether services are affected.

                                +

                                Services are interrupted.

                                +

                                Scheduled specification modification canceled

                                +

                                instance_resize_canceled

                                +

                                Major

                                +

                                Scheduled specifications modification is canceled.

                                +

                                None

                                +

                                None

                                +

                                Scheduled specification modification to be executed

                                +

                                instance_resize_scheduled

                                +

                                Major

                                +

                                Specifications will be modified as scheduled.

                                +

                                Check the impact on services during the execution window.

                                +

                                None

                                +

                                Scheduled redeployment to be executed

                                +

                                instance_redeploy_scheduled

                                +

                                Major

                                +

                                ECSs will be redeployed on new hosts as scheduled.

                                +

                                Check the impact on services during the execution window.

                                +

                                None

                                +

                                Scheduled restart to be executed

                                +

                                instance_reboot_scheduled

                                +

                                Major

                                +

                                ECSs will be restarted as scheduled.

                                +

                                Check the impact on services during the execution window.

                                +

                                None

                                +

                                Scheduled stop to be executed

                                +

                                instance_stop_scheduled

                                +

                                Major

                                +

                                ECSs will be stopped as scheduled as they are affected by underlying hardware or system O&M.

                                +

                                Check the impact on services during the execution window.

                                +

                                None

                                +

                                Live migration started

                                +

                                liveMigrationStarted

                                +

                                Major

                                +

                                The host where the ECS is located may be faulty. Live migrate the ECS in advance to prevent service interruptions caused by host breakdown.

                                +

                                Wait for the event to end and check whether services are affected.

                                +

                                Services may be interrupted for less than 1s.

                                +

                                Live migration completed

                                +

                                liveMigrationCompleted

                                +

                                Major

                                +

                                The live migration is complete, and the ECS is running properly.

                                +

                                Check whether services are running properly.

                                +

                                None

                                +

                                Live migration failure

                                +

                                liveMigrationFailed

                                +

                                Major

                                +

                                An error occurred during the live migration of an ECS.

                                +

                                Check whether services are running properly.

                                +

                                There is a low probability that services are interrupted.

                                +

                                FPGA link fault

                                +

                                FPGALinkFault

                                +

                                Critical

                                +

                                The FPGA of the host on which the ECS is located was

                                +
                                • faulty.
                                • recovering from a fault.
                                +

                                Deploy service applications in HA mode.

                                +

                                After the FPGA fault is rectified, check whether services are restored.

                                +

                                Services are interrupted.

                                +

                                Scheduled redeployment to be authorized

                                +

                                instance_redeploy_inquiring

                                +

                                Major

                                +

                                As being affected by underlying hardware or system O&M, ECSs will be redeployed on new hosts as scheduled.

                                +

                                Authorize scheduled redeployment.

                                +

                                None

                                +

                                Local disk replacement canceled

                                +

                                localdisk_recovery_canceled

                                +

                                Major

                                +

                                Local disk failure

                                +

                                None

                                +

                                None

                                +

                                Local disk replacement to be executed

                                +

                                localdisk_recovery_scheduled

                                +

                                Major

                                +

                                Local disk failure

                                +

                                Clarify the impact on services during the execution window.

                                +

                                None

                                +

                                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.

                                +

                                NPU: uncorrectable ECC error

                                +

                                UncorrectableEccErrorCount

                                +

                                Major

                                +

                                There are uncorrectable ECC errors on the NPU.

                                +

                                If services are affected, replace the NPU with another one.

                                +

                                Services may be interrupted.

                                +

                                Scheduled redeployment canceled

                                +

                                instance_redeploy_canceled

                                +

                                Major

                                +

                                As being affected by underlying hardware or system O&M, ECSs will be redeployed on new hosts as scheduled.

                                +

                                None

                                +

                                None

                                +

                                Scheduled redeployment being executed

                                +

                                instance_redeploy_executing

                                +

                                Major

                                +

                                As being affected by underlying hardware or system O&M, ECSs will be redeployed on new hosts as scheduled.

                                +

                                Wait until the event is complete and check whether services are affected.

                                +

                                Services are interrupted.

                                +

                                Scheduled redeployment completed

                                +

                                instance_redeploy_completed

                                +

                                Major

                                +

                                As being affected by underlying hardware or system O&M, ECSs will be redeployed on new hosts as scheduled.

                                +

                                Wait until the redeployed ECSs are available and check whether services are affected.

                                +

                                None

                                +

                                Scheduled redeployment failed

                                +

                                instance_redeploy_failed

                                +

                                Major

                                +

                                As being affected by underlying hardware or system O&M, ECSs will be redeployed on new hosts as scheduled.

                                +

                                Contact O&M personnel.

                                +

                                Services are interrupted.

                                +

                                Local disk replacement to be authorized

                                +

                                localdisk_recovery_inquiring

                                +

                                Major

                                +

                                Local disks are faulty.

                                +

                                Authorize local disk replacement.

                                +

                                Local disks are unavailable.

                                +

                                Local disks being replaced

                                +

                                localdisk_recovery_executing

                                +

                                Major

                                +

                                Local disk failure

                                +

                                Wait until the local disks are replaced and check whether the local disks are available.

                                +

                                Local disks are unavailable.

                                +

                                Local disks replaced

                                +

                                localdisk_recovery_completed

                                +

                                Major

                                +

                                Local disk failure

                                +

                                Wait until the services are running properly and check whether local disks are available.

                                +

                                None

                                +

                                Local disk replacement failed

                                +

                                localdisk_recovery_failed

                                +

                                Major

                                +

                                Local disks are faulty.

                                +

                                Contact O&M personnel.

                                +

                                Local disks are unavailable.

                                +

                                NPU: device not found by npu-smi info

                                +

                                NPUSMICardNotFound

                                +

                                Major

                                +

                                The Ascend driver is faulty or the NPU is disconnected.

                                +

                                Transfer this issue to the Ascend or hardware team for handling.

                                +

                                The NPU cannot be used normally.

                                +

                                NPU: PCIe link error

                                +

                                PCIeErrorFound

                                +

                                Major

                                +

                                The possible cause is deskew_fifo overflow, symbol_unlock, deskew_unlock event, or phystatus timeout.

                                +

                                Transfer this issue to the hardware team for handling.

                                +

                                The NPU cannot be used properly.

                                +

                                NPU: device not found by lspci

                                +

                                LspciCardNotFound

                                +

                                Major

                                +

                                The NPU is disconnected.

                                +

                                Transfer this issue to the hardware team for handling.

                                +

                                The NPU cannot be used normally.

                                +

                                NPU: overtemperature

                                +

                                TemperatureOverUpperLimit

                                +

                                Major

                                +

                                The temperature of DDR or software is too high.

                                +

                                Stop services, restart the BMS, check the heat dissipation system, and reset the devices.

                                +

                                The ECS may be powered off due to overtemperature and devices may not be found.

                                +

                                NPU: request for instance restart

                                +

                                RebootVirtualMachine

                                +

                                Informational

                                +

                                A fault occurs and the BMS needs to be restarted.

                                +

                                Collect the fault information, and restart the BMS.

                                +

                                Services may be interrupted.

                                +

                                NPU: request for SoC reset

                                +

                                ResetSOC

                                +

                                Informational

                                +

                                A fault occurs and the SoC needs to be reset.

                                +

                                Collect the fault information, and reset the SoC.

                                +

                                Services may be interrupted.

                                +

                                NPU: request for restart AI process

                                +

                                RestartAIProcess

                                +

                                Informational

                                +

                                A fault occurs and the AI process needs to be restarted.

                                +

                                Collect the fault information, and restart the AI process.

                                +

                                The current AI task will be interrupted.

                                +

                                NPU: error codes

                                +

                                NPUErrorCodeWarning

                                +

                                Major

                                +

                                A large number of NPU error codes indicating major or higher-level errors are returned. You can further locate the faults based on the error codes.

                                +

                                Locate the faults according to the Black Box Error Code Information List and Health Management Error Definition.

                                +

                                Services may be interrupted.

                                +

                                DAVP: die device node not found by vasmi

                                +

                                DAVPSMICardNotFound

                                +

                                Major

                                +

                                The driver may be faulty or the card may be disconnected.

                                +

                                Restart the VM. If the device still cannot be loaded, transfer this issue to the hardware team for handling.

                                +

                                The DAVP cannot be used properly.

                                +

                                DAVP: device not found by lspci

                                +

                                DAVPLspciCardNotFound

                                +

                                Major

                                +

                                The DAVP is disconnected.

                                +

                                Transfer this issue to the hardware team for handling.

                                +

                                The DAVP cannot be used properly.

                                +

                                DAVP: temperature higher than the threshold 85°C

                                +

                                TemperatureOverDfLimit

                                +

                                Major

                                +

                                The core module temperature exceeds 85°C, which causes frequency reduction.

                                +

                                Stop services. Contact the hardware team to check the heat dissipation system and reset the device.

                                +

                                The DAVP card frequency is reduced.

                                +

                                DAVP: temperature higher than the threshold 105°C

                                +

                                TemperatureOverSdLimit

                                +

                                Major

                                +

                                The core module temperature exceeds 105°C, which generates a high temperature alarm.

                                +

                                Stop services. Contact the hardware team to check the heat dissipation system and reset the device.

                                +

                                Power-off protection is triggered. The DAVP cannot be used properly.

                                +

                                DAVP: core unit exception of the device node

                                +

                                DeviceCoreAbnormal

                                +

                                Major

                                +

                                You may need to restart the die device node.

                                +

                                Collect the fault information and restart die.

                                +

                                Services may be interrupted.

                                +

                                VM deletion failure

                                +

                                faultDeleteServer

                                +

                                Major

                                +

                                Failed to delete the ECS.

                                +

                                Check whether services are affected.

                                +

                                The ECS resources fail to be deleted.

                                +

                                Failed to delete the ECS.

                                +

                                Check whether services are affected.
                                -

                                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.

                                +

                                Automatic recovery: If the hardware where an ECS is located is faulty, the system automatically migrates it to a normal physical host. The ECS will restart during the migration.

                                -
                                Table 2 Advanced Anti-DDoS (AAD)

                                Event Source

                                +
                                - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                                Table 2 Bare Metal Server (BMS)

                                Event Source

                                Namespace

                                +

                                Namespace

                                Event Name

                                +

                                Event Name

                                Event ID

                                +

                                Event ID

                                Event Severity

                                +

                                Event Severity

                                Description

                                +

                                Description

                                Solution

                                +

                                Solution

                                Impact

                                +

                                Impact

                                AAD

                                +

                                BMS

                                +

                                SYS.BMS

                                +

                                BMS restarted

                                +

                                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.

                                +

                                Unexpected restart

                                +

                                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.

                                +

                                BMS stopped

                                +

                                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.

                                +

                                Unexpected 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.

                                +

                                Network disconnection

                                +

                                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 fault

                                +

                                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.

                                +

                                EVS 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.

                                +

                                System maintenance inquiring

                                +

                                system_maintenance_inquiring

                                +

                                Major

                                +

                                The scheduled BMS maintenance task is being inquired.

                                +

                                Authorize the maintenance.

                                +

                                None

                                +

                                System maintenance waiting

                                +

                                system_maintenance_scheduled

                                +

                                Major

                                +

                                The scheduled BMS maintenance task is waiting to be executed.

                                +

                                Clarify the impact on services during the execution window.

                                +

                                None

                                +

                                System maintenance canceled

                                +

                                system_maintenance_canceled

                                +

                                Major

                                +

                                The scheduled BMS maintenance is canceled.

                                +

                                None

                                +

                                None

                                +

                                System maintenance executing

                                +

                                system_maintenance_executing

                                +

                                Major

                                +

                                BMSs are being maintained as scheduled.

                                +

                                After the maintenance is complete, check whether services are affected.

                                +

                                Services are interrupted.

                                +

                                System maintenance completed

                                +

                                system_maintenance_completed

                                +

                                Major

                                +

                                The scheduled BMS maintenance is completed.

                                +

                                Wait until the BMSs become available and check whether services recover.

                                +

                                None

                                +

                                System maintenance failure

                                +

                                system_maintenance_failed

                                +

                                Major

                                +

                                The scheduled BMS maintenance task failed.

                                +

                                Contact O&M personnel.

                                +

                                Services are interrupted.

                                +

                                NPU: device not found by npu-smi info

                                +

                                NPUSMICardNotFound

                                +

                                Major

                                +

                                The Ascend driver is faulty or the NPU is disconnected.

                                +

                                Transfer this issue to the Ascend or hardware team for handling.

                                +

                                The NPU cannot be used normally.

                                +

                                NPU: PCIe link error

                                +

                                PCIeErrorFound

                                +

                                Major

                                +

                                The lspci command returns rev ff indicating that the NPU is abnormal.

                                +

                                Restart the BMS. If the issue persists, transfer it to the hardware team for processing.

                                +

                                The NPU cannot be used normally.

                                +

                                NPU: device not found by lspci

                                +

                                LspciCardNotFound

                                +

                                Major

                                +

                                The NPU is disconnected.

                                +

                                Transfer this issue to the hardware team for handling.

                                +

                                The NPU cannot be used normally.

                                +

                                NPU: overtemperature

                                +

                                TemperatureOverUpperLimit

                                +

                                Major

                                +

                                The temperature of DDR or software is too high.

                                +

                                Stop services, restart the BMS, check the heat dissipation system, and reset the devices.

                                +

                                The BMS may be powered off and devices may not be found.

                                +

                                NPU: uncorrectable ECC error

                                +

                                UncorrectableEccErrorCount

                                +

                                Major

                                +

                                There are uncorrectable ECC errors on the NPU.

                                +

                                If services are affected, replace the NPU with another one.

                                +

                                Services may be interrupted.

                                +

                                NPU: request for BMS restart

                                +

                                RebootVirtualMachine

                                +

                                Informational

                                +

                                A fault occurs and the BMS needs to be restarted.

                                +

                                Collect the fault information, and restart the BMS.

                                +

                                Services may be interrupted.

                                +

                                NPU: request for SoC reset

                                +

                                ResetSOC

                                +

                                Informational

                                +

                                A fault occurs and the SoC needs to be reset.

                                +

                                Collect the fault information, and reset the SoC.

                                +

                                Services may be interrupted.

                                +

                                NPU: request for restart AI process

                                +

                                RestartAIProcess

                                +

                                Informational

                                +

                                A fault occurs and the AI process needs to be restarted.

                                +

                                Collect the fault information, and restart the AI process.

                                +

                                The current AI task will be interrupted.

                                +

                                NPU: error codes

                                +

                                NPUErrorCodeWarning

                                +

                                Major

                                +

                                A large number of NPU error codes indicating major or higher-level errors are returned. You can further locate the faults based on the error codes.

                                +

                                Locate the faults according to the Black Box Error Code Information List and Health Management Error Definition.

                                +

                                Services may be interrupted.

                                +

                                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.

                                +

                                nv_peer_mem loading error

                                +

                                NvPeerMemException

                                +

                                Minor

                                +

                                The NVLink or nv_peer_mem cannot be loaded.

                                +

                                Restore or reinstall the NVLink.

                                +

                                nv_peer_mem cannot be used.

                                +

                                Fabric Manager error

                                +

                                NvFabricManagerException

                                +

                                Minor

                                +

                                The BMS meets the NVLink conditions and NVLink is installed, but Fabric Manager is abnormal.

                                +

                                Restore or reinstall the NVLink.

                                +

                                NVLink cannot be used normally.

                                +

                                IB card error

                                +

                                InfinibandStatusException

                                +

                                Major

                                +

                                The IB card or its physical status is abnormal.

                                +

                                Transfer this issue to the hardware team for handling.

                                +

                                The IB card cannot work normally.

                                +

                                Local disk replacement to be authorized

                                +

                                localdisk_recovery_inquiring

                                +

                                Major

                                +

                                The local disk is faulty. Local disk replacement authorization is in progress.

                                +

                                Authorize local disk replacement.

                                +

                                Local disks are unavailable.

                                +

                                Local disks being replaced

                                +

                                localdisk_recovery_executing

                                +

                                Major

                                +

                                The local disk is faulty and is being replaced.

                                +

                                When the replacement is complete, check whether the local disks are available.

                                +

                                Local disks are unavailable.

                                +

                                Local disks replaced

                                +

                                localdisk_recovery_completed

                                +

                                Major

                                +

                                The local disk is faulty and is replaced.

                                +

                                Wait until the services are running properly and check whether local disks are available.

                                +

                                None

                                +

                                Local disk replacement failed

                                +

                                localdisk_recovery_failed

                                +

                                Major

                                +

                                The local disk is faulty and fails to be replaced.

                                +

                                Contact O&M personnel.

                                +

                                Local disks are unavailable.

                                +
                                +
                                + +
                                + + + + + + + + + + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                Table 3 Advanced Anti-DDoS (AAD)

                                Event Source

                                +

                                Namespace

                                +

                                Event Name

                                +

                                Event ID

                                +

                                Event Severity

                                +

                                Description

                                +

                                Solution

                                +

                                Impact

                                +

                                AAD

                                SYS.DDOS

                                +

                                SYS.DDOS

                                DDoS Attack Events

                                +

                                DDoS Attack Events

                                ddosAttackEvents

                                +

                                ddosAttackEvents

                                Major

                                +

                                Major

                                A DDoS attack occurs in the AAD protected lines.

                                +

                                A DDoS attack occurs in the AAD protected lines.

                                Judge the impact on services based on the attack traffic and attack type. If the attack traffic exceeds your purchased elastic bandwidth, change to another line or increase your bandwidth.

                                +

                                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.

                                +

                                Services may be interrupted.

                                Domain name scheduling event

                                +

                                Domain name scheduling event

                                domainNameDispatchEvents

                                +

                                domainNameDispatchEvents

                                Major

                                +

                                Major

                                The high-defense CNAME corresponding to the domain name is scheduled, and the domain name is resolved to another high-defense IP address.

                                +

                                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.

                                +

                                Pay attention to the workloads involving the domain name.

                                Services are not affected.

                                +

                                Services are not affected.

                                Blackhole event

                                +

                                Blackhole event

                                blackHoleEvents

                                +

                                blackHoleEvents

                                Major

                                +

                                Major

                                The attack traffic exceeds the purchased AAD protection threshold.

                                +

                                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.

                                +

                                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.

                                +

                                Services may be interrupted.

                                Cancel Blackhole

                                +

                                Cancel Blackhole

                                cancelBlackHole

                                +

                                cancelBlackHole

                                Informational

                                +

                                Informational

                                The customer's AAD instance recovers from the black hole state.

                                +

                                The customer's AAD instance recovers from the black hole state.

                                This is only a prompt and no action is required.

                                +

                                This is only a prompt and no action is required.

                                Customer services recover.

                                +

                                Customer services recover.

                                IP address scheduling triggered

                                +

                                IP address scheduling triggered

                                ipDispatchEvents

                                +

                                ipDispatchEvents

                                Major

                                +

                                Major

                                IP route changed

                                +

                                IP route changed

                                Check the workloads of the IP address.

                                +

                                Check the workloads of the IP address.

                                Services are not affected.

                                +

                                Services are not affected.
                                -
                                Table 3 Elastic Load Balance (ELB)

                                Event Source

                                +
                                - - - - - - - - - - - - - - - - - - - - -
                                Table 4 Elastic Load Balance (ELB)

                                Event Source

                                Namespace

                                +

                                Namespace

                                Event Name

                                +

                                Event Name

                                Event ID

                                +

                                Event ID

                                Event Severity

                                +

                                Event Severity

                                Description

                                +

                                Description

                                Solution

                                +

                                Solution

                                Impact

                                +

                                Impact

                                ELB

                                +

                                ELB

                                SYS.ELB

                                +

                                SYS.ELB

                                The backend servers are unhealthy.

                                +

                                The backend servers are unhealthy.

                                healthCheckUnhealthy

                                +

                                healthCheckUnhealthy

                                Major

                                +

                                Major

                                Generally, this problem occurs because backend server services are offline. This event will not be reported after it is reported for several times.

                                +

                                Generally, this problem occurs because backend server services are offline. This event will not be reported after it is reported for several times.

                                Ensure that the backend servers are running properly.

                                +

                                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.

                                +

                                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.

                                The backend server is detected healthy.

                                +

                                The backend server is detected healthy.

                                healthCheckRecovery

                                +

                                healthCheckRecovery

                                Minor

                                +

                                Minor

                                The backend server is detected healthy.

                                +

                                The backend server is detected healthy.

                                No further action is required.

                                +

                                No further action is required.

                                The load balancer can properly route requests to the backend server.

                                +

                                The load balancer can properly route requests to the backend server.
                                -
                                Table 4 Cloud Backup and Recovery (CBR)

                                Event Source

                                +
                                - - - - - - + - - - - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                Table 5 Cloud Backup and Recovery (CBR)

                                Event Source

                                Event Name

                                +

                                Namespace

                                Event ID

                                +

                                Event Name

                                Event Severity

                                +

                                Event ID

                                Description

                                +

                                Event Severity

                                Solution

                                +

                                Description

                                Impact

                                +

                                Solution

                                +

                                Impact

                                CBR

                                +

                                CBR

                                Failed to create the backup.

                                +

                                SYS.CBR

                                +

                                +

                                +

                                +

                                +

                                +

                                +

                                +

                                +

                                +

                                +

                                backupFailed

                                +

                                Failed to create the backup.

                                Critical

                                +

                                backupFailed

                                The backup failed to be created.

                                +

                                Critical

                                Manually create a backup or contact customer service.

                                +

                                The backup failed to be created.

                                Data loss may occur.

                                +

                                Manually create a backup or contact customer service.

                                +

                                Data loss may occur.

                                Failed to restore the resource using a backup.

                                +

                                Failed to restore the resource using a backup.

                                restorationFailed

                                +

                                restorationFailed

                                Critical

                                +

                                Critical

                                The resource failed to be restored using a backup.

                                +

                                The resource failed to be restored using a backup.

                                Restore the resource using another backup or contact customer service.

                                +

                                Restore the resource using another backup or contact customer service.

                                Data loss may occur.

                                +

                                Data loss may occur.

                                Failed to delete the backup.

                                +

                                Failed to delete the backup.

                                backupDeleteFailed

                                +

                                backupDeleteFailed

                                Critical

                                +

                                Critical

                                The backup failed to be deleted.

                                +

                                The backup failed to be deleted.

                                Try again later or contact customer service.

                                +

                                Try again later or contact customer service.

                                Charging may be abnormal.

                                +

                                Charging may be abnormal.

                                Failed to delete the vault.

                                +

                                Failed to delete the vault.

                                vaultDeleteFailed

                                +

                                vaultDeleteFailed

                                Critical

                                +

                                Critical

                                The vault failed to be deleted.

                                +

                                The vault failed to be deleted.

                                Try again later or contact technical support.

                                +

                                Try again later or contact technical support.

                                Charging may be abnormal.

                                +

                                Charging may be abnormal.

                                Replication failure

                                +

                                Replication failure

                                replicationFailed

                                +

                                replicationFailed

                                Critical

                                +

                                Critical

                                The backup failed to be replicated.

                                +

                                The backup failed to be replicated.

                                Try again later or contact technical support.

                                +

                                Try again later or contact technical support.

                                Data loss may occur.

                                +

                                Data loss may occur.

                                The backup is created successfully.

                                +

                                The backup is created successfully.

                                backupSucceeded

                                +

                                backupSucceeded

                                Major

                                +

                                Major

                                The backup was created.

                                +

                                The backup was created.

                                None

                                +

                                None

                                None

                                +

                                None

                                Resource restoration using a backup succeeded.

                                +

                                Resource restoration using a backup succeeded.

                                restorationSucceeded

                                +

                                restorationSucceeded

                                Major

                                +

                                Major

                                The resource was restored using a backup.

                                +

                                The resource was restored using a backup.

                                Check whether the data is successfully restored.

                                +

                                Check whether the data is successfully restored.

                                None

                                +

                                None

                                The backup is deleted successfully.

                                +

                                The backup is deleted successfully.

                                backupDeletionSucceeded

                                +

                                backupDeletionSucceeded

                                Major

                                +

                                Major

                                The backup was deleted.

                                +

                                The backup was deleted.

                                None

                                +

                                None

                                None

                                +

                                None

                                The vault is deleted successfully.

                                +

                                The vault is deleted successfully.

                                vaultDeletionSucceeded

                                +

                                vaultDeletionSucceeded

                                Major

                                +

                                Major

                                The vault was deleted.

                                +

                                The vault was deleted.

                                None

                                +

                                None

                                None

                                +

                                None

                                Replication success

                                +

                                Replication success

                                replicationSucceeded

                                +

                                replicationSucceeded

                                Major

                                +

                                Major

                                The backup was replicated successfully.

                                +

                                The backup was replicated successfully.

                                None

                                +

                                None

                                None

                                +

                                None

                                Client offline

                                +

                                Client offline

                                agentOffline

                                +

                                agentOffline

                                Critical

                                +

                                Critical

                                The backup client was offline.

                                +

                                The backup client was offline.

                                Ensure that the Agent status is normal and the backup client can be connected to .

                                +

                                Ensure that the Agent status is normal and the backup client can be connected to .

                                Backup tasks may fail.

                                +

                                Backup tasks may fail.

                                Client online

                                +

                                Client online

                                agentOnline

                                +

                                agentOnline

                                Major

                                +

                                Major

                                The backup client was online.

                                +

                                The backup client was online.

                                None

                                +

                                None

                                None

                                +

                                None
                                -
                                Table 5 Relational Database Service (RDS) — resource exception

                                Event Source

                                +
                                - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                Table 6 Relational Database Service (RDS) — resource exception

                                Event Source

                                Namespace

                                +

                                Namespace

                                Event Name

                                +

                                Event Name

                                Event ID

                                +

                                Event ID

                                Event Severity

                                +

                                Event Severity

                                Description

                                +

                                Description

                                Solution

                                +

                                Solution

                                Impact

                                +

                                Impact

                                RDS

                                +

                                RDS

                                +

                                +

                                +

                                +

                                +

                                SYS.RDS

                                +

                                SYS.RDS

                                +

                                +

                                +

                                +

                                +

                                DB instance creation failure

                                +

                                DB instance creation failure

                                createInstanceFailed

                                +

                                createInstanceFailed

                                Major

                                +

                                Major

                                Generally, the cause is that the number of disks is insufficient due to quota limits, or underlying resources are exhausted.

                                +

                                Generally, the cause is that the number of disks is insufficient due to quota limits, or underlying resources are exhausted.

                                The selected resource specifications are insufficient. Select other available specifications and try again.

                                +

                                The selected resource specifications are insufficient. Select other available specifications and try again.

                                DB instances cannot be created.

                                +

                                DB instances cannot be created.

                                Full backup failure

                                +

                                Full backup failure

                                fullBackupFailed

                                +

                                fullBackupFailed

                                Major

                                +

                                Major

                                A single full backup failure does not affect the files that have been successfully backed up, but prolong the incremental backup time during the point-in-time restore (PITR).

                                +

                                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).

                                Try again.

                                +

                                Try again.

                                Restoration using backups will be affected.

                                +

                                Full backup failed.

                                Read replica promotion failure

                                +

                                Read replica promotion failure

                                activeStandBySwitchFailed

                                +

                                activeStandBySwitchFailed

                                Major

                                +

                                Major

                                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.

                                +

                                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.

                                Perform the operation again during off-peak hours.

                                +

                                Perform the switchover again during off-peak hours.

                                Read replica promotion failed.

                                +

                                The primary/standby switchover will fail.

                                Replication status abnormal

                                +

                                Replication status abnormal

                                abnormalReplicationStatus

                                +

                                abnormalReplicationStatus

                                Major

                                +

                                Major

                                The possible causes are as follows:

                                +

                                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.

                                The issue is being fixed. Please wait for our notifications.

                                +

                                Database replication is being repaired. You will be notified immediately after the repair.

                                The replication status is abnormal.

                                +

                                The replication status is abnormal.

                                Replication status recovered

                                +

                                Replication status recovered

                                replicationStatusRecovered

                                +

                                replicationStatusRecovered

                                Major

                                +

                                Major

                                The replication delay between the primary and standby instances is within the normal range, or the network connection between them has restored.

                                +

                                The replication delay between the primary and standby instances is within the normal range, or the network connection between them has restored.

                                Check whether services are running properly.

                                +

                                Check whether services are running properly.

                                Replication status is recovered.

                                +

                                Replication status is recovered.

                                DB instance faulty

                                +

                                DB instance faulty

                                faultyDBInstance

                                +

                                faultyDBInstance

                                Major

                                +

                                Major

                                A single or primary DB instance was faulty due to a catastrophic failure, for example, server failure.

                                +

                                A single or primary DB instance was faulty due to a catastrophic failure, for example, server failure.

                                The issue is being fixed. Please wait for our notifications.

                                +

                                Instance status is being repaired. You will be notified immediately after the repair.

                                The instance status is abnormal.

                                +

                                The instance status is abnormal.

                                DB instance recovered

                                +

                                DB instance recovered

                                DBInstanceRecovered

                                +

                                DBInstanceRecovered

                                Major

                                +

                                Major

                                RDS rebuilds the standby DB instance with its high availability. After the instance is rebuilt, this event will be reported.

                                +

                                RDS rebuilds the standby DB instance with its high availability. After the instance is rebuilt, this event will be reported.

                                The DB instance status is normal. Check whether services are running properly.

                                +

                                The DB instance status is normal. Check whether services are running properly.

                                The instance is recovered.

                                +

                                The instance is recovered.

                                Failure of changing single DB instance to primary/standby

                                +

                                Failure of changing single DB instance to primary/standby

                                singleToHaFailed

                                +

                                singleToHaFailed

                                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.

                                +

                                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.

                                Automatic retry is in progress.

                                +

                                Automatic retry is in progress.

                                Changing a single DB instance to primary/standby failed.

                                +

                                Changing a single DB instance to primary/standby failed.

                                Database process restarted

                                +

                                Database process restarted

                                DatabaseProcessRestarted

                                +

                                DatabaseProcessRestarted

                                Major

                                +

                                Major

                                The database process is stopped due to insufficient memory or high load.

                                +

                                The database process is stopped due to insufficient memory or high load.

                                Check whether services are running properly.

                                +

                                Check whether services are running properly.

                                The primary instance is restarted. Services are interrupted for a short period of time.

                                +

                                The primary instance is restarted. Services are interrupted for a short period of time.

                                Instance storage full

                                +

                                Instance storage full

                                instanceDiskFull

                                +

                                instanceDiskFull

                                Major

                                +

                                Major

                                Generally, the cause is that the data space usage is too high.

                                +

                                Generally, the cause is that the data space usage is too high.

                                Scale up the storage.

                                +

                                Scale up the storage.

                                The instance storage is used up. No data can be written into databases.

                                +

                                The instance storage is used up. No data can be written into databases.

                                Instance storage full recovered

                                +

                                Instance storage full recovered

                                instanceDiskFullRecovered

                                +

                                instanceDiskFullRecovered

                                Major

                                +

                                Major

                                The instance disk is recovered.

                                +

                                The instance disk is recovered.

                                Check whether services are running properly.

                                +

                                Check whether services are running properly.

                                The instance has available storage.

                                +

                                The instance has available storage.

                                Kafka connection failed

                                +

                                Kafka connection failed

                                kafkaConnectionFailed

                                +

                                kafkaConnectionFailed

                                Major

                                +

                                Major

                                The network is unstable or the Kafka server does not work properly.

                                +

                                The network is unstable or the Kafka server does not work properly.

                                Check whether services are affected.

                                +

                                Check whether services are affected.

                                None

                                +

                                None
                                -
                                Table 6 Document Database Service (DDS)

                                Event Source

                                +
                                - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                Table 7 Document Database Service (DDS)

                                Event Source

                                Namespace

                                +

                                Namespace

                                Event Name

                                +

                                Event Name

                                Event ID

                                +

                                Event ID

                                Event Severity

                                +

                                Event Severity

                                Description

                                +

                                Description

                                Solution

                                +

                                Solution

                                Impact

                                +

                                Impact

                                DDS

                                +

                                DDS

                                SYS.DDS

                                +

                                SYS.DDS

                                DB instance creation failure

                                +

                                DB instance creation failure

                                DDSCreateInstanceFailed

                                +

                                DDSCreateInstanceFailed

                                Major

                                +

                                Major

                                A DDS instance fails to be created due to insufficient disks, quotas, and underlying resources.

                                +

                                A DDS instance fails to be created due to insufficient disks, quotas, and underlying resources.

                                Check the number and quota of disks. Release resources and create DDS instances again.

                                +

                                Check the number and quota of disks. Release resources and create DDS instances again.

                                DDS instances cannot be created.

                                +

                                DDS instances cannot be created.

                                Replication failed

                                +

                                Replication failed

                                DDSAbnormalReplicationStatus

                                +

                                DDSAbnormalReplicationStatus

                                Major

                                +

                                Major

                                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.

                                +

                                The possible causes are as follows:

                                +
                                1. 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.
                                2. The network between the primary instance and the standby instance or a read replica is disconnected.

                                Submit a service ticket.

                                +

                                Submit a service ticket.

                                Your applications are not affected because this event does not interrupt data read and write.

                                +
                                1. Read and write operations on the original instance are not interrupted, but data updates on the standby instance may experience delays.
                                2. The replication delay keeps growing between the primary and standby instances, and the standby instance may be disconnected.

                                Replication recovered

                                +

                                Replication status recovered

                                DDSReplicationStatusRecovered

                                +

                                DDSReplicationStatusRecovered

                                Major

                                +

                                Major

                                The replication delay between the primary and standby instances is within the normal range, or the network connection between them has restored.

                                +

                                The replication delay between the primary and standby instances is within the normal range, or the network connection between them has restored.

                                No action is required.

                                +

                                No action is required.

                                None

                                +

                                None

                                DB instance failed

                                +

                                DB instance failed

                                DDSFaultyDBInstance

                                +

                                DDSFaultyDBInstance

                                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

                                DDSDBInstanceRecovered

                                +

                                DDSDBInstanceRecovered

                                Major

                                +

                                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.

                                +

                                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.

                                +

                                No action is required.

                                None

                                +

                                None

                                Faulty node

                                +

                                Faulty node

                                DDSFaultyDBNode

                                +

                                DDSFaultyDBNode

                                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.

                                Node recovered

                                +

                                Node recovered

                                DDSDBNodeRecovered

                                +

                                DDSDBNodeRecovered

                                Major

                                +

                                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.

                                +

                                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.

                                +

                                No action is required.

                                None

                                +

                                None

                                Primary/standby switchover or failover

                                +

                                Primary/standby switchover or failover

                                DDSPrimaryStandbySwitched

                                +

                                DDSPrimaryStandbySwitched

                                Major

                                +

                                Major

                                A primary/standby switchover is performed or a failover is triggered.

                                +

                                This event is reported when a primary/secondary switchover or failover is triggered.

                                No action is required.

                                +

                                No action is required.

                                None

                                +

                                None

                                Insufficient storage space

                                +

                                Insufficient storage space

                                DDSRiskyDataDiskUsage

                                +

                                DDSRiskyDataDiskUsage

                                Major

                                +

                                Major

                                The storage space is insufficient.

                                +

                                The storage space is insufficient.

                                Scale up storage space. For details, see section "Scaling Up Storage Space" in the corresponding user guide.

                                +

                                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.

                                +

                                The instance is set to read-only and data cannot be written to the instance.

                                Data disk expanded and being writable

                                +

                                Data disk expanded and being writable

                                DDSDataDiskUsageRecovered

                                +

                                DDSDataDiskUsageRecovered

                                Major

                                +

                                Major

                                The capacity of a data disk has been expanded and the data disk becomes writable.

                                +

                                The capacity of a data disk has been expanded and the data disk becomes writable.

                                No further action is required.

                                +

                                No further action is required.

                                No adverse impact.

                                +

                                No adverse impact.

                                Schedule for deleting a KMS key

                                +

                                Schedule for deleting a KMS key

                                DDSplanDeleteKmsKey

                                +

                                planDeleteKmsKey

                                Major

                                +

                                Major

                                A request to schedule deletion of a KMS key was submitted.

                                +

                                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 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.

                                +

                                After the KMS key is deleted, users cannot encrypt disks.
                                -
                                Table 7 GaussDB(for MySQL)

                                Event Source

                                +
                                - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                                Table 8 GeminiDB

                                Event Source

                                Namespace

                                +

                                Namespace

                                Event Name

                                +

                                Event Name

                                Event ID

                                +

                                Event ID

                                Event Severity

                                +

                                Event Severity

                                Description

                                +

                                Description

                                Solution

                                +

                                Solution

                                Impact

                                +

                                Impact

                                GaussDB(for MySQL)

                                +

                                GeminiDB

                                +

                                +

                                SYS.GAUSSDB

                                +

                                SYS.NoSQL

                                +

                                +

                                +

                                DB instance creation failed

                                +

                                NoSQLCreateInstanceFailed

                                +

                                Major

                                +

                                The instance quota or underlying resources are insufficient.

                                +

                                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.

                                +

                                Specifications modification failed

                                +

                                NoSQLResizeInstanceFailed

                                +

                                Major

                                +

                                The underlying resources are insufficient.

                                +

                                Submit a service ticket. The O&M personnel will coordinate resources in the background, and then you need to change the specifications again.

                                +

                                Services are interrupted.

                                +

                                Node adding failed

                                +

                                NoSQLAddNodesFailed

                                +

                                Major

                                +

                                The underlying resources are insufficient.

                                +

                                Submit a service ticket. The O&M personnel will coordinate resources in the background, and then you delete the node that failed to be added and add a new node.

                                +

                                None

                                +

                                Node deletion failed

                                +

                                NoSQLDeleteNodesFailed

                                +

                                Major

                                +

                                The underlying resources fail to be released.

                                +

                                Delete the node again.

                                +

                                None

                                +

                                Storage space scale-up failed

                                +

                                +

                                NoSQLScaleUpStorageFailed

                                +

                                Major

                                +

                                The underlying resources are insufficient.

                                +

                                Submit a service ticket. The O&M personnel will coordinate resources in the background and then you scale up the storage space again.

                                +

                                Services may be interrupted.

                                +

                                Password reset failed

                                +

                                NoSQLResetPasswordFailed

                                +

                                Major

                                +

                                Resetting the password times out.

                                +

                                Reset the password again.

                                +

                                None

                                +

                                Parameter group change failed

                                +

                                NoSQLUpdateInstanceParamGroupFailed

                                +

                                Major

                                +

                                Changing a parameter group times out.

                                +

                                Change the parameter group again.

                                +

                                None

                                +

                                Backup policy configuration failed

                                +

                                NoSQLSetBackupPolicyFailed

                                +

                                Major

                                +

                                The database connection is abnormal.

                                +

                                Configure the backup policy again.

                                +

                                None

                                +

                                Manual backup creation failed

                                +

                                NoSQLCreateManualBackupFailed

                                +

                                Major

                                +

                                The backup files fail to be exported or uploaded.

                                +

                                Submit a service ticket to the O&M personnel.

                                +

                                Data cannot be backed up.

                                +

                                Automated backup creation failed

                                +

                                NoSQLCreateAutomatedBackupFailed

                                +

                                Major

                                +

                                The backup files fail to be exported or uploaded.

                                +

                                Submit a service ticket to the O&M personnel.

                                +

                                Data cannot be backed up.

                                +

                                Faulty DB instance

                                +

                                NoSQLFaultyDBInstance

                                +

                                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

                                +

                                NoSQLDBInstanceRecovered

                                +

                                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

                                +

                                NoSQLFaultyDBNode

                                +

                                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

                                +

                                NoSQLDBNodeRecovered

                                +

                                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

                                +

                                NoSQLPrimaryStandbySwitched

                                +

                                Major

                                +

                                This event is reported when a primary/secondary switchover or failover is triggered.

                                +

                                No action is required.

                                +

                                None

                                +

                                HotKey occurred

                                +

                                HotKeyOccurs

                                +

                                Major

                                +

                                The primary key is improperly configured. As a result, hotspot data is distributed in one partition. The improper application design causes frequent read and write operations on a key.

                                +

                                1. Choose a proper partition key.

                                +

                                2. Add service cache. The service application reads hotspot data from the cache first.

                                +

                                The service request success rate is affected, and the cluster performance and stability also be affected.

                                +

                                BigKey occurred

                                +

                                BigKeyOccurs

                                +

                                Major

                                +

                                The primary key design is improper. The number of records or data in a single partition is too large, causing unbalanced node loads.

                                +

                                1. Choose a proper partition key.

                                +

                                2. Add a new partition key for hashing data.

                                +

                                As the data in the large partition increases, the cluster stability deteriorates.

                                +

                                Insufficient storage space

                                +

                                NoSQLRiskyDataDiskUsage

                                +

                                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

                                +

                                NoSQLDataDiskUsageRecovered

                                +

                                Major

                                +

                                The capacity of a data disk has been expanded and the data disk becomes writable.

                                +

                                No operation is required.

                                +

                                None

                                +

                                Index creation failed

                                +

                                NoSQLCreateIndexFailed

                                +

                                Major

                                +

                                The service load exceeds what the instance specifications can take. In this case, creating indexes consumes more instance resources. As a result, the response is slow or even frame freezing occurs, and the creation times out.

                                +

                                Select the matched instance specifications based on the service load.

                                +

                                Create indexes during off-peak hours.

                                +

                                Create indexes in the background.

                                +

                                Select indexes as required.

                                +

                                The index fails to be created or is incomplete. As a result, the index is invalid. Delete the index and create an index.

                                +

                                Write speed decreased

                                +

                                NoSQLStallingOccurs

                                +

                                Major

                                +

                                The write speed is fast, which is close to the maximum write capability allowed by the cluster scale and instance specifications. As a result, the flow control mechanism of the database is triggered, and requests may fail.

                                +

                                1. Adjust the cluster scale or node specifications based on the maximum write rate of services.

                                +

                                2. Measures the maximum write rate of services.

                                +

                                The success rate of service requests is affected.

                                +

                                Data write stopped

                                +

                                NoSQLStoppingOccurs

                                +

                                Major

                                +

                                The data write is too fast, reaching the maximum write capability allowed by the cluster scale and instance specifications. As a result, the flow control mechanism of the database is triggered, and requests may fail.

                                +

                                1. Adjust the cluster scale or node specifications based on the maximum write rate of services.

                                +

                                2. Measures the maximum write rate of services.

                                +

                                The success rate of service requests is affected.

                                +

                                Database restart failed

                                +

                                NoSQLRestartDBFailed

                                +

                                Major

                                +

                                The instance status is abnormal.

                                +

                                Submit a service ticket to the O&M personnel.

                                +

                                The DB instance status may be abnormal.

                                +

                                Restoration to new DB instance failed

                                +

                                NoSQLRestoreToNewInstanceFailed

                                +

                                Major

                                +

                                The underlying resources are insufficient.

                                +

                                Submit a service order to ask the O&M personnel to coordinate resources in the background and add new nodes.

                                +

                                Data cannot be restored to a new DB instance.

                                +

                                Restoration to existing DB instance failed

                                +

                                NoSQLRestoreToExistInstanceFailed

                                +

                                Major

                                +

                                The backup file fails to be downloaded or restored.

                                +

                                Submit a service ticket to the O&M personnel.

                                +

                                The current DB instance may be unavailable.

                                +

                                Backup file deletion failed

                                +

                                NoSQLDeleteBackupFailed

                                +

                                Major

                                +

                                The backup files fail to be deleted from OBS.

                                +

                                Delete the backup files again.

                                +

                                None

                                +

                                Failed to enable Show Original Log

                                +

                                NoSQLSwitchSlowlogPlainTextFailed

                                +

                                Major

                                +

                                The DB engine does not support this function.

                                +

                                Refer to the GaussDB NoSQL User Guide to ensure that the DB engine supports Show Original Log. Submit a service ticket to the O&M personnel.

                                +

                                None

                                +

                                EIP binding failed

                                +

                                NoSQLBindEipFailed

                                +

                                Major

                                +

                                The node status is abnormal, an EIP has been bound to the node, or the EIP to be bound is invalid.

                                +

                                Check whether the node is normal and whether the EIP is valid.

                                +

                                The DB instance cannot be accessed from the Internet.

                                +

                                EIP unbinding failed

                                +

                                NoSQLUnbindEipFailed

                                +

                                Major

                                +

                                The node status is abnormal or the EIP has been unbound from the node.

                                +

                                Check whether the node and EIP status are normal.

                                +

                                None

                                +

                                Parameter modification failed

                                +

                                NoSQLModifyParameterFailed

                                +

                                Major

                                +

                                The parameter value is invalid.

                                +

                                Check whether the parameter value is within the valid range and submit a service ticket to the O&M personnel.

                                +

                                None

                                +

                                Parameter group application failed

                                +

                                NoSQLApplyParameterGroupFailed

                                +

                                Major

                                +

                                The instance status is abnormal. As a result, the parameter group cannot be applied.

                                +

                                Submit a service ticket to the O&M personnel.

                                +

                                None

                                +

                                Failed to enable or disable SSL

                                +

                                NoSQLSwitchSSLFailed

                                +

                                Major

                                +

                                Enabling or disabling SSL times out.

                                +

                                Try again or submit a service ticket. Do not change the connection mode.

                                +

                                The connection mode cannot be changed.

                                +

                                Row size too large

                                +

                                LargeRowOccurs

                                +

                                Major

                                +

                                If there is too much data in a single row, queries may time out, causing faults like OOM error.

                                +

                                1. Control the length of each column and row so that the sum of key and value lengths in each row does not exceed the preset threshold.

                                +

                                2. Check whether there are invalid writes or encoding resulting in large keys or values.

                                +

                                If there are rows that are too large, the cluster performance will deteriorate as the data volume grows.

                                +

                                Schedule for deleting a KMS key

                                +

                                planDeleteKmsKey

                                +

                                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.

                                +

                                Too many query tombstones

                                +

                                TooManyQueryTombstones

                                +

                                Major

                                +

                                If there are too many query tombstones, queries may time out, affecting query performance.

                                +

                                Select right query and deleting methods and avoid long range queries.

                                +

                                Queries may time out, affecting query performance.

                                +

                                Too large collection column

                                +

                                TooLargeCollectionColumn

                                +

                                Major

                                +

                                If there are too many elements in a collection column, queries to the column will fail.

                                +
                                1. Limit elements in a collection column.
                                2. Check for abnormal writes or coding at the service side.
                                +

                                Queries to the collection column will fail.

                                +

                                GeminiDB Influx instance connection limit reached

                                +

                                InfluxDBConnectionFull

                                +

                                Major

                                +

                                The connections on the instance node reach the upper limit.

                                +

                                1. Upgrade specifications if they cannot meet service requirements.

                                +

                                2. Check whether the client properly manages connections, for example, whether there are unreleased or long connections.

                                +

                                If no new connection can be created on a node, the client may fail to connect to a GeminiDB Influx instance. As a result, services may become instable.

                                +

                                High availability switchover

                                +

                                nodeHaSwitch

                                +

                                Major

                                +

                                The high availability switchover is triggered by underlying network jitters.

                                +

                                Check whether the business is normal and it can be restored automatically.

                                +

                                The network jitter causes a few seconds of delay.

                                +
                                +
                                + +
                                + + + + + + + + + + + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                Table 9 TaurusDB

                                Event Source

                                +

                                Namespace

                                +

                                Event Name

                                +

                                Event ID

                                +

                                Event Severity

                                +

                                Description

                                +

                                Solution

                                +

                                Impact

                                +

                                TaurusDB

                                +

                                SYS.GAUSSDB

                                Incremental backup failure

                                +

                                Incremental backup failure

                                TaurusIncrementalBackupInstanceFailed

                                +

                                TaurusIncrementalBackupInstanceFailed

                                Major

                                +

                                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.

                                +

                                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.

                                +

                                Submit a service ticket.

                                Backup jobs fail.

                                +

                                Backup jobs fail.

                                Read replica creation failure

                                +

                                Read replica creation failure

                                addReadonlyNodesFailed

                                +

                                addReadonlyNodesFailed

                                Major

                                +

                                Major

                                The quota is insufficient or underlying resources are exhausted.

                                +

                                The quota is insufficient or underlying resources are exhausted.

                                Check the read replica quota. Release resources and create read replicas again.

                                +

                                Check the read replica quota. Release resources and create read replicas again.

                                Read replicas fail to be created.

                                +

                                Read replicas fail to be created.

                                DB instance creation failure

                                +

                                DB instance creation failure

                                createInstanceFailed

                                +

                                createInstanceFailed

                                Major

                                +

                                Major

                                The instance quota or underlying resources are insufficient.

                                +

                                The instance quota or underlying resources are insufficient.

                                Check the instance quota. Release resources and create instances again.

                                +

                                Check the instance quota. Release resources and create instances again.

                                DB instances fail to be created.

                                +

                                DB instances fail to be created.

                                Read replica promotion failure

                                +

                                Read replica promotion failure

                                activeStandBySwitchFailed

                                +

                                activeStandBySwitchFailed

                                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 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.

                                +

                                Submit a service ticket.

                                The read replica fails to be promoted to the primary node.

                                +

                                The read replica fails to be promoted to the primary node.

                                Instance specifications change failure

                                +

                                Instance specifications change failure

                                flavorAlterationFailed

                                +

                                flavorAlterationFailed

                                Major

                                +

                                Major

                                The quota is insufficient or underlying resources are exhausted.

                                +

                                The quota is insufficient or underlying resources are exhausted.

                                Submit a service ticket.

                                +

                                Submit a service ticket.

                                Instance specifications fail to be changed.

                                +

                                Instance specifications fail to be changed.

                                Faulty DB instance

                                +

                                Faulty DB instance

                                TaurusInstanceRunningStatusAbnormal

                                +

                                TaurusInstanceRunningStatusAbnormal

                                Major

                                +

                                Major

                                The instance process is faulty or the communications between the instance and the DFV storage are abnormal.

                                +

                                The instance process is faulty or the communications between the instance and the DFV storage are abnormal.

                                Submit a service ticket.

                                +

                                Submit a service ticket.

                                Services may be affected.

                                +

                                Services may be affected.

                                DB instance recovered

                                +

                                DB instance recovered

                                TaurusInstanceRunningStatusRecovered

                                +

                                TaurusInstanceRunningStatusRecovered

                                Major

                                +

                                Major

                                The instance is recovered.

                                +

                                The instance is recovered.

                                Observe the service running status.

                                +

                                Observe the service running status.

                                None

                                +

                                None

                                Faulty node

                                +

                                Faulty node

                                TaurusNodeRunningStatusAbnormal

                                +

                                TaurusNodeRunningStatusAbnormal

                                Major

                                +

                                Major

                                The node process is faulty or the communications between the node and the DFV storage are abnormal.

                                +

                                The node process is faulty or the communications between the node and the DFV storage are abnormal.

                                Observe the instance and service running statuses.

                                +

                                Observe the instance and service running statuses.

                                A read replica may be promoted to the primary node.

                                +

                                A read replica may be promoted to the primary node.

                                Node recovered

                                +

                                Node recovered

                                TaurusNodeRunningStatusRecovered

                                +

                                TaurusNodeRunningStatusRecovered

                                Major

                                +

                                Major

                                The node is recovered.

                                +

                                The node is recovered.

                                Observe the service running status.

                                +

                                Observe the service running status.

                                None

                                +

                                None

                                Read replica deletion failure

                                +

                                Read replica deletion failure

                                TaurusDeleteReadOnlyNodeFailed

                                +

                                TaurusDeleteReadOnlyNodeFailed

                                Major

                                +

                                Major

                                The communications between the management plane and the read replica are abnormal or the VM fails to be deleted from IaaS.

                                +

                                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.

                                +

                                Submit a service ticket.

                                Read replicas fail to be deleted.

                                +

                                Read replicas fail to be deleted.

                                Password reset failure

                                +

                                Password reset failure

                                TaurusResetInstancePasswordFailed

                                +

                                TaurusResetInstancePasswordFailed

                                Major

                                +

                                Major

                                The communications between the management plane and the instance are abnormal or the instance is abnormal.

                                +

                                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.

                                +

                                Check the instance status and try again. If the fault persists, submit a service ticket.

                                Passwords fail to be reset for instances.

                                +

                                Passwords fail to be reset for instances.

                                DB instance reboot failure

                                +

                                DB instance reboot failure

                                TaurusRestartInstanceFailed

                                +

                                TaurusRestartInstanceFailed

                                Major

                                +

                                Major

                                The network between the management plane and the instance is abnormal or the instance is abnormal.

                                +

                                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.

                                +

                                Check the instance status and try again. If the fault persists, submit a service ticket.

                                Instances fail to be rebooted.

                                +

                                Instances fail to be rebooted.

                                Restoration to new DB instance failure

                                +

                                Restoration to new DB instance failure

                                TaurusRestoreToNewInstanceFailed

                                +

                                TaurusRestoreToNewInstanceFailed

                                Major

                                +

                                Major

                                The instance quota is insufficient, underlying resources are exhausted, or the data restoration logic is incorrect.

                                +

                                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.

                                +

                                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.

                                +

                                Backup data fails to be restored to new instances.

                                EIP binding failure

                                +

                                EIP binding failure

                                TaurusBindEIPToInstanceFailed

                                +

                                TaurusBindEIPToInstanceFailed

                                Major

                                +

                                Major

                                The binding task fails.

                                +

                                The binding task fails.

                                Submit a service ticket.

                                +

                                Submit a service ticket.

                                EIPs fail to be bound to instances.

                                +

                                EIPs fail to be bound to instances.

                                EIP unbinding failure

                                +

                                EIP unbinding failure

                                TaurusUnbindEIPFromInstanceFailed

                                +

                                TaurusUnbindEIPFromInstanceFailed

                                Major

                                +

                                Major

                                The unbinding task fails.

                                +

                                The unbinding task fails.

                                Submit a service ticket.

                                +

                                Submit a service ticket.

                                EIPs fail to be unbound from instances.

                                +

                                EIPs fail to be unbound from instances.

                                Parameter modification failure

                                +

                                Parameter modification failure

                                TaurusUpdateInstanceParameterFailed

                                +

                                TaurusUpdateInstanceParameterFailed

                                Major

                                +

                                Major

                                The network between the management plane and the instance is abnormal or the instance is abnormal.

                                +

                                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.

                                +

                                Check the instance status and try again. If the fault persists, submit a service ticket.

                                Instance parameters fail to be modified.

                                +

                                Instance parameters fail to be modified.

                                Parameter template application failure

                                +

                                Parameter template application failure

                                TaurusApplyParameterGroupToInstanceFailed

                                +

                                TaurusApplyParameterGroupToInstanceFailed

                                Major

                                +

                                Major

                                The network between the management plane and instances is abnormal or the instances are abnormal.

                                +

                                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.

                                +

                                Check the instance status and try again. If the fault persists, submit a service ticket.

                                Parameter templates fail to be applied to instances.

                                +

                                Parameter templates fail to be applied to instances.

                                Full backup failure

                                +

                                Full backup failure

                                TaurusBackupInstanceFailed

                                +

                                TaurusBackupInstanceFailed

                                Major

                                +

                                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.

                                +

                                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.

                                +

                                Submit a service ticket.

                                Backup jobs fail.

                                +

                                Backup jobs fail.

                                Primary/standby failover

                                +

                                Primary/standby failover

                                TaurusActiveStandbySwitched

                                +

                                TaurusActiveStandbySwitched

                                Major

                                +

                                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.

                                +

                                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.

                                1. Check whether the service is running properly.
                                2. Check whether an alarm is generated, indicating that the read replica failed to be promoted to primary.
                                +
                                1. Check whether the service is running properly.
                                2. 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.

                                +

                                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

                                +

                                Database read-only

                                NodeReadonlyMode

                                +

                                NodeReadonlyMode

                                Major

                                +

                                Major

                                The database supports only query operations.

                                +

                                The database supports only query operations.

                                Submit a service ticket.

                                +

                                Submit a service ticket.

                                After the database becomes read-only, write operations cannot be processed.

                                +

                                After the database becomes read-only, write operations cannot be processed.

                                Database read/write

                                +

                                Database read/write

                                NodeReadWriteMode

                                +

                                NodeReadWriteMode

                                Major

                                +

                                Major

                                The database supports both write and read operations.

                                +

                                The database supports both write and read operations.

                                Submit a service ticket.

                                +

                                Submit a service ticket.

                                None.

                                +

                                None

                                Instance DR switchover

                                +

                                Instance DR switchover

                                DisasterSwitchOver

                                +

                                DisasterSwitchOver

                                Major

                                +

                                Major

                                If an instance is faulty and unavailable, a switchover is performed to ensure that the instance continues to provide services.

                                +

                                If an instance is faulty and unavailable, a switchover is performed to ensure that the instance continues to provide services.

                                Contact technical support.

                                +

                                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.

                                +

                                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

                                +

                                Database process restarted

                                TaurusDatabaseProcessRestarted

                                +

                                TaurusDatabaseProcessRestarted

                                Major

                                +

                                Major

                                The database process is stopped due to insufficient memory or high load.

                                +

                                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.

                                +

                                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.

                                +

                                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

                                +
                                - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                Table 10 GaussDB(for openGauss)

                                Event Source

                                Namespace

                                +

                                Namespace

                                Event Name

                                +

                                Event Name

                                Event ID

                                +

                                Event ID

                                Event Severity

                                +

                                Event Severity

                                Description

                                +

                                Description

                                Solution

                                +

                                Solution

                                Impact

                                +

                                Impact

                                GaussDB

                                +

                                GaussDB(for openGauss)

                                +

                                +

                                +

                                +

                                SYS.GAUSSDBV5

                                +

                                SYS.GAUSSDBV5

                                +

                                +

                                +

                                +

                                Process status alarm

                                +

                                Process status alarm

                                ProcessStatusAlarm

                                +

                                ProcessStatusAlarm

                                Major

                                +

                                Major

                                Key processes exit, including CMS/CMA, ETCD, GTM, CN, and DN processes.

                                +

                                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.

                                +

                                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.

                                +

                                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

                                +

                                Component status alarm

                                ComponentStatusAlarm

                                +

                                ComponentStatusAlarm

                                Major

                                +

                                Major

                                Key components do not respond, including CMA, ETCD, GTM, CN, and DN components.

                                +

                                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.

                                +

                                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.

                                +

                                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

                                +

                                Cluster status alarm

                                ClusterStatusAlarm

                                +

                                ClusterStatusAlarm

                                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 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.

                                +

                                Contact SRE engineers.

                                If the cluster status is read-only, only read services are processed.

                                +

                                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

                                +

                                DB instance creation failure

                                TaurusInstanceRunningStatusAbnormal

                                +

                                GaussDBV5CreateInstanceFailed

                                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.

                                +

                                Instances fail to be created because the quota is insufficient or underlying resources are exhausted.

                                Submit a service ticket.

                                +

                                Release the instances that are no longer used and try to provision them again, or submit a service ticket to adjust the quota.

                                The database service may be unavailable.

                                +

                                DB instances cannot be created.

                                DB instance recovered

                                +

                                Node adding failure

                                TaurusInstanceRunningStatusRecovered

                                +

                                GaussDBV5ExpandClusterFailed

                                Major

                                +

                                Major

                                GaussDB(openGauss) provides an HA tool for automated or manual rectification of faults. After the fault is rectified, this event is reported.

                                +

                                The underlying resources are insufficient.

                                No further action is required.

                                +

                                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

                                Faulty DB node

                                +

                                Storage scale-up failure

                                TaurusNodeRunningStatusAbnormal

                                +

                                GaussDBV5EnlargeVolumeFailed

                                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.

                                +

                                The underlying resources are insufficient.

                                Check whether the database service is available and submit a service ticket.

                                +

                                Submit a service ticket. The O&M personnel will coordinate resources in the background and then you scale up the storage space again.

                                The database service may be unavailable.

                                +

                                Services may be interrupted.

                                DB node recovered

                                +

                                Reboot failure

                                TaurusNodeRunningStatusRecovered

                                +

                                GaussDBV5RestartInstanceFailed

                                Major

                                +

                                Major

                                GaussDB(openGauss) provides an HA tool for automated or manual rectification of faults. After the fault is rectified, this event is reported.

                                +

                                The network is abnormal.

                                No further action is required.

                                +

                                Retry the reboot operation or submit a service ticket to the O&M personnel.

                                None

                                +

                                The database service may be unavailable.

                                DB instance creation failure

                                +

                                Full backup failure

                                GaussDBV5CreateInstanceFailed

                                +

                                GaussDBV5FullBackupFailed

                                Major

                                +

                                Major

                                Instances fail to be created because the quota is insufficient or underlying resources are exhausted.

                                +

                                The backup files fail to be exported or uploaded.

                                Release the instances that are no longer used and try to provision them again, or submit a service ticket to adjust the quota.

                                +

                                Submit a service ticket to the O&M personnel.

                                DB instances cannot be created.

                                +

                                Data cannot be backed up.

                                Node adding failure

                                +

                                Differential backup failure

                                GaussDBV5ExpandClusterFailed

                                +

                                GaussDBV5DifferentialBackupFailed

                                Major

                                +

                                Major

                                The underlying resources are insufficient.

                                +

                                The backup files fail to be exported or uploaded.

                                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 to the O&M personnel.

                                None

                                +

                                Data cannot be backed up.

                                Storage scale-up failure

                                +

                                Backup deletion failure

                                GaussDBV5EnlargeVolumeFailed

                                +

                                GaussDBV5DeleteBackupFailed

                                Major

                                +

                                Major

                                The underlying resources are insufficient.

                                +

                                The backup files fail to be deleted from OBS.

                                Submit a service ticket. The O&M personnel will coordinate resources in the background and then you scale up the storage space again.

                                +

                                Delete the backup files again.

                                Services may be interrupted.

                                +

                                None

                                Reboot failure

                                +

                                EIP binding failure

                                GaussDBV5RestartInstanceFailed

                                +

                                GaussDBV5BindEIPFailed

                                Major

                                +

                                Major

                                The network is abnormal.

                                +

                                The EIP is bound to another resource.

                                Retry the reboot operation or submit a service ticket to the O&M personnel.

                                +

                                Submit a service ticket to the O&M personnel.

                                The database service may be unavailable.

                                +

                                The instance cannot be accessed from the public network.

                                Full backup failure

                                +

                                EIP unbinding failure

                                GaussDBV5FullBackupFailed

                                +

                                GaussDBV5UnbindEIPFailed

                                Major

                                +

                                Major

                                The backup files fail to be exported or uploaded.

                                +

                                The network is faulty or EIP is abnormal.

                                Submit a service ticket to the O&M personnel.

                                +

                                Unbind the IP address again or submit a service ticket to the O&M personnel.

                                Data cannot be backed up.

                                +

                                IP addresses may be residual.

                                Differential backup failure

                                +

                                Parameter template application failure

                                GaussDBV5DifferentialBackupFailed

                                +

                                GaussDBV5ApplyParamFailed

                                Major

                                +

                                Major

                                The backup files fail to be exported or uploaded.

                                +

                                Modifying a parameter template times out.

                                Submit a service ticket to the O&M personnel.

                                +

                                Modify the parameter template again.

                                Data cannot be backed up.

                                +

                                None

                                Backup deletion failure

                                +

                                Parameter modification failure

                                GaussDBV5DeleteBackupFailed

                                +

                                GaussDBV5UpdateInstanceParamGroupFailed

                                Major

                                +

                                Major

                                This function does not need to be implemented.

                                +

                                Modifying a parameter template times out.

                                N/A

                                +

                                Modify the parameter template again.

                                N/A

                                +

                                None

                                EIP binding failure

                                +

                                Backup and restoration failure

                                GaussDBV5BindEIPFailed

                                +

                                GaussDBV5RestoreFromBcakupFailed

                                Major

                                +

                                Major

                                The EIP is bound to another resource.

                                +

                                The underlying resources are insufficient or backup files fail to be downloaded.

                                Submit a service ticket to the O&M personnel.

                                +

                                Submit a service ticket.

                                The instance cannot be accessed from the Internet.

                                +

                                The database service may be unavailable during the restoration failure.

                                EIP unbinding failure

                                +

                                Failed to upgrade the hot patch

                                GaussDBV5UnbindEIPFailed

                                +

                                GaussDBV5UpgradeHotfixFailed

                                Major

                                +

                                Major

                                The network is faulty or EIP is abnormal.

                                +

                                Generally, this fault is caused by an error reported during kernel upgrade.

                                Unbind the IP address again or submit a service ticket to the O&M personnel.

                                +

                                View the error information about the workflow and redo or skip the job.

                                IP addresses may be residual.

                                +

                                None

                                Parameter template application failure

                                +

                                DB instance faulty

                                GaussDBV5ApplyParamFailed

                                +

                                GaussDBV5FaultyDBInstance

                                Major

                                +

                                Major

                                Modifying a parameter template times out.

                                +

                                This event is a key alarm event and is reported when an instance is faulty due to a disaster or a server failure.

                                Modify the parameter template again.

                                +

                                Submit a service ticket.

                                None

                                +

                                The database service may be unavailable.

                                Parameter modification failure

                                +

                                DB instance recovered

                                GaussDBV5UpdateInstanceParamGroupFailed

                                +

                                GaussDBV5InstanceRecovered

                                Major

                                +

                                Major

                                Modifying a parameter template times out.

                                +

                                GaussDB(for openGauss) provides an HA tool for automated or manual rectification of faults. After the fault is rectified, this event is reported.

                                Modify the parameter template again.

                                +

                                No action is required.

                                None

                                +

                                None

                                Backup and restoration failure

                                +

                                Faulty node

                                GaussDBV5RestoreFromBcakupFailed

                                +

                                GaussDBV5FaultyDBNode

                                Major

                                +

                                Major

                                The underlying resources are insufficient or backup files fail to be downloaded.

                                +

                                This event is a key alarm event and is reported when a database node is faulty due to a disaster or a server failure.

                                Submit a service ticket.

                                +

                                This event is a key alarm event and is reported when a database node is faulty due to a disaster or a server failure.

                                The database service may be unavailable during the restoration failure.

                                +

                                The database service may be unavailable.

                                Failed to upgrade the hot patch

                                +

                                Node recovered

                                GaussDBV5UpgradeHotfixFailed

                                +

                                GaussDBV5FaultyDBNodeRecovered

                                Major

                                +

                                Major

                                Generally, this fault is caused by an error reported during kernel upgrade.

                                +

                                GaussDB(for openGauss) provides an HA tool for automated or manual rectification of faults. After the fault is rectified, this event is reported.

                                View the error information about the workflow and redo or skip the job.

                                +

                                No action is required.

                                None

                                +

                                None
                                -
                                Table 9 Distributed Database Middleware (DDM)

                                Event Source

                                +
                                - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                Table 11 Distributed Database Middleware (DDM)

                                Event Source

                                Namespace

                                +

                                Namespace

                                Event Name

                                +

                                Event Name

                                Event ID

                                +

                                Event ID

                                Event Severity

                                +

                                Event Severity

                                Description

                                +

                                Description

                                Solution

                                +

                                Solution

                                Impact

                                +

                                Impact

                                DDM

                                +

                                DDM

                                SYS.DDM

                                +

                                SYS.DDM (DDM 1.0)

                                +

                                SYS.DDMS (DDM 2.0)

                                Failed to create a DDM instance

                                +

                                Failed to create a DDM instance

                                createDdmInstanceFailed

                                +

                                createDdmInstanceFailed

                                Major

                                +

                                Major

                                The underlying resources are insufficient.

                                +

                                The underlying resources are insufficient.

                                Release resources and create the instance again.

                                +

                                Release resources and create the instance again.

                                DDM instances cannot be created.

                                +

                                DDM instances cannot be created.

                                Failed to change class of a DDM instance

                                +

                                Failed to change class of a DDM instance

                                resizeFlavorFailed

                                +

                                resizeFlavorFailed

                                Major

                                +

                                Major

                                The underlying resources are insufficient.

                                +

                                The underlying resources are insufficient.

                                Submit a service ticket to the O&M personnel to coordinate resources and try again.

                                +

                                Submit a service ticket to the O&M personnel to coordinate resources and try again.

                                Services on some nodes are interrupted.

                                +

                                Services on some nodes are interrupted.

                                Failed to scale out a DDM instance

                                +

                                Failed to scale out a DDM instance

                                enlargeNodeFailed

                                +

                                enlargeNodeFailed

                                Major

                                +

                                Major

                                The underlying resources are insufficient.

                                +

                                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.

                                +

                                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.

                                +

                                The instance fails to be scaled out.

                                Failed to scale in a DDM instance

                                +

                                Failed to scale in a DDM instance

                                reduceNodeFailed

                                +

                                reduceNodeFailed

                                Major

                                +

                                Major

                                The underlying resources fail to be released.

                                +

                                The underlying resources fail to be released.

                                Submit a service ticket to the O&M personnel to release resources.

                                +

                                Submit a service ticket to the O&M personnel to release resources.

                                The instance fails to be scaled in.

                                +

                                The instance fails to be scaled in.

                                Failed to restart a DDM instance

                                +

                                Failed to restart a DDM instance

                                restartInstanceFailed

                                +

                                restartInstanceFailed

                                Major

                                +

                                Major

                                The DB instances associated are abnormal.

                                +

                                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.

                                +

                                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.

                                +

                                Services on some nodes are interrupted.

                                Failed to create a schema

                                +

                                Failed to create a schema

                                createLogicDbFailed

                                +

                                createLogicDbFailed

                                Major

                                +

                                Major

                                The possible causes are as follows:

                                +

                                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

                                +

                                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.

                                +

                                Services cannot run properly.

                                Failed to bind an EIP

                                +

                                Failed to bind an EIP

                                bindEipFailed

                                +

                                bindEipFailed

                                Major

                                +

                                Major

                                The EIP is abnormal.

                                +

                                The EIP is abnormal.

                                Try again later. In case of emergency, contact O&M personnel to rectify the fault.

                                +

                                Try again later. In case of emergency, contact O&M personnel to rectify the fault.

                                The DDM instance cannot be accessed from the Internet.

                                +

                                The DDM instance cannot be accessed from the Internet.

                                Failed to scale out a schema

                                +

                                Failed to scale out a schema

                                migrateLogicDbFailed

                                +

                                migrateLogicDbFailed

                                Major

                                +

                                Major

                                The underlying resources fail to be processed.

                                +

                                The underlying resources fail to be processed.

                                Submit a service ticket to the O&M personnel.

                                +

                                Submit a service ticket to the O&M personnel.

                                The schema cannot be scaled out.

                                +

                                The schema cannot be scaled out.

                                Failed to re-scale out a schema

                                +

                                Failed to re-scale out a schema

                                retryMigrateLogicDbFailed

                                +

                                retryMigrateLogicDbFailed

                                Major

                                +

                                Major

                                The underlying resources fail to be processed.

                                +

                                The underlying resources fail to be processed.

                                Submit a service ticket to the O&M personnel.

                                +

                                Submit a service ticket to the O&M personnel.

                                The schema cannot be scaled out.

                                +

                                The schema cannot be scaled out.
                                -
                                Table 10 Elastic Volume Service (EVS)

                                Event Source

                                +
                                - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                Table 12 Elastic Volume Service (EVS)

                                Event Source

                                Namespace

                                +

                                Namespace

                                Event Name

                                +

                                Event Name

                                Event ID

                                +

                                Event ID

                                Event Severity

                                +

                                Event Severity

                                Description

                                +

                                Description

                                Solution

                                +

                                Solution

                                Impact

                                +

                                Impact

                                EVS

                                +

                                EVS

                                SYS.EVS

                                +

                                SYS.EVS

                                Update disk

                                +

                                Update disk

                                updateVolume

                                +

                                updateVolume

                                Minor

                                +

                                Minor

                                Update the name and description of an EVS disk.

                                +

                                Update the name and description of an EVS disk.

                                No further action is required.

                                +

                                No further action is required.

                                None

                                +

                                None

                                Expand disk

                                +

                                Expand disk

                                extendVolume

                                +

                                extendVolume

                                Minor

                                +

                                Minor

                                Expand an EVS disk.

                                +

                                Expand an EVS disk.

                                No further action is required.

                                +

                                No further action is required.

                                None

                                +

                                None

                                Delete disk

                                +

                                Delete disk

                                deleteVolume

                                +

                                deleteVolume

                                Major

                                +

                                Major

                                Delete an EVS disk.

                                +

                                Delete an EVS disk.

                                No further action is required.

                                +

                                No further action is required.

                                Deleted disks cannot be recovered.

                                +

                                Deleted disks cannot be recovered.

                                QoS upper limit reached

                                +

                                QoS upper limit reached

                                +
                                NOTE:

                                This event is no longer supported for EVS and will be removed from Cloud Eye.

                                +

                                reachQoS

                                +

                                reachQoS

                                Major

                                +

                                Major

                                The I/O latency increases as the QoS upper limits of the disk are frequently reached and flow control triggered.

                                +

                                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.

                                +

                                Change the disk type to one with a higher specification.

                                The current disk may fail to meet service requirements.

                                +

                                The current disk may fail to meet service requirements.
                                -
                                Table 11 Key Management Service (KMS)

                                Event Source

                                +
                                - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                                Table 13 Identity and Access Management (IAM)

                                Event Source

                                Namespace

                                +

                                Namespace

                                Event Name

                                +

                                Event Name

                                Event ID

                                +

                                Event ID

                                Event Severity

                                +

                                Event Severity

                                KMS

                                +

                                IAM

                                SYS.KMS

                                +

                                SYS.IAM

                                Key disabled

                                +

                                Login

                                disableKey

                                +

                                login

                                Major

                                +

                                Minor

                                Key deletion scheduled

                                +

                                Logout

                                scheduleKeyDeletion

                                +

                                logout

                                Minor

                                +

                                Minor

                                Grant retired

                                +

                                Password changed

                                retireGrant

                                +

                                changePassword

                                Major

                                +

                                Major

                                Grant revoked

                                +

                                User created

                                revokeGrant

                                +

                                createUser

                                Major

                                +

                                Minor

                                +

                                User deleted

                                +

                                deleteUser

                                +

                                Major

                                +

                                User updated

                                +

                                updateUser

                                +

                                Minor

                                +

                                User group created

                                +

                                createUserGroup

                                +

                                Minor

                                +

                                User group deleted

                                +

                                deleteUserGroup

                                +

                                Major

                                +

                                User group updated

                                +

                                updateUserGroup

                                +

                                Minor

                                +

                                Identity provider created

                                +

                                createIdentityProvider

                                +

                                Minor

                                +

                                Identity provider deleted

                                +

                                deleteIdentityProvider

                                +

                                Major

                                +

                                Identity provider updated

                                +

                                updateIdentityProvider

                                +

                                Minor

                                +

                                Metadata updated

                                +

                                updateMetadata

                                +

                                Minor

                                +

                                Security policy updated

                                +

                                updateSecurityPolicies

                                +

                                Major

                                +

                                Credential added

                                +

                                addCredential

                                +

                                Major

                                +

                                Credential deleted

                                +

                                deleteCredential

                                +

                                Major

                                +

                                Project created

                                +

                                createProject

                                +

                                Minor

                                +

                                Project updated

                                +

                                updateProject

                                +

                                Minor

                                +

                                Project suspended

                                +

                                suspendProject

                                +

                                Major
                                -
                                Table 12 Cloud Eye

                                Event Source

                                +
                                - - - - - + + - - - - - - + + + + + + + + + + + + + + + + + + + + + + +
                                Table 14 Key Management Service (KMS)

                                Event Source

                                Event Name

                                +

                                Namespace

                                Event ID

                                +

                                Event Name

                                Event Severity

                                +

                                Event ID

                                Description

                                +

                                Event Severity

                                Solution

                                +

                                Description

                                +

                                Solution

                                +

                                Impact

                                Cloud Eye

                                +

                                KMS

                                Agent heartbeat interruption

                                +

                                SYS.KMS

                                agentHeartbeatInterrupted

                                +

                                Key disabled

                                Major

                                +

                                disableKey

                                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.

                                +

                                Major

                                • 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.
                                +

                                A key is disabled and cannot be used.

                                +

                                If the customer needs to disable the key, no action is required. However, if the key is disabled by mistake, the customer needs to log in to the DEW console and enable it again.

                                +

                                Services may be affected if the key is being used.

                                +

                                Key deletion scheduled

                                +

                                scheduleKeyDeletion

                                +

                                Minor

                                +

                                A key is scheduled to be deleted and cannot be used.

                                +

                                If the customer needs to delete the key, no action is required. However, if the deletion of the key is scheduled by mistake, the customer needs to log in to the DEW console, cancel the scheduled deletion, and enable the key again.

                                +

                                Services may be affected if the key is being used.

                                +

                                Grant retired

                                +

                                retireGrant

                                +

                                Major

                                +

                                A grant is retired and the key cannot be used.

                                +

                                If the customer needs to cancel the key grant, no action is required. However, if the grant is canceled by mistake, the customer needs to log in to the DEW console and create the grant again.

                                +

                                Services may be affected if the key is being used.

                                +

                                Grant revoked

                                +

                                revokeGrant

                                +

                                Major

                                +

                                A grant is revoked and the key cannot be used.

                                +

                                If the customer needs to cancel the key grant, no action is required. However, if the grant is canceled by mistake, the customer needs to log in to the DEW console and create the grant again.

                                +

                                Services may be affected if the key is being used.
                                -
                                Table 13 Distributed Cache Service (DCS)

                                Event Source

                                +
                                - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                Table 15 Cloud Eye (CES)

                                Event Source

                                Namespace

                                +

                                Namespace

                                Event Name

                                +

                                Event Name

                                Event ID

                                +

                                Event ID

                                Event Severity

                                +

                                Event Severity

                                Description

                                +

                                Description

                                Solution

                                +

                                Solution

                                Impact

                                +

                                Impact

                                DCS

                                +

                                Cloud Eye

                                SYS.DCS

                                +

                                SYS.CES

                                Full sync retry during online migration

                                +

                                Agent heartbeat interruption

                                migrationFullResync

                                +

                                agentHeartbeatInterrupted

                                Minor

                                +

                                Major

                                If online migration fails, full synchronization will be triggered because incremental synchronization cannot be performed.

                                +

                                The collecting process of the Agent is faulty.

                                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.

                                +
                                • 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.

                                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.

                                +

                                The Agent will stop collecting and reporting metrics.
                                  

                                masterStandbyFailover

                                +

                                Agent back to normal

                                Minor

                                +

                                agentResumed

                                The master node was abnormal, promoting a replica to master.

                                +

                                Informational

                                		    

                                Memcached master/standby switchover

                                +

                                The Agent was back to normal.

                                memcachedMasterStandbyFailover

                                +

                                No action is required.

                                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 will be interrupted.

                                +

                                None

                                Redis server abnormal

                                +

                                Agent faulty

                                redisNodeStatusAbnormal

                                +

                                agentFaulted

                                Major

                                +

                                Major

                                The Redis server status was abnormal.

                                +

                                The Agent was faulty and this status was reported to Cloud Eye.

                                Check whether services are affected. If yes, contact O&M personnel.

                                +

                                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.

                                +

                                Update the Agent to the latest version.

                                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.

                                +

                                The Agent will stop collecting and reporting metrics.

                                Redis server recovered

                                +

                                Agent disconnected

                                redisNodeStatusNormal

                                +

                                agentDisconnected

                                Major

                                +

                                Major

                                The Redis server status recovered.

                                +

                                The communication process of the Agent is faulty.

                                Check whether services can recover. If the applications are not reconnected, restart them.

                                +

                                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.

                                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 will be 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 will be interrupted.

                                +

                                The Agent will stop collecting and reporting metrics.
                                -
                                Table 14 Config

                                Event Source

                                +
                                - - - - - - + - - - - - - - + - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                                Table 16 Distributed Cache Service (DCS)

                                Event Source

                                Event Name

                                +

                                Namespace

                                Event ID

                                +

                                Event Name

                                Event Severity

                                +

                                Event ID

                                Description

                                +

                                Event Severity

                                Solution

                                +

                                Description

                                Impact

                                +

                                Solution

                                +

                                Impact

                                RMS

                                +

                                DCS

                                +

                                +

                                Configuration noncompliance notification

                                +

                                SYS.DCS

                                +

                                +

                                configurationNoncomplianceNotification

                                +

                                Full sync retry during online migration

                                Major

                                +

                                migrationFullResync

                                The assignment evaluation result is Non-compliant.

                                +

                                Minor

                                Modify the noncompliant configuration items of the resource.

                                +

                                If online migration fails, full synchronization will be triggered because incremental synchronization cannot be performed.

                                None

                                +

                                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.

                                Configuration compliance notification

                                +

                                Memcached master/standby switchover

                                configurationComplianceNotification

                                +

                                memcachedMasterStandbyFailover

                                Informational

                                +

                                Minor

                                The assignment evaluation result changed to be Compliant.

                                +

                                The master node was abnormal, promoting the standby node to master.

                                None

                                +

                                Check whether services can recover by themselves. If applications cannot recover, restart them.

                                None

                                +

                                Persistent connections to the instance will be 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 by themselves. If applications cannot recover, restart them.

                                +

                                Persistent connections to the instance will be 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 will be interrupted.

                                +

                                Automatic failover

                                +

                                masterStandbyFailover

                                +

                                Major

                                +

                                The master node failed due to a hard/software fault, triggering the replica node to take over services.

                                +

                                Check that the application reconnected to the instance and the fault was rectified. Otherwise, restart the application.

                                +

                                Access errors interrupt persistent connections to the instance.

                                +

                                Manual switchover

                                +

                                masterStandbySwitchover

                                +

                                Major

                                +

                                Performing master/standby switchovers on the console or calling the master/standby switchover API triggers these events. Master/Standby switchovers occur during specification changes or after instance restarts. Manual O&M on the backend required by fault drills or resource migration initiates master/standby switchovers.

                                +

                                Check that the application reconnected to the instance and the fault was rectified. Otherwise, restart the application.

                                +

                                Access errors interrupt persistent connections to the instance.
                                -
                                Table 15 Host Security Service

                                Event Source

                                +
                                - - - - - - - - - - - - - - - - - - - - -
                                Table 17 Host Security Service (HSS)

                                Event Source

                                Namespace

                                +

                                Namespace

                                Event Name

                                +

                                Event Name

                                Event ID

                                +

                                Event ID

                                Event Severity

                                +

                                Event Severity

                                Description

                                +

                                Description

                                Solution

                                +

                                Solution

                                Impact

                                +

                                Impact

                                HSS

                                +

                                HSS

                                SYS.HSS

                                +

                                SYS.HSS

                                HSS agent disconnected

                                +

                                HSS agent disconnected

                                hssAgentAbnormalOffline

                                +

                                hssAgentAbnormalOffline

                                Major

                                +

                                Major

                                The communication between the agent and the server is abnormal, or the agent process on the server is abnormal.

                                +

                                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.

                                +

                                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.

                                +

                                Services are interrupted.

                                Abnormal HSS agent status

                                +

                                Abnormal HSS agent status

                                hssAgentAbnormalProtection

                                +

                                hssAgentAbnormalProtection

                                Major

                                +

                                Major

                                The agent is abnormal probably because it does not have sufficient resources.

                                +

                                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.

                                +

                                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.

                                +

                                Services are interrupted.
                                -
                                Table 16 Image Management Service

                                Event Source

                                +
                                - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                Table 18 Image Management Service (IMS)

                                Event Source

                                Namespace

                                +

                                Namespace

                                Event Name

                                +

                                Event Name

                                Event ID

                                +

                                Event ID

                                Event Severity

                                +

                                Event Severity

                                Description

                                +

                                Description

                                Solution

                                +

                                Solution

                                Impact

                                +

                                Impact

                                IMS

                                +

                                IMS

                                SYS.IMS

                                +

                                SYS.IMS

                                Create Image

                                +

                                Create Image

                                createImage

                                +

                                createImage

                                Major

                                +

                                Major

                                An image was created.

                                +

                                An image was created.

                                None

                                +

                                None

                                You can use this image to create cloud servers.

                                +

                                You can use this image to create cloud servers.

                                Update Image

                                +

                                Update Image

                                updateImage

                                +

                                updateImage

                                Major

                                +

                                Major

                                Metadata of an image was modified.

                                +

                                Metadata of an image was modified.

                                None

                                +

                                None

                                Cloud servers may fail to be created from this image.

                                +

                                Cloud servers may fail to be created from this image.

                                Delete Image

                                +

                                Delete Image

                                deleteImage

                                +

                                deleteImage

                                Major

                                +

                                Major

                                An image was deleted.

                                +

                                An image was deleted.

                                None

                                +

                                None

                                This image will be unavailable on the management console.

                                +

                                This image will be unavailable on the management console.
                                -
                                Table 17 Bare Metal Server (BMS)

                                Event Source

                                +
                                - - - - - - + - - - - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                Table 19 Virtual Private Cloud (VPC)

                                Event Source

                                Event Name

                                +

                                Namespace

                                Event ID

                                +

                                Event Name

                                Event Severity

                                +

                                Event ID

                                Description

                                +

                                Event Severity

                                Solution

                                +

                                Description

                                Impact

                                +

                                Solution

                                +

                                Impact

                                BMS

                                +

                                Elastic IP and bandwidth

                                +

                                +

                                +

                                +

                                ECC uncorrectable errors generated on GPU SRAM

                                +

                                SYS.VPC

                                +

                                +

                                +

                                +

                                SRAMUncorrectableEccError

                                +

                                Delete VPC

                                Major

                                +

                                deleteVpc

                                There are ECC uncorrectable errors generated on GPU SRAM.

                                +

                                Major

                                If services are affected, submit a service ticket.

                                +

                                The VPC resources were deleted.

                                The GPU hardware may be faulty. As a result, the GPU memory is faulty, and services exit abnormally.

                                +

                                Check whether the VPC resources were deleted by mistake.

                                +

                                Deleting the VPC may affect customer services.

                                osShutdown

                                +

                                Modify VPC

                                osShutdown

                                +

                                modifyVpc

                                Major

                                +

                                Minor

                                The BMS was stopped

                                -
                                • on the management console.
                                • by calling APIs.
                                +

                                The VPC information was modified.

                                • Deploy service applications in HA mode.
                                • After the BMS is started, check whether services recover.
                                +

                                Check whether the VPC information was modified by mistake.

                                Services are interrupted.

                                +

                                Modifying the VPC may affect customer services.

                                Abnormal shutdown

                                +

                                Delete subnet

                                serverShutdown

                                +

                                deleteSubnet

                                Major

                                +

                                Minor

                                The BMS was stopped unexpectedly, which may be caused by

                                -
                                • unexpected power-off.
                                • hardware faults.
                                +

                                Subnets are deleted.

                                • Deploy service applications in HA mode.
                                • After the BMS is started, check whether services recover.
                                +

                                Check whether the EIP was release by mistake.

                                Services are interrupted.

                                +

                                Deleting the VPC subnets may affect customer services.

                                Abnormal reboot

                                +

                                Modify subnet

                                serverReboot

                                +

                                modifySubnet

                                Major

                                +

                                Minor

                                The BMS restarted unexpectedly, which may be caused by

                                -
                                • OS faults.
                                • hardware faults.
                                +

                                The subnet information was modified.

                                • Deploy service applications in HA mode.
                                • After the BMS is restarted, check whether services recover.
                                +

                                Check whether the subnet information was modified by mistake.

                                Services are interrupted.

                                +

                                Modifying the VPC subnets may affect customer services.

                                Network interruption

                                +

                                Modify bandwidth

                                linkDown

                                +

                                modifyBandwidth

                                Major

                                +

                                Minor

                                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.
                                +

                                The bandwidth information was modified.

                                • Deploy service applications in HA mode.
                                • After the BMS is started, check whether services recover.
                                +

                                Check whether the bandwidth information was modified by mistake.

                                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.

                                -
                                1. If services are interrupted, restart the services to restore.
                                2. If services cannot be restarted, restart the VM where services are running.
                                3. 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.

                                -
                                1. If services are interrupted, restart the services to restore.
                                2. If services cannot be restarted, restart the VM where services are running.
                                3. 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.

                                -
                                1. If services are interrupted, restart the services to restore.
                                2. If services cannot be restarted, restart the VM where services are running.
                                3. 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.

                                -
                                1. If services are interrupted, restart the services to restore.
                                2. If services cannot be restarted, restart the VM where services are running.
                                3. 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.

                                -
                                1. If services are interrupted, restart the services to restore.
                                2. If services cannot be restarted, restart the VM where services are running.
                                3. 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.

                                -
                                1. Restart the VM to restore services.
                                2. 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.

                                +

                                Services may be interrupted.
                                -
                                Table 18 Virtual Private Cloud

                                Event Source

                                +
                                - - - + + + + - - - - + + + + - - - + + + - - - + + + - - - - - - - - - - - - - - -
                                Table 20 Object Storage Service (OBS)

                                Event Source

                                Event Name

                                +

                                Namespace

                                Event ID

                                +

                                Event Name

                                Event Severity

                                +

                                Event ID

                                +

                                Event Severity

                                +

                                Description

                                +

                                Solution

                                +

                                Impact

                                Elastic IP and bandwidth

                                +

                                OBS

                                Delete VPC

                                +

                                SYS.OBS

                                deleteVpc

                                +

                                Delete bucket

                                Major

                                +

                                deleteBucket

                                +

                                Major

                                +

                                An event is reported when a bucket deletion takes place.

                                +

                                Once deleted, buckets cannot be restored. Create a new one if needed.

                                +
                                CAUTION:

                                If you want to reuse the name of a deleted bucket for a new bucket, wait at least 30 minutes after the bucket is deleted.

                                +
                                +

                                Deleting buckets may affect your services. Before deleting a bucket, make sure that your services do not depend on it.

                                Modify VPC

                                +

                                Delete bucket policy

                                modifyVpc

                                +

                                deleteBucketPolicy

                                Minor

                                +

                                Major

                                +

                                An event is reported when a bucket policy deletion takes place.

                                +
                                • You can delete unwanted bucket policies.
                                • If you delete a bucket policy by mistake, you can create one.
                                +

                                After a bucket policy is deleted, some users may fail to access the associated bucket and the objects in it.

                                Delete subnet

                                +

                                Set bucket ACL

                                deleteSubnet

                                +

                                setBucketAcl

                                Minor

                                +

                                Minor

                                +

                                An event is reported when a bucket ACL configuration takes place.

                                +

                                If you do not want an account to access a bucket or the objects in it, you can delete the bucket ACL.

                                +

                                A bucket ACL grants an account the access to the bucket and the objects in it.

                                Modify subnet

                                +

                                Set bucket policy

                                modifySubnet

                                +

                                setBucketPolicy

                                Minor

                                +

                                Minor

                                Modify bandwidth

                                +

                                An event is reported when a bucket policy configuration takes place.

                                modifyBandwidth

                                +

                                If you do not need a bucket policy to perform fine-grained access control over a bucket and the objects in it, you can delete the bucket policy.

                                Minor

                                -

                                Delete VPN

                                -

                                deleteVpn

                                -

                                Major

                                -

                                Modify VPN

                                -

                                modifyVpn

                                -

                                Minor

                                +

                                A bucket policy grants an account some operation permissions for the bucket or the objects in it under certain conditions.
                                -
                                Table 19 Object Storage Service (OBS)

                                Event Source

                                +
                                - - - + + + - - - - - - - - - - - - - - - - - - -
                                Table 21 Elastic IP (EIP)

                                Event Source

                                Event Name

                                +

                                Event Name

                                Event ID

                                +

                                Event ID

                                Event Severity

                                +

                                Event Severity

                                +

                                Description

                                +

                                Solution

                                +

                                Impact

                                OBS

                                +

                                EIP

                                Delete bucket

                                +

                                EIP bandwidth overflow

                                deleteBucket

                                +

                                EIPBandwidthOverflow

                                Major

                                +

                                Major

                                Delete bucket policy

                                -

                                deleteBucketPolicy

                                -

                                Major

                                -

                                Set bucket ACL

                                -

                                setBucketAcl

                                -

                                Minor

                                -

                                Set bucket policy

                                -

                                setBucketPolicy

                                -

                                Minor

                                -
                                -
                                - -
                                - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/ces/umn/ces_01_0056.html b/docs/ces/umn/ces_01_0056.html index 4ffce69ef..afdc137d2 100644 --- a/docs/ces/umn/ces_01_0056.html +++ b/docs/ces/umn/ces_01_0056.html @@ -5,7 +5,7 @@

                                An account can create a maximum of 20 data dump tasks.

                                -

                                Procedure

                                1. Log in to the management console.
                                2. Click Service List in the upper left corner and select Cloud Eye.
                                3. In the navigation pane on the left, choose Data Dump.
                                4. Click Add Dump Task.
                                5. On the Add Dump Task page, configure parameters by referring to Table 1.
                                  Figure 1 Adding a dump task
                                  +

                                  Procedure

                                  1. Log in to the management console.
                                  2. Choose Service List > Cloud Eye.
                                  3. In the navigation pane, choose Data Dump.
                                  4. Click Add Dump Task.
                                  5. On the Add Dump Task page, configure parameters by referring to Table 1.
                                    Figure 1 Adding a dump task
                                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 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)

                                +

                                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.

                                +

                                Check whether the EIP bandwidth keeps increasing and whether services are normal. Increase bandwidth if necessary.

                                The network becomes slow or packets are lost.

                                +

                                The network becomes slow or packets are lost.

                                Delete EIP

                                +

                                Delete EIP

                                deleteEip

                                +

                                deleteEip

                                Minor

                                +

                                Minor

                                The EIP was released.

                                +

                                The EIP was released.

                                Check whether the EIP was release by mistake.

                                +

                                Check whether the EIP was release by mistake.

                                The server that has the EIP bound cannot access the Internet.

                                +

                                The server that has the EIP bound cannot access the Internet.

                                EIP blocked

                                +

                                EIP blocked

                                blockEIP

                                +

                                blockEIP

                                Critical

                                +

                                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.

                                +

                                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.

                                +

                                Replace the EIP to prevent services from being affected.

                                Locate and deal with the fault.

                                Services are impacted.

                                +

                                Services are impacted.

                                EIP unblocked

                                +

                                EIP unblocked

                                unblockEIP

                                +

                                unblockEIP

                                Critical

                                +

                                Critical

                                The EIP was unblocked.

                                +

                                The EIP was unblocked.

                                Use the previous EIP again.

                                +

                                Use the previous EIP again.

                                None

                                +

                                None

                                Start DDoS traffic scrubbing

                                +

                                Start DDoS traffic scrubbing

                                ddosCleanEIP

                                +

                                ddosCleanEIP

                                Major

                                +

                                Major

                                Traffic scrubbing on the EIP was started to prevent DDoS attacks.

                                +

                                Traffic scrubbing on the EIP was started to prevent DDoS attacks.

                                Check whether the EIP was attacked.

                                +

                                Check whether the EIP was attacked.

                                Services may be interrupted.

                                +

                                Services may be interrupted.

                                Stop DDoS traffic scrubbing

                                +

                                Stop DDoS traffic scrubbing

                                ddosEndCleanEip

                                +

                                ddosEndCleanEip

                                Major

                                +

                                Major

                                Traffic scrubbing on the EIP to prevent DDoS attacks was ended.

                                +

                                Traffic scrubbing on the EIP to prevent DDoS attacks was ended.

                                Check whether the EIP was attacked.

                                +

                                Check whether the EIP was attacked.

                                Services may be interrupted.

                                +

                                Services may be interrupted.

                                Enterprise-class QoS bandwidth limit exceeded

                                +

                                Enterprise-class QoS bandwidth limit exceeded

                                EIPBandwidthRuleOverflow

                                +

                                EIPBandwidthRuleOverflow

                                Major

                                +

                                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)

                                +

                                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.

                                +

                                Check whether the EIP bandwidth keeps increasing and whether services are normal. Increase bandwidth if necessary.

                                The network becomes slow or packets are lost.

                                +

                                The network becomes slow or packets are lost.
                                @@ -45,6 +45,11 @@ + + +
                                Table 1 Dump task parameters

                                Parameter

                                The type can only be Distributed Message Service for Kafka.

                                Project Name

                                +

                                Specifies the project of the resource.

                                +

                                Destination

                                Specifies the Kafka instance and topic where the data is to be dumped.

                                diff --git a/docs/ces/umn/ces_01_0057.html b/docs/ces/umn/ces_01_0057.html index a39f4f619..c6b2d0b4d 100644 --- a/docs/ces/umn/ces_01_0057.html +++ b/docs/ces/umn/ces_01_0057.html @@ -3,7 +3,7 @@

                                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

                                1. Log in to the management console.
                                2. Click Service List in the upper left corner and select Cloud Eye.
                                3. In the navigation pane, choose Data Dump.
                                4. Locate a dump task and click Modify in the Operation column.

                                  The Modify Dump Task page is displayed.

                                  +

                                  Modifying a Dump Task

                                  1. Log in to the management console.
                                  2. Choose Service List > Cloud Eye.
                                  3. In the navigation pane, choose Data Dump.
                                  4. Locate a dump task and click Modify in the Operation column.

                                    The Modify Dump Task page is displayed.

                                  5. Modify the task settings.
                                  6. Click Modify.

                                  Disabling Dump Tasks

                                  After you disable a dump task, collected monitoring data will not be dumped but existing data is still saved.

                                  diff --git a/docs/ces/umn/ces_01_0064.html b/docs/ces/umn/ces_01_0064.html index 1a8598a95..a14118092 100644 --- a/docs/ces/umn/ces_01_0064.html +++ b/docs/ces/umn/ces_01_0064.html @@ -8,6 +8,8 @@
                                5. Viewing Metrics
                                  6. +
                                6. Cloud Services Displayed in the Cloud Service Monitoring List
                                  +
                                diff --git a/docs/ces/umn/ces_01_0067.html b/docs/ces/umn/ces_01_0067.html index 7d47f8bb2..36178ae35 100644 --- a/docs/ces/umn/ces_01_0067.html +++ b/docs/ces/umn/ces_01_0067.html @@ -12,6 +12,8 @@
                              6. Viewing Alarm Records
                                7. +
                              7. One-Click Monitoring
                                +
                              8. Alarm Rule Management
                              9. Alarm Templates
                                diff --git a/docs/ces/umn/ces_01_0068.html b/docs/ces/umn/ces_01_0068.html index 3c646fd17..6c930cc72 100644 --- a/docs/ces/umn/ces_01_0068.html +++ b/docs/ces/umn/ces_01_0068.html @@ -1,7 +1,7 @@

                                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 SMS messages, or sends HTTP/HTTPS requests, enabling you to quickly respond to resource changes.

                                +

                                You can set alarm rules for key metrics of cloud services. When the conditions in an alarm rule are met, Cloud Eye notifies you of faults via emails, or SMS messages, or HTTP/HTTPS requests. This way, you can quickly handle the faults (if needed) and prevent service loss due 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 account contact.

                                diff --git a/docs/ces/umn/ces_01_0076.html b/docs/ces/umn/ces_01_0076.html index c7dd49c7e..ce1f5fb76 100644 --- a/docs/ces/umn/ces_01_0076.html +++ b/docs/ces/umn/ces_01_0076.html @@ -1,13 +1,15 @@

                                Viewing Alarm Records

                                -

                                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.

                                +

                                The Alarm Records page displays the status changes for all alarm rules, making it easy to track and review them in one place. By default, alarm records of the last seven days are displayed. You can select a time range to display alarm records in the past 180 days.

                                When an alarm is generated, you can view the alarm records about the cloud resource.

                                -

                                Procedure

                                1. Log in to the management console.
                                2. In the upper left corner, select a region and project.
                                3. Click Service List in the upper left corner and select Cloud Eye.
                                4. 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.

                                  -
                                5. 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.
                                  +

                                  Viewing Alarm Records

                                  1. Log in to the management console.
                                  2. In the upper left corner, select a region and project.
                                  3. Choose Service List > Cloud Eye.
                                  4. 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.

                                    +
                                  5. 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.

                                    On the Alarm Records page, click Export in the upper left corner to export alarm records.

                                  +

                                  Filtering Alarm Records

                                  • You can select a time range within the past 180 days to view alarm records.
                                  • On the Alarm Records page, you can select a property type and enter a value to filter alarm records by status, alarm severity, alarm rule name, resource type, resource ID, or alarm rule ID.
                                  +
                                  diff --git a/docs/ces/umn/ces_01_0077.html b/docs/ces/umn/ces_01_0077.html index 6fac818c3..fb392210e 100644 --- a/docs/ces/umn/ces_01_0077.html +++ b/docs/ces/umn/ces_01_0077.html @@ -1,7 +1,8 @@

                                  Alarm Rule Management

                                  -

                                  This topic describes how to manage alarm rules as your system grows.

                                  +

                                  This topic describes how to manage alarm rules as your system grows.

                                  +

                                    diff --git a/docs/ces/umn/ces_01_0078.html b/docs/ces/umn/ces_01_0078.html index a3b58554d..c05c0e3e4 100644 --- a/docs/ces/umn/ces_01_0078.html +++ b/docs/ces/umn/ces_01_0078.html @@ -1,308 +1,253 @@

                                    Modifying an Alarm Rule

                                    -

                                    Procedure

                                    1. Log in to the management console.
                                    2. In the upper left corner, select a region and project.
                                    3. Click Service List in the upper left corner and select Cloud Eye.
                                    4. Choose Alarm Management > Alarm Rules.
                                    5. 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.
                                      +

                                      If there are service changes or you need to replan an alarm rule, you can modify the alarm rule.

                                      +

                                      Procedure

                                      1. Log in to the management console.
                                      2. In the upper left corner, select a region and project.
                                      3. Choose Service List > Cloud Eye.
                                      4. Choose Alarm Management > Alarm Rules.
                                      5. 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.
                                      6. On the Modify Alarm Rule page, modify alarm rule parameters as needed. -
                                        Table 1 Configuring metric alarm parameters

                                        Parameter

                                        +
                                        - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + - - - - - - - -
                                        Table 1 Configuring metric alarm parameters

                                        Parameter

                                        Description

                                        +

                                        Description

                                        Example Value

                                        +

                                        Example Value

                                        Name

                                        +

                                        Name

                                        Specifies the alarm rule name.

                                        +

                                        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

                                        Alarm Type

                                        +

                                        Monitored Object

                                        Specifies the alarm type to which the alarm rule applies.

                                        +

                                        When you set Monitoring Scope to Specific resources, you can add new monitored objects and remove the original monitored objects.

                                        Metric

                                        +

                                        N/A

                                        Resource Type

                                        +

                                        Method

                                        Specifies the type of the resource the alarm rule is created for.

                                        +

                                        You can select Associate template or Configure manually.

                                        +
                                        NOTE:
                                        • If you select Associate template, the alarm policies that match the current resource and dimension in the alarm template will be synchronized to the alarm policies of the current alarm rule. These policies will automatically be modified accordingly after the associated custom template is modified.
                                        • For custom metric based alarm rules, only the Configure manually option is available.
                                        +

                                        Elastic Cloud Server

                                        +

                                        Configure manually

                                        Dimension

                                        +

                                        Alarm Policy

                                        Specifies the metric dimension of the selected resource type.

                                        -

                                        ECSs

                                        -

                                        Monitoring Scope

                                        -

                                        Specifies the monitoring scope the alarm rule applies to.

                                        -

                                        Resource Groups

                                        -

                                        Monitored Object

                                        -

                                        When you set Monitoring Scope to Specific resources, you can add new monitored objects and remove the original monitored objects.

                                        -

                                        -

                                        -

                                        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

                                        -

                                        Alarm Policy

                                        -

                                        Specifies the policy for triggering an alarm.

                                        +

                                        Specifies the policy for triggering an alarm.

                                        Whether to trigger an alarm depends on whether the data in the specified consecutive periods reaches the threshold. For example, Cloud Eye triggers an alarm if the average CPU usage of the monitored object is 80% or more for three consecutive 5-minute periods.

                                        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

                                        Metric Name

                                        +

                                        Metric Name

                                        For example:

                                        -
                                        • CPU Usage

                                          Indicates the CPU usage of the monitored object in percent.

                                          +

                                        Examples:

                                        +
                                        • CPU Usage

                                          CPU usage of the monitored object in percent.

                                        -
                                        • Memory Usage

                                          Indicates the memory usage of the monitored object in percent.

                                          +
                                          • Memory Usage

                                            Memory usage of the monitored object in percent.

                                        CPU Usage

                                        +

                                        CPU Usage

                                        Alarm Policy

                                        +

                                        Alarm Policy

                                        Specifies the policy for triggering an alarm.

                                        +

                                        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

                                        Operation

                                        +

                                        Operation

                                        You can click Delete to delete an alarm policy.
                                        NOTE:

                                        Under the policy table, you can also click Add Alarm Policy to add more alarm policies if needed.

                                        +
                                        You can click Delete to delete an alarm policy.
                                        NOTE:

                                        Under the policy table, you can also click Add Alarm Policy to add more alarm policies if needed.

                                        Delete

                                        +

                                        Delete

                                        Mount Point or Disk

                                        +

                                        Mount Point or Disk

                                        This parameter is displayed on the console and can be configured only when the following conditions are met:

                                        +

                                        This parameter is displayed on the console and can be configured only when the following conditions are met:

                                        • The monitoring scope is Resource groups or 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.

                                        +

                                        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

                                        +

                                        /dev

                                        Alarm Notification

                                        +

                                        Alarm Notification

                                        Specifies whether to notify users by sending emails, SMS messages, or HTTP/HTTPS messages.

                                        +

                                        Specifies whether to notify users by sending emails, SMS messages, or HTTP/HTTPS messages.

                                        N/A

                                        +

                                        N/A

                                        Notification Object

                                        +

                                        Notification Object

                                        Specifies the object to which alarm notifications will be sent. You can select the account contact or a topic.

                                        +

                                        Specifies the object that receives alarm notifications, which can be an account 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 and add subscriptions to it first. For details, see Creating a Topic and Adding Subscriptions.
                                        		  

                                        Notification Window

                                        +

                                        N/A

                                        Cloud Eye sends notifications only within the validity period specified in the alarm rule.

                                        +

                                        Notification Window

                                        +

                                        Cloud Eye sends notifications only within the validity period specified in the alarm rule.

                                        If Notification Window is set to 00:00-08:00, Cloud Eye sends notifications only from 00:00 to 08:00.

                                        N/A

                                        +

                                        N/A

                                        Trigger Condition

                                        +

                                        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.

                                        +

                                        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.

                                        N/A

                                        -

                                        (Optional) Enterprise Project

                                        -

                                        Specifies the enterprise project that the alarm rule belongs to. Only users with the enterprise project permissions can manage the alarm rule.

                                        -

                                        default

                                        +

                                        N/A
                                        -
                                        Table 2 Configuring event alarm parameters

                                        Parameter

                                        +
                                        - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + - - - - - - - - diff --git a/docs/ces/umn/ces_01_0082.html b/docs/ces/umn/ces_01_0082.html index 378e3a9b2..0950313e0 100644 --- a/docs/ces/umn/ces_01_0082.html +++ b/docs/ces/umn/ces_01_0082.html @@ -7,13 +7,13 @@
                                        Table 2 Configuring event alarm parameters

                                        Parameter

                                        Description

                                        +

                                        Description

                                        Example Value

                                        +

                                        Example Value

                                        Name

                                        +

                                        Name

                                        Specifies the alarm rule name.

                                        +

                                        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

                                        Alarm Type

                                        +

                                        Method

                                        Specifies the alarm type to which the alarm rule applies.

                                        +

                                        You can select Associate template or Configure manually.

                                        +
                                        NOTE:
                                        • If you select Associate template, the alarm policies that match the current resource and dimension in the alarm template will be synchronized to the alarm policies of the current alarm rule. These policies will automatically be modified accordingly after the associated custom template is modified.
                                        • For custom event based alarm rules, only the Configure manually option is available.
                                        +

                                        Event

                                        +

                                        Configure manually

                                        Event Type

                                        +

                                        Template

                                        Specifies the event type, which can be System event or Custom event.

                                        +

                                        Specifies the template to be used.

                                        +

                                        You can select a default or a custom alarm template.

                                        Custom event

                                        +

                                        ECS event template

                                        Event Source

                                        +

                                        Alarm Policy

                                        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.

                                        +

                                        Specifies the policy for triggering an alarm.

                                        The event that triggers an alarm is an instant operation. 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

                                        +

                                        N/A

                                        Event Name

                                        +

                                        Event Name

                                        Specifies the event name.

                                        +

                                        Specifies the event name.

                                        For events supported by event monitoring, see Events Supported by Event Monitoring.

                                        ECS deleted

                                        +

                                        ECS deleted

                                        Trigger Mode

                                        +

                                        Trigger Mode

                                        You can select Immediate trigger or Accumulative trigger based on the operation severity.

                                        +

                                        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

                                        +

                                        Immediate trigger

                                        Alarm Policy

                                        +

                                        Alarm Policy

                                        Specifies the policy for triggering an alarm.

                                        +

                                        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.

                                        +

                                        An alarm is triggered if the event occurred for three consecutive periods of 5 minutes.

                                        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

                                        Operation

                                        +

                                        Operation

                                        You can click Delete to delete the alarm policy.
                                        NOTE:

                                        Under the policy table, you can also click Add Alarm Policy to add more alarm policies if needed.

                                        +
                                        You can click Delete to delete an alarm policy.
                                        NOTE:

                                        Under the policy table, you can also click Add Alarm Policy to add more alarm policies if needed.

                                        Delete

                                        +

                                        Delete

                                        Alarm Notification

                                        +

                                        Alarm Notification

                                        Specifies whether to notify users when alarms are triggered. Notifications can be sent by email, SMS message, or HTTP/HTTPS message.

                                        +

                                        Specifies whether to notify users when alarms are triggered. Notifications can be sent by email, SMS message, or HTTP/HTTPS request.

                                        N/A

                                        +

                                        N/A

                                        Notification Object

                                        +

                                        Notification Object

                                        Specifies the object to which alarm notifications will be sent. You can select the account contact or a topic.

                                        +

                                        Specifies the object that receives alarm notifications, which can be an account 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 and add subscriptions to it first. For details, see Creating a Topic and Adding Subscriptions.
                                        		  

                                        Notification Window

                                        +

                                        N/A

                                        Cloud Eye sends notifications only within the validity period specified in the alarm rule.

                                        +

                                        Notification Window

                                        +

                                        Cloud Eye sends notifications only within the validity period specified in the alarm rule.

                                        If Notification Window is set to 00:00-08:00, Cloud Eye sends notifications only from 00:00 to 08:00.

                                        N/A

                                        +

                                        N/A

                                        Trigger Condition

                                        +

                                        Trigger Condition

                                        You can only select Generated alarm as the condition for triggering alarm notifications.

                                        +

                                        You can only select Generated alarm as the condition for triggering alarm notifications.

                                        N/A

                                        -

                                        (Optional) Enterprise Project

                                        -

                                        Specifies the enterprise project that the alarm rule belongs to. Only users with the enterprise project permissions can manage the alarm rule.

                                        -

                                        default

                                        +

                                        N/A
                                        @@ -20,6 +20,16 @@ + + + + + + diff --git a/docs/ces/umn/ces_01_0084.html b/docs/ces/umn/ces_01_0084.html index 0fba55498..b281a6e47 100644 --- a/docs/ces/umn/ces_01_0084.html +++ b/docs/ces/umn/ces_01_0084.html @@ -1,7 +1,7 @@ -

                                        Modifying a Custom Alarm Template

                                        -
                                        1. Log in to the management console.
                                        2. In the upper left corner, select a region and project.
                                        3. Click Service List in the upper left corner and select Cloud Eye.
                                        4. Choose Alarm Management > Alarm Templates.
                                        5. Click the Custom Templates tab.
                                        6. Locate the row containing the alarm template to be modified, and click Modify in the Operation column.
                                        7. On the Modify Custom Template page, modify the configured parameters by referring to Table 1.
                                          Figure 1 Modify Custom Template
                                          +

                                          Modifying a Custom Metric or Event Template

                                          +
                                          1. Log in to the management console.
                                          2. In the upper left corner, select a region and project.
                                          3. Choose Service List > Cloud Eye.
                                          4. Choose Alarm Management > Alarm Templates.
                                          5. Click the Custom Templates or Custom Event Templates tab.
                                          6. Locate the row containing the alarm template to be modified, and click Modify in the Operation column.
                                          7. On the Modify Custom Template page, modify the configured parameters by referring to Table 1.
                                            Figure 1 Modifying a custom template
                                          8. Click Modify.
                                          diff --git a/docs/ces/umn/ces_01_0085.html b/docs/ces/umn/ces_01_0085.html index 1e5ceb006..203d52487 100644 --- a/docs/ces/umn/ces_01_0085.html +++ b/docs/ces/umn/ces_01_0085.html @@ -1,11 +1,11 @@ -

                                          Deleting a Custom Alarm Template

                                          +

                                          Deleting a Custom Metric or Event Template

                                          Deleted custom templates cannot be restored. Exercise caution when performing this operation.

                                          -
                                          1. Log in to the management console.
                                          2. In the upper left corner, select a region and project.
                                          3. Click Service List in the upper left corner and select Cloud Eye.
                                          4. Choose Alarm Management > Alarm Templates.
                                          5. Click the Custom Templates tab.
                                            • Locate the alarm template to be deleted and click Delete in the Operation column.
                                            • Select multiple templates and click Delete above the list.
                                            +
                                            1. Log in to the management console.
                                            2. In the upper left corner, select a region and project.
                                            3. Choose Service List > Cloud Eye.
                                            4. Choose Alarm Management > Alarm Templates.
                                            5. Click the Custom Templates or Custom Event Templates tab.
                                              • Locate the alarm template to be deleted and click Delete in the Operation column.
                                              • Select multiple templates and click Delete above the list.
                                            6. In the displayed dialog box, click OK.
                                            -
                                            Figure 1 Delete Custom Template
                                            +
                                            Figure 1 Deleting a custom template
                                          diff --git a/docs/ces/umn/ces_01_0086.html b/docs/ces/umn/ces_01_0086.html deleted file mode 100644 index 4da65bdc0..000000000 --- a/docs/ces/umn/ces_01_0086.html +++ /dev/null @@ -1,14 +0,0 @@ - - -

                                          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 index 79814d79c..aed488988 100644 --- a/docs/ces/umn/ces_01_0087.html +++ b/docs/ces/umn/ces_01_0087.html @@ -1,127 +1,240 @@ -

                                          Key Cloud Eye Operations

                                          -
                                          -
                                        Table 1 Parameters

                                        Parameter

                                        (Optional) Provides supplementary information about the custom template.

                                        Alarm Type

                                        +

                                        You can select Metric or Event.

                                        +

                                        Event Type

                                        +

                                        Specifies the event type when you set Alarm Type to Event. You can only select System event.

                                        +

                                        Method

                                        You can select Using existing template or Configure manually.

                                        @@ -29,7 +39,7 @@

                                        Add Resource Type

                                        Specifies the type of the resource the alarm rule is created for.

                                        -

                                        Example value: Elastic Cloud Server

                                        +

                                        Example value: Elastic Cloud Server

                                        NOTE:

                                        A maximum of 50 resource types can be added for each service.

                                        - - + + + - - - @@ -39,25 +82,25 @@ - - - - @@ -83,139 +126,139 @@ - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/ces/umn/ces_01_0108.html b/docs/ces/umn/ces_01_0108.html new file mode 100644 index 000000000..d4e37c74f --- /dev/null +++ b/docs/ces/umn/ces_01_0108.html @@ -0,0 +1,100 @@ + + +

                                        Task Center

                                        +

                                        On the Task Center page, you can export data including monitoring data and alarm records. You can go to the Alarm Records and Server Monitoring (Elastic Cloud Server) pages to create an export task. After the export task is submitted, you can view the progress and download the file on the Task Center page.

                                        +

                                        The export tasks on the Monitoring Data Export Tasks and Alarm Record Export Tasks tabs will be cleared seven days after they are created.

                                        +
                                        +

                                        Exporting Monitoring Data

                                        1. Log in to the management console.
                                        2. Choose Service List > Cloud Eye.
                                          • Export ECS or BMS monitoring data. In the navigation pane, choose Server Monitoring > Elastic Cloud Server.
                                          • Export cloud service monitoring data. In the navigation pane, choose Cloud Service Monitoring.
                                          +
                                        3. Click Export Data in the upper right corner.
                                          Figure 1 Exporting data
                                          +

                                          The export feature of the new edition only works with certain cloud services, while others still require the older edition. Future updates will extend this compatibility to all cloud services. This enhanced feature allows you to export more monitoring data without restrictions. Once you submit an export task, you can manage it in the task center.

                                          +
                                          For services that support the new export feature, the Export Data dialog box of the new edition is displayed by default. To return to the earlier version, click Earlier Edition. Figure 2 shows the earlier edition of the Export Data dialog box. In the earlier edition, the data export task is not displayed on the Task Center page. Data can be directly downloaded on the current page.
                                          Figure 2 Exporting data (earlier edition)
                                          +
                                          +
                                          +
                                        4. In the Export Data dialog box, set parameters. +
                                        Table 1 Cloud Eye operations that can be recorded by CTS

                                        Operation

                                        +

                                        Key Cloud Eye Operations Supported by CTS

                                        +

                                        With CTS, you can record operations associated with Cloud Eye for future query, audit, and backtracking.

                                        +

                                        Prerequisites

                                        CTS has been enabled.

                                        +
                                        +

                                        Key Cloud Eye Operations

                                        +
                                        - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                                        Table 1 Cloud Eye operations that can be recorded by CTS

                                        Operation

                                        Resource Type

                                        +

                                        Resource Type

                                        Trace Name

                                        +

                                        Event Name

                                        Creating an alarm rule

                                        +

                                        Creating an alarm rule

                                        alarm_rule

                                        +

                                        alarm_rule

                                        createAlarmRule

                                        +

                                        createAlarmRule

                                        Deleting an alarm rule

                                        +

                                        Deleting an alarm rule

                                        alarm_rule

                                        +

                                        alarm_rule

                                        deleteAlarmRule

                                        +

                                        deleteAlarmRule

                                        Disabling an alarm rule

                                        +

                                        Disabling an alarm rule

                                        alarm_rule

                                        +

                                        alarm_rule

                                        disableAlarmRule

                                        +

                                        disableAlarmRule

                                        Enabling an alarm rule

                                        +

                                        Enabling an alarm rule

                                        alarm_rule

                                        +

                                        alarm_rule

                                        enableAlarmRule

                                        +

                                        enableAlarmRule

                                        Modifying an alarm rule

                                        +

                                        Modifying an alarm rule

                                        alarm_rule

                                        +

                                        alarm_rule

                                        updateAlarmRule

                                        +

                                        updateAlarmRule

                                        Updating the alarm status to Alarm

                                        +

                                        Creating a custom template

                                        alarm_rule

                                        +

                                        alarm_template

                                        alarmStatusChangeToAlarm

                                        +

                                        createAlarmTemplate

                                        Updating the alarm status to Insufficient data

                                        +

                                        Deleting a custom template

                                        alarm_rule

                                        +

                                        alarm_template

                                        alarmStatusChangeToInsufficientData

                                        +

                                        deleteAlarmTemplate

                                        Updating the alarm status to OK

                                        +

                                        Modifying a custom template

                                        alarm_rule

                                        +

                                        alarm_template

                                        alarmStatusChangeToOk

                                        +

                                        updateAlarmTemplate

                                        Creating a custom template

                                        +

                                        Creating a dashboard

                                        alarm_template

                                        +

                                        dashboard

                                        createAlarmTemplate

                                        +

                                        createDashboard

                                        Deleting a custom template

                                        +

                                        Deleting a dashboard

                                        alarm_template

                                        +

                                        dashboard

                                        deleteAlarmTemplate

                                        +

                                        deleteDashboard

                                        Modifying a custom template

                                        +

                                        Modifying a dashboard

                                        alarm_template

                                        +

                                        dashboard

                                        updateAlarmTemplate

                                        +

                                        updateDashboard

                                        Creating a dashboard

                                        +

                                        Enabling or disabling a Kafka data dump task

                                        dashboard

                                        +

                                        data_share_job

                                        createDashboard

                                        +

                                        actionDataShareJob

                                        Deleting a dashboard

                                        +

                                        Creating a Kafka data dump task

                                        dashboard

                                        +

                                        data_share_job

                                        deleteDashboard

                                        +

                                        createDataShareJob

                                        Modifying a dashboard

                                        +

                                        Deleting a Kafka data dump task

                                        dashboard

                                        +

                                        data_share_job

                                        updateDashboard

                                        +

                                        deleteDataShareJob

                                        Exporting monitoring data

                                        +

                                        Updating a Kafka data dump task

                                        metric

                                        +

                                        data_share_job

                                        downloadMetricsReport

                                        +

                                        updateDataShareJob

                                        +

                                        Sorting metrics

                                        +

                                        metric

                                        +

                                        createMetricSort

                                        +

                                        Exporting monitoring data

                                        +

                                        metrics_job

                                        +

                                        createMetricsJobs

                                        +

                                        Batch enabling or disabling alarm policies for one-click monitoring

                                        +

                                        one_click_alarm

                                        +

                                        batchActionOneClickAlarmPolicy

                                        +

                                        Batch disabling one-click monitoring

                                        +

                                        one_click_alarm

                                        +

                                        batchDeleteOneClickAlarm

                                        +

                                        Enabling or disabling one-click monitoring

                                        +

                                        one_click_alarm

                                        +

                                        updateOneClickAlarm

                                        +

                                        Updating alarm notifications for one service in one-click monitoring

                                        +

                                        one_click_alarm

                                        +

                                        updateOneClickAlarmNotifications

                                        +

                                        Batch deleting data export tasks

                                        +

                                        report_job

                                        +

                                        batchDeleteReportJobs

                                        +

                                        Creating a data export task

                                        +

                                        report_job

                                        +

                                        createReportJobs

                                        +

                                        Downloading an export report

                                        +

                                        report_job

                                        +

                                        downloadReportJobs

                                        +

                                        Clearing tenant resources

                                        +

                                        resource_clear

                                        +

                                        clearAllResource

                                        +

                                        Creating a resource group

                                        +

                                        resource_group

                                        +

                                        createResourceGroup

                                        +

                                        Updating a resource group

                                        +

                                        resource_group

                                        +

                                        deleteResourceGroup

                                        +

                                        Deleting a resource group

                                        +

                                        resource_group

                                        +

                                        updateResourceGroup

                                        +

                                        Creating a graph

                                        +

                                        widget

                                        +

                                        createWidget

                                        +

                                        Updating a graph

                                        +

                                        widget

                                        +

                                        deleteWidget

                                        +

                                        Deleting a graph

                                        +

                                        widget

                                        +

                                        updateWidget
                                        -
                                        -
                                        -
                                        Parent topic: Auditing Operation Records on Cloud Eye
                                        +

                                        Viewing Audit Logs

                                        For details, see Querying Real-Time Traces.

                                        diff --git a/docs/ces/umn/ces_01_0088.html b/docs/ces/umn/ces_01_0088.html deleted file mode 100644 index a43738667..000000000 --- a/docs/ces/umn/ces_01_0088.html +++ /dev/null @@ -1,22 +0,0 @@ - - -

                                        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

                                        1. Log in to the management console.
                                        2. In the upper left corner, select a region and project.
                                        3. Click in the upper left corner and choose Management & Deployment > Cloud Trace Service. The CTS console is displayed.
                                        4. Choose Trace List in the navigation pane on the left.
                                        5. Set filters to search for your desired traces, as shown in Figure 1. The following filters are available.
                                          Figure 1 Filters
                                          -
                                          • 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: Select Last 1 hour, Last 1 day, or Last 1 week, or specify a custom time range within the last seven days.
                                          -
                                          -
                                        6. Click Query.
                                        7. 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 5,000 records.
                                          • Click to view the latest information about traces.
                                          -
                                        8. Click on the left of a trace to expand its details.
                                          Figure 2 Expanding trace details
                                          -
                                        9. 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_0090.html b/docs/ces/umn/ces_01_0090.html index 297f2d3eb..58e1e07a7 100644 --- a/docs/ces/umn/ces_01_0090.html +++ b/docs/ces/umn/ces_01_0090.html @@ -11,11 +11,11 @@

                                        Process Flow

                                        Figure 1 Process for granting Cloud Eye permissions

                                        -
                                        1. 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.

                                          +
                                          1. 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 are all Cloud Eye permissions. For more refined Cloud Eye permissions, see Table 3.
                                            -
                                          2. 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.
                                          3. Log in and verify permissions.

                                            Log in to the Cloud Eye console as the created user, and verify that the user 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.

                                            +
                                          4. 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.
                                          5. Log in to the console and verify permissions.

                                            Log in to the Cloud Eye console as the created user, and verify that the user 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 index 5bb771a33..136a3f17b 100644 --- a/docs/ces/umn/ces_01_0091.html +++ b/docs/ces/umn/ces_01_0091.html @@ -18,7 +18,7 @@ }
                                        -
                                        • 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.

                                          +
                                          • Example 2: denying alarm rule deletion

                                            A policy with only "Deny" permissions must be used 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": [
diff --git a/docs/ces/umn/ces_01_0097.html b/docs/ces/umn/ces_01_0097.html
index 379d7411b..006c09b19 100644
--- a/docs/ces/umn/ces_01_0097.html
+++ b/docs/ces/umn/ces_01_0097.html
@@ -8,27 +8,70 @@

                                        2025-02-14

                                        +

                                        2025-11-18

                                        This release incorporates the following changes:

                                        - +

                                        Modified the following content:

                                        +

                                        Added Viewing My Dashboards.

                                        +

                                        Added Copying a Dashboard.

                                        +

                                        Added One-Click Monitoring.

                                        +

                                        Added Configuring an Agency by One Click.

                                        +

                                        Added Task Center.

                                        +

                                        Added Cloud Services Displayed in the Cloud Service Monitoring List.

                                        +

                                        Added How Do I Configure an Agency?.

                                        +

                                        Added What Can I Do If the System Displays a Message Indicating Insufficient Permissions When I Click Configure on the Server Monitoring Page?.

                                        +

                                        Added How Do I Enable or Disable Metric Collection by Modifying the Configuration File?.

                                        +

                                        Added How Do I Change the Agent Resource Usage Threshold by Modifying the Configuration File?.

                                        +

                                        Added How Do I Change the Process Collection Frequency by Modifying the Configuration File?.

                                        +

                                        Added What Metrics Are Supported by the Agent?.

                                        +

                                        Updated Constraints.

                                        +

                                        Updated Permissions.

                                        +

                                        Updated Viewing Overview.

                                        +

                                        Updated My Dashboards.

                                        +

                                        Updated Creating a Resource Group.

                                        +

                                        Updated Resource Group List.

                                        +

                                        Updated Resource Overview.

                                        +

                                        Updated Creating an Alarm Rule.

                                        +

                                        Updated Viewing Alarm Records.

                                        +

                                        Updated Modifying an Alarm Rule.

                                        +

                                        Updated Copying an Alarm Rule.

                                        +

                                        Updated Alarm Templates.

                                        +

                                        Updated Introduction to Server Monitoring.

                                        +

                                        Updated Modifying the DNS Server Address and Adding Security Group Rules (Linux).

                                        +

                                        Updated Installing the Agent on a Linux Server.

                                        +

                                        Updated (Optional) Manually Configuring the Agent on a Linux Server.

                                        +

                                        Updated Installing the Agent on a Windows server.

                                        +

                                        Updated (Optional) Manually Configuring the Agent on a Windows Server.

                                        +

                                        Updated Installing the Agents in Batches on Linux ECSs.

                                        +

                                        Updated Managing the Agent.

                                        +

                                        Updated Viewing Server Monitoring Metrics.

                                        +

                                        Updated Events Supported by Event Monitoring.

                                        +

                                        Updated Adding a Dump Task.

                                        +

                                        Updated Key Cloud Eye Operations Supported by CTS.

                                        +

                                        Updated Services Interconnected with Cloud Eye.

                                        +

                                        Updated How Long Is Metric Data Retained?.

                                        +

                                        2025-02-14

                                        +

                                        Modified the following content:

                                        +

                                        2024-09-13

                                        This release incorporates the following changes: +
                                        Modified the following content:

                                        2022-10-10

                                        This release incorporates the following changes:

                                        +

                                        Modified the following content:

                                        • 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:

                                        +

                                        Modified the following content:

                                        Added Resource Groups.

                                        2019-11-30

                                        This release incorporates the following changes:

                                        +

                                        Modified the following content:

                                        • 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

                                        This release incorporates the following changes:

                                        +

                                        Modified the following content:

                                        2019-08-31

                                        This release incorporates the following changes:

                                        +

                                        Modified the following content:

                                        2019-07-31

                                        This release incorporates the following changes:

                                        +

                                        Modified the following content:

                                        2018-08-30

                                        This release incorporates the following changes:

                                        +

                                        Modified the following content:

                                        Interconnected with Cloud Search Service (CSS).

                                        2018-07-30

                                        This release incorporates the following changes:

                                        +

                                        Modified the following content:

                                        Users can search for or select monitored objects when creating alarm rules.

                                        2018-06-30

                                        This release incorporates the following changes:

                                        -
                                        • Users can sort graphs by dragging them.
                                        • Users can view graphs directly from the alarm rule list on the Alarm Rules page.
                                        • Added the automatic refresh function to both standard and expanded graphs.
                                        • Added metrics for the enhanced load balancer and enhanced load balancer listener.
                                        +

                                        Modified the following content:

                                        +
                                        • Users can sort graphs by dragging them.
                                        • Users can view graphs directly from the alarm rule list on the Alarm Rules page.
                                        • Added the automatic refresh function to both standard and expanded graphs.
                                        • Added metrics for enhanced load balancers and their listeners.

                                        2018-05-30

                                        This release incorporates the following changes:

                                        +

                                        Modified the following content:

                                        • Added the auto refresh button to the monitoring panels.

                                        2018-04-30

                                        This release incorporates the following changes:

                                        +

                                        Modified the following content:

                                        Optimized the strings for alarm rule creation.

                                        2018-03-30

                                        This release incorporates the following changes:

                                        +

                                        Modified the following content:

                                        • Added Virtual Private Cloud (VPC) traffic metrics.
                                        • Added the Alarm History page.
                                        • Optimized the monitoring data export function, in which users can select the time for the data to be exported.

                                        2018-02-28

                                        This release incorporates the following changes:

                                        +

                                        Modified the following content:

                                        Updated Virtual Private Cloud (VPC) metrics.

                                        2018-01-30

                                        This release incorporates the following changes:

                                        +

                                        Modified the following content:

                                        Launched the Custom Monitoring function.

                                        2017-11-30

                                        This release incorporates the following changes:

                                        +

                                        Modified the following content:

                                        Added Auto Scaling (AS) metrics.

                                        2017-10-30

                                        This release incorporates the following changes:

                                        +

                                        Modified the following content:

                                        • Optimized the descriptions of Distributed Message Service (DMS) metrics.
                                        • When you create a topic, the page jumps from the Cloud Eye console to the SMN console.
                                        • Added Scalable File Service (SFS) metrics.

                                        2017-09-30

                                        This release incorporates the following changes:

                                        +

                                        Modified the following content:

                                        • Added the Custom Alarm Templates function.
                                        • Added Monitoring Overview.

                                        2017-08-30

                                        This release incorporates the following changes:

                                        +

                                        Modified the following content:

                                        • Added the alarm template.
                                        • Updated the process of adding alarm rules.

                                        2017-07-30

                                        This release incorporates the following changes:

                                        +

                                        Modified the following content:

                                        • Added Distributed Cache Service (DCS) metrics.
                                        • Added descriptions for API Gateway metrics.
                                        • Deleted an Elastic Cloud Server (ECS) metric that can recover ECSs.
                                        • Added an FAQ: Under What Circumstances Will an Alarm Rule Trigger "Insufficient data"?

                                        2017-06-30

                                        This release incorporates the following changes:

                                        +

                                        Modified the following content:

                                        Optimized the Instance Monitoring page and supported tiled display of multiple metrics.

                                        2017-05-26

                                        This release incorporates the following changes:
                                        • Added Distributed Message Service (DMS) metrics.
                                        • Added Elastic Cloud Server (ECS) metrics.
                                        • Added Metric Quantity description.
                                        • Added Sum. as an aggregation method.
                                        +
                                        Modified the following content:
                                        • Added Distributed Message Service (DMS) metrics.
                                        • Added Elastic Cloud Server (ECS) metrics.
                                        • Added Metric Quantity description.
                                        • Added Sum. as a rollup method.

                                        2017-04-28

                                        This release incorporates the following changes:

                                        +

                                        Modified the following content:

                                        Added Virtual Private Cloud (VPC) traffic metrics.

                                        2017-03-30

                                        This release incorporates the following changes:
                                        • Added an Elastic Cloud Server (ECS) metric that can recover ECSs.
                                        +
                                        Modified the following content:
                                        • Added an Elastic Cloud Server (ECS) metric that can recover ECSs.

                                        2017-02-27

                                        This release incorporates the following changes:

                                        +

                                        Modified the following content:

                                        • Added the operation of creating a monitoring panel.
                                        • Added the Cloud Eye data aggregation mechanism.
                                        • Interconnected Cloud Eye to the SMN console to create topics.

                                        2017-01-19

                                        This release incorporates the following changes:

                                        -

                                        Added the aggregation methods supported by Cloud Eye.

                                        +

                                        Modified the following content:

                                        +

                                        Added the rollup methods supported by Cloud Eye.

                                        2016-12-30

                                        This release incorporates the following changes:

                                        +

                                        Modified the following content:

                                        Added the custom metric function.

                                        2016-11-24

                                        This release incorporates the following changes:

                                        +

                                        Modified the following content:

                                        Added the function of querying historical alarms.

                                        2016-10-19

                                        This release incorporates the following changes:

                                        +

                                        Modified the following content:

                                        Deleted Resource Template Service (RTS) metrics.

                                        2016-07-15

                                        This release incorporates the following changes:

                                        +

                                        Modified the following content:

                                        Added descriptions for Relational Database Service (RDS) metrics.
                                        + + + + + + + + + + + + + + + + + + + +
                                        Table 1 Parameters for exporting data (new edition)

                                        Parameter

                                        +

                                        Description

                                        +

                                        Task Name

                                        +

                                        Name of an export task.

                                        +

                                        The value allows 1 to 32 characters and can only contain letters, digits, hyphens (-), and underscores (_).

                                        +

                                        Statistic

                                        +

                                        There are two modes: Aggregated data and Raw data.

                                        +
                                        • Aggregated data: Data can be exported after being aggregated using the maximum value, minimum value, average value, or sum value.
                                        • Raw data: The original data is exported.
                                        +

                                        Time Range

                                        +

                                        Select the time range for the data to be exported.

                                        +
                                        • Data of a maximum of the last 90 days can be exported for an aggregate value.
                                        • Raw data from the last 48 hours is available for export.
                                        +

                                        Aggregated By

                                        +

                                        This parameter is mandatory when Statistic is set to Aggregated data.

                                        +

                                        If you select Custom range, data aggregated during your configured time range will be exported. If you select one of the other options, data will be aggregated based on your selected granularity and then exported.

                                        +

                                        Monitoring Item

                                        +
                                        • Resource Type: The selected cloud service is used by default. You do not need to set this parameter.
                                        • Dimension: Specify the dimension name of the metric to be exported.
                                        • Monitored Object: You can select All Resources or Specific resources.
                                        • Metric: Specify one or more metrics to be exported.
                                        +
                                        +
                                        + +
                                        + + + + + + + + + + + + + + + + +
                                        Table 2 Parameters for exporting data (earlier edition)

                                        Parameter

                                        +

                                        Description

                                        +

                                        Time Range

                                        +

                                        Select the time range for the data to be exported.

                                        +

                                        Period

                                        +

                                        Select how often you want to export the monitoring data.

                                        +

                                        Statistic

                                        +

                                        This parameter is required when Period is set to 5 minutes, 20 minutes, 1 hour, 4 hours, or 2 hours. You can export the aggregated maximum value, minimum value, average value, or sum value.

                                        +

                                        Monitoring Item

                                        +
                                        • Resource Type: The selected cloud service is used by default. You do not need to set this parameter.
                                        • Dimension: Specify the dimension name of the metric to be exported.
                                        • Monitored Object: You can select All Resources or Specific resources.
                                        • Metric: Specify one or more metrics to be exported.
                                        +
                                        +
                                        +
                                      7. After the configuration is complete, click Export.

                                        After the export task is submitted, choose Task Center. On the Monitoring Data Export Tasks tab, view and download task.

                                        +
                                      8. In the navigation pane, choose Task Center.
                                      9. On the Monitoring Data Export Task tab page, view or delete export tasks, and download their export results.
                                        • Filtering export tasks: In the search box above the list, filter export tasks by task name, resource type, statistical method, time range, status, or creation time.
                                        • Viewing details of multiple export tasks in batches: Select multiple export tasks from the list and click the small arrow in the bottom-right corner to view the monitoring details of multiple events in batches.
                                        • Downloading the export results: Locate the target export task and click Download in the Operation column.
                                        • Deleting one or more export tasks:
                                          • Locate an export task and click Delete in the Operation column to delete it.
                                          • Select desired export tasks and click Delete above the list to delete them in batches.
                                          +
                                        +
                                        Figure 3 Viewing monitoring data export tasks
                                        +
                                        10. + +

                                        Exporting Alarm Records

                                        1. Log in to the management console.
                                        2. Choose Service List > Cloud Eye.
                                        3. Choose Alarm Management > Alarm Records.
                                        4. On the Alarm Records page, click Export.

                                          You can export all alarm records or alarm records filtered by status, alarm severity, alarm rule name, resource type, resource ID, and alarm rule ID above the alarm record list.

                                          +
                                          +
                                        5. In the displayed Export Alarm Records dialog box, enter an export task name and click OK.

                                          The name allows 1 to 32 characters and can only contain letters, digits, hyphens (-), and underscores (_).

                                          +
                                          Figure 4 Entering an export task name
                                          +

                                          After the export task is submitted, you can view and download the alarm records under the Alarm Record Export Tasks tab on the Task Center page.

                                          +
                                        6. In the navigation pane, choose Task Center.
                                        7. On the Alarm Record Export Tasks tab page, view or delete export tasks, and download their export results.
                                          • Filtering export tasks: In the search box above the export list, filter export tasks by task name, time range, filter criteria, status, or creation time.
                                          • Downloading the export results: Locate the target export task and click Download in the Operation column.
                                          • Deleting one or more export tasks:
                                            • Locate an export task and click Delete in the Operation column to delete it.
                                            • Select desired export tasks and click Delete above the list to delete them in batches.
                                            +
                                          +
                                          Figure 5 Viewing alarm record export tasks
                                          +
                                        +
                                        +

                                        + + diff --git a/docs/ces/umn/ces_01_0109.html b/docs/ces/umn/ces_01_0109.html index e321b7d89..fc8c7c618 100644 --- a/docs/ces/umn/ces_01_0109.html +++ b/docs/ces/umn/ces_01_0109.html @@ -3,7 +3,7 @@

                                        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: 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.
                                        • Creating 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 aggregation 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.
                                        • Creating 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 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 aggregation 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 31a2c0523..bda6a3b22 100644 --- a/docs/ces/umn/ces_01_0110.html +++ b/docs/ces/umn/ces_01_0110.html @@ -1,11 +1,11 @@

                                        Viewing Metrics

                                        -
                                        1. Log in to the management console.
                                        2. In the upper left corner, select a region and project.
                                        3. Click Service List in the upper left corner and select Cloud Eye.
                                        4. In the navigation pane on the left, choose Cloud Service Monitoring and select the cloud service whose resources you want to view.
                                        5. 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.
                                          • For details about how to export monitoring data, see How Can I Export Collected Data?
                                          +
                                          1. Log in to the management console.
                                          2. In the upper left corner, select a region and project.
                                          3. Choose Service List > Cloud Eye.
                                          4. In the navigation pane on the left, choose Cloud Service Monitoring and select the cloud service whose resources you want to view.
                                          5. 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.
                                            • You can export monitoring data by referring to Exporting Monitoring Data.
                                          6. 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.

                                            -
                                          7. 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.
                                            • If you select 1h, 3h, 12h, or 1d, raw data is displayed by default. You can set Period and Statistic to change the aggregation period of monitoring data. For details about aggregation periods, see What Is Aggregation?
                                            • If you select 7d or 30d, aggregated data is displayed by default. You can set Period and Statistic to change the aggregation period of monitoring data.
                                            +
                                          8. Hover your mouse over a graph. In the upper right corner, click to view monitoring details on an enlarged graph. Select a default or custom time range to view the metrics.
                                            • 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.
                                          9. 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 index b59b32f5a..b693d467b 100644 --- a/docs/ces/umn/ces_01_0112.html +++ b/docs/ces/umn/ces_01_0112.html @@ -1,7 +1,7 @@

                                          Copying an Alarm Template

                                          -
                                          1. Log in to the management console.
                                          2. In the upper left corner, select a region and project.
                                          3. Click Service List in the upper left corner and select Cloud Eye.
                                          4. Choose Alarm Management > Alarm Templates.
                                            1. On the Default Templates tab, locate the desired alarm template and click Copy in the Operation column.
                                            2. Click the Custom Templates tab, locate the desired alarm template, and choose More > Copy in the Operation column.
                                            +
                                            1. Log in to the management console.
                                            2. In the upper left corner, select a region and project.
                                            3. Choose Service List > Cloud Eye.
                                            4. Choose Alarm Management > Alarm Templates.
                                              1. On the Default Templates or Default Event Templates tab, locate the desired template and click Copy in the Operation column.
                                              2. Click the Custom Templates or Custom Event Templates tab, locate the desired alarm template, and choose More > Copy in the Operation column.
                                            5. 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 02294ef96..46f156d9f 100644 --- a/docs/ces/umn/ces_01_0120.html +++ b/docs/ces/umn/ces_01_0120.html @@ -7,19 +7,13 @@
                                            • Introduction to Server Monitoring
                                              • +
                                            • Configuring an Agency by One Click
                                              +
                                            • Agent Installation and Configuration
                                              • -
                                            • Installing and Configuring the Agent on a Linux ECS or BMS
                                              -
                                              • -
                                            • Installing and Configuring the Agent on a Windows ECS
                                              -
                                              • -
                                            • Installing the Agents in Batches on Linux ECSs
                                              -
                                            • Managing the Agent
                                              • -
                                            • Process Monitoring
                                              -
                                              • -
                                            • Viewing Server Monitoring Metrics
                                              +
                                            • Viewing Metrics
                                            • Creating an Alarm Rule to Monitor a Server
                                              • diff --git a/docs/ces/umn/ces_01_0123.html b/docs/ces/umn/ces_01_0123.html index d1b35882f..12e37e098 100644 --- a/docs/ces/umn/ces_01_0123.html +++ b/docs/ces/umn/ces_01_0123.html @@ -2,9 +2,7 @@

                                              Copying an Alarm Rule

                                              -

                                              That it will be available only in the next version.

                                              -
                                              -

                                              Procedure

                                              1. Log in to the management console.
                                              2. In the upper left corner, select a region and project.
                                              3. Click Service List in the upper left corner and select Cloud Eye.
                                              4. Choose Alarm Management > Alarm Rules.
                                              5. On the Alarm Rules page, locate the alarm rule you want to copy, and choose More > Copy in the Operation column.
                                              +

                                              Procedure

                                              1. Log in to the management console.
                                              2. In the upper left corner, select a region and project.
                                              3. Choose Service List > Cloud Eye.
                                              4. Choose Alarm Management > Alarm Rules.
                                              5. On the Alarm Rules page, locate the alarm rule you want to copy, and choose More > Copy in the Operation column.
                                              6. On the Create Alarm Rule page, modify the alarm rule parameters as needed, and click Create.
                                              diff --git a/docs/ces/umn/ces_01_0160.html b/docs/ces/umn/ces_01_0160.html new file mode 100644 index 000000000..13efb8b98 --- /dev/null +++ b/docs/ces/umn/ces_01_0160.html @@ -0,0 +1,38 @@ + + +

                                              Cloud Services Displayed in the Cloud Service Monitoring List

                                              +

                                              Some connected cloud services may not appear in the monitoring list. If no monitoring data is reported for all instances of a cloud service for a certain period of time, the cloud service will not be displayed in the list.

                                              +

                                              For cloud services listed in Table 1, if all instances of a cloud service have not reported any data to Cloud Eye for more than three hours but less than seven days, the cloud service remains on the cloud service monitoring list. However, if no data is sent for more than seven days, the service will be removed from the list.

                                              +

                                              For other cloud services, if all instances of a cloud service have not reported any data to Cloud Eye for more than three hours, this cloud service will not be displayed in the service list.

                                              + +
                                              + + + + + + + + + + + + + +
                                              Table 1 Cloud services with their monitoring data retained for seven days

                                              Cloud Service

                                              +

                                              Namespace

                                              +

                                              API Gateway

                                              +

                                              SYS.APIC

                                              +

                                              Object Storage Service

                                              +

                                              SYS.OBS

                                              +

                                              Scalable File Service

                                              +

                                              SYS.SFS

                                              +
                                              +
                                              +
                                              +
                                              +
                                              +
                                              Parent topic: Cloud Service Monitoring
                                              +
                                              +
                                              + diff --git a/docs/ces/umn/ces_01_0185.html b/docs/ces/umn/ces_01_0185.html index 157152adf..9e64a2946 100644 --- a/docs/ces/umn/ces_01_0185.html +++ b/docs/ces/umn/ces_01_0185.html @@ -1,12 +1,15 @@ -

                                              Importing and Exporting Custom Alarm Templates

                                              -

                                              Importing Custom Alarm Templates

                                              1. Log in to the management console.
                                              2. In the upper left corner, select a region and project.
                                              3. Click Service List in the upper left corner and select Cloud Eye.
                                              4. In the navigation pane on the left, choose Alarm Management > Alarm Templates.
                                              5. Click the Custom Templates tab.
                                              6. Click Import.
                                              7. Upload a JSON file, enter a template name, and click OK.
                                                Figure 1 Import Template
                                                +

                                                Importing and Exporting Custom Metric or Event Templates

                                                +

                                                If you want to quickly create a metric or event template using an existing custom template, you can export the target template, modify the content as needed, and then import the modified template. This section describes how to import and export custom metric or event templates.

                                                +

                                                Constraints

                                                Monitoring metrics and events vary by Cloud Eye version. Importing custom metric or event templates across regions with different versions may result in errors.

                                                +
                                                +

                                                Importing Custom Metric or Event Templates

                                                1. Log in to the management console.
                                                2. In the upper left corner, select a region and project.
                                                3. Choose Service List > Cloud Eye.
                                                4. In the navigation pane on the left, choose Alarm Management > Alarm Templates.
                                                5. Click the Custom Templates or Custom Event Templates tab.
                                                6. Click Import.
                                                7. 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.

                                                +

                                                The template name must be different from that of a default one.

                                                -

                                                Exporting Custom Alarm Templates

                                                1. Log in to the management console.
                                                2. In the upper left corner, select a region and project.
                                                3. Click Service List in the upper left corner and select Cloud Eye.
                                                4. In the navigation pane on the left, choose Alarm Management > Alarm Templates.
                                                5. Click the Custom Templates tab.
                                                6. Locate the custom template and choose More > Export in the Operation column.
                                                +

                                                Exporting Custom Metric or Event Templates

                                                1. Log in to the management console.
                                                2. In the upper left corner, select a region and project.
                                                3. Choose Service List > Cloud Eye.
                                                4. In the navigation pane on the left, choose Alarm Management > Alarm Templates.
                                                5. Click the Custom Templates or Custom Event Templates tab.
                                                6. Locate the custom template and choose More > Export in the Operation column.
                                                diff --git a/docs/ces/umn/ces_01_0207.html b/docs/ces/umn/ces_01_0207.html deleted file mode 100644 index 8d7621aa9..000000000 --- a/docs/ces/umn/ces_01_0207.html +++ /dev/null @@ -1,23 +0,0 @@ - - -

                                                Dashboards

                                                -
                                                - - diff --git a/docs/ces/umn/ces_01_0230.html b/docs/ces/umn/ces_01_0230.html new file mode 100644 index 000000000..19d8f5217 --- /dev/null +++ b/docs/ces/umn/ces_01_0230.html @@ -0,0 +1,41 @@ + + +

                                                Viewing a Graph

                                                +

                                                After adding a graph, you can view monitoring data in a default or custom time range.

                                                +

                                                Procedure

                                                1. Log in to the management console.
                                                2. In the upper left corner, select a region and project.
                                                3. Choose Service List > Cloud Eye.
                                                1. In the navigation pane, choose My Dashboards.
                                                2. Click the name of the dashboard you created and view all graphs on it.
                                                  • You can drag a graph to adjust its display sequence or modify how many graphs appear per row as needed.
                                                  • You can also click Full Screen to view the graphs in full-screen mode. For details, see Using the Full Screen.
                                                  • You can configure the refresh interval for graphs on the dashboard. The default option is Never refresh.
                                                  • You can click the unit above the Y-axis on the graph to switch the metric unit if supported.
                                                  +
                                                  +
                                                  +
                                                3. On the monitoring graph page, click or select an auto refresh interval to refresh the graph.
                                                  Figure 1 Refreshing a graph
                                                  +
                                                4. Hover your mouse over a graph. In the upper right corner, click to view monitoring details. You can select a default or custom time range for viewing metrics of a cloud service. In the search box, select filters and then the monitored objects to be displayed. Select the refresh interval and aggregation method to display metrics.
                                                  Figure 2 Viewing monitoring details in a line chart
                                                  +

                                                  By default, raw metric data is displayed if Last 1h, Last 3h, or Last 12h is selected. For Last 1d, Last 7d, and longer time ranges, aggregated data is displayed by default.

                                                  +

                                                  On the monitoring details page of the line chart, you can perform the operations described in Customizing a Period to View Metrics or Selecting Monitored Objects and Viewing Metrics.

                                                  +

                                                  +
                                                  Figure 3 Viewing graphs
                                                  +
                                                +
                                                +

                                                Using the Full Screen

                                                The full screen displays metric data more clearly.

                                                +
                                                • To enter the full screen, select a dashboard, click its name, and click Full Screen in the upper left corner.
                                                • To exit the full screen, press Esc.

                                                  +
                                                  Figure 4 Full screen
                                                  +
                                                +
                                                +

                                                Customizing a Period to View Metrics

                                                By default, you can select Last 1h, Last 3h, Last 12h, Last 1d, or Last 7d. In a line chart, if you want to view metrics in the last two hours or a custom 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 custom time range, click the second icon on the right, as shown in Figure 5. Drag the mouse to select a customized time range. The system displays the monitoring data in the selected time range.
                                                  Figure 5 Customizing a time range
                                                  +
                                                • To stop viewing the metric details within a custom time range, click the third icon on the right, as shown in Figure 6. The system will reset the time range.
                                                  Figure 6 Going back to the default time range
                                                  +
                                                +
                                                +

                                                Selecting Monitored Objects and Viewing Metrics

                                                In a line chart, you can compare the same metric of multiple resources on one graph. When there are a large number of resources, you can select only some resources and compare their metrics.

                                                +
                                                • Select monitored objects. By default, resources are sorted by Name, as shown in Figure 7. You can also select resources by ID, Metric Name, or Resource Type. The system displays the data of selected resources and hides that of other resources.
                                                  Figure 7 Selecting monitored objects
                                                  +
                                                • To clear the monitored resources you have selected, click .
                                                  Figure 8 Clearing monitored objects
                                                  +
                                                • Click to display the monitored objects. Click to customize columns to be displayed in the list below the graph.
                                                  Figure 9 Viewing monitoring items
                                                  +
                                                • Alternatively, click the fourth icon on the right of the graph and select the instance range to be viewed. Then, the system automatically displays the data of the selected monitored objects and hides the monitoring data of other monitored objects.
                                                  Figure 10 Select Metrics
                                                  +
                                                • Click the fifth icon on the right of the graph to reset the selected instance range. The system will display data of all monitored objects.
                                                  Figure 11 Reset Metrics
                                                  +
                                                • Click the sixth icon on the right of the graph to reset the selected custom time range and instance range.
                                                  Figure 12 Reset
                                                  +
                                                +
                                                +
                                                +
                                                +
                                                +
                                                Parent topic: My Dashboards
                                                +
                                                +
                                                + diff --git a/docs/ces/umn/ces_01_0232.html b/docs/ces/umn/ces_01_0232.html new file mode 100644 index 000000000..7934eb742 --- /dev/null +++ b/docs/ces/umn/ces_01_0232.html @@ -0,0 +1,16 @@ + + +

                                                Deleting a Graph

                                                +

                                                If there are service changes or you need to replan parameters for a graph, you can delete the graph.

                                                +

                                                Procedure

                                                1. Log in to the management console.
                                                2. In the upper left corner, select a region and project.
                                                3. Choose Service List > Cloud Eye.
                                                1. In the navigation pane, choose My Dashboards.
                                                2. Locate the dashboard from which you want to delete a graph and click the dashboard name.
                                                3. Click and choose Delete.
                                                  Figure 1 Deleting a graph
                                                  +
                                                4. In the displayed Delete Graph dialog box, click OK.

                                                  +
                                                  Figure 2 Deleting a graph
                                                  +
                                                +
                                                +
                                                +
                                                +
                                                +
                                                Parent topic: My Dashboards
                                                +
                                                +
                                                + diff --git a/docs/ces/umn/ces_01_0233.html b/docs/ces/umn/ces_01_0233.html new file mode 100644 index 000000000..d26d7a7af --- /dev/null +++ b/docs/ces/umn/ces_01_0233.html @@ -0,0 +1,15 @@ + + +

                                                Deleting a Dashboard

                                                +

                                                If an existing dashboard cannot meet your requirements, you can delete it and replan graphs on a new dashboard. After you delete a dashboard, all graphs added to it will also be deleted.

                                                +

                                                Procedure

                                                1. Log in to the management console.
                                                2. In the upper left corner, select a region and project.
                                                3. Choose Service List > Cloud Eye.
                                                1. In the navigation pane, choose My Dashboards.
                                                  • To delete a single dashboard, click Delete in the Operation column of the dashboard.
                                                  • To delete multiple dashboards, select the check boxes of the dashboards and click Delete above the list.
                                                  +
                                                2. In the displayed Delete Dashboard dialog box, click OK.
                                                  Figure 1 Delete Dashboard
                                                  +
                                                +
                                                +
                                                +
                                                +
                                                +
                                                Parent topic: My Dashboards
                                                +
                                                +
                                                + diff --git a/docs/ces/umn/ces_01_0248.html b/docs/ces/umn/ces_01_0248.html new file mode 100644 index 000000000..cb4cba947 --- /dev/null +++ b/docs/ces/umn/ces_01_0248.html @@ -0,0 +1,16 @@ + + +

                                                Copying a Dashboard

                                                +

                                                You can copy a dashboard. If you need to create a dashboard with the same configurations and graphs as an existing one, you can simply copy the dashboard. The following describes how to copy a dashboard.

                                                +

                                                Procedure

                                                1. Log in to the management console.
                                                2. In the upper left corner, select a region and project.
                                                3. Choose Service List > Cloud Eye.
                                                1. Choose My Dashboards.
                                                2. Locate the dashboard to be copied and click Copy in the Operation column.
                                                3. On the Copy Dashboard page, set parameters.
                                                  • Name: Enter a maximum of 128 characters. Only letters, digits, hyphens (-), and underscores (_) are allowed.
                                                  • Enterprise Project: Select an enterprise project to be associated with the dashboard. Only users who have all permissions for the selected enterprise project can manage the dashboard.

                                                    Enterprise Project is available only in certain regions.

                                                    +
                                                    +
                                                  +
                                                4. Click OK.
                                                +
                                                +
                                                +
                                                +
                                                +
                                                Parent topic: My Dashboards
                                                +
                                                +
                                                + diff --git a/docs/ces/umn/ces_01_0255.html b/docs/ces/umn/ces_01_0255.html new file mode 100644 index 000000000..23ab14753 --- /dev/null +++ b/docs/ces/umn/ces_01_0255.html @@ -0,0 +1,16 @@ + + +

                                                Viewing My Dashboards

                                                +

                                                After creating dashboards, you can view all of them in your account on the My Dashboards page.

                                                +

                                                Procedure

                                                1. Log in to the management console.
                                                2. In the upper left corner, select a region and project.
                                                3. Choose Service List > Cloud Eye.
                                                1. Click My Dashboards.
                                                  • Searching for dashboards: In the search box above the list, select a property and enter a keyword to search for the target dashboard.

                                                    You can search for dashboards by Name, Created by, Created, or Enterprise Project.

                                                    +
                                                  • Adding dashboards to favorites: Locate the dashboard you want to add and click in the Favorites column.

                                                    Then, you can select the Display favorites only checkbox in the upper right corner to display all favorite dashboards.

                                                    +
                                                  • Switching the dashboard view: Click in the upper right corner of the list to display dashboards in a list. You can also click to display dashboards in a view.
                                                  +
                                                +
                                                +
                                                +
                                                +
                                                +
                                                Parent topic: My Dashboards
                                                +
                                                +
                                                + diff --git a/docs/ces/umn/ces_06_0001.html b/docs/ces/umn/ces_06_0001.html index cac771ddb..e86099a6d 100644 --- a/docs/ces/umn/ces_06_0001.html +++ b/docs/ces/umn/ces_06_0001.html @@ -4,7 +4,7 @@
                                                  -
                                                • Viewing the Overview Page
                                                  +
                                                • Viewing Overview
                                                • Querying Metrics of a Cloud Service
                                                  • diff --git a/docs/ces/umn/ces_06_0003.html b/docs/ces/umn/ces_06_0003.html index 9f9e4a028..38c2cf2cc 100644 --- a/docs/ces/umn/ces_06_0003.html +++ b/docs/ces/umn/ces_06_0003.html @@ -2,7 +2,7 @@

                                                  Using Server Monitoring

                                                  Server monitoring includes basic monitoring, process monitoring, and OS monitoring for servers.

                                                  -
                                                  • Basic monitoring provides Agent-free monitoring for basic ECS or BMS metrics.
                                                  • OS monitoring provides proactive and fine-grained OS monitoring for servers, and it requires the Agent to be installed on all servers that will be monitored.
                                                  • Process monitoring provides monitoring of active processes on hosts.
                                                  +
                                                  • Basic monitoring provides Agent-free monitoring for basic ECS or BMS metrics.
                                                  • OS monitoring provides proactive and fine-grained OS monitoring for ECSs or BMSs installed with the Agent.
                                                  • Process monitoring provides monitoring of active processes on hosts.

                                                  Agent access statement: After the Agent is installed, it collects and reports server monitoring data to the Cloud Eye service. When you update the Agent software package, Cloud Eye accesses the software package repository address to update the software. In addition to the preceding behaviors, the Agent does not access any other addresses.

                                                  Functions

                                                  • Various Metrics

                                                    Server monitoring provides more than 40 metrics, such as metrics for CPU, memory, disk, and network usage, meeting the basic monitoring and O&M requirements for servers.

                                                    @@ -10,8 +10,8 @@
                                                  • 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

                                                  1. Log in to the management console.
                                                  2. Click Service List in the upper left corner and select Cloud Eye.
                                                  3. In the navigation pane on the left, choose Server Monitoring.
                                                  4. Select the ECS or BMS and install the Agent on it.
                                                    1. Change the DNS server address 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).
                                                    2. Install the Agent. For details, see Installing the Agent on a Linux Server or Installing and Configuring the Agent on a Windows Server.
                                                    -
                                                  5. After 5 minutes, check whether the Agent status is Running.

                                                    If yes, the Agent has been installed successfully.

                                                    +

                                                    Using Server Monitoring

                                                    1. Log in to the management console.
                                                    2. Choose Service List > Cloud Eye.
                                                    3. In the navigation pane, choose Server Monitoring > Elastic Cloud Server (or Bare Metal Server).
                                                    4. Select the ECS or BMS and install the Agent on it.
                                                      1. Change the DNS server address 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).
                                                      2. Install the Agent. For details, see Installing the Agent on a Linux Server or Installing and Configuring the Agent on a Windows Server.
                                                      +
                                                    5. After five minutes, check whether the Agent status is Running.

                                                      If yes, the Agent has been installed successfully.

                                                      On the right of the ECS, click View Metric in the Operation column to view the monitoring data.

                                                    diff --git a/docs/ces/umn/ces_06_0005.html b/docs/ces/umn/ces_06_0005.html index a0e108541..df24ec120 100644 --- a/docs/ces/umn/ces_06_0005.html +++ b/docs/ces/umn/ces_06_0005.html @@ -2,13 +2,13 @@

                                                    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

                                                    1. Log in to the management console.
                                                    2. Click Service List in the upper left corner and select Cloud Eye.
                                                    3. In the navigation pane on the left, choose Custom Monitoring.
                                                    4. On the Custom Monitoring page, view the data reported by yourself through API requests, including custom services and metrics.
                                                    5. Locate the cloud service resource and click View Metric in the Operation column.

                                                      On the page displayed, you can view graphs based on data collected in 1h, 3h, 12h, 1d, and 7d. In the upper right corner of each graph, the maximum and minimum values of the metric in the corresponding time periods are dynamically displayed.

                                                      +

                                                      For details about how to add monitoring data, see Adding Monitoring Data.

                                                      +

                                                      Viewing Custom Monitoring

                                                      1. Log in to the management console.
                                                      2. Choose Service List > Cloud Eye.
                                                      3. In the navigation pane on the left, choose Custom Monitoring.
                                                      4. On the Custom Monitoring page, view the data reported by yourself through API requests, including custom services and metrics.
                                                      5. Locate the cloud service resource and click View Metric in the Operation column.

                                                        On the page displayed, you can view graphs based on data collected in 1h, 3h, 12h, 1d, and 7d. In the upper right corner of each graph, the maximum and minimum values of the metric in the corresponding time periods are dynamically displayed.

                                                      6. 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, set Period and Statistic to configure the aggregation method.

                                                        +

                                                        In the upper left corner of the graph, set Period and Statistic to configure the rollup method.

                                                      -

                                                      Creating an Alarm Rule

                                                      1. Log in to the management console.
                                                      2. Click Service List in the upper left corner and select Cloud Eye.
                                                      3. In the navigation pane on the left, choose Custom Monitoring.
                                                      4. Locate the cloud service resource and click Create Alarm Rule in the Operation column.
                                                      5. 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.

                                                        +

                                                        Creating an Alarm Rule

                                                        1. Log in to the management console.
                                                        2. Choose Service List > Cloud Eye.
                                                        3. In the navigation pane on the left, choose Custom Monitoring.
                                                        4. Locate the cloud service resource and click Create Alarm Rule in the Operation column.
                                                        5. 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.

                                                      diff --git a/docs/ces/umn/ces_06_0006.html b/docs/ces/umn/ces_06_0006.html index ae531fb9f..1425d5a03 100644 --- a/docs/ces/umn/ces_06_0006.html +++ b/docs/ces/umn/ces_06_0006.html @@ -4,11 +4,11 @@

                                                      You can query system events and custom events reported to Cloud Eye through the API. You can create alarm rules for both system events and custom events. When specific events occur, Cloud Eye generates alarms for you.

                                                      Events are key operations on cloud service resources that are stored and monitored by Cloud Eye. You can view events to see operations performed by specific users on specific resources, such as deleting or rebooting an ECS.

                                                      Event monitoring is enabled by default. You can view monitoring details about system events and custom events. For details about the supported system events, see Events Supported by Event Monitoring.

                                                      -

                                                      Event monitoring provides an API for reporting custom events, which helps you collect and report abnormal events or important change events generated by services to Cloud Eye.

                                                      -

                                                      Viewing Event Monitoring Graphs

                                                      1. Log in to the management console.
                                                      2. Click Service List in the upper left corner and select Cloud Eye.
                                                      3. 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. For details about how to report custom events, see Reporting Events.

                                                        +

                                                        Viewing Event Monitoring Graphs

                                                        1. Log in to the management console.
                                                        2. Choose Service List > Cloud Eye.
                                                        3. 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.

                                                        4. Select an event and click View Graph in the Operation column.
                                                        -

                                                        Creating an Alarm Rule

                                                        1. Log in to the management console.
                                                        2. Click Service List in the upper left corner and select Cloud Eye.
                                                        3. In the navigation pane on the left, choose Event Monitoring.
                                                        4. In the event list, locate the event and click Create Alarm Rule in the Operation column.
                                                        5. Configure the alarm rule name, alarm policy, and alarm notification as prompted.

                                                          After you create the alarm rule, if an event occurs, Cloud Eye will immediately notify you of cloud resource exceptions through SMN to avoid losses.

                                                          +

                                                          Creating an Alarm Rule

                                                          1. Log in to the management console.
                                                          2. Choose Service List > Cloud Eye.
                                                          3. In the navigation pane on the left, choose Event Monitoring.
                                                          4. In the event list, locate the event and click Create Alarm Rule in the Operation column.
                                                          5. Configure the alarm rule name, alarm policy, and alarm notification as prompted.

                                                            After you create the alarm rule, if an event occurs, Cloud Eye will immediately notify you of cloud resource exceptions through SMN to avoid losses.

                                                        diff --git a/docs/ces/umn/ces_06_0007.html b/docs/ces/umn/ces_06_0007.html index 3b363e93a..469bfefef 100644 --- a/docs/ces/umn/ces_06_0007.html +++ b/docs/ces/umn/ces_06_0007.html @@ -7,7 +7,7 @@

                                                      Functions

                                                      • Resource groups enable you to manage your cloud resources across products.
                                                      • 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

                                                      1. Log in to the management console.
                                                      2. Click Service List in the upper left corner and select Cloud Eye.
                                                      3. In the navigation pane on the left, choose Resource Groups.
                                                      4. In the upper right corner, click Create Resource Group. On the page displayed, enter a group name as prompted.
                                                      5. Select cloud service resources.
                                                      6. Click Create.

                                                        For details about how to create and manage resource groups, see Introduction to Resource Groups.

                                                        +

                                                        Using Resource Groups

                                                        1. Log in to the management console.
                                                        2. Choose Service List > Cloud Eye.
                                                        3. In the navigation pane on the left, choose Resource Groups.
                                                        4. In the upper right corner, click Create Resource Group. On the page displayed, enter a group name as prompted.
                                                        5. Select cloud service resources.
                                                        6. Click Create.

                                                          For details about how to create and manage resource groups, see Introduction to Resource Groups.

                                                      diff --git a/docs/ces/umn/ces_07_0001.html b/docs/ces/umn/ces_07_0001.html index 9ab55ed97..9031f9da5 100644 --- a/docs/ces/umn/ces_07_0001.html +++ b/docs/ces/umn/ces_07_0001.html @@ -12,7 +12,7 @@
                                                    6. Basic Concepts
                                                      7. -
                                                    7. Notes and Constraints
                                                      +
                                                    8. Constraints
                                                    9. Region and AZ
                                                      10. diff --git a/docs/ces/umn/ces_07_0002.html b/docs/ces/umn/ces_07_0002.html index ded48d329..24e04c29e 100644 --- a/docs/ces/umn/ces_07_0002.html +++ b/docs/ces/umn/ces_07_0002.html @@ -8,7 +8,7 @@

                                                    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 a metric reaches the threshold specified in an alarm rule, Cloud Eye notifies you by sending emails, SMS messages, or HTTP/HTTPS messages. You can track the service status and establish programs accordingly to handle the alarms.

                                                    +

                                                    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 sending emails, SMS messages, or HTTP/HTTPS messages. You can track the service status and establish programs accordingly to handle the alarms.

                                                    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_0006.html b/docs/ces/umn/ces_07_0006.html index 5629b8171..bb8aca054 100644 --- a/docs/ces/umn/ces_07_0006.html +++ b/docs/ces/umn/ces_07_0006.html @@ -2,23 +2,22 @@

                                                    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.

                                                    +

                                                    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.

                                                    -

                                                    Aggregation

                                                    Aggregation 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 aggregation period. Cloud Eye supports the following aggregation periods: 5 minutes, 20 minutes, 1 hour, 4 hours, and 24 hours.

                                                    +

                                                    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 a rollup period. Cloud Eye supports the following rollup periods: 5 minutes, 20 minutes, 1 hour, 4 hours, and 24 hours.

                                                    -

                                                    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.

                                                    +

                                                    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 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.

                                                    +

                                                    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, SMS messages, or HTTP/HTTPS messages.

                                                    +

                                                    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.

                                                    -

                                                    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.

                                                    +

                                                    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 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.

                                                    +

                                                    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.

                                                    +

                                                    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 d24a8e8ab..06c236c1f 100644 --- a/docs/ces/umn/ces_07_0007.html +++ b/docs/ces/umn/ces_07_0007.html @@ -1,11 +1,11 @@ -

                                                    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.

                                                    +

                                                    Constraints

                                                    +

                                                    Table 1 lists the default Cloud Eye resource quotas per user. For details about how to adjust the quotas, see Quota Adjustment. You can contact the Cloud Eye owner to obtain adjusted quotas.

                                                    -
                                                    Table 1 Resources and their default quotas

                                                    Resource

                                                    +
                                                    - @@ -14,29 +14,36 @@ - - - - - + + + - diff --git a/docs/ces/umn/ces_07_0009.html b/docs/ces/umn/ces_07_0009.html index 28f5ff902..feae7b6b4 100644 --- a/docs/ces/umn/ces_07_0009.html +++ b/docs/ces/umn/ces_07_0009.html @@ -1,14 +1,14 @@

                                                    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.

                                                    +

                                                    If you need to grant your enterprise personnel permission to access your Cloud Eye resources, use Identity and Access Management (IAM). IAM provides identity authentication, fine-grained permissions management, and access control. IAM helps you secure access to your cloud 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.

                                                      +
                                                      • 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 need to also 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 Permissions Policies and Supported Actions.

                                                      Table 1 lists the system-defined policies supported by Cloud Eye.

                                                      @@ -29,25 +29,36 @@
                                                    - - - - - + + + + + @@ -55,669 +66,808 @@

                                                    Table 2 lists common operations supported by the Cloud Eye system policies.

                                                    -
                                                    Table 1 Resource quotas

                                                    Item

                                                    Default Quota

                                                    +

                                                    Default Limit

                                                    1,000

                                                    Custom alarm templates that can be created

                                                    +

                                                    Number of alarm templates that can be created

                                                    200

                                                    Alarm rules that can be added to an alarm template

                                                    +

                                                    Number of alarm policies that can be configured for a single service in an alarm template

                                                    20

                                                    +

                                                    50

                                                    Dashboards that can be created

                                                    20

                                                    +

                                                    10

                                                    Graphs that can be added to a dashboard

                                                    24

                                                    +

                                                    50

                                                    +

                                                    Monitoring items that can be added to a line graph

                                                    +

                                                    50

                                                    +
                                                    NOTE:

                                                    If 10 monitored objects and 5 metrics are selected, 50 monitoring items will be created.

                                                    +

                                                    Time that the alarm history can be kept

                                                    4,416 hours

                                                    +

                                                    180 days

                                                    Objects that can be selected for monitoring when creating an alarm rule

                                                    @@ -59,7 +66,7 @@

                                                    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.

                                                    +
                                                    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.
                                                    • The restrictions apply only to the earlier version of the monitoring data export feature, not the new version.

                                                    Depends on the Tenant Guest policy.

                                                    Tenant Guest: a global policy, which must be assigned in the Global project

                                                    System-defined role

                                                    +

                                                    System-defined roles

                                                    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.

                                                    +

                                                    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

                                                    +

                                                    System-defined policies

                                                    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.

                                                    +

                                                    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

                                                    +

                                                    System-defined policies

                                                    +

                                                    CES AgentAccess

                                                    +

                                                    Permissions required for the Cloud Eye Agent to run properly

                                                    +
                                                    NOTE:

                                                    To ensure that the CES Agent can provide services properly, you need to configure an agency. For details, see How Do I Configure an Agency?.

                                                    +
                                                    +

                                                    None

                                                    +

                                                    System-defined policies
                                                    Table 2 Common operations supported by the Cloud Eye system policies

                                                    Feature

                                                    +
                                                    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + - - - - - - - - - - - - - - - - + + + + + + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + +
                                                    Table 2 Common operations supported by the Cloud Eye system policies

                                                    Feature

                                                    Operation

                                                    +

                                                    Operation

                                                    CES Administrator

                                                    +

                                                    CES Administrator

                                                    (The Tenant Guest policy must be added at the same time.)

                                                    Tenant Guest

                                                    +

                                                    Tenant Guest

                                                    CES FullAccess

                                                    +

                                                    CES FullAccess

                                                    CES ReadOnlyAccess

                                                    +

                                                    CES ReadOnlyAccess

                                                    Monitoring Overview

                                                    +

                                                    Overview

                                                    Viewing monitoring overview

                                                    +

                                                    Viewing overview

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    Dashboards

                                                    +

                                                    My Dashboards

                                                    Creating a dashboard

                                                    +

                                                    Creating my dashboards

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    Viewing full screen monitoring

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    Querying a dashboard

                                                    +

                                                    Viewing my dashboards

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    Deleting a dashboard

                                                    +

                                                    Deleting my dashboards

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    +

                                                    Copying my dashboards

                                                    +

                                                    Supported

                                                    +

                                                    Not supported

                                                    +

                                                    Supported

                                                    +

                                                    Not supported

                                                    Adding a graph

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    Viewing a graph

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    Modifying a graph

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    Deleting a graph

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    +

                                                    Copying a monitoring view

                                                    +

                                                    Supported

                                                    +

                                                    Not supported

                                                    +

                                                    Supported

                                                    +

                                                    Not supported

                                                    Adjusting the position of a graph

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    Resource Groups

                                                    +

                                                    Resource Groups

                                                    Creating a resource group

                                                    +

                                                    Creating a resource group

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    Viewing the resource group list

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    Viewing resource groups (Resource Overview)

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    Viewing resource groups (Alarm Rules)

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    -

                                                    Viewing resource groups (Alarm Records)

                                                    -

                                                    √

                                                    -

                                                    √

                                                    -

                                                    √

                                                    -

                                                    √

                                                    +

                                                    Supported

                                                    Modifying a resource group

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    Deleting a resource group

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    Alarm Rules

                                                    +

                                                    Alarm Rules

                                                    Creating an alarm rule

                                                    +

                                                    Creating an alarm rule

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    +

                                                    Copying an alarm rule

                                                    +

                                                    Supported

                                                    +

                                                    Not supported

                                                    +

                                                    Supported

                                                    +

                                                    Not supported

                                                    Modifying an alarm rule

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    Enabling an alarm rule

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    Disabling an alarm rule

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    Deleting an alarm rule

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    Querying the alarm rule list

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    Viewing details of an alarm rule

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    Alarm Records

                                                    +

                                                    Alarm Records

                                                    +

                                                    Viewing a graph

                                                    +

                                                    Viewing a graph

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    Viewing alarm records

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    Alarm Templates

                                                    +

                                                    Exporting alarm records

                                                    Viewing a default template

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Not supported

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    -

                                                    √

                                                    +

                                                    Not supported

                                                    Viewing a custom template

                                                    +

                                                    Alarm Templates

                                                    √

                                                    +

                                                    Viewing the default metric/event template

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    +

                                                    Supported

                                                    Creating a custom template

                                                    +

                                                    Viewing a custom metric/event template

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Supported

                                                    Modifying a custom template

                                                    +

                                                    Creating a custom metric/event template

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    Deleting a custom template

                                                    +

                                                    Modifying a custom metric/event template

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    Server Monitoring

                                                    +

                                                    Copying a metric/event template

                                                    Viewing the server list

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Not supported

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Not supported

                                                    √

                                                    +

                                                    Importing a custom metric/event template

                                                    +

                                                    Supported

                                                    +

                                                    Not supported

                                                    +

                                                    Supported

                                                    +

                                                    Not supported

                                                    +

                                                    Exporting a custom metric/event template

                                                    +

                                                    Supported

                                                    +

                                                    Not supported

                                                    +

                                                    Supported

                                                    +

                                                    Supported

                                                    +

                                                    Deleting a custom metric/event template

                                                    +

                                                    Supported

                                                    +

                                                    Not supported

                                                    +

                                                    Supported

                                                    +

                                                    Not supported

                                                    +

                                                    One-Click Monitoring

                                                    +

                                                    Enable one-click monitoring

                                                    +

                                                    Supported

                                                    +

                                                    Not supported

                                                    +

                                                    Supported

                                                    +

                                                    Not supported

                                                    +

                                                    Viewing one-click monitoring

                                                    +

                                                    Supported

                                                    +

                                                    Supported

                                                    +

                                                    Supported

                                                    +

                                                    Supported

                                                    +

                                                    Modifying one-click monitoring

                                                    +

                                                    Supported

                                                    +

                                                    Not supported

                                                    +

                                                    Supported

                                                    +

                                                    Not supported

                                                    +

                                                    Disabling one-click monitoring

                                                    +

                                                    Supported

                                                    +

                                                    Not supported

                                                    +

                                                    Supported

                                                    +

                                                    Not supported

                                                    +

                                                    Server Monitoring

                                                    +

                                                    Viewing the server list

                                                    +

                                                    Supported

                                                    +

                                                    Supported

                                                    +

                                                    Supported

                                                    +

                                                    Supported

                                                    Viewing server monitoring metrics

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    Installing the Agent

                                                    √ (You must have the ECS FullAccess permission.)

                                                    ×

                                                    +

                                                    Not supported

                                                    √ (You must have the ECS FullAccess permission.)

                                                    +

                                                    √ (You must have the ECS FullAccess permission.)

                                                    ×

                                                    +

                                                    Not supported

                                                    Restoring the Agent configurations

                                                    +

                                                    Enabling one-click configuration

                                                    √ (You must have the Security Administrator and ECS FullAccess permissions.)

                                                    ×

                                                    +

                                                    Not supported

                                                    √ (You must have the Security Administrator and ECS FullAccess permissions.)

                                                    +

                                                    √ (You must have the Security Administrator and ECS FullAccess permissions.)

                                                    ×

                                                    +

                                                    Not supported

                                                    Uninstalling the Agent

                                                    √ (You must have the ECS FullAccess permission.)

                                                    ×

                                                    +

                                                    Not supported

                                                    √ (You must have the ECS FullAccess permission.)

                                                    ×

                                                    +

                                                    Not supported

                                                    Configuring process monitoring

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    Configuring monitoring for a process

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    Cloud Service Monitoring

                                                    +

                                                    Cloud Service Monitoring

                                                    Viewing the cloud service list

                                                    +

                                                    Viewing the cloud service list

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    √ (Cloud services need to support fine-grained authorization.)

                                                    +

                                                    Supported (Cloud services need to support fine-grained authorization.)

                                                    √ (Cloud services need to support fine-grained authorization.)

                                                    +

                                                    Supported (Cloud services need to support fine-grained authorization.)

                                                    Querying cloud service metrics

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    Custom Monitoring

                                                    +

                                                    Custom Monitoring

                                                    Adding custom monitoring data

                                                    +

                                                    Adding custom monitoring data

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    Viewing the custom monitoring list

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    Viewing custom monitoring data

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    Event Monitoring

                                                    +

                                                    Event Monitoring

                                                    Adding a custom event

                                                    +

                                                    Adding a custom event

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    Viewing the event list

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    Viewing details of an event

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    Data Dumping to DMS Kafka

                                                    +

                                                    Data Dumping to DMS for Kafka

                                                    Creating a dump task

                                                    +

                                                    Creating a dump task

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    Querying data dumping tasks

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    Querying a specified data dump task

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    Modifying a data dump task

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    Starting a data dump task

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    Stopping a data dump task

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    Deleting a data dump task

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    Others

                                                    +

                                                    Others

                                                    Exporting monitoring data

                                                    +

                                                    Exporting monitoring data

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Not supported

                                                    Sending an alarm notification

                                                    +

                                                    Task Center

                                                    +

                                                    +

                                                    √

                                                    +

                                                    Viewing an export task

                                                    ×

                                                    +

                                                    Supported

                                                    √

                                                    +

                                                    Supported

                                                    ×

                                                    +

                                                    Supported

                                                    +

                                                    Supported

                                                    +

                                                    Downloading exported results

                                                    +

                                                    Supported

                                                    +

                                                    Not supported

                                                    +

                                                    Supported

                                                    +

                                                    Not supported

                                                    +

                                                    Deleting an export task

                                                    +

                                                    Supported

                                                    +

                                                    Not supported

                                                    +

                                                    Supported

                                                    +

                                                    Not supported
                                                    -

                                                    If predefined permissions cannot meet your requirements, you can create custom policies. Custom policies allow you to perform fine-grained access control flexibly. For details about how to create a custom policy, see Cloud Eye Custom Policies.

                                                    +

                                                    If the system-defined policies and roles cannot meet your requirements, you can create custom policies and apply these policies to user groups for refined access control. For more information, see Cloud Eye Custom Policies.

                                                    The following table lists fine-grained actions and dependencies for Cloud Eye.

                                                    -
                                                    Table 3 Cloud Eye fine-grained actions

                                                    Action

                                                    +
                                                    - - - @@ -746,7 +896,9 @@ - @@ -764,7 +916,7 @@ - @@ -773,9 +925,20 @@ - - + + + + + - + + + + + - + + + + + + + + + + + + + + + - @@ -836,7 +1035,7 @@ - @@ -845,7 +1044,7 @@ - @@ -868,6 +1067,15 @@ + + + + + - @@ -899,7 +1107,7 @@ - @@ -917,11 +1125,20 @@ - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                                                    Table 3 Cloud Eye fine-grained actions

                                                    Action

                                                    Description

                                                    Dependencies

                                                    +

                                                    Dependencies

                                                    Scenario

                                                    +

                                                    Scenario

                                                    ces:alarmHistory:list

                                                    Grants permission to query historical alarms.

                                                    +

                                                    Grants permission to list historical alarms.

                                                    -

                                                    Grants permission to create an alarm rule.

                                                    ces:alarms:list

                                                    +

                                                    ces:namespaces:list, ces:namespacesDimensions:list, ces:sysEventsNames:list, ces:resourceGroups:get, ces:resourceGroups:list, ces:customAlarmTemplates:list, ces:sysAlarmTemplates:list, ces:currentRegionSupportedMetrics:list, smn:topic:list, eps:enterpriseProjects:list

                                                    +
                                                    NOTE:

                                                    If Monitoring Scope is set to Specific resources, instance query permissions for the cloud services are also required.

                                                    +

                                                    Creating an alarm rule

                                                    Grants permission to query monitored resources in an alarm rule.

                                                    -

                                                    +

                                                    ces:alarms:list

                                                    Querying monitored resources in an alarm rule

                                                    Grants permission to update an alarm rule.

                                                    ces:alarms:list

                                                    +

                                                    ces:alarms:list, ces:customAlarmTemplates:list, ces:sysAlarmTemplates:list, ces:currentRegionSupportedMetrics:list, smn:topic:list

                                                    +
                                                    NOTE:

                                                    If Monitoring Scope of the alarm rule is set to Specific resources, instance query permissions for the cloud services are also required.

                                                    +

                                                    Modifying an alarm rule

                                                    +

                                                    Updating an alarm rule

                                                    +

                                                    ces:alarmsonoff:put

                                                    +

                                                    Grants permission to enable or disable an alarm rule.

                                                    +

                                                    ces:alarms:list

                                                    +

                                                    Enabling or disabling alarm rules

                                                    ces:customAlarmTemplates:list

                                                    @@ -791,11 +954,20 @@

                                                    Grants permission to create a custom template.

                                                    ces:customAlarmTemplates:list

                                                    +

                                                    ces:customAlarmTemplates:list, ces:namespaces:list, ces:namespacesDimensions:list, ces:sysEventsNames:list, ces:currentRegionSupportedMetrics:list

                                                    Creating a custom template

                                                    ces:customAlarmTemplates:get

                                                    +

                                                    Grants permission to query details about a custom alarm template.

                                                    +

                                                    ces:customAlarmTemplates:list

                                                    +

                                                    Querying details about a custom alarm template

                                                    +

                                                    ces:customAlarmTemplates:delete

                                                    Grants permission to delete a custom template.

                                                    @@ -809,16 +981,43 @@

                                                    Grants permission to update a custom template.

                                                    ces:customAlarmTemplates:list

                                                    +

                                                    ces:customAlarmTemplates:list, ces:namespaces:list, ces:namespacesDimensions:list, ces:sysEventsNames:list, ces:currentRegionSupportedMetrics:list

                                                    Updating a custom template

                                                    ces:sysAlarmTemplates:get

                                                    +

                                                    Grants permission to query details about a default system alarm template.

                                                    +

                                                    ces:sysAlarmTemplates:list

                                                    +

                                                    Querying details about a default system alarm template

                                                    +

                                                    ces:sysAlarmTemplates:list

                                                    +

                                                    Grants permission to list default system alarm templates.

                                                    +

                                                    -

                                                    +

                                                    Listing default system alarm templates

                                                    +

                                                    ces:alarmTemplates:list

                                                    +

                                                    Grants permission to batch query alarm templates.

                                                    +

                                                    -

                                                    +

                                                    Batch querying alarm templates

                                                    +

                                                    ces:events:get

                                                    Grants permission to query details of an event.

                                                    -

                                                    +

                                                    ces:events:list

                                                    Querying details of an event

                                                    Grants permission to report events.

                                                    ces:events:list

                                                    +

                                                    -

                                                    Reporting events

                                                    Grants permission to report metrics.

                                                    ces:metricData:list

                                                    +

                                                    -

                                                    Reporting metrics

                                                    Querying metrics

                                                    ces:namespaces:list

                                                    +

                                                    Grants permission to batch query namespaces.

                                                    +

                                                    -

                                                    +

                                                    Batch querying namespaces

                                                    +

                                                    ces:namespacesDimensions:list

                                                    Grants permission to query Agent-related metrics of a server.

                                                    @@ -890,7 +1098,7 @@

                                                    Grants permission to create a resource group.

                                                    -

                                                    +

                                                    ces:namespaces:list, ces:namespacesDimensions:list, eps:enterpriseProjects:list, and instance query permissions for the selected cloud services

                                                    Creating a resource group

                                                    Grants permission to delete a resource group.

                                                    -

                                                    +

                                                    ces:resourceGroups:get

                                                    Deleting a resource group

                                                    Grants permission to update a resource group.

                                                    ces:resourceGroups:get

                                                    +

                                                    ces:resourceGroups:get, ces:namespaces:list, ces:namespacesDimensions:list, and instance query permissions for the selected cloud services

                                                    Updating a resource group

                                                    ces:resourceGroups:list

                                                    +

                                                    Grants permission to list all resource groups.

                                                    +

                                                    -

                                                    +

                                                    Querying all resource groups

                                                    +

                                                    ces:sapEventData:list

                                                    Grants permission to query the server configuration.

                                                    @@ -931,11 +1148,317 @@

                                                    Querying the server configuration

                                                    ces:taskInvocation:post

                                                    +

                                                    Grants permission to batch create Agent tasks.

                                                    +

                                                    -

                                                    +

                                                    Batch creating Agent tasks

                                                    +

                                                    ces:taskInvocation:get

                                                    +

                                                    Grants permission to list Agent tasks.

                                                    +

                                                    -

                                                    +

                                                    Querying the Agent tasks

                                                    +

                                                    ces:oneClickAlarms:list

                                                    +

                                                    Grants permission to query services and resources that support one-click monitoring.

                                                    +

                                                    ces:namespacesMetrics:list

                                                    +

                                                    Querying services and resources that support one-click monitoring

                                                    +

                                                    ces:oneClickAlarms:post

                                                    +

                                                    Grants permission to enable one-click monitoring for a cloud service.

                                                    +

                                                    ces:oneClickAlarms:list, ces:namespacesMetrics:list, smn:topic:list

                                                    +

                                                    Enabling one-click monitoring for a cloud service

                                                    +

                                                    ces:oneClickAlarms:put

                                                    +

                                                    Grants permission to enable or disable one-click monitoring for alarm rules and alarm policies.

                                                    +

                                                    ces:oneClickAlarms:list, ces:namespacesMetrics:list

                                                    +

                                                    Enabling or disabling one-click monitoring for alarm rules and alarm policies

                                                    +

                                                    ces:oneClickAlarms:updateNotifications

                                                    +

                                                    Grants permission to batch modify alarm notifications for one service in one-click monitoring.

                                                    +

                                                    ces:oneClickAlarms:list, ces:namespacesMetrics:list, smn:topic:list

                                                    +

                                                    Batch modifying alarm notifications for one service in one-click monitoring

                                                    +

                                                    ces:oneClickAlarms:delete

                                                    +

                                                    Grants permission to disable one-click monitoring for a cloud service.

                                                    +

                                                    ces:oneClickAlarms:list, ces:namespacesMetrics:list

                                                    +

                                                    Disabling one-click monitoring for a cloud service

                                                    +

                                                    ces:agentStatus:get

                                                    +

                                                    Grants permission to query the Agent status.

                                                    +

                                                    -

                                                    +

                                                    Querying the Agent status

                                                    +

                                                    ces:agentClientPluginInfo:get

                                                    +

                                                    Grants permission to batch query plug-in information of specified servers.

                                                    +

                                                    -

                                                    +

                                                    Batch querying plug-in information of specified servers

                                                    +

                                                    ces:agentClientAvailabilityTask:get

                                                    +

                                                    Grants permission to get Agent availability task details.

                                                    +

                                                    -

                                                    +

                                                    Getting Agent availability task details

                                                    +

                                                    ces:agentTask:get

                                                    +

                                                    Grants permission to batch query task invocation of specified servers.

                                                    +

                                                    -

                                                    +

                                                    Querying task invocation of specified server in batches

                                                    +

                                                    ces:agentClientPluginInfo:put

                                                    +

                                                    Grants permission to batch update the plug-in information of specified servers.

                                                    +

                                                    -

                                                    +

                                                    Updating the plug-in information of specified servers in batches

                                                    +

                                                    ces:agentClientMonitor:put

                                                    +

                                                    Grants permission to update server monitoring metrics of a specified server.

                                                    +

                                                    -

                                                    +

                                                    Updating the server monitoring metrics of a specified server

                                                    +

                                                    ces:heartbeat:post

                                                    +

                                                    Grants permission to update the Agent status of a specified instance.

                                                    +

                                                    -

                                                    +

                                                    Updating the Agent status of a specified instance

                                                    +

                                                    ces:agentClientAvailabilityTask:put

                                                    +

                                                    Grants permission to update an Agent availability task.

                                                    +

                                                    -

                                                    +

                                                    Updating an Agent availability task

                                                    +

                                                    ces:agentTask:post

                                                    +

                                                    Grants permission to submit task results of a specified server.

                                                    +

                                                    -

                                                    +

                                                    Submitting task results of a specified server

                                                    +

                                                    ces:dataShareJob:list

                                                    +

                                                    Grants permission to batch query the list of data dump tasks.

                                                    +

                                                    -

                                                    +

                                                    Querying data dump tasks in batches

                                                    +

                                                    ces:dataShareJob:get

                                                    +

                                                    Grants permission to query a specified data dump task.

                                                    +

                                                    ces:dataShareJob:list

                                                    +

                                                    Querying a specified data dump task

                                                    +

                                                    ces:dataShareJob:action

                                                    +

                                                    Grants permission to start or stop a data dump task.

                                                    +

                                                    ces:dataShareJob:list

                                                    +

                                                    Starting or stopping a data dump task.

                                                    +

                                                    ces:dataShareJob:put

                                                    +

                                                    Grants permission to modify a data dump task.

                                                    +

                                                    ces:dataShareJob:list, ces:namespaces:list, ces:namespacesDimensions:list, dms:instance:list, dms:instance:get

                                                    +

                                                    Modifying a data dump task

                                                    +

                                                    ces:dataShareJob:delete

                                                    +

                                                    Grants permission to delete a specified data dump task.

                                                    +

                                                    ces:dataShareJob:list

                                                    +

                                                    Deleting a specified data dump task

                                                    +

                                                    ces:dataShareJob:create

                                                    +

                                                    Grants permission to create a data dump task.

                                                    +

                                                    ces:namespaces:list, ces:namespacesDimensions:list, dms:instance:list, dms:instance:get

                                                    +

                                                    Creating a data dump task

                                                    +

                                                    ces:resourcesConsole:list

                                                    +

                                                    Grants permission to batch query resource data of a specified namespace on the console.

                                                    +

                                                    -

                                                    +

                                                    Batch querying resource data of a specified namespace on the console

                                                    +

                                                    ces:dashboard:listResourceStatistics

                                                    +

                                                    Grants permission to query resource statistics of a specified dimension on the cloud service dashboard.

                                                    +

                                                    -

                                                    +

                                                    Querying resource statistics of a specified dimension on the cloud service dashboard

                                                    +

                                                    ces:alarmHistoriesReportJob:list

                                                    +

                                                    Grants permission to batch query tasks for alarm record reporting.

                                                    +

                                                    ces:namespaces:list, ces:currentRegionSupportedMetrics:list, ces:i18n:list

                                                    +

                                                    Viewing alarm record export tasks

                                                    +

                                                    ces:alarmHistoriesReportJob:create

                                                    +

                                                    Grants permission to batch create tasks for alarm record reporting.

                                                    +

                                                    ces:alarmHistory:list

                                                    +

                                                    Exporting alarm records

                                                    +

                                                    ces:alarmHistoriesReportJob:delete

                                                    +

                                                    Grants permission to batch delete tasks for alarm record reporting.

                                                    +

                                                    ces:alarmHistoriesReportJob:list

                                                    +

                                                    Deleting alarm record export tasks

                                                    +

                                                    ces:metricReportJob:create

                                                    +

                                                    Grants permission to batch create metric reporting tasks.

                                                    +

                                                    ces:metricData:list

                                                    +

                                                    Exporting monitoring data

                                                    +

                                                    ces:metricReportJobs:list

                                                    +

                                                    Grants permission to batch query metric reporting tasks.

                                                    +

                                                    ces:namespaces:list, ces:currentRegionSupportedMetrics:list, ces:i18n:list

                                                    +

                                                    Viewing monitoring data export tasks

                                                    +

                                                    ces:metricReportJobs:delete

                                                    +

                                                    Grants permission to batch delete metric reporting tasks.

                                                    +

                                                    ces:metricReportJobs:list

                                                    +

                                                    Deleting monitoring data export tasks

                                                    +

                                                    ces:resourcesMetadata:list

                                                    +

                                                    Grants permission to batch query resource metadata.

                                                    +

                                                    -

                                                    +

                                                    Batch querying resource metadata

                                                    +

                                                    ces:i18n:list

                                                    +

                                                    Grants permission to obtain internationalization information.

                                                    +

                                                    -

                                                    +

                                                    Obtaining internationalization information

                                                    +

                                                    ces:currentRegionSupportedMetrics:list

                                                    +

                                                    Grants permission to batch query metrics.

                                                    +

                                                    -

                                                    +

                                                    Batch querying metrics

                                                    +

                                                    ces:metricDataExport:get

                                                    +

                                                    Grants permission to export metric data.

                                                    +

                                                    ces:metricData:list

                                                    +

                                                    Exporting metric data

                                                    +
                                                    -

                                                    Helpful Links

                                                    +

                                                    Helpful Links

                                                    diff --git a/docs/ces/umn/ces_faq_0004.html b/docs/ces/umn/ces_faq_0004.html index 2ae652d8b..5fba026a1 100644 --- a/docs/ces/umn/ces_faq_0004.html +++ b/docs/ces/umn/ces_faq_0004.html @@ -2,7 +2,7 @@

                                                    What Alarm Status Does Cloud Eye Support?

                                                    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.
                                                    +
                                                    • 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_0008.html b/docs/ces/umn/ces_faq_0008.html index 922ee2f48..4210ccfd2 100644 --- a/docs/ces/umn/ces_faq_0008.html +++ b/docs/ces/umn/ces_faq_0008.html @@ -4,7 +4,7 @@

                                                    Because the sampling period in Cloud Eye is different from that of the metric monitoring tool in ECS.

                                                    Cloud Eye collects ECS and EVS disk data every 4 minutes (5 minutes for KVM ECSs). In contrast, the metric monitoring tool in ECS collects data every second.

                                                    The larger the sampling period, the greater the data distortion in the short term. Cloud Eye is more suitable for long-term monitoring for websites and applications running on ECSs.

                                                    -

                                                    Furthermore, to improve reliability, you can configure alarm thresholds to enable Cloud Eye to generate alarms where there are resource exceptions or insufficiencies.

                                                    +

                                                    To improve reliability, you can configure alarm thresholds to enable Cloud Eye to generate alarms where there are resource exceptions or shortages.

                                                    diff --git a/docs/ces/umn/ces_faq_0009.html b/docs/ces/umn/ces_faq_0009.html index d4c3e9e1e..231823443 100644 --- a/docs/ces/umn/ces_faq_0009.html +++ b/docs/ces/umn/ces_faq_0009.html @@ -1,13 +1,13 @@ -

                                                    What Is Aggregation?

                                                    -

                                                    Aggregation is a process where Cloud Eye calculates the maximum, minimum, average, sum, or variance value of raw data sampled for different periods and repeats the process for each subsequent period. A calculation period is called an aggregation period.

                                                    -

                                                    The aggregation process involves the smoothing of data sets. Configure a longer aggregation period if you want more smoothing to be performed. If more smoothing is performed, the generated data will be more precise, enabling you to predict trends more precisely. Configure a shorter aggregation period if you want more accurate alarm reporting.

                                                    -

                                                    The aggregation period can be 5 minutes, 20 minutes, 1 hour, 4 hours, or 1 day.

                                                    -

                                                    During the aggregation, Cloud Eye processes data sampled based on the data type.

                                                    +

                                                    What Is Rollup?

                                                    +

                                                    Rollup is a process where Cloud Eye calculates the maximum, minimum, average, sum, or variance value of raw data sampled for different periods and repeats the process for each subsequent period. A calculation period is called a rollup period.

                                                    +

                                                    During the rollup, data sets are smoothed. A longer rollup period means more smoothing and precise data, enabling you to predict trends more precisely. On the contrary, a shorter rollup period means more accurate alarms.

                                                    +

                                                    The rollup period can be 5 minutes, 20 minutes, 1 hour, 4 hours, or 1 day.

                                                    +

                                                    During the rollup, Cloud Eye processes data sampled based on the data type.

                                                    • If the data sampled is integers, Cloud Eye rounds off the aggregation results.
                                                    • If the data includes decimal values (floating point number), Cloud Eye truncates the data after the second decimal place.
                                                    -

                                                    For example, if the instance quantity in Auto Scaling is an integer value, the aggregation period is 5 minutes, and the current time is 10:35, Cloud Eye rolls up the raw data generated between 10:30 and 10:35 to the time point of 10:30. If the sampled metrics are 1 and 4 respectively, after aggregation, the maximum value is 4, the minimum value is 1, and the average value is [(1 + 4)/2] = 2, instead of 2.5.

                                                    -

                                                    Choose whichever aggregation method best meets your service requirements.

                                                    +

                                                    For example, if the instance quantity in Auto Scaling is an integer value, the rollup period is 5 minutes, and the current time is 10:35, Cloud Eye rolls up the raw data generated between 10:30 and 10:35 to the time point of 10:30. If the sampled metrics are 1 and 4 respectively, after aggregation, the maximum value is 4, the minimum value is 1, and the average value is [(1 + 4)/2] = 2, instead of 2.5.

                                                    +

                                                    Choose whichever rollup method best meets your service requirements.

                                                    diff --git a/docs/ces/umn/ces_faq_0010.html b/docs/ces/umn/ces_faq_0010.html index 0b69b91f8..1a1c51eb9 100644 --- a/docs/ces/umn/ces_faq_0010.html +++ b/docs/ces/umn/ces_faq_0010.html @@ -2,8 +2,8 @@

                                                    How Long Is Metric Data Retained?

                                                    Metric data includes raw data and rolled-up data.

                                                    -
                                                    • Raw data is retained for two days.
                                                    • Rolled-up data is data aggregated based on raw data. The retention period for rolled-up data depends on the aggregation period. -
                                                      Table 1 Retention periods for rolled-up data

                                                      Aggregation Period

                                                      +
                                                      • Raw data is retained for two days.
                                                      • Rolled-up data is data aggregated based on raw data. The retention period for rolled-up data depends on the rollup period. +
                                                        diff --git a/docs/ces/umn/ces_faq_0011.html b/docs/ces/umn/ces_faq_0011.html deleted file mode 100644 index 1c4e5f517..000000000 --- a/docs/ces/umn/ces_faq_0011.html +++ /dev/null @@ -1,12 +0,0 @@ - - -

                                                        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.

                                                        -
                                                        -
                                                        -
                                                        -
                                                        Parent topic: Monitored Data Exceptions
                                                        -
                                                        -
                                                        - diff --git a/docs/ces/umn/ces_faq_0012.html b/docs/ces/umn/ces_faq_0012.html deleted file mode 100644 index e5c93521f..000000000 --- a/docs/ces/umn/ces_faq_0012.html +++ /dev/null @@ -1,16 +0,0 @@ - - -

                                                        How Can I Export Collected Data?

                                                        -
                                                        1. On the Cloud Eye console, choose Cloud Service Monitoring or Server Monitoring.
                                                        2. Click Export Data.
                                                        3. Configure the time range, resource type, dimension, monitored object, and metric.
                                                        4. Click Export.
                                                        -

                                                        You can export data for multiple metrics at a time to a CSV file.

                                                        -
                                                        -
                                                        • 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:
                                                          1. Use Excel to open a .csv file.
                                                          2. Use the following formula to convert the time:

                                                            Target time = [Unix timestamp/1000 + (Target time zone) x 3600]/86400 + 70 x 365 + 19

                                                            -
                                                          3. Set cell format to Date.
                                                          -
                                                        -
                                                        -
                                                        -
                                                        -
                                                        Parent topic: General Consulting
                                                        -
                                                        -
                                                        - diff --git a/docs/ces/umn/ces_faq_0013.html b/docs/ces/umn/ces_faq_0013.html index e2a5c118d..3f2e92e92 100644 --- a/docs/ces/umn/ces_faq_0013.html +++ b/docs/ces/umn/ces_faq_0013.html @@ -1,13 +1,13 @@

                                                        How Many Rollup Methods Does Cloud Eye Support?

                                                        -

                                                        Cloud Eye supports the following rollup methods:

                                                        -
                                                        • Average

                                                          If Avg. is selected for Statistic, Cloud Eye calculates the average value of metrics collected within a rollup period.

                                                          -
                                                        • Maximum

                                                          If Max. is selected for Statistic, Cloud Eye calculates the maximum value of metrics collected within a rollup period.

                                                          -
                                                        • Minimum

                                                          If Min. is selected for Statistic, Cloud Eye calculates the minimum value of metrics collected within a rollup period.

                                                          -
                                                        • Sum

                                                          If Sum is selected for Statistic, Cloud Eye calculates the sum of metrics collected within a rollup period.

                                                          -
                                                        • Variance

                                                          If Variance is selected for Statistic, Cloud Eye calculates the variance value of metrics collected within a rollup period.

                                                          -

                                                          Take a 5-minute period as an example. If it is 10:35 now and the rollup period starts at 10:30, the raw data generated between 10:30 and 10:35 is rolled up.

                                                          +

                                                          Cloud Eye supports the following five rollup methods, among which variance has been disabled and will be removed in later versions:

                                                          +
                                                          • Average

                                                            If Statistic is set to Avg., Cloud Eye calculates the average value of metrics collected within a rollup period.

                                                            +
                                                          • Maximum

                                                            If Statistic is set to Max., Cloud Eye calculates the maximum value of metrics collected within a rollup period.

                                                            +
                                                          • Minimum

                                                            If Statistic is set to Min., Cloud Eye calculates the minimum value of metrics collected within a rollup period.

                                                            +
                                                          • Sum

                                                            If Statistic is set to Sum, Cloud Eye calculates the sum of metrics collected within a rollup period.

                                                            +
                                                          • Variance

                                                            If Statistic is set to Variance, Cloud Eye calculates the variance value of metrics collected within a rollup period.

                                                            +

                                                            Take a 5-minute period as an example. If it is 10:35 now and the rollup period starts at 10:30, the raw data generated between 10:30 and 10:35 is rolled up to 10:30.

                                                          diff --git a/docs/ces/umn/ces_faq_0024.html b/docs/ces/umn/ces_faq_0024.html new file mode 100644 index 000000000..b556455ed --- /dev/null +++ b/docs/ces/umn/ces_faq_0024.html @@ -0,0 +1,153 @@ + + +

                                                          What OSs Does the Agent Support?

                                                          +

                                                          The following table lists OSs compatible with the Agent. More OSs will be supported soon.

                                                          +

                                                          Using the OSs or versions that have not been verified may adversely affect your services. Exercise caution when using them.

                                                          +
                                                          +

                                                          Table 2 lists the supported OSs.

                                                          + +
                                                        Table 1 Retention periods for rolled-up data

                                                        Rollup Period

                                                        Retention Period
                                                        + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                                                        Table 1 OS versions supported by the early version of the Agent for ECS

                                                        OS (64 bit)

                                                        +

                                                        Version

                                                        +

                                                        CentOS

                                                        +

                                                        6.3, 6.5, 6.8, 6.9, 7.1, 7.2, 7.3, 7.4, 7.5, 7.6

                                                        +

                                                        OpenSUSE

                                                        +

                                                        13.2, 42.2

                                                        +

                                                        Debian

                                                        +

                                                        7.5.0, 8.2.0, 8.8.0, 9.0.0

                                                        +

                                                        Ubuntu

                                                        +

                                                        14.04 server, 16.04 server

                                                        +

                                                        EulerOS

                                                        +

                                                        2.2, 2.3

                                                        +

                                                        SUSE

                                                        +

                                                        Enterprise11 SP4, Enterprise12 SP1, Enterprise12 SP2

                                                        +

                                                        Fedora

                                                        +

                                                        24, 25

                                                        +

                                                        Oracle Linux

                                                        +

                                                        6.9, 7.4

                                                        +

                                                        CoreOS

                                                        +

                                                        10.10.5

                                                        +
                                                        NOTE:

                                                        Cloud-Init cannot be installed automatically. Install it manually in the / directory.

                                                        +

                                                        To query the Agent status, run systemctl telescoped status.

                                                        +
                                                        +

                                                        Other

                                                        +

                                                        Gentoo Linux 13.0, Gentoo Linux 17.0

                                                        +
                                                        NOTE:

                                                        To query the Agent status, run rc-service telescoped status.

                                                        +
                                                        +

                                                        Windows

                                                        +

                                                        Windows Server 2022 Standard 64-bit

                                                        +

                                                        Windows Server 2019 Standard 64-bit

                                                        +

                                                        Windows Server 2016 Standard 64-bit

                                                        +

                                                        Windows Server 2016 Datacenter 64-bit

                                                        +

                                                        Windows Server 2012 R2 Standard 64-bit

                                                        +

                                                        Windows Server 2012 R2 Datacenter 64-bit

                                                        +

                                                        Windows Server 2008 R2 Standard 64-bit

                                                        +

                                                        Windows Server 2008 R2 Datacenter 64-bit

                                                        +

                                                        Windows Server 2008 R2 Enterprise 64-bit

                                                        +

                                                        Windows Server 2008 R2 Web 64-bit

                                                        +

                                                        Arm general-computing

                                                        +

                                                        CentOS 7.4 64bit with ARM (40 GB)

                                                        +

                                                        CentOS 7.5 64bit with ARM (40 GB)

                                                        +

                                                        CentOS 7.6 64bit with ARM (40 GB)

                                                        +

                                                        EulerOS 2.8 64bit with ARM (40 GB)

                                                        +

                                                        Fedora 29 64bit with ARM (40 GB)

                                                        +

                                                        Ubuntu 18.04 64bit with ARM (40 GB)

                                                        +
                                                        +
                                                        + +
                                                        + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
                                                        Table 2 OS versions supported by the new version of the Agent for ECS

                                                        OS (64 bit)

                                                        +

                                                        Version

                                                        +

                                                        CentOS

                                                        +

                                                        6.5, 6.8, 6.9, 6.10, 7.2, 7.3, 7.4, 7.5, 7.6, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2

                                                        +

                                                        OpenSUSE

                                                        +

                                                        15.0

                                                        +

                                                        Debian

                                                        +

                                                        8.2, 8.8, 9.0, 10.0

                                                        +

                                                        Ubuntu

                                                        +

                                                        16.04, 18.04, 20.04

                                                        +

                                                        EulerOS

                                                        +

                                                        2.2, 2.3, 2.5

                                                        +

                                                        Fedora

                                                        +

                                                        30

                                                        +

                                                        openEuler

                                                        +

                                                        20.3

                                                        +

                                                        Windows

                                                        +

                                                        2012, 2016, 2019, 2022

                                                        +
                                                        +
                                                        + +
                                                        +
                                                        +
                                                        Parent topic: Server Monitoring
                                                        +
                                                        +
                                                        + diff --git a/docs/ces/umn/ces_faq_0025.html b/docs/ces/umn/ces_faq_0025.html index 11c0185f7..84f957426 100644 --- a/docs/ces/umn/ces_faq_0025.html +++ b/docs/ces/umn/ces_faq_0025.html @@ -3,10 +3,13 @@

                                                        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 three consecutive minutes, Agent Status is displayed as Faulty.

                                                        It may because:

                                                        -
                                                        • 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
                                                          +
                                                          • 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 accidentally. In this case, reinstall the Agent.
                                                          • The server time is inconsistent with the local standard time.
                                                          • 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 on a Linux Server.
                                                          • Specific causes are logged. You can check the log file for the cause. The log path varies with the Agent version.

                                                            The log paths are as follows:

                                                            +
                                                            • Linux:

                                                              New Agent version: /usr/local/uniagent/extension/install/telescope/log/ces.log

                                                              +

                                                              Early Agent version: /usr/local/telescope/log/ces.log

                                                              +
                                                            • Windows:

                                                              New version: C:\Program Files\uniagent\extension\install\telescope\log\ces.log

                                                              +

                                                              Earlier version: path where the Agent installation package is decompressed. For example, if the decompression path is D:\Agent, the log path is D:\Agent\telescope_windows_amd64\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.

                                                        diff --git a/docs/ces/umn/ces_faq_0027.html b/docs/ces/umn/ces_faq_0027.html deleted file mode 100644 index fbdfa8257..000000000 --- a/docs/ces/umn/ces_faq_0027.html +++ /dev/null @@ -1,12 +0,0 @@ - - -

                                                        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 ECS and click Restore Agent Configurations. In the displayed Restore Agent Configurations dialog box, click One-Click Restore.

                                                        -
                                                        -
                                                        -
                                                        -
                                                        Parent topic: Server Monitoring
                                                        -
                                                        -
                                                        - diff --git a/docs/ces/umn/ces_faq_0028.html b/docs/ces/umn/ces_faq_0028.html index c14779a7f..2587f39e8 100644 --- a/docs/ces/umn/ces_faq_0028.html +++ b/docs/ces/umn/ces_faq_0028.html @@ -44,7 +44,7 @@

                                                        Agency Configuration

                                                        If no agency is configured for a server, perform the following operations to configure an agency:

                                                        1. Log in to the management console.
                                                        2. Choose Service List > Computing > Elastic Cloud Server.

                                                          If you purchase a BMS, choose Computing > Bare Metal Server.

                                                          -
                                                        3. Click the name of the ECS or BMS where the Agent is located. The parameter configuration page is displayed.
                                                        4. In the Management Information area, select the agency created in 5 for Agency and click the green tick to make the agency take effect.
                                                        +
                                                      • Click the name of the ECS or BMS where the Agent is located. The parameter configuration page is displayed.
                                                      • For Agency Name, select the agency name created in 5 and click the green tick to confirm your selection.
                                                        • diff --git a/docs/ces/umn/ces_faq_0032.html b/docs/ces/umn/ces_faq_0032.html index b1a766f08..636de1e74 100644 --- a/docs/ces/umn/ces_faq_0032.html +++ b/docs/ces/umn/ces_faq_0032.html @@ -1,7 +1,7 @@ -

                                                        What Can't I Create Another Agency?

                                                        -

                                                        It may be that your quota is used up. If this is the case, you can delete unneeded agencies first or increase the agency quota. Then you can use the agency to restore the Agent configuration.

                                                        +

                                                        Why Can't I Create Another Agency?

                                                        +

                                                        Your quota may be used up. In this case, you can delete unneeded agencies first or request a higher agency quota. Then you can use the agency to restore the Agent configuration. For details about how to adjust quotas, see Quota Adjustment.

                                                        diff --git a/docs/ces/umn/ces_faq_0037.html b/docs/ces/umn/ces_faq_0037.html index da7f2c4d0..425eb18d4 100644 --- a/docs/ces/umn/ces_faq_0037.html +++ b/docs/ces/umn/ces_faq_0037.html @@ -2,14 +2,22 @@

                                                        What Should I Do If the Service Port Is Used by the Agent?

                                                        Cloud Eye Agent uses HTTP requests to report data. Any port in the range obtained from path /proc/sys/net/ipv4/ip_local_port_range may be occupied. If any service port is used by the Agent, you can modify path /proc/sys/net/ipv4/ip_local_port_range and restart the Agent to solve the problem.

                                                        -

                                                        Procedure

                                                        1. Log in an ECS or BMS as user root.
                                                        2. Open the sysctl.conf file:

                                                          vim /etc/sysctl.conf

                                                          -
                                                        3. (Permanent change) Add new ports to the sysctl.conf file:

                                                          net.ipv4.ip_local_port_range=49152 65536

                                                          -
                                                        4. Make the modification take effect:

                                                          sysctl -p /etc/sysctl.conf

                                                          -
                                                          • The permanent change still takes effect after the ECS or BMS is restarted.
                                                          • For temporary modification (which expires after the ECS or BMS is restarted), run # echo 49152 65536 > /proc/sys/net/ipv4/ip_local_port_range.
                                                          -
                                                          -
                                                        5. Run the following command to restart the Agent:

                                                          /usr/local/telescope/telescoped restart

                                                          -

                                                          For Windows, in the directory where the Agent installation package is stored, double-click the shutdown.bat script to stop the Agent, and execute the start.bat script to start the Agent.

                                                          +

                                                          Linux

                                                          1. Log in an ECS or BMS as user root.
                                                          2. Open the sysctl.conf file.
                                                            vim /etc/sysctl.conf
                                                            +
                                                          3. (Permanent change) Add new ports to the sysctl.conf file.
                                                            net.ipv4.ip_local_port_range=49152 65536
                                                            +
                                                          4. Apply the changes.
                                                            sysctl -p /etc/sysctl.conf
                                                            +
                                                            • The permanent change still takes effect after the ECS or BMS is restarted.
                                                            • For temporary changes (which expires after the ECS or BMS is restarted), run the # echo 49152 65536 > /proc/sys/net/ipv4/ip_local_port_range command.
                                                            +
                                                          5. Restart the Agent.
                                                            Earlier version:
                                                            /usr/local/telescope/telescoped restart
                                                            +
                                                            +
                                                            New version:
                                                            service ces-uniagent stop
+service ces-uniagent start
+/usr/local/uniagent/extension/install/telescope/telescoped restart
                                                            +
                                                            +
                                                          +
                                                          +

                                                          Windows

                                                          1. Log in to the ECS as an administrator.
                                                          2. Open Windows PowerShell and run the following command to change the number of ports:
                                                            netsh int ipv4 set dynamicportrange tcp start=49152 num=16384
                                                            +
                                                          3. Go to the Agent installation directory, double-click the shutdown.bat script to stop the Agent, and then run the start.bat script to start the Agent.

                                                            Earlier version: The Agent is installed in the directory where the Agent installation package is decompressed, for example, if the package is decompressed in D:\Agent, the installation path would be D:\Agent\telescope_windows_amd64.

                                                            +

                                                            New version: The default Agent installation path is C:\Program Files\uniagent\extension\install\telescope.

                                                          diff --git a/docs/ces/umn/ces_faq_0053.html b/docs/ces/umn/ces_faq_0053.html index e6eea276f..efd667426 100644 --- a/docs/ces/umn/ces_faq_0053.html +++ b/docs/ces/umn/ces_faq_0053.html @@ -6,7 +6,7 @@

                                                          Possible Causes

                                                          The Agent determines whether a server is an ECS or BMS based on the services provided by IP address 169.254.169.254. If the route for this address is changed, the Agent will consider the server to be an ECS by default.

                                                          Solution

                                                          Manually modify the Agent configuration file by adding BMS identifier BmsFlag and setting it to true.

                                                          - +
                                                          diff --git a/docs/ces/umn/ces_faq_0059.html b/docs/ces/umn/ces_faq_0059.html index 4ac3dcd4e..c769fff8a 100644 --- a/docs/ces/umn/ces_faq_0059.html +++ b/docs/ces/umn/ces_faq_0059.html @@ -8,15 +8,17 @@
                                                          diff --git a/docs/ces/umn/ces_faq_0062.html b/docs/ces/umn/ces_faq_0062.html index 4ecd250e0..46f5aa9b6 100644 --- a/docs/ces/umn/ces_faq_0062.html +++ b/docs/ces/umn/ces_faq_0062.html @@ -9,8 +9,6 @@
                                                        6. Why Are the Network Traffic Metric Values in Cloud Eye Different from Those Detected in ECS?
                                                          7. -
                                                        7. What Are the Impacts on ECS Metrics If OTC Tools Are Not Installed on ECSs?
                                                          -
                                                      diff --git a/docs/ces/umn/ces_faq_0064.html b/docs/ces/umn/ces_faq_0064.html index c42f72fa6..2151214ab 100644 --- a/docs/ces/umn/ces_faq_0064.html +++ b/docs/ces/umn/ces_faq_0064.html @@ -7,6 +7,8 @@
                                                      diff --git a/docs/ces/umn/ces_faq_0072.html b/docs/ces/umn/ces_faq_0072.html new file mode 100644 index 000000000..906acc1b6 --- /dev/null +++ b/docs/ces/umn/ces_faq_0072.html @@ -0,0 +1,51 @@ + + +

                                                      What Can I Do If the System Displays a Message Indicating Insufficient Permissions When I Click Configure on the Server Monitoring Page?

                                                      +

                                                      Symptoms

                                                      When an IAM user clicked Configure on the Server Monitoring page, a message indicating insufficient permissions was displayed.

                                                      +
                                                      +

                                                      Possible Causes

                                                      The IAM agency permissions are not configured for the IAM user.

                                                      +
                                                      +

                                                      Procedure

                                                      1. Add a policy for querying the agencies.

                                                        1. Log in to the management console using an account or IAM user that has the permissions to create custom policies and grant permissions to other IAM users.
                                                        2. Ensure that the account has been granted the Agent permissions for the region by performing the following operations: On the Cloud Eye console, choose Server Monitoring > Elastic Cloud Server. Check whether Configure is displayed above the ECS list.
                                                          • If no, the Agent permissions have been granted for the region.
                                                          • If yes, click Configure to enable the Agent permissions for the region.
                                                          +
                                                        3. In the service list, select Identity and Access Management.
                                                        4. In the navigation pane, choose Permissions > Policies/Roles. Search for the CES agency policy CES AgencyCheck Access. If the policy can be found, grant permissions by referring to Step 2. If the policy does not exist, perform the following steps to create a custom policy:
                                                          1. Click Create Custom Policy in the upper right corner.
                                                            1. Configure the following parameters:
                                                              • Policy Name: Specify a custom policy name.
                                                              • Policy View: Select JSON.
                                                              • Policy Content: Copy the following code and paste it to the text box.
                                                                {
+    "Version": "1.1",
+    "Statement": [
+        {
+            "Action": [
+                "iam:agencies:createAgency",
+                "iam:agencies:getAgency",
+                "iam:agencies:listAgencies",
+                "iam:permissions:grantRoleToAgency",
+                "iam:permissions:grantRoleToAgencyOnDomain",
+                "iam:permissions:grantRoleToAgencyOnProject",
+                "iam:permissions:listRolesForAgency",
+                "iam:permissions:listRolesForAgencyOnDomain",
+                "iam:permissions:listRolesForAgencyOnProject",
+                "iam:permissions:revokeRoleFromAgency",
+                "iam:permissions:revokeRoleFromAgencyOnDomain",
+                "iam:permissions:revokeRoleFromAgencyOnProject",
+                "iam:roles:createRole",
+                "iam:roles:listRoles",
+                "iam:roles:updateRole"
+            ],
+            "Effect": "Allow"
+        }
+    ]
+}
                                                                +
                                                              • Description: (Optional) Provide supplementary information about the policy.
                                                              +
                                                            2. Confirm the policy content and click OK to save the policy.
                                                            +
                                                          +
                                                        +

                                                      2. Assign permissions to the IAM user.

                                                        1. In the navigation pane, choose User Groups, locate the user group that contains the IAM user, and choose Authorize in the Operation column.

                                                          +
                                                        2. Search for the added custom policy name or CES AgencyCheck Access, select the policy, and click Next.

                                                          +
                                                        3. Select Global services and click OK.

                                                          +
                                                        4. If Authorization successful is displayed, click Finish.

                                                          +
                                                        +

                                                      +
                                                      +
                                                      +
                                                      +
                                                      +
                                                      Parent topic: User Permissions
                                                      +
                                                      +
                                                      + diff --git a/docs/ces/umn/ces_faq_0126.html b/docs/ces/umn/ces_faq_0126.html new file mode 100644 index 000000000..b36647623 --- /dev/null +++ b/docs/ces/umn/ces_faq_0126.html @@ -0,0 +1,47 @@ + + +

                                                      How Do I Enable or Disable Metric Collection by Modifying the Configuration File?

                                                      +

                                                      This following describes how to enable or disable metric collection by modifying the configuration file.

                                                      +

                                                      This operation applies only to Agent 2.7.2 or later.

                                                      +
                                                      +

                                                      Modifying the Configuration File to Enable Metric Collection

                                                      1. Log in to a server as the root user (Linux) or as an administrator (Windows).
                                                      2. Modify the custom_conf.json file.
                                                        1. Go to the configuration file directory.
                                                          Windows:
                                                          cd C:\Program Files\uniagent\extension\install\telescope\conf
                                                          +
                                                          +
                                                          Linux:
                                                          cd /usr/local/uniagent/extension/install/telescope/conf
                                                          +
                                                          +
                                                        2. Open the custom_conf.json file.
                                                          vi custom_conf.json
                                                          +
                                                        3. Enter the following configuration content in {}. Replace metric_name1 and metric_name2 with the metric values in What Metrics Are Supported by the Agent.
                                                          "telescope.metric.metric_name1.enable": "true",
+"telescope.metric.metric_name2.enable": "true"
                                                          +
                                                          Example: Figure 1 shows the configuration content for enabling metric collection for cpu_usage and cpu_usage_idle.
                                                          Figure 1 Enabling metric collection for cpu_usage and cpu_usage_idle
                                                          +
                                                          +
                                                        +
                                                      3. Restart the Agent.
                                                        • Windows:
                                                          1. In the C:\Program Files\uniagent\extension\install\telescope directory, double-click shutdown.bat to stop the Agent, and then run start.bat to start the Agent.
                                                          2. In the C:\Program Files\uniagent\script directory, double-click shutdown.bat to stop the Agent, and then run start.bat to start the Agent.
                                                          +
                                                        • Linux:
                                                          service ces-uniagent stop
+service ces-uniagent start
+/usr/local/uniagent/extension/install/telescope/telescoped restart
                                                          +
                                                        +
                                                      +
                                                      +

                                                      Modifying the Configuration File to Disable Metric Collection

                                                      1. Log in to the server as the root user (Linux) or as an administrator (Windows).
                                                      2. Modify the custom_conf.json file.
                                                        1. Go to the configuration file directory.
                                                          Windows:
                                                          cd C:\Program Files\uniagent\extension\install\telescope\conf
                                                          +
                                                          +
                                                          Linux:
                                                          cd /usr/local/uniagent/extension/install/telescope/conf
                                                          +
                                                          +
                                                        2. Open the custom_conf.json file.
                                                          vi custom_conf.json
                                                          +
                                                        3. Enter the following configuration content in {}. Replace metric_name1 and metric_name2 with the metric values in What Metrics Are Supported by the Agent.
                                                          "telescope.metric.metric_name1.enable": "false",
+"telescope.metric.metric_name2.enable": "false"
                                                          +
                                                          Example: Figure 2 shows the configuration content for disabling metric collection for cpu_usage and cpu_usage_idle.
                                                          Figure 2 Disabling metric collection for cpu_usage and cpu_usage_idle
                                                          +
                                                          +
                                                        +
                                                      3. Restart the Agent.
                                                        • Windows:
                                                          1. In the C:\Program Files\uniagent\extension\install\telescope directory, double-click shutdown.bat to stop the Agent, and then run start.bat to start the Agent.
                                                          2. In the C:\Program Files\uniagent\script directory, double-click shutdown.bat to stop the Agent, and then run start.bat to start the Agent.
                                                          +
                                                        • Linux:
                                                          service ces-uniagent stop
+service ces-uniagent start
+/usr/local/uniagent/extension/install/telescope/telescoped restart
                                                          +
                                                        +
                                                      +
                                                      +
                                                      +
                                                      +
                                                      +
                                                      Parent topic: Server Monitoring
                                                      +
                                                      +
                                                      + diff --git a/docs/ces/umn/ces_faq_0127.html b/docs/ces/umn/ces_faq_0127.html new file mode 100644 index 000000000..6b5bbe91d --- /dev/null +++ b/docs/ces/umn/ces_faq_0127.html @@ -0,0 +1,127 @@ + + +

                                                      How Do I Change the Agent Resource Usage Threshold by Modifying the Configuration File?

                                                      +

                                                      This section describes how to modify the configuration file to change the Agent resource usage threshold.

                                                      +

                                                      This operation applies only to Agent 2.7.2 or later.

                                                      +
                                                      +

                                                      Procedure

                                                      +
                                                      1. Use the root account to log in to the ECS or BMS for which the Agent does not report data.
                                                      2. Modify the conf.json configuration file.
                                                        1. Go to the Agent installation path bin by running the following command:
                                                          Windows:
                                                          cd C:\Program Files\uniagent\extension\install\telescope\bin
                                                          +
                                                          +
                                                          Linux:
                                                          cd /usr/local/uniagent/extension/install/telescope/bin
                                                          +
                                                          +
                                                        2. Open conf.json.
                                                          vi conf.json
                                                          +
                                                        3. Add the following parameters to the conf.json file.
                                                          {
+    "cpu_first_pct_threshold": xx,
+    "memory_first_threshold": xxx,
+    "cpu_second_pct_threshold": xx,
+    "memory_second_threshold": xxx
+}
                                                          + +
                                                          + + + + + + + + + + + + + + + + + + +
                                                          Table 1 Parameters in the conf.json file

                                                          Parameter

                                                          +

                                                          Description

                                                          +

                                                          How to Query Parameter Values

                                                          +

                                                          cpu_first_pct_threshold

                                                          +

                                                          Tier-1 threshold of CPU usage. The default value is 10 (%).

                                                          +

                                                          To query the CPU usage and memory usage of the Agent process, use either of the following methods:

                                                          +
                                                          • Linux:

                                                            top -p telescope PID

                                                            +
                                                          • Windows:

                                                            View the details of the Agent process in Task Manager.

                                                            +
                                                          +

                                                          +

                                                          +

                                                          +

                                                          memory_first_threshold

                                                          +

                                                          Tier-1 threshold of memory usage. The default value is 209715200 (200 MB). The unit is byte.

                                                          +

                                                          cpu_second_pct_threshold

                                                          +

                                                          Tier-2 threshold of CPU usage. The default value is 30 (%).

                                                          +

                                                          memory_second_threshold

                                                          +

                                                          Tier-2 threshold of memory usage. The default value is 734003200 (700 MB). The unit is byte.

                                                          +
                                                          +
                                                          +
                                                        4. Save the conf.json file and exit.
                                                          :wq
                                                          +
                                                        +
                                                      3. Modify the manifest.json configuration file.
                                                        1. Switch to the manifest.json file directory.
                                                          Windows:
                                                          cd C:\Program Files\uniagent\extension\holder\telescope
                                                          +
                                                          +
                                                          Linux:
                                                          cd /usr/local/uniagent/extension/holder/telescope
                                                          +
                                                          +
                                                        2. Open manifest.json.
                                                          vi manifest.json
                                                          +
                                                        3. Modify the parameters mem and cpuUsage in resourceLimit, three parameter sets in total. Retain the default values of other parameters.
                                                          [
+	{
+		"arch": "amd64",
+		...
+		"resourceLimit": {
+			"mem": 200,
+			"cpuUsage": 10
+		}
+	},
+	{
+		"arch": "arm64",
+		...
+		"resourceLimit": {
+			"mem": 200,
+			"cpuUsage": 10
+		}
+	},
+	{
+		"arch": "amd64",
+		"os": "linux",
+		...
+		"resourceLimit": {
+			"mem": 200,
+			"cpuUsage": 10
+		}
+	}
+]
                                                          + +
                                                          + + + + + + + +
                                                          Table 2 Parameters in the manifest.json file

                                                          Parameter

                                                          +

                                                          Description

                                                          +

                                                          "resourceLimit": {

                                                          +

                                                          "mem": 200,

                                                          +

                                                          "cpuUsage": 10

                                                          +

                                                          }

                                                          +

                                                          mem: memory threshold. The default value is 200, in MB.

                                                          +

                                                          cpuUsage: CPU usage threshold (%). The default value is 10.

                                                          +
                                                          +
                                                          +
                                                        4. Save the manifest.json file and exit.
                                                          :wq
                                                          +
                                                        +
                                                      4. Restart the Agent.
                                                        • Windows:
                                                          1. In the C:\Program Files\uniagent\extension\install\telescope directory, double-click shutdown.bat to stop the Agent, and then run start.bat to start the Agent.
                                                          2. In the C:\Program Files\uniagent\script directory, double-click shutdown.bat to stop the Agent, and then run start.bat to start the Agent.
                                                          +
                                                        • Linux:
                                                          service ces-uniagent stop
+service ces-uniagent start
+/usr/local/uniagent/extension/install/telescope/telescoped restart
                                                          +
                                                        +
                                                      +

                                                      +
                                                      +
                                                      +
                                                      +
                                                      Parent topic: Server Monitoring
                                                      +
                                                      +
                                                      + diff --git a/docs/ces/umn/ces_faq_0128.html b/docs/ces/umn/ces_faq_0128.html new file mode 100644 index 000000000..0dfd7004c --- /dev/null +++ b/docs/ces/umn/ces_faq_0128.html @@ -0,0 +1,30 @@ + + +

                                                      How Do I Change the Process Collection Frequency by Modifying the Configuration File?

                                                      +

                                                      The following describes how to modify the configuration file to change the process collection frequency.

                                                      +

                                                      This operation applies only to Agent 2.7.2 or later.

                                                      +
                                                      +

                                                      Linux

                                                      1. Log in to a server as user root.
                                                      2. Modify the configuration file.

                                                        cd /usr/local/uniagent/extension/install/telescope/conf && vi custom_conf.json
                                                        +

                                                        Enter the following configuration content in {} to change the number of processes updated per minute. The calculation method is as follows: (${telescope.metric.proc.flush_metric_batch_size} x ${telescope.metric.proc.flush_metric_period})/60

                                                        +
                                                        "telescope.metric.proc.flush_metric_batch_size":"num1",
+"telescope.metric.proc.flush_metric_period":"num2"
                                                        +

                                                        Configurations for updating 50 processes per minute

                                                        +

                                                        +

                                                      3. Restart the Agent.

                                                        service ces-uniagent stop
+service ces-uniagent start
+/usr/local/uniagent/extension/install/telescope/telescoped restart
                                                        +

                                                      +
                                                      +

                                                      Windows

                                                      1. Log in to a server.
                                                      2. Modify the custom_conf.json configuration file in C:\Program Files\uniagent\extension\install\telescope\conf to change the number of processes updated per minute. The calculation method is as follows: (${telescope.metric.proc.flush_metric_batch_size} x ${telescope.metric.proc.flush_metric_period})/60

                                                        Example: If you want to update 50 processes every minute, enter the following content in {}:

                                                        +
                                                        "telescope.metric.proc.flush_metric_batch_size":"50",
+"telescope.metric.proc.flush_metric_period":"60"
                                                        +

                                                      3. In the C:\Program Files\uniagent\extension\install\telescope directory, restart the Agent.

                                                        1. Double-click shutdown.bat to stop the Agent process.
                                                        2. Double-click start.bat to start the Agent process.
                                                        +

                                                      +
                                                      +
                                                      +
                                                      +
                                                      +
                                                      Parent topic: Server Monitoring
                                                      +
                                                      +
                                                      + diff --git a/docs/ces/umn/ces_faq_2502.html b/docs/ces/umn/ces_faq_2502.html new file mode 100644 index 000000000..e5e01942a --- /dev/null +++ b/docs/ces/umn/ces_faq_2502.html @@ -0,0 +1,18 @@ + + +

                                                      How Do I Configure an Agency?

                                                      +

                                                      To enable you to monitor servers more securely and efficiently, Cloud Eye provides the latest Agent permission-granting method. That is, before installing Agents, you only need to click Configure on the Server Monitoring page of the Cloud Eye console, the system will perform temporary AK/SK authorization for the Agents installed on all ECSs or BMSs in the region. And in the future, newly created ECSs or BMSs in this region will automatically get this authorization. This section describes the authorization as follows:

                                                      +
                                                      • Authorization object

                                                        On the Cloud Eye console, if you choose Server Monitoring > Elastic Cloud Server (or Bare Metal Server), select a server, and click Configure, the system will create an agency named cesagency on IAM. The agency permissions are automatically granted to Cloud Eye internal account op_svc_ces.

                                                        +

                                                        If the system displays a message indicating that the tenant does not have insufficient permissions, see What Can I Do If the System Displays a Message Indicating Insufficient Permissions When I Click Configure on the Server Monitoring Page?

                                                        +
                                                        +
                                                      • Authorization scope

                                                        Add the CES AgentAccess permissions to internal account op_svc_ces in the region.

                                                        +
                                                      • Authorization reason
                                                        The Cloud Eye Agent runs on ECSs or BMSs and reports the collected monitoring data to Cloud Eye. After being authorized, the Agent automatically obtains a temporary AK/SK. This way, you can query the ECS or BMS monitoring data on the Cloud Eye console or by calling the Cloud Eye APIs.
                                                        1. Security: The AK/SK used by the Agent is only the temporary AK/SK that has the CES AgentAccess permissions. That is, the temporary AK/SK can only be used to operate Cloud Eye resources.
                                                        2. Convenient: You only need to configure the Cloud Eye Agent once in each region instead of manually configuring each Agent.
                                                        +
                                                        +
                                                      +
                                                      +
                                                      +
                                                      +
                                                      Parent topic: Server Monitoring
                                                      +
                                                      +
                                                      + diff --git a/docs/ces/umn/ces_faq_2513.html b/docs/ces/umn/ces_faq_2513.html new file mode 100644 index 000000000..639e2e4f1 --- /dev/null +++ b/docs/ces/umn/ces_faq_2513.html @@ -0,0 +1,1258 @@ + + +

                                                      What Metrics Are Supported by the Agent?

                                                      +

                                                      The Monitoring Period (Raw Data) of the agent metrics is 1 minute.

                                                      +
                                                      +

                                                      OS metric: CPU

                                                      +
                                                      + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

                                                      Metric

                                                      +

                                                      Name

                                                      +

                                                      Description

                                                      +

                                                      Value Range

                                                      +

                                                      Unit

                                                      +

                                                      Earliest Agent Version Required

                                                      +

                                                      cpu_usage

                                                      +

                                                      (Agent) CPU Usage

                                                      +

                                                      Used to monitor CPU usage

                                                      +
                                                      • Collection method (Linux): Check the metric value changes in file /proc/stat in a collection period. You can run the top command to check the %Cpu(s) value.
                                                      • Collection method (Windows): Obtain the metric value using the API GetSystemTimes.
                                                      +

                                                      0-100

                                                      +

                                                      %

                                                      +

                                                      2.4.1

                                                      +

                                                      cpu_usage_idle

                                                      +

                                                      (Agent) Idle CPU Usage

                                                      +

                                                      Percentage of the time that CPU is idle

                                                      +

                                                      Unit: Percent

                                                      +
                                                      • Collection method (Linux): Check the metric value changes in file /proc/stat in a collection period.
                                                      • Collection method (Windows): Obtain the metric value using the API GetSystemTimes.
                                                      +

                                                      0-100

                                                      +

                                                      %

                                                      +

                                                      2.4.5

                                                      +

                                                      cpu_usage_other

                                                      +

                                                      (Agent) Other Process CPU Usage

                                                      +

                                                      Other CPU usage of the monitored object

                                                      +
                                                      • Collection method (Linux): Other Process CPU Usage = 1– Idle CPU Usage – Kernel Space CPU Usage – User Space CPU Usage
                                                      • Collection method (Windows): Other Process CPU Usage = 1– Idle CPU Usage – Kernel Space CPU Usage – User Space CPU Usage
                                                      +

                                                      0-100

                                                      +

                                                      %

                                                      +

                                                      2.4.5

                                                      +

                                                      cpu_usage_system

                                                      +

                                                      (Agent) Kernel Space CPU Usage

                                                      +

                                                      Percentage of time that the CPU is used by kernel space

                                                      +
                                                      • Collection method (Linux): Check the metric value changes in file /proc/stat in a collection period. You can run the top command to check the %Cpu(s) sy value.
                                                      • Collection method (Windows): Obtain the metric value using the API GetSystemTimes.
                                                      +

                                                      0-100

                                                      +

                                                      %

                                                      +

                                                      2.4.5

                                                      +

                                                      cpu_usage_user

                                                      +

                                                      (Agent) User Space CPU Usage

                                                      +

                                                      Percentage of time that the CPU is used by user space

                                                      +
                                                      • Collection method (Linux): Check the metric value changes in file /proc/stat in a collection period. You can run the top command to check the %Cpu(s) us value.
                                                      • Collection method (Windows): Obtain the metric value using the API GetSystemTimes.
                                                      +

                                                      0-100

                                                      +

                                                      %

                                                      +

                                                      2.4.5

                                                      +

                                                      cpu_usage_nice

                                                      +

                                                      (Agent) Nice Process CPU Usage

                                                      +

                                                      Percentage of the time that the CPU is in user mode with low-priority processes which can easily be interrupted by higher-priority processes

                                                      +
                                                      • Collection method (Linux): Check the metric value changes in file /proc/stat in a collection period. You can run the top command to check the %Cpu(s) ni value.
                                                      • Collection method (Windows): not supported
                                                      +

                                                      0-100

                                                      +

                                                      %

                                                      +

                                                      2.4.5

                                                      +

                                                      cpu_usage_iowait

                                                      +

                                                      (Agent) iowait Process CPU Usage

                                                      +

                                                      Percentage of time that the CPU is waiting for I/O operations to complete

                                                      +
                                                      • Collection method (Linux): Check the metric value changes in file /proc/stat in a collection period. You can run the top command to check the %Cpu(s) wa value.
                                                      • Collection method (Windows): not supported
                                                      +

                                                      0-100

                                                      +

                                                      %

                                                      +

                                                      2.4.5

                                                      +

                                                      cpu_usage_irq

                                                      +

                                                      (Agent) CPU Interrupt Time

                                                      +

                                                      Percentage of time that the CPU is servicing interrupts

                                                      +
                                                      • Collection method (Linux): Check the metric value changes in file /proc/stat in a collection period. You can run the top command to check the %Cpu(s) hi value.
                                                      • Collection method (Windows): not supported
                                                      +

                                                      0-100

                                                      +

                                                      %

                                                      +

                                                      2.4.5

                                                      +

                                                      cpu_usage_softirq

                                                      +

                                                      (Agent) CPU Software Interrupt Time

                                                      +

                                                      Percentage of time that the CPU is servicing software interrupts

                                                      +
                                                      • Collection method (Linux): Check the metric value changes in file /proc/stat in a collection period. You can run the top command to check the %Cpu(s) si value.
                                                      • Collection method (Windows): not supported
                                                      +

                                                      0-100

                                                      +

                                                      %

                                                      +

                                                      2.4.5

                                                      +
                                                      +
                                                      +
                                                      +

                                                      OS Metric: CPU Load

                                                      +
                                                      + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

                                                      Metric

                                                      +

                                                      Name

                                                      +

                                                      Description

                                                      +

                                                      Value Range

                                                      +

                                                      Unit

                                                      +

                                                      Earliest Agent Version Required

                                                      +

                                                      load_average1

                                                      +

                                                      (Agent) 1-Minute Load Average

                                                      +

                                                      CPU load averaged from the last 1 minute

                                                      +
                                                      • Collection method (Linux): The value of this metric is the result of the value of load1 in /proc/loadavg divided by the number of logical CPUs. You can run the top command to check the value of load1.
                                                      • Collection method (Windows): not supported
                                                      +

                                                      ≥ 0

                                                      +

                                                      None

                                                      +

                                                      2.4.1

                                                      +

                                                      load_average5

                                                      +

                                                      (Agent) 5-Minute Load Average

                                                      +

                                                      CPU load averaged from the last 5 minutes

                                                      +
                                                      • Collection method (Linux): The value of this metric is the result of the value of load5 in /proc/loadavg divided by the number of logical CPUs. You can run the top command to check the value of load5.
                                                      • Collection method (Windows): not supported
                                                      +

                                                      ≥ 0

                                                      +

                                                      None

                                                      +

                                                      2.4.1

                                                      +

                                                      load_average15

                                                      +

                                                      (Agent) 15-Minute Load Average

                                                      +

                                                      CPU load averaged from the last 15 minutes

                                                      +
                                                      • Collection method (Linux): The value of this metric is the result of the value of load15 in /proc/loadavg divided by the number of logical CPUs. You can run the top command to check the value of load15.
                                                      • Collection method (Windows): not supported
                                                      +

                                                      ≥ 0

                                                      +

                                                      None

                                                      +

                                                      2.4.1

                                                      +
                                                      +
                                                      +
                                                      +

                                                      OS Metric: Memory

                                                      +
                                                      + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

                                                      Metric

                                                      +

                                                      Name

                                                      +

                                                      Description

                                                      +

                                                      Value Range

                                                      +

                                                      Unit

                                                      +

                                                      Earliest Agent Version Required

                                                      +

                                                      mem_available

                                                      +

                                                      (Agent) Available Memory

                                                      +

                                                      Amount of memory that is available and can be given instantly to processes

                                                      +
                                                      • Collection method (Linux): Obtain the metric value from /proc/meminfo.

                                                        If MemAvailable is displayed in /proc/meminfo, obtain the value.

                                                        +

                                                        If MemAvailable is not displayed in /proc/meminfo, MemAvailable = MemFree + Buffers+Cached

                                                        +
                                                      • Collection method (Windows): formula (Available memory – Used memory) The value is obtained by calling the Windows API GlobalMemoryStatusEx.
                                                      +

                                                      ≥ 0

                                                      +

                                                      GB

                                                      +

                                                      2.4.5

                                                      +

                                                      mem_usedPercent

                                                      +

                                                      (Agent) Memory Usage

                                                      +

                                                      Memory usage of the instance

                                                      +
                                                      • Collection method (Linux): Obtain the metric value from the /proc/meminfo file (MemTotal-MemAvailable)/MemTotal.

                                                        If MemAvailable is displayed in /proc/meminfo, MemUsedPercent = (MemTotal-MemAvailable)/MemTotal

                                                        +

                                                        If MemAvailable is not displayed in /proc/meminfo, MemUsedPercent = (MemTotal – MemFree – Buffers – Cached)/MemTotal

                                                        +
                                                      • Collection method (Windows): formula (Used memory size/Total memory size x 100%)
                                                      +

                                                      0-100

                                                      +

                                                      %

                                                      +

                                                      2.4.1

                                                      +

                                                      mem_free

                                                      +

                                                      (Agent) Idle Memory

                                                      +

                                                      Amount of memory that is not being used

                                                      +
                                                      • Collection method (Linux): Obtain the metric value from /proc/meminfo.
                                                      • Collection method (Windows): not supported
                                                      +

                                                      ≥ 0

                                                      +

                                                      GB

                                                      +

                                                      2.4.5

                                                      +

                                                      mem_buffers

                                                      +

                                                      (Agent) Buffer

                                                      +

                                                      Amount of memory that is being used for buffers

                                                      +
                                                      • Collection method (Linux): Obtain the metric value from /proc/meminfo. You can run the top command to check the KiB Mem:buffers value.
                                                      • Collection method (Windows): not supported
                                                      +

                                                      ≥ 0

                                                      +

                                                      GB

                                                      +

                                                      2.4.5

                                                      +

                                                      mem_cached

                                                      +

                                                      (Agent) Cache

                                                      +

                                                      Amount of memory that is being used for file caches

                                                      +
                                                      • Collection method (Linux): Obtain the metric value from /proc/meminfo. You can run the top command to check the KiB Swap:cached Mem value.
                                                      • Collection method (Windows): not supported
                                                      +

                                                      ≥ 0

                                                      +

                                                      GB

                                                      +

                                                      2.4.5

                                                      +

                                                      total_open_files

                                                      +

                                                      (Agent) Total File Handles

                                                      +

                                                      Total handles used by all processes

                                                      +
                                                      • Collection method (Linux): Use the /proc/{pid}/fd file to summarize the handles used by all processes.
                                                      • Collection method (Windows): not supported
                                                      +

                                                      ≥ 0

                                                      +

                                                      Count

                                                      +

                                                      2.4.5

                                                      +
                                                      +
                                                      +
                                                      +

                                                      OS Metric: Disk

                                                      Currently, CES Agent can collect only physical disk metrics and does not support disks mounted using the network file system protocol.

                                                      +

                                                      By default, CES Agent will not monitor Docker-related mount points. The prefix of the mount point is as follows:

                                                      +
                                                      /var/lib/docker;/mnt/paas/kubernetes;/var/lib/mesos
                                                      +
                                                      + +
                                                      + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

                                                      Metric

                                                      +

                                                      Name

                                                      +

                                                      Description

                                                      +

                                                      Value Range

                                                      +

                                                      Unit

                                                      +

                                                      Earliest Agent Version Required

                                                      +

                                                      disk_free

                                                      +

                                                      (Agent) Available Disk Space

                                                      +

                                                      Free space on the disks

                                                      +
                                                      • Collection method (Linux): Run the df -h command to check the value in the Avail column. The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), periods (.), and swung dashes (~).
                                                      • Collection method (Windows): Use the Windows Management Instrumentation (WMI) API GetDiskFreeSpaceExW to obtain disk space data. The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), periods (.), and swung dashes (~).
                                                      +

                                                      ≥ 0

                                                      +

                                                      GB

                                                      +

                                                      2.4.1

                                                      +

                                                      disk_total

                                                      +

                                                      (Agent) Disk Storage Capacity

                                                      +

                                                      Total disk capacity

                                                      +
                                                      • Collection method (Linux): Run the df -h command to check the value in the Size column.

                                                        The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), periods (.), and swung dashes (~).

                                                        +
                                                      • Collection method (Windows): Use the WMI API GetDiskFreeSpaceExW to obtain disk space data. The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), periods (.), and swung dashes (~).
                                                      +

                                                      ≥ 0

                                                      +

                                                      GB

                                                      +

                                                      2.4.5

                                                      +

                                                      disk_used

                                                      +

                                                      (Agent) Used Disk Space

                                                      +

                                                      Disk's used space

                                                      +
                                                      • Collection method (Linux): Run the df -h command to check the value in the Used column. The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), periods (.), and swung dashes (~).
                                                      • Collection method (Windows): Use the WMI API GetDiskFreeSpaceExW to obtain disk space data. The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), periods (.), and swung dashes (~).
                                                      +

                                                      ≥ 0

                                                      +

                                                      GB

                                                      +

                                                      2.4.5

                                                      +

                                                      disk_usedPercent

                                                      +

                                                      (Agent) Disk Usage

                                                      +

                                                      Percentage of used disk space. It is calculated as follows: Disk Usage = Used Disk Space/Disk Storage Capacity.

                                                      +
                                                      • Collection method (Linux): It is calculated as follows: Used/Size. The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), periods (.), and swung dashes (~).
                                                      • Collection method (Windows): Use the WMI API GetDiskFreeSpaceExW to obtain disk space data. The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), periods (.), and swung dashes (~).
                                                      +

                                                      0-100

                                                      +

                                                      %

                                                      +

                                                      2.4.1

                                                      +

                                                      disk_rwstate

                                                      +

                                                      (Agent) Disk Read/Write Status

                                                      +

                                                      Read and write status of the disk attached to the monitored object. The status can be 0 (read and write) or 1 (read-only).

                                                      +
                                                      • Collection method (Linux): Obtain the disk attachment status from the /proc/1/mountinfo file.
                                                      • Collection method (Windows): not supported
                                                      +
                                                      • 0: read and write
                                                      • 1: read-only
                                                      +

                                                      None

                                                      +

                                                      2.5.6

                                                      +
                                                      +
                                                      +
                                                      +

                                                      OS Metric: Disk I/O

                                                      +
                                                      + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

                                                      Metric

                                                      +

                                                      Name

                                                      +

                                                      Description

                                                      +

                                                      Value Range

                                                      +

                                                      Unit

                                                      +

                                                      Earliest Agent Version Required

                                                      +

                                                      disk_agt_read_bytes_rate

                                                      +

                                                      (Agent) Disks Read Rate

                                                      +

                                                      Volume of data read from the instance per second

                                                      +
                                                      • Collection method (Linux):

                                                        Calculate the data changes in the sixth column of the corresponding device in file /proc/diskstats in a collection period.

                                                        +

                                                        The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), periods (.), and swung dashes (~).

                                                        +
                                                      • Collection method (Windows):

                                                        Use Win32_PerfFormattedData_PerfDisk_LogicalDisk object in WMI to obtain disk I/O data.

                                                        +

                                                        The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), periods (.), and swung dashes (~).

                                                        +

                                                        When the CPU usage is high, monitoring data obtaining timeout may occur and monitoring data cannot be obtained.

                                                        +
                                                      +

                                                      ≥ 0

                                                      +

                                                      byte/s

                                                      +

                                                      2.4.5

                                                      +

                                                      disk_agt_read_requests_rate

                                                      +

                                                      (Agent) Disks Read Requests

                                                      +

                                                      Number of read requests sent to the monitored disk per second

                                                      +
                                                      • Collection method (Linux):

                                                        The disk read requests are calculated by calculating the data changes in the fourth column of the corresponding device in file /proc/diskstats in a collection period.

                                                        +

                                                        The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), periods (.), and swung dashes (~).

                                                        +
                                                      • Collection method (Windows):

                                                        Use Win32_PerfFormattedData_PerfDisk_LogicalDisk object in WMI to obtain disk I/O data.

                                                        +

                                                        The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), periods (.), and swung dashes (~).

                                                        +

                                                        When the CPU usage is high, monitoring data obtaining timeout may occur and monitoring data cannot be obtained.

                                                        +
                                                      +

                                                      ≥ 0

                                                      +

                                                      Request/s

                                                      +

                                                      2.4.5

                                                      +

                                                      disk_agt_write_bytes_rate

                                                      +

                                                      (Agent) Disks Write Rate

                                                      +

                                                      Volume of data written to the instance per second

                                                      +
                                                      • Collection method (Linux):

                                                        The disk write rate is calculated by calculating the data changes in the tenth column of the corresponding device in file /proc/diskstats in a collection period.

                                                        +

                                                        The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), periods (.), and swung dashes (~).

                                                        +
                                                      • Collection method (Windows):

                                                        Use Win32_PerfFormattedData_PerfDisk_LogicalDisk object in WMI to obtain disk I/O data.

                                                        +

                                                        The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), periods (.), and swung dashes (~).

                                                        +

                                                        When the CPU usage is high, monitoring data obtaining timeout may occur and monitoring data cannot be obtained.

                                                        +
                                                      +

                                                      ≥ 0

                                                      +

                                                      byte/s

                                                      +

                                                      2.4.5

                                                      +

                                                      disk_agt_write_requests_rate

                                                      +

                                                      (Agent) Disks Write Requests

                                                      +

                                                      Number of write requests sent to the monitored disk per second

                                                      +
                                                      • Collection method (Linux):

                                                        The disk write requests are calculated by calculating the data changes in the eighth column of the corresponding device in file /proc/diskstats in a collection period.

                                                        +

                                                        The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), periods (.), and swung dashes (~).

                                                        +
                                                      • Collection method (Windows):

                                                        Use Win32_PerfFormattedData_PerfDisk_LogicalDisk object in WMI to obtain disk I/O data.

                                                        +

                                                        The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), periods (.), and swung dashes (~).

                                                        +

                                                        When the CPU usage is high, monitoring data obtaining timeout may occur and monitoring data cannot be obtained.

                                                        +
                                                      +

                                                      ≥ 0

                                                      +

                                                      Request/s

                                                      +

                                                      2.4.5

                                                      +

                                                      disk_readTime

                                                      +

                                                      (Agent) Average Read Request Time

                                                      +

                                                      The average time taken for disk read operations

                                                      +
                                                      • Collection method (Linux):

                                                        The average read request time is calculated by calculating the data changes in the seventh column of the corresponding device in file /proc/diskstats in a collection period.

                                                        +

                                                        The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), periods (.), and swung dashes (~).

                                                        +
                                                      • Collection method (Windows): not supported
                                                      +

                                                      ≥ 0

                                                      +

                                                      ms/count

                                                      +

                                                      2.4.5

                                                      +

                                                      disk_writeTime

                                                      +

                                                      (Agent) Average Write Request Time

                                                      +

                                                      The average time taken for disk write operations

                                                      +
                                                      • Collection method (Linux):

                                                        The average write request time is calculated by calculating the data changes in the eleventh column of the corresponding device in file /proc/diskstats in a collection period.

                                                        +

                                                        The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), periods (.), and swung dashes (~).

                                                        +
                                                      • Collection method (Windows): not supported
                                                      +

                                                      ≥ 0

                                                      +

                                                      ms/count

                                                      +

                                                      2.4.5

                                                      +

                                                      disk_ioUtils

                                                      +

                                                      (Agent) Disk I/O Usage

                                                      +

                                                      Percentage of the time that the disk has had I/O requests queued to the total disk operation time

                                                      +
                                                      • Collection method (Linux):

                                                        The disk I/O usage is calculated by calculating the data changes in the thirteenth column of the corresponding device in file /proc/diskstats in a collection period.

                                                        +

                                                        The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), periods (.), and swung dashes (~).

                                                        +
                                                      • Collection method (Windows): not supported
                                                      +

                                                      0-100

                                                      +

                                                      %

                                                      +

                                                      2.4.1

                                                      +

                                                      disk_queue_length

                                                      +

                                                      (Agent) Disk Queue Length

                                                      +

                                                      Average number of read or write requests queued up for completion for the monitored disk in the monitoring period

                                                      +
                                                      • Collection method (Linux):

                                                        The average disk queue length is calculated by calculating the data changes in the fourteenth column of the corresponding device in file /proc/diskstats in a collection period.

                                                        +

                                                        The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), periods (.), and swung dashes (~).

                                                        +
                                                      • Collection method (Windows): not supported
                                                      +

                                                      ≥ 0

                                                      +

                                                      count

                                                      +

                                                      2.4.5

                                                      +

                                                      disk_write_bytes_per_operation

                                                      +

                                                      Disk Bytes Per Write Operation

                                                      +

                                                      Average number of bytes in an I/O write for the monitored disk in the monitoring period

                                                      +
                                                      • Collection method (Linux):

                                                        The average disk write size is calculated by calculating the data changes in the tenth column of the corresponding device to divide that of the eighth column in file /proc/diskstats in a collection period.

                                                        +

                                                        The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), periods (.), and swung dashes (~).

                                                        +
                                                      • Collection method (Windows): not supported
                                                      +

                                                      ≥ 0

                                                      +

                                                      Byte/op

                                                      +

                                                      2.4.5

                                                      +

                                                      disk_read_bytes_per_operation

                                                      +

                                                      Disk Bytes Per Read Operation

                                                      +

                                                      Average number of bytes in an I/O read for the monitored disk in the monitoring period

                                                      +
                                                      • Collection method (Linux):

                                                        The average disk read size is calculated by using the data changes in the sixth column of the corresponding device to divide that of the fourth column in file /proc/diskstats in a collection period.

                                                        +

                                                        The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), periods (.), and swung dashes (~).

                                                        +
                                                      • Collection method (Windows): not supported
                                                      +

                                                      ≥ 0

                                                      +

                                                      Byte/op

                                                      +

                                                      2.4.5

                                                      +

                                                      disk_io_svctm

                                                      +

                                                      (Agent) Disk I/O Service Time

                                                      +

                                                      Average time in an I/O read or write for the monitored disk in the monitoring period

                                                      +
                                                      • Collection method (Linux):

                                                        The average disk I/O service time is calculated by using the data changes in the thirteenth column of the corresponding device to divide the sum of data changes in the fourth and eighth columns in file /proc/diskstats in a collection period.

                                                        +

                                                        The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), periods (.), and swung dashes (~).

                                                        +
                                                      • Collection method (Windows): not supported
                                                      +

                                                      ≥ 0

                                                      +

                                                      ms/op

                                                      +

                                                      2.4.5

                                                      +

                                                      disk_device_used_percent

                                                      +

                                                      +

                                                      Block Device Usage

                                                      +

                                                      Percentage of total disk space that is used. The calculation formula is as follows: Used storage space of all mounted disk partitions/Total disk storage space.

                                                      + +

                                                      0-100

                                                      +

                                                      %

                                                      +

                                                      2.5.6

                                                      +
                                                      +
                                                      +
                                                      +

                                                      OS Metric: File System

                                                      +
                                                      + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

                                                      Metric

                                                      +

                                                      Name

                                                      +

                                                      Description

                                                      +

                                                      Value Range

                                                      +

                                                      Unit

                                                      +

                                                      Earliest Agent Version Required

                                                      +

                                                      disk_fs_rwstate

                                                      +

                                                      (Agent) File System Read/Write Status

                                                      +

                                                      Read and write status of the mounted file system of the monitored object The status can be 0 (read and write) or 1 (read-only).

                                                      +
                                                      • Collection method (Linux): Check file system information in the fourth column in file /proc/mounts.
                                                      • Collection method (Windows): not supported
                                                      +
                                                      • 0: read and write
                                                      • 1: read-only
                                                      +

                                                      None

                                                      +

                                                      2.4.5

                                                      +

                                                      disk_inodesTotal

                                                      +

                                                      (Agent) Disk inode Total

                                                      +

                                                      Total number of index nodes on the disk

                                                      +
                                                      • Collection method (Linux): Run the df -i command to check the value in the Inodes column. The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), periods (.), and swung dashes (~).
                                                      • Collection method (Windows): not supported
                                                      +

                                                      ≥ 0

                                                      +

                                                      None

                                                      +

                                                      2.4.5

                                                      +

                                                      disk_inodesUsed

                                                      +

                                                      (Agent) Total inode Used

                                                      +

                                                      Number of used index nodes on the disk

                                                      +
                                                      • Collection method (Linux): Run the df -i command to check the value in the IUsed column. The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), periods (.), and swung dashes (~).
                                                      • Collection method (Windows): not supported
                                                      +

                                                      ≥ 0

                                                      +

                                                      None

                                                      +

                                                      2.4.5

                                                      +

                                                      disk_inodesUsedPercent

                                                      +

                                                      (Agent) Percentage of Total inode Used

                                                      +

                                                      Number of used index nodes on the disk

                                                      +
                                                      • Collection method (Linux): Run the df -i command to check the value in the IUse% column. The path of the mount point prefix cannot exceed 64 characters. It must start with a letter, and contain only digits, letters, hyphens (-), periods (.), and swung dashes (~).
                                                      • Collection method (Windows): not supported
                                                      +

                                                      0-100

                                                      +

                                                      %

                                                      +

                                                      2.4.1

                                                      +
                                                      +
                                                      +
                                                      +

                                                      OS Metric: NTP

                                                      +
                                                      + + + + + + + + + + + + + + + + + +

                                                      Metric

                                                      +

                                                      Name

                                                      +

                                                      Description

                                                      +

                                                      Value Range

                                                      +

                                                      Unit

                                                      +

                                                      Conversion Rule

                                                      +

                                                      Earliest Agent Version Required

                                                      +

                                                      ntp_offset

                                                      +

                                                      (Agent) NTP Offset

                                                      +

                                                      NTP offset of the monitored object

                                                      +
                                                      • Collection method (Linux): Run the ntpq -p or chronyc sources -v command.
                                                      • Collection method (Windows): not supported
                                                      +

                                                      ≥ 0

                                                      +

                                                      ms

                                                      +

                                                      N/A

                                                      +

                                                      2.7.1

                                                      +
                                                      +
                                                      +
                                                      +

                                                      OS Metric: TCP Connections

                                                      By default, two basic metrics related to TCP connections are collected: (Agent) TCP TOTAL and (Agent) TCP ESTABLISHED.

                                                      + +
                                                      + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

                                                      Metric

                                                      +

                                                      Name

                                                      +

                                                      Description

                                                      +

                                                      Value Range

                                                      +

                                                      Unit

                                                      +

                                                      Earliest Agent Version Required

                                                      +

                                                      net_tcp_total

                                                      +

                                                      (Agent) Total Number of TCP Connections

                                                      +

                                                      Total number of TCP connections

                                                      +
                                                      • Collection method (Linux): Run the ss -s command to view the total number of TCP connections.
                                                        NOTE:

                                                        The number of TCP connections refers to the number of all active TCP connections on an ECS.

                                                        +
                                                        +
                                                      • Collection method (Windows): Obtain the metric value using the GetTcpTable2 API.
                                                      +

                                                      ≥ 0

                                                      +

                                                      count

                                                      +

                                                      2.4.1

                                                      +

                                                      net_tcp_established

                                                      +

                                                      (Agent) Number of connections in the ESTABLISHED state

                                                      +

                                                      Number of TCP connections in the ESTABLISHED state

                                                      +
                                                      • Collection method (Linux): Obtain TCP connections in all states from the /proc/net/tcp file, and then collect the number of connections in each state.
                                                      • Collection method (Windows): Obtain the metric value using the GetTcpTable2 API.
                                                      +

                                                      ≥ 0

                                                      +

                                                      count

                                                      +

                                                      2.4.1

                                                      +

                                                      net_tcp_sys_sent

                                                      +

                                                      (Agent) Number of connections in the TCP SYS_SENT state.

                                                      +

                                                      Number of TCP connections that are being requested by the client

                                                      +
                                                      • Collection method (Linux): Obtain TCP connections in all states from the /proc/net/tcp file, and then collect the number of connections in each state.
                                                      • Collection method (Windows): Obtain the metric value using the GetTcpTable2 API.
                                                      +

                                                      ≥ 0

                                                      +

                                                      count

                                                      +

                                                      2.4.5

                                                      +

                                                      net_tcp_sys_recv

                                                      +

                                                      (Agent) Number of connections in the TCP SYS_RECV state.

                                                      +

                                                      Number of pending TCP connections received by the server

                                                      +
                                                      • Collection method (Linux): Obtain TCP connections in all states from the /proc/net/tcp file, and then collect the number of connections in each state.
                                                      • Collection method (Windows): Obtain the metric value using the GetTcpTable2 API.
                                                      +

                                                      ≥ 0

                                                      +

                                                      count

                                                      +

                                                      2.4.5

                                                      +

                                                      net_tcp_fin_wait1

                                                      +

                                                      (Agent) Number of TCP connections in the FIN_WAIT1 state.

                                                      +

                                                      Number of TCP connections waiting for ACK packets when the connections are being actively closed by the client

                                                      +
                                                      • Collection method (Linux): Obtain TCP connections in all states from the /proc/net/tcp file, and then collect the number of connections in each state.
                                                      • Collection method (Windows): Obtain the metric value using the GetTcpTable2 API.
                                                      +

                                                      ≥ 0

                                                      +

                                                      count

                                                      +

                                                      2.4.5

                                                      +

                                                      net_tcp_fin_wait2

                                                      +

                                                      (Agent) Number of TCP connections in the FIN_WAIT2 state.

                                                      +

                                                      Number of TCP connections in the FIN_WAIT2 state

                                                      +
                                                      • Collection method (Linux): Obtain TCP connections in all states from the /proc/net/tcp file, and then collect the number of connections in each state.
                                                      • Collection method (Windows): Obtain the metric value using the GetTcpTable2 API.
                                                      +

                                                      ≥ 0

                                                      +

                                                      count

                                                      +

                                                      2.4.5

                                                      +

                                                      net_tcp_time_wait

                                                      +

                                                      (Agent) TCP TIME_WAIT Connections

                                                      +

                                                      Number of TCP connections in the TIME_WAIT state

                                                      + +

                                                      ≥ 0

                                                      +

                                                      count

                                                      +

                                                      2.4.5

                                                      +

                                                      net_tcp_close

                                                      +

                                                      (Agent) Number of TCP connections in the CLOSE state.

                                                      +

                                                      Number of closed TCP connections

                                                      +
                                                      • Collection method (Linux): Obtain TCP connections in all states from the /proc/net/tcp file, and then collect the number of connections in each state.
                                                      • Collection method (Windows): Obtain the metric value using the GetTcpTable2 API.
                                                      +

                                                      ≥ 0

                                                      +

                                                      count

                                                      +

                                                      2.4.5

                                                      +

                                                      net_tcp_close_wait

                                                      +

                                                      (Agent) TCP CLOSE_WAIT Connections

                                                      +

                                                      Number of TCP connections in the CLOSE_WAIT state

                                                      + +

                                                      ≥ 0

                                                      +

                                                      count

                                                      +

                                                      2.4.5

                                                      +

                                                      net_tcp_last_ack

                                                      +

                                                      (Agent) Number of TCP connections in the LAST_ACK state.

                                                      +

                                                      Number of TCP connections waiting for ACK packets when the connections are being passively closed by the client

                                                      +
                                                      • Collection method (Linux): Obtain TCP connections in all states from the /proc/net/tcp file, and then collect the number of connections in each state.
                                                      • Collection method (Windows): Obtain the metric value using the GetTcpTable2 API.
                                                      +

                                                      ≥ 0

                                                      +

                                                      count

                                                      +

                                                      2.4.5

                                                      +

                                                      net_tcp_listen

                                                      +

                                                      (Agent) Number of TCP connections in the LISTEN state.

                                                      +

                                                      Number of TCP connections in the LISTEN state

                                                      +
                                                      • Collection method (Linux): Obtain TCP connections in all states from the /proc/net/tcp file, and then collect the number of connections in each state.
                                                      • Collection method (Windows): Obtain the metric value using the GetTcpTable2 API.
                                                      +

                                                      ≥ 0

                                                      +

                                                      count

                                                      +

                                                      2.4.5

                                                      +

                                                      net_tcp_closing

                                                      +

                                                      (Agent) Number of TCP connections in the CLOSING state.

                                                      +

                                                      Number of TCP connections to be automatically closed by the server and the client at the same time

                                                      +
                                                      • Collection method (Linux): Obtain TCP connections in all states from the /proc/net/tcp file, and then collect the number of connections in each state.
                                                      • Collection method (Windows): Obtain the metric value using the GetTcpTable2 API.
                                                      +

                                                      ≥ 0

                                                      +

                                                      count

                                                      +

                                                      2.4.5

                                                      +

                                                      net_tcp_retrans

                                                      +

                                                      (Agent) TCP Retransmission Rate

                                                      +

                                                      Percentage of packets that are resent

                                                      +
                                                      • Collection method (Linux): Obtain the metric value from the /proc/net/snmp file. The value is the ratio of the number of sent packets to the number of retransmitted packages in a collection period.
                                                      • Collection method (Windows): Obtain the metric value using the GetTcpStatistics API.
                                                      +

                                                      0-100

                                                      +

                                                      %

                                                      +

                                                      2.4.5

                                                      +
                                                      +
                                                      +
                                                      +

                                                      OS Metric: NIC

                                                      +
                                                      + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

                                                      Metric

                                                      +

                                                      Name

                                                      +

                                                      Description

                                                      +

                                                      Value Range

                                                      +

                                                      Unit

                                                      +

                                                      Earliest Agent Version Required

                                                      +

                                                      net_bitRecv

                                                      +

                                                      (Agent) Outbound Bandwidth

                                                      +

                                                      Number of bits sent by this NIC per second

                                                      +
                                                      • Collection method (Linux): Check metric value changes in file /proc/net/dev in a collection period.
                                                      • Collection method (Windows): Use the MibIfRow object in WMI to obtain network metric data.
                                                      +

                                                      ≥ 0

                                                      +

                                                      bit/s

                                                      +

                                                      2.4.1

                                                      +

                                                      net_bitSent

                                                      +

                                                      (Agent) Inbound Bandwidth

                                                      +

                                                      Number of bits received by this NIC per second

                                                      +
                                                      • Collection method (Linux): Check metric value changes in file /proc/net/dev in a collection period.
                                                      • Collection method (Windows): Use the MibIfRow object in WMI to obtain network metric data.
                                                      +

                                                      ≥ 0

                                                      +

                                                      bit/s

                                                      +

                                                      2.4.1

                                                      +

                                                      net_packetRecv

                                                      +

                                                      (Agent) NIC Packet Receive Rate

                                                      +

                                                      Number of packets received by this NIC per second

                                                      +
                                                      • Collection method (Linux): Check metric value changes in file /proc/net/dev in a collection period.
                                                      • Collection method (Windows): Use the MibIfRow object in WMI to obtain network metric data.
                                                      +

                                                      ≥ 0

                                                      +

                                                      Count/s

                                                      +

                                                      2.4.1

                                                      +

                                                      net_packetSent

                                                      +

                                                      (Agent) NIC Packet Send Rate

                                                      +

                                                      Number of packets sent by this NIC per second

                                                      +
                                                      • Collection method (Linux): Check metric value changes in file /proc/net/dev in a collection period.
                                                      • Collection method (Windows): Use the MibIfRow object in WMI to obtain network metric data.
                                                      +

                                                      ≥ 0

                                                      +

                                                      Count/s

                                                      +

                                                      2.4.1

                                                      +

                                                      net_errin

                                                      +

                                                      (Agent) Receive Error Rate

                                                      +

                                                      Percentage of receive errors detected by this NIC per second

                                                      +
                                                      • Collection method (Linux): Check metric value changes in file /proc/net/dev in a collection period.
                                                      • Collection method (Windows): not supported
                                                      +

                                                      0-100

                                                      +

                                                      %

                                                      +

                                                      2.4.5

                                                      +

                                                      net_errout

                                                      +

                                                      (Agent) Transmit Error Rate

                                                      +

                                                      Percentage of transmit errors detected by this NIC per second

                                                      +
                                                      • Collection method (Linux): Check metric value changes in file /proc/net/dev in a collection period.
                                                      • Collection method (Windows): not supported
                                                      +

                                                      0-100

                                                      +

                                                      %

                                                      +

                                                      2.4.5

                                                      +

                                                      net_dropin

                                                      +

                                                      (Agent) Received Packet Drop Rate

                                                      +

                                                      Percentage of packets received by this NIC which were dropped per second

                                                      +
                                                      • Collection method (Linux): Check metric value changes in file /proc/net/dev in a collection period.
                                                      • Collection method (Windows): not supported
                                                      +

                                                      0-100

                                                      +

                                                      %

                                                      +

                                                      2.4.5

                                                      +

                                                      net_dropout

                                                      +

                                                      (Agent) Transmitted Packet Drop Rate

                                                      +

                                                      Percentage of packets transmitted by this NIC which were dropped per second

                                                      +
                                                      • Collection method (Linux): Check metric value changes in file /proc/net/dev in a collection period.
                                                      • Collection method (Windows): not supported
                                                      +

                                                      0-100

                                                      +

                                                      %

                                                      +

                                                      2.4.5

                                                      +
                                                      +
                                                      +
                                                      +

                                                      Process Monitoring Metrics

                                                      +
                                                      + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

                                                      Metric

                                                      +

                                                      Name

                                                      +

                                                      Description

                                                      +

                                                      Value Range

                                                      +

                                                      Unit

                                                      +

                                                      Earliest Agent Version Required

                                                      +

                                                      proc_pHashId_cpu

                                                      +

                                                      (Agent) CPU Usage

                                                      +

                                                      CPU consumed by a process. pHashId (process name and process ID) is the value of md5.

                                                      +
                                                      • Collection method (Linux): Check the metric value changes in file /proc/pid/stat.
                                                      • Collection method (Windows): Call the Windows API GetProcessTimes to obtain the CPU usage of the process.
                                                      +

                                                      0–1 x Number of vCPUs

                                                      +

                                                      %

                                                      +

                                                      2.4.1

                                                      +

                                                      proc_pHashId_mem

                                                      +

                                                      (Agent) Memory Usage

                                                      +

                                                      Memory consumed by a process. pHashId (process name and process ID) is the value of md5.

                                                      +
                                                      • Collection method (Linux):

                                                        RSS*PAGESIZE/MemTotal

                                                        +

                                                        Obtain the RSS value by checking the second column of file /proc/pid/statm.

                                                        +

                                                        Obtain the PAGESIZE value by running the getconf PAGESIZE command.

                                                        +

                                                        Obtain the MemTotal value by checking file /proc/meminfo.

                                                        +
                                                      • Collection method (Windows): Call the Windows API procGlobalMemoryStatusEx to obtain the total memory size. Call GetProcessMemoryInfo to obtain the used memory size. Use the used memory size to divide the total memory size to get the memory usage.
                                                      +

                                                      0-100

                                                      +

                                                      %

                                                      +

                                                      2.4.1

                                                      +

                                                      proc_pHashId_file

                                                      +

                                                      (Agent) Number of opened files

                                                      +

                                                      Number of files opened by a process. pHashId (process name and process ID) is the value of md5.

                                                      +
                                                      • Collection method (Linux): Run the ls -l /proc/pid/fd command to view the number of opened files.
                                                      • Collection method (Windows): not supported
                                                      +

                                                      ≥ 0

                                                      +

                                                      Count

                                                      +

                                                      2.4.1

                                                      +

                                                      proc_running_count

                                                      +

                                                      (Agent) Running processes

                                                      +

                                                      Number of processes that are running

                                                      +
                                                      • Collection method (Linux): You can obtain the state of each process by checking the Status value in the /proc/pid/status file, and then collect the total number of processes in each state.
                                                      • Collection method (Windows): not supported
                                                      +

                                                      ≥ 0

                                                      +

                                                      None

                                                      +

                                                      2.4.1

                                                      +

                                                      proc_idle_count

                                                      +

                                                      (Agent) Idle Processes

                                                      +

                                                      Number of processes that are idle

                                                      +
                                                      • Collection method (Linux): You can obtain the state of each process by checking the Status value in the /proc/pid/status file, and then collect the total number of processes in each state.
                                                      • Collection method (Windows): not supported
                                                      +

                                                      ≥ 0

                                                      +

                                                      None

                                                      +

                                                      2.4.1

                                                      +

                                                      proc_zombie_count

                                                      +

                                                      (Agent) Zombie Processes

                                                      +

                                                      Number of zombie processes

                                                      +
                                                      • Collection method (Linux): You can obtain the state of each process by checking the Status value in the /proc/pid/status file, and then collect the total number of processes in each state.
                                                      • Collection method (Windows): not supported
                                                      +

                                                      ≥ 0

                                                      +

                                                      None

                                                      +

                                                      2.4.1

                                                      +

                                                      proc_blocked_count

                                                      +

                                                      (Agent) Blocked Processes

                                                      +

                                                      Number of processes that are blocked

                                                      +
                                                      • Collection method (Linux): You can obtain the state of each process by checking the Status value in the /proc/pid/status file, and then collect the total number of processes in each state.
                                                      • Collection method (Windows): not supported
                                                      +

                                                      ≥ 0

                                                      +

                                                      None

                                                      +

                                                      2.4.1

                                                      +

                                                      proc_sleeping_count

                                                      +

                                                      (Agent) Sleeping Processes

                                                      +

                                                      Number of processes that are sleeping

                                                      +
                                                      • Collection method (Linux): You can obtain the state of each process by checking the Status value in the /proc/pid/status file, and then collect the total number of processes in each state.
                                                      • Collection method (Windows): not supported
                                                      +

                                                      ≥ 0

                                                      +

                                                      None

                                                      +

                                                      2.4.1

                                                      +

                                                      proc_total_count

                                                      +

                                                      (Agent) Total Processes

                                                      +

                                                      Total number of processes on the monitored object

                                                      +
                                                      • Collection method (Linux): You can obtain the state of each process by checking the Status value in the /proc/pid/status file, and then collect the total number of processes in each state.
                                                      • Collection method (Windows): Obtain the total number of processes by using the system process status support module psapi.dll.
                                                      +

                                                      ≥ 0

                                                      +

                                                      None

                                                      +

                                                      2.4.1

                                                      +

                                                      proc_specified_count

                                                      +

                                                      (Agent) Specified Processes

                                                      +

                                                      Number of specified processes

                                                      +
                                                      • Collection method (Linux): You can obtain the state of each process by checking the Status value in the /proc/pid/status file, and then collect the total number of processes in each state.
                                                      • Collection method (Windows): Obtain the total number of processes by using the system process status support module psapi.dll.
                                                      +

                                                      ≥ 0

                                                      +

                                                      None

                                                      +

                                                      2.4.1

                                                      +
                                                      +
                                                      +
                                                      +
                                                      +
                                                      +
                                                      +
                                                      Parent topic: Server Monitoring
                                                      +
                                                      +
                                                      + diff --git a/docs/ces/umn/ces_faq_2514.html b/docs/ces/umn/ces_faq_2514.html new file mode 100644 index 000000000..f1294c9f3 --- /dev/null +++ b/docs/ces/umn/ces_faq_2514.html @@ -0,0 +1,25 @@ + + +

                                                      How Can I Fix the "SSH dial error" During Batch Agent Installation?

                                                      +

                                                      Symptom

                                                      When the Agent installation command provided by the Cloud Eye console is used to batch install the Agent, the error message "SSH dial error" was displayed. As a result, the Agent failed to be installed, as shown in Figure 1.
                                                      Figure 1 Batch Agent installation failed
                                                      +
                                                      +
                                                      +

                                                      Possible Causes

                                                      Login to the target server as user root or using a password is not allowed in its sshd settings.

                                                      +
                                                      +

                                                      Solution

                                                      • Check the sshd configuration file.
                                                        1. Log in to the server where Agent installation fails as user root.
                                                        2. Check whether both PermitRootLogin and PasswordAuthentication are set to yes in the sshd configuration file.
                                                          If they are not, modify their settings by referring to Modifying the sshd Configuration File.
                                                          cat /etc/ssh/sshd_config
                                                          +
                                                          +
                                                        +
                                                      • Modify the sshd configuration file.
                                                        1. Edit the sshd_config file.
                                                          vi /etc/ssh/sshd_config
                                                          +
                                                        2. Modify the configuration items.
                                                          PermitRootLogin yes
+PasswordAuthentication yes
                                                          +
                                                        3. Restart the sshd process.
                                                          systemctl restart sshd
                                                          +
                                                        +
                                                      +
                                                      +
                                                      +
                                                      +
                                                      +
                                                      Parent topic: Server Monitoring
                                                      +
                                                      +
                                                      + diff --git a/docs/ces/umn/en-us_image_0000001567952750.png b/docs/ces/umn/en-us_image_0000001567952750.png new file mode 100644 index 000000000..65fffcc0a Binary files /dev/null and b/docs/ces/umn/en-us_image_0000001567952750.png differ diff --git a/docs/ces/umn/en-us_image_0000001644915302.png b/docs/ces/umn/en-us_image_0000001644915302.png deleted file mode 100644 index 570730abe..000000000 Binary files a/docs/ces/umn/en-us_image_0000001644915302.png and /dev/null differ diff --git a/docs/ces/umn/en-us_image_0000001644929274.png b/docs/ces/umn/en-us_image_0000001644929274.png deleted file mode 100644 index b93e70e5f..000000000 Binary files a/docs/ces/umn/en-us_image_0000001644929274.png and /dev/null differ diff --git a/docs/ces/umn/en-us_image_0000001645095252.png b/docs/ces/umn/en-us_image_0000001645095252.png index 3eb709d7f..89df3fb21 100644 Binary files a/docs/ces/umn/en-us_image_0000001645095252.png and b/docs/ces/umn/en-us_image_0000001645095252.png differ diff --git a/docs/ces/umn/en-us_image_0000001645205332.png b/docs/ces/umn/en-us_image_0000001645205332.png deleted file mode 100644 index bf390079e..000000000 Binary files a/docs/ces/umn/en-us_image_0000001645205332.png and /dev/null differ diff --git a/docs/ces/umn/en-us_image_0000001645251798.png b/docs/ces/umn/en-us_image_0000001645251798.png index 33fa14304..9a98f26e2 100644 Binary files a/docs/ces/umn/en-us_image_0000001645251798.png and b/docs/ces/umn/en-us_image_0000001645251798.png differ diff --git a/docs/ces/umn/en-us_image_0000001645256436.png b/docs/ces/umn/en-us_image_0000001645256436.png index 2c54661cb..7578c3ce9 100644 Binary files a/docs/ces/umn/en-us_image_0000001645256436.png and b/docs/ces/umn/en-us_image_0000001645256436.png differ diff --git a/docs/ces/umn/en-us_image_0000001645582436.png b/docs/ces/umn/en-us_image_0000001645582436.png new file mode 100644 index 000000000..9237ec19a Binary files /dev/null and b/docs/ces/umn/en-us_image_0000001645582436.png differ diff --git a/docs/ces/umn/en-us_image_0000001692960961.png b/docs/ces/umn/en-us_image_0000001692960961.png deleted file mode 100644 index e45bb025e..000000000 Binary files a/docs/ces/umn/en-us_image_0000001692960961.png and /dev/null differ diff --git a/docs/ces/umn/en-us_image_0000001693096685.png b/docs/ces/umn/en-us_image_0000001693096685.png deleted file mode 100644 index ad8ac0eb9..000000000 Binary files a/docs/ces/umn/en-us_image_0000001693096685.png and /dev/null differ diff --git a/docs/ces/umn/en-us_image_0000001693305821.png b/docs/ces/umn/en-us_image_0000001693305821.png new file mode 100644 index 000000000..aba460087 Binary files /dev/null and b/docs/ces/umn/en-us_image_0000001693305821.png differ diff --git a/docs/ces/umn/en-us_image_0000001693521761.png b/docs/ces/umn/en-us_image_0000001693521761.png index b5413749b..29dc511a4 100644 Binary files a/docs/ces/umn/en-us_image_0000001693521761.png and b/docs/ces/umn/en-us_image_0000001693521761.png differ diff --git a/docs/ces/umn/en-us_image_0000001693741013.png b/docs/ces/umn/en-us_image_0000001693741013.png new file mode 100644 index 000000000..cca2b9711 Binary files /dev/null and b/docs/ces/umn/en-us_image_0000001693741013.png differ diff --git a/docs/ces/umn/en-us_image_0000001693747229.png b/docs/ces/umn/en-us_image_0000001693747229.png index 2709a6710..91b05cda8 100644 Binary files a/docs/ces/umn/en-us_image_0000001693747229.png and b/docs/ces/umn/en-us_image_0000001693747229.png differ diff --git a/docs/ces/umn/en-us_image_0000001693820629.png b/docs/ces/umn/en-us_image_0000001693820629.png new file mode 100644 index 000000000..567bb9498 Binary files /dev/null and b/docs/ces/umn/en-us_image_0000001693820629.png differ diff --git a/docs/ces/umn/en-us_image_0000001696202802.png b/docs/ces/umn/en-us_image_0000001696202802.png new file mode 100644 index 000000000..99252882f Binary files /dev/null and b/docs/ces/umn/en-us_image_0000001696202802.png differ diff --git a/docs/ces/umn/en-us_image_0000001696678850.png b/docs/ces/umn/en-us_image_0000001696678850.png deleted file mode 100644 index 6b11888bb..000000000 Binary files a/docs/ces/umn/en-us_image_0000001696678850.png and /dev/null differ diff --git a/docs/ces/umn/en-us_image_0000001696838310.png b/docs/ces/umn/en-us_image_0000001696838310.png deleted file mode 100644 index 582b16181..000000000 Binary files a/docs/ces/umn/en-us_image_0000001696838310.png and /dev/null differ diff --git a/docs/ces/umn/en-us_image_0000001744042857.png b/docs/ces/umn/en-us_image_0000001744042857.png new file mode 100644 index 000000000..b5d7b8e34 Binary files /dev/null and b/docs/ces/umn/en-us_image_0000001744042857.png differ diff --git a/docs/ces/umn/en-us_image_0000001744598325.png b/docs/ces/umn/en-us_image_0000001744598325.png deleted file mode 100644 index 3e15dbf97..000000000 Binary files a/docs/ces/umn/en-us_image_0000001744598325.png and /dev/null differ diff --git a/docs/ces/umn/en-us_image_0000001835186776.png b/docs/ces/umn/en-us_image_0000001835186776.png new file mode 100644 index 000000000..76eff84f7 Binary files /dev/null and b/docs/ces/umn/en-us_image_0000001835186776.png differ diff --git a/docs/ces/umn/en-us_image_0000001835931196.png b/docs/ces/umn/en-us_image_0000001835931196.png new file mode 100644 index 000000000..586ff42e0 Binary files /dev/null and b/docs/ces/umn/en-us_image_0000001835931196.png differ diff --git a/docs/ces/umn/en-us_image_0000001881907489.png b/docs/ces/umn/en-us_image_0000001881907489.png new file mode 100644 index 000000000..e13303f4a Binary files /dev/null and b/docs/ces/umn/en-us_image_0000001881907489.png differ diff --git a/docs/ces/umn/en-us_image_0000001881907649.png b/docs/ces/umn/en-us_image_0000001881907649.png new file mode 100644 index 000000000..d95b9e98d Binary files /dev/null and b/docs/ces/umn/en-us_image_0000001881907649.png differ diff --git a/docs/ces/umn/en-us_image_0000001881909965.png b/docs/ces/umn/en-us_image_0000001881909965.png new file mode 100644 index 000000000..9b830ed9a Binary files /dev/null and b/docs/ces/umn/en-us_image_0000001881909965.png differ diff --git a/docs/ces/umn/en-us_image_0000001882024953.png b/docs/ces/umn/en-us_image_0000001882024953.png new file mode 100644 index 000000000..865c1671e Binary files /dev/null and b/docs/ces/umn/en-us_image_0000001882024953.png differ diff --git a/docs/ces/umn/en-us_image_0000001882025765.png b/docs/ces/umn/en-us_image_0000001882025765.png new file mode 100644 index 000000000..e3c9f2879 Binary files /dev/null and b/docs/ces/umn/en-us_image_0000001882025765.png differ diff --git a/docs/ces/umn/en-us_image_0000001882035325.png b/docs/ces/umn/en-us_image_0000001882035325.png new file mode 100644 index 000000000..b84c20004 Binary files /dev/null and b/docs/ces/umn/en-us_image_0000001882035325.png differ diff --git a/docs/ces/umn/en-us_image_0000001902856296.png b/docs/ces/umn/en-us_image_0000001902856296.png index aa91b6cad..519c5fe0a 100644 Binary files a/docs/ces/umn/en-us_image_0000001902856296.png and b/docs/ces/umn/en-us_image_0000001902856296.png differ diff --git a/docs/ces/umn/en-us_image_0000001940391649.png b/docs/ces/umn/en-us_image_0000001940391649.png index e68c27db3..37eb53baf 100644 Binary files a/docs/ces/umn/en-us_image_0000001940391649.png and b/docs/ces/umn/en-us_image_0000001940391649.png differ diff --git a/docs/ces/umn/en-us_image_0000001967826817.png b/docs/ces/umn/en-us_image_0000001967826817.png new file mode 100644 index 000000000..8cbde6aa8 Binary files /dev/null and b/docs/ces/umn/en-us_image_0000001967826817.png differ diff --git a/docs/ces/umn/en-us_image_0000002048254333.png b/docs/ces/umn/en-us_image_0000002048254333.png index adc04a6d4..d3ddffe07 100644 Binary files a/docs/ces/umn/en-us_image_0000002048254333.png and b/docs/ces/umn/en-us_image_0000002048254333.png differ diff --git a/docs/ces/umn/en-us_image_0000002048262997.png b/docs/ces/umn/en-us_image_0000002048262997.png index e0b7fecae..eea0cd4b3 100644 Binary files a/docs/ces/umn/en-us_image_0000002048262997.png and b/docs/ces/umn/en-us_image_0000002048262997.png differ diff --git a/docs/ces/umn/en-us_image_0000002055287841.png b/docs/ces/umn/en-us_image_0000002055287841.png deleted file mode 100644 index 1bc44cfa9..000000000 Binary files a/docs/ces/umn/en-us_image_0000002055287841.png and /dev/null differ diff --git a/docs/ces/umn/en-us_image_0000002126246800.png b/docs/ces/umn/en-us_image_0000002126246800.png new file mode 100644 index 000000000..9b830ed9a Binary files /dev/null and b/docs/ces/umn/en-us_image_0000002126246800.png differ diff --git a/docs/ces/umn/en-us_image_0000002126246804.png b/docs/ces/umn/en-us_image_0000002126246804.png new file mode 100644 index 000000000..24e5aec97 Binary files /dev/null and b/docs/ces/umn/en-us_image_0000002126246804.png differ diff --git a/docs/ces/umn/en-us_image_0000002178756434.png b/docs/ces/umn/en-us_image_0000002178756434.png new file mode 100644 index 000000000..59bc1bc12 Binary files /dev/null and b/docs/ces/umn/en-us_image_0000002178756434.png differ diff --git a/docs/ces/umn/en-us_image_0000002236842869.png b/docs/ces/umn/en-us_image_0000002236842869.png new file mode 100644 index 000000000..3443ba6c3 Binary files /dev/null and b/docs/ces/umn/en-us_image_0000002236842869.png differ diff --git a/docs/ces/umn/en-us_image_0000002318778793.png b/docs/ces/umn/en-us_image_0000002318778793.png new file mode 100644 index 000000000..f5fed4773 Binary files /dev/null and b/docs/ces/umn/en-us_image_0000002318778793.png differ diff --git a/docs/ces/umn/en-us_image_0000002353540498.png b/docs/ces/umn/en-us_image_0000002353540498.png new file mode 100644 index 000000000..8cbde6aa8 Binary files /dev/null and b/docs/ces/umn/en-us_image_0000002353540498.png differ diff --git a/docs/ces/umn/en-us_image_0000002385201528.png b/docs/ces/umn/en-us_image_0000002385201528.png new file mode 100644 index 000000000..b24a5fcb6 Binary files /dev/null and b/docs/ces/umn/en-us_image_0000002385201528.png differ diff --git a/docs/ces/umn/en-us_image_0000002387101041.png b/docs/ces/umn/en-us_image_0000002387101041.png new file mode 100644 index 000000000..8cbde6aa8 Binary files /dev/null and b/docs/ces/umn/en-us_image_0000002387101041.png differ diff --git a/docs/ces/umn/en-us_image_0000002410287150.png b/docs/ces/umn/en-us_image_0000002410287150.png new file mode 100644 index 000000000..7b0c9d840 Binary files /dev/null and b/docs/ces/umn/en-us_image_0000002410287150.png differ diff --git a/docs/ces/umn/en-us_image_0000002414598814.png b/docs/ces/umn/en-us_image_0000002414598814.png new file mode 100644 index 000000000..c575ed861 Binary files /dev/null and b/docs/ces/umn/en-us_image_0000002414598814.png differ diff --git a/docs/ces/umn/en-us_image_0000002414599170.png b/docs/ces/umn/en-us_image_0000002414599170.png new file mode 100644 index 000000000..ebbeda9b6 Binary files /dev/null and b/docs/ces/umn/en-us_image_0000002414599170.png differ diff --git a/docs/ces/umn/en-us_image_0000002414759378.png b/docs/ces/umn/en-us_image_0000002414759378.png new file mode 100644 index 000000000..9160616ca Binary files /dev/null and b/docs/ces/umn/en-us_image_0000002414759378.png differ diff --git a/docs/ces/umn/en-us_image_0000002418825513.png b/docs/ces/umn/en-us_image_0000002418825513.png new file mode 100644 index 000000000..06b1dd0bc Binary files /dev/null and b/docs/ces/umn/en-us_image_0000002418825513.png differ diff --git a/docs/ces/umn/en-us_image_0000002418840729.png b/docs/ces/umn/en-us_image_0000002418840729.png new file mode 100644 index 000000000..8653a7635 Binary files /dev/null and b/docs/ces/umn/en-us_image_0000002418840729.png differ diff --git a/docs/ces/umn/en-us_image_0000002418840789.png b/docs/ces/umn/en-us_image_0000002418840789.png new file mode 100644 index 000000000..37d351477 Binary files /dev/null and b/docs/ces/umn/en-us_image_0000002418840789.png differ diff --git a/docs/ces/umn/en-us_image_0000002418960597.png b/docs/ces/umn/en-us_image_0000002418960597.png new file mode 100644 index 000000000..e953aca11 Binary files /dev/null and b/docs/ces/umn/en-us_image_0000002418960597.png differ diff --git a/docs/ces/umn/en-us_image_0000002418960629.png b/docs/ces/umn/en-us_image_0000002418960629.png new file mode 100644 index 000000000..51d72eb50 Binary files /dev/null and b/docs/ces/umn/en-us_image_0000002418960629.png differ diff --git a/docs/ces/umn/en-us_image_0000002425764801.png b/docs/ces/umn/en-us_image_0000002425764801.png new file mode 100644 index 000000000..aa7d9d697 Binary files /dev/null and b/docs/ces/umn/en-us_image_0000002425764801.png differ diff --git a/docs/ces/umn/en-us_image_0000002425765261.png b/docs/ces/umn/en-us_image_0000002425765261.png new file mode 100644 index 000000000..118e8dd7b Binary files /dev/null and b/docs/ces/umn/en-us_image_0000002425765261.png differ diff --git a/docs/ces/umn/en-us_image_0000002425844405.png b/docs/ces/umn/en-us_image_0000002425844405.png new file mode 100644 index 000000000..9c64b8a68 Binary files /dev/null and b/docs/ces/umn/en-us_image_0000002425844405.png differ diff --git a/docs/ces/umn/en-us_image_0000002448236001.png b/docs/ces/umn/en-us_image_0000002448236001.png new file mode 100644 index 000000000..116b77bbf Binary files /dev/null and b/docs/ces/umn/en-us_image_0000002448236001.png differ diff --git a/docs/ces/umn/en-us_image_0000002448236893.png b/docs/ces/umn/en-us_image_0000002448236893.png new file mode 100644 index 000000000..0179b349b Binary files /dev/null and b/docs/ces/umn/en-us_image_0000002448236893.png differ diff --git a/docs/ces/umn/en-us_image_0000002448237989.png b/docs/ces/umn/en-us_image_0000002448237989.png new file mode 100644 index 000000000..a1e38d3d8 Binary files /dev/null and b/docs/ces/umn/en-us_image_0000002448237989.png differ diff --git a/docs/ces/umn/en-us_image_0000002451256404.png b/docs/ces/umn/en-us_image_0000002451256404.png new file mode 100644 index 000000000..8fc40869f Binary files /dev/null and b/docs/ces/umn/en-us_image_0000002451256404.png differ diff --git a/docs/ces/umn/en-us_image_0000002461365577.png b/docs/ces/umn/en-us_image_0000002461365577.png new file mode 100644 index 000000000..4e8dd80cf Binary files /dev/null and b/docs/ces/umn/en-us_image_0000002461365577.png differ diff --git a/docs/ces/umn/en-us_image_0000002461366529.png b/docs/ces/umn/en-us_image_0000002461366529.png new file mode 100644 index 000000000..71fcd4454 Binary files /dev/null and b/docs/ces/umn/en-us_image_0000002461366529.png differ diff --git a/docs/ces/umn/en-us_image_0000002462468769.png b/docs/ces/umn/en-us_image_0000002462468769.png new file mode 100644 index 000000000..73093a624 Binary files /dev/null and b/docs/ces/umn/en-us_image_0000002462468769.png differ diff --git a/docs/ces/umn/en-us_image_0000002464136293.png b/docs/ces/umn/en-us_image_0000002464136293.png new file mode 100644 index 000000000..09e10a8d1 Binary files /dev/null and b/docs/ces/umn/en-us_image_0000002464136293.png differ diff --git a/docs/ces/umn/en-us_image_0000002464270489.png b/docs/ces/umn/en-us_image_0000002464270489.png new file mode 100644 index 000000000..ec3e1383f Binary files /dev/null and b/docs/ces/umn/en-us_image_0000002464270489.png differ diff --git a/docs/ces/umn/en-us_image_0000002473248828.png b/docs/ces/umn/en-us_image_0000002473248828.png new file mode 100644 index 000000000..c24f818f5 Binary files /dev/null and b/docs/ces/umn/en-us_image_0000002473248828.png differ diff --git a/docs/ces/umn/en-us_image_0000002473248950.png b/docs/ces/umn/en-us_image_0000002473248950.png new file mode 100644 index 000000000..dc0d1c95f Binary files /dev/null and b/docs/ces/umn/en-us_image_0000002473248950.png differ diff --git a/docs/ces/umn/en-us_image_0110317533.jpg b/docs/ces/umn/en-us_image_0110317533.jpg deleted file mode 100644 index f67319898..000000000 Binary files a/docs/ces/umn/en-us_image_0110317533.jpg and /dev/null differ diff --git a/docs/ces/umn/en-us_image_0111203217.jpg b/docs/ces/umn/en-us_image_0111203217.jpg deleted file mode 100644 index 2d51646cf..000000000 Binary files a/docs/ces/umn/en-us_image_0111203217.jpg and /dev/null differ diff --git a/docs/ces/umn/en-us_image_0111203223.png b/docs/ces/umn/en-us_image_0111203223.png deleted file mode 100644 index c26de80e9..000000000 Binary files a/docs/ces/umn/en-us_image_0111203223.png and /dev/null differ diff --git a/docs/ces/umn/en-us_image_0239514208.png b/docs/ces/umn/en-us_image_0239514208.png deleted file mode 100644 index 9976b1798..000000000 Binary files a/docs/ces/umn/en-us_image_0239514208.png and /dev/null differ diff --git a/docs/ces/umn/en-us_image_0239514842.png b/docs/ces/umn/en-us_image_0239514842.png deleted file mode 100644 index 9976b1798..000000000 Binary files a/docs/ces/umn/en-us_image_0239514842.png and /dev/null differ diff --git a/docs/ces/umn/en-us_image_0239599900.png b/docs/ces/umn/en-us_image_0239599900.png deleted file mode 100644 index 9976b1798..000000000 Binary files a/docs/ces/umn/en-us_image_0239599900.png and /dev/null differ diff --git a/docs/ces/umn/en-us_topic_0000001360217524.html b/docs/ces/umn/en-us_topic_0000001360217524.html index 9805b0b3c..da3cfd85f 100644 --- a/docs/ces/umn/en-us_topic_0000001360217524.html +++ b/docs/ces/umn/en-us_topic_0000001360217524.html @@ -6,7 +6,7 @@

                                                      Figure 1 shows the relationship between regions and AZs.

                                                      Figure 1 Regions and AZs
                                                      -

                                                      Selecting a Region

                                                      Select a region closest to your target users for lower network latency and quick access.

                                                      +

                                                      Selecting a Region

                                                      You are advised to select a region close to you or your target users. This helps ensure low access latency.

                                                      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.
                                                      diff --git a/docs/ces/umn/en-us_topic_0000001374986910.html b/docs/ces/umn/en-us_topic_0000001374986910.html index ccad8f5e7..ca47a2c04 100644 --- a/docs/ces/umn/en-us_topic_0000001374986910.html +++ b/docs/ces/umn/en-us_topic_0000001374986910.html @@ -1,7 +1,7 @@

                                                      Viewing Details of an Alarm Rule

                                                      -

                                                      Procedure

                                                      1. Log in to the management console.
                                                      2. In the upper left corner, select a region and project.
                                                      3. Click Service List in the upper left corner and select Cloud Eye.
                                                      4. Choose Alarm Management > Alarm Rules.
                                                      5. On the displayed page, click the name of the alarm rule to be viewed.
                                                        Figure 1 Alarm rule details
                                                        +

                                                        Procedure

                                                        1. Log in to the management console.
                                                        2. In the upper left corner, select a region and project.
                                                        3. Choose Service List > Cloud Eye.
                                                        4. Choose Alarm Management > Alarm Rules.
                                                        5. On the displayed page, click the name of the alarm rule to be viewed.
                                                          Figure 1 Alarm rule details
                                                          @@ -162,7 +162,7 @@ - @@ -170,7 +170,7 @@ diff --git a/docs/ces/umn/en-us_topic_0000001835759456.html b/docs/ces/umn/en-us_topic_0000001835759456.html new file mode 100644 index 000000000..1ffb720f4 --- /dev/null +++ b/docs/ces/umn/en-us_topic_0000001835759456.html @@ -0,0 +1,27 @@ + + +

                                                          My Dashboards

                                                          +
                                                          + + diff --git a/docs/ces/umn/en-us_topic_0000002452369417.html b/docs/ces/umn/en-us_topic_0000002452369417.html new file mode 100644 index 000000000..21623f358 --- /dev/null +++ b/docs/ces/umn/en-us_topic_0000002452369417.html @@ -0,0 +1,22 @@ + + +

                                                          Configuring an Agency by One Click

                                                          +

                                                          To enable you to monitor servers more securely and efficiently, Cloud Eye provides the latest Agent permission-granting method. That is, before installing Agents, you only need to click Configure on the Server Monitoring page of the Cloud Eye console, the system will perform temporary AK/SK authorization for the Agents installed on all ECSs or BMSs in the region. And in the future, newly created ECSs or BMSs in this region will automatically get this authorization. This section describes the authorization as follows:

                                                          +
                                                          • Authorization object

                                                            On the Cloud Eye console, if you choose Server Monitoring > Elastic Cloud Server (or Bare Metal Server), selecting a server, and click Configure, the system automatically creates an agency named cesagency on IAM. The agency permissions are automatically granted to Cloud Eye internal account op_svc_ces. For details about the AgentAccess permissions, see Permissions.

                                                            +

                                                            +

                                                            If the system displays a message indicating that you do not have the required permissions, see What Can I Do If the System Displays a Message Indicating Insufficient Permissions When I Click Configure on the Server Monitoring Page?

                                                            +
                                                            +
                                                          • Authorization scope

                                                            The CES AgentAccess permissions are only assigned to the internal account op_svc_ces in the region of the current account.

                                                            +
                                                          • Authorization reason
                                                            The Cloud Eye Agent runs on ECSs or BMSs and reports the collected monitoring data to Cloud Eye. After being authorized, the Agent automatically obtains a temporary AK/SK. This way, you can query the ECS or BMS monitoring data on the Cloud Eye console or by calling the Cloud Eye APIs.
                                                            1. Security: The AK/SK used by the Agent is only the temporary AK/SK that has the CES AgentAccess permissions. That is, the temporary AK/SK can only be used to operate Cloud Eye resources.
                                                            2. Simplified operations: You only need to configure the Cloud Eye Agent once in one region.
                                                            +
                                                            +
                                                          +

                                                          Procedure

                                                          1. Log in to the management console.
                                                          2. In the upper left corner, select a region and project.
                                                          3. Choose Service List > Cloud Eye.
                                                          4. Choose Server Monitoring > Elastic Cloud Server. The Server Monitoring page is displayed.
                                                          5. Click Configure under the operation guide to grant the Agent-related permissions for the current region.

                                                            Once completed, the Agent configurations of all servers in this region are restored by default, and the Configure link is no longer displayed.

                                                            +
                                                          +
                                                          +
                                                          +
                                                          +
                                                          +
                                                          Parent topic: Server Monitoring
                                                          +
                                                          +
                                                          + diff --git a/docs/ces/umn/en-us_topic_0015479880.html b/docs/ces/umn/en-us_topic_0015479880.html index a7b177838..91cfe1ff6 100644 --- a/docs/ces/umn/en-us_topic_0015479880.html +++ b/docs/ces/umn/en-us_topic_0015479880.html @@ -1,7 +1,7 @@

                                                          Introduction to Alarm Rules

                                                          -

                                                          You can flexibly create alarm rules on the Cloud Eye console. You can create an alarm rule for a specific metric or use the alarm template to create alarm rules in batches for multiple cloud service resources.

                                                          +

                                                          You can flexibly create alarm rules on Cloud Eye. You can create an alarm rule for a specific metric or use the alarm template to create alarm rules in batches for multiple cloud service resources.

                                                          Cloud Eye provides you with default alarm templates tailored to each service. In addition, you can also create custom alarm templates by modifying the default alarm template or by specifying every required field.

                                                          diff --git a/docs/ces/umn/en-us_topic_0015479882.html b/docs/ces/umn/en-us_topic_0015479882.html index 769a1199f..6194bcfa0 100644 --- a/docs/ces/umn/en-us_topic_0015479882.html +++ b/docs/ces/umn/en-us_topic_0015479882.html @@ -7,9 +7,9 @@

                                                          Cloud Eye provides the following functions:

                                                          • Automatic monitoring

                                                            Monitoring starts automatically after you create resources such as Elastic Cloud Servers (ECSs). On the Cloud Eye console, you can view statuses of the resources and configure alarm rules for them as needed.

                                                          • Server monitoring

                                                            After you install the Agent (Telescope) on an ECS or a Bare Metal Server (BMS), you can collect ECS or BMS monitoring data at a real-time granularity of 60 seconds. Cloud Eye tracks 40 different metrics, such as CPU, memory, and disk usage, for resources. For details, see Introduction to Server Monitoring.

                                                            -
                                                          • Flexible alarm rule configurations

                                                            You can create alarm rules for multiple resources at the same time. After you create an alarm rule, you can modify, enable, disable, or delete it at any time. For more information, see Alarm Rule Management.

                                                            -
                                                          • Real-time notifications

                                                            You can enable Alarm Notification when creating alarm rules. When the cloud service status changes and metrics reach the thresholds specified in alarm rules, Cloud Eye notifies you by sending emails, SMS messages, or HTTP/HTTPS messages, allowing you to monitor your cloud resource statuses and changes in real time.

                                                            -
                                                          • Dashboard

                                                            Various dashboards enable you to view cross-service and cross-dimension monitoring data. They display key metrics and provide an overview of the service status and monitoring details that you can use for troubleshooting. For more information, see Introduction to Dashboards.

                                                            +
                                                          • Flexible alarm rule configurations

                                                            You can create alarm rules for multiple resources at the same time. After you create an alarm rule, you can modify, copy, enable, disable, or delete it at any time. For more information, see Alarm Rule Management.

                                                            +
                                                          • Real-time notifications

                                                            You can enable Alarm Notification when creating alarm rules. When the cloud service status changes and metrics reach the thresholds specified in alarm rules, Cloud Eye notifies you by sending emails, SMS messages, or HTTP/HTTPS messages, allowing you to monitor your cloud resource statuses and changes in real time.

                                                            +
                                                          • Dashboard

                                                            Various dashboards enable you to view cross-service and cross-dimension monitoring data. They display key metrics and provide an overview of the service status and monitoring details that you can use for troubleshooting. For more information, see My Dashboards.

                                                          • Resource group

                                                            A resource group allows you to add and monitor correlated resources and provides a collective health status for all resources that it contains.

                                                          • 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.

                                                          • Data dump

                                                            You can use the data dump function to query metrics on the DMS for Kafka console or on an open-source Kafka client. It helps you dump cloud service monitoring data to Kafka in real time.

                                                            diff --git a/docs/ces/umn/en-us_topic_0015479891.html b/docs/ces/umn/en-us_topic_0015479891.html index f28116aaf..a494a5d9e 100644 --- a/docs/ces/umn/en-us_topic_0015479891.html +++ b/docs/ces/umn/en-us_topic_0015479891.html @@ -1,19 +1,20 @@ -

                                                            Viewing the Overview Page

                                                            -

                                                            The Overview page provides different modules, helping you track the resource usage and alarms in real time.

                                                            +

                                                            Viewing Overview

                                                            +

                                                            The Overview page provides resource overview, alarm statistics, server monitoring, network monitoring, and storage monitoring. You can view Monitoring Overview to learn the resource usage and alarms of each cloud service in real time.

                                                            +

                                                            The overview page collects statistics on all resources. If you use enterprise project authorization, data not managed by the current enterprise project will also be collected. When you view resources managed in other enterprise projects, the system displays a message about insufficient permissions.

                                                            Resource Overview

                                                            This module displays the total number of monitored cloud service resources and alarms generated for these resources in the current account.

                                                            Alarm Statistics

                                                            This module displays the alarm trend for the last seven days and the number of alarms of each severity.

                                                            After you click corresponding alarm severity area, the Alarm Records page is displayed, showing all alarm records of the severity.

                                                            -

                                                            ECS Monitoring

                                                            This module displays the CPU usages of all ECSs, memory usages of Windows ECSs, top 5 ECSs on which the Agent is installed and have the highest memory usage, and top 5 ECSs on which the Agent is installed and have the highest CPU usage.

                                                            +

                                                            Server Monitoring

                                                            This module displays the CPU and memory usages of all ECSs, top 5 ECSs (Agent installed) with the highest CPU usage in the last five minutes, memory usages of Windows ECSs, and top 5 ECSs (Agent installed) with the highest memory usage.

                                                            Clicking an ECS takes you to the corresponding Basic Monitoring page.

                                                            -

                                                            Network Monitoring

                                                            Displays the outbound bandwidth and inbound bandwidth of the current EIP and bandwidth in the last 1 hour.

                                                            -
                                                            • Inbound bandwidth: indicates the network rate of inbound traffic.
                                                            • Outbound bandwidth: indicates the network rate of outbound traffic.
                                                            • Total outbound bandwidth of all EIPs: indicates the total network rate of outbound traffic of all EIPs.
                                                            • Top 5 EIPs by outbound bandwidth: indicates the top 5 EIPs by outbound bandwidth.
                                                            +

                                                            Network Monitoring

                                                            This module displays the outbound bandwidth and inbound bandwidth of the current EIP and bandwidth in the last 1 hour.

                                                            +
                                                            • Inbound bandwidth: network rate of inbound traffic.
                                                            • Outbound bandwidth: network rate of outbound traffic.
                                                            • Total outbound bandwidth of all EIPs: total network rate of outbound traffic of all EIPs in the last five minutes.
                                                            • Top 5 EIPs by outbound bandwidth: top 5 EIPs by outbound bandwidth in the last five minutes. You can click the bandwidth name to access the corresponding cloud service monitoring dashboard.
                                                            -

                                                            Storage Monitoring

                                                            Storage Monitoring (EVS) on the left displays the top 5 EVS disks by read and write bandwidth. Storage Monitoring (EVS) on the right displays the top 5 EVS disks by read and write IOPS.

                                                            +

                                                            Storage Monitoring

                                                            Storage Monitoring (EVS) displays the top 5 EVS disks by read and write bandwidth and the top 5 EVS disks by read and write IOPS in the last five minutes. You can click the EVS disk name to access the corresponding cloud service monitoring dashboard.

                                                            diff --git a/docs/ces/umn/en-us_topic_0015479901-A.html b/docs/ces/umn/en-us_topic_0015479901-A.html new file mode 100644 index 000000000..2e57e1a39 --- /dev/null +++ b/docs/ces/umn/en-us_topic_0015479901-A.html @@ -0,0 +1,12 @@ + + +

                                                            Overview

                                                            +

                                                            You can use dashboards to view core metrics and compare the performance data of different services.

                                                            +

                                                            You can create or delete a dashboard, and add graphs to the dashboard to view custom monitoring data. You can also edit or delete the graphs on the dashboard.

                                                            +
                                                            +
                                                            +
                                                            +
                                                            Parent topic: My Dashboards
                                                            +
                                                            +
                                                            + diff --git a/docs/ces/umn/en-us_topic_0015479901.html b/docs/ces/umn/en-us_topic_0015479901.html deleted file mode 100644 index 6342fc896..000000000 --- a/docs/ces/umn/en-us_topic_0015479901.html +++ /dev/null @@ -1,11 +0,0 @@ - - -

                                                            Introduction to Dashboards

                                                            -

                                                            Dashboards serve as custom monitoring platforms and allow you to view core metrics and compare the performance data of different services.

                                                            -
                                                            -
                                                            -
                                                            -
                                                            Parent topic: Dashboards
                                                            -
                                                            -
                                                            - diff --git a/docs/ces/umn/en-us_topic_0018121651.html b/docs/ces/umn/en-us_topic_0018121651.html index fb2dcda72..174155b14 100644 --- a/docs/ces/umn/en-us_topic_0018121651.html +++ b/docs/ces/umn/en-us_topic_0018121651.html @@ -3,8 +3,8 @@

                                                            Querying Metrics of a Cloud Service

                                                            Cloud Eye provides multiple built-in metrics based on the characteristics of each service. After you enable one cloud service on the cloud platform, Cloud Eye automatically associates its built-in metrics. You can track the cloud service status by monitoring these metrics.

                                                            This topic describes how to view monitoring data of a cloud service resource.

                                                            -

                                                            Procedure

                                                            1. Log in to the management console.
                                                            1. In the upper left corner, select a region and project.
                                                            2. Click Service List in the upper left corner and select Cloud Eye.
                                                            3. In the navigation pane on the left, choose Cloud Service Monitoring and select a cloud service.

                                                              The cloud service page is displayed.

                                                              -
                                                            4. Locate the row containing the cloud service resource you want to monitor and click View Metric in the Operation column.

                                                              The detailed monitoring page is displayed.

                                                              +

                                                              Procedure

                                                              1. Log in to the management console.
                                                              1. In the upper left corner, select a region and project.
                                                              2. Choose Service List > Cloud Eye.
                                                              3. In the navigation pane on the left, choose Cloud Service Monitoring and select a cloud service.

                                                                The cloud service page is displayed.

                                                                +
                                                              4. Locate the row containing the cloud service resource you want to monitor and click View Metric in the Operation column.

                                                                The detailed monitoring page is displayed.

                                                                You can view graphs based on raw data collected in the last 1h, 3h, 12h, 1d, and 7d. You can also customize the time range. In the upper right corner of the graph, the maximum and minimum values of the metric in the corresponding time periods are dynamically displayed. You can also enable Auto Refresh to view the real-time data refreshed every minute.
                                                                Figure 1 Viewing graphs
                                                                • Units of some metrics can be changed between byte or byte/s and GB or GB/s on graphs. When you are changing the unit, if the maximum value of a metric is smaller than 10^ (-5), both the maximum value and the minimum value of this metric are 0. In addition, all data displayed on the graph is 0.
                                                                • If Auto Refresh is enabled, data is automatically refreshed every minute.
                                                                • You can search for a specific metric in the search box.
                                                                • Some cloud services allow you to view resource details. You can click View Resource Details in the upper part of the page to view details about monitored resources.
                                                                @@ -12,11 +12,11 @@
                                                              5. 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.

                                                              6. Hover your mouse over a graph and click in the upper right corner.

                                                                An enlarged graph of the metric is displayed, on which you can view the metric monitoring details for longer time ranges. In the upper left corner, you can see six default monitoring periods: 1h, 3h, 12h, 1d, 7d, and 30d. You can also view historical monitoring data for any period during the last six months by customizing the monitoring period in the upper right corner of the graph.

                                                                -
                                                                • If you select 1h, 3h, 12h, or 1d, raw data is displayed by default. You can set Period and Statistic to change the aggregation period of the monitoring data. For details about the aggregation period, see What Is Aggregation?
                                                                • If you select 7d or 30d, aggregated data is displayed by default. You can set Period and Statistic to change the aggregation period of monitoring data.
                                                                +
                                                                • 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 the rollup period, 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.
                                                              7. In the upper right corner of the monitoring view, click to create an alarm rule for a metric.

                                                                This icon is not available in the enlarged graph mode.

                                                                -
                                                              8. To export data, click Export Data on the Cloud Service Monitoring page, configure parameters, and click Export. For details, see How Can I Export Collected Data?
                                                              +
                                                            5. To export data, click Export Data on the Cloud Service Monitoring page, configure parameters, and click Export. For details, see Exporting Monitoring Data.
                                                            diff --git a/docs/ces/umn/en-us_topic_0077185772.html b/docs/ces/umn/en-us_topic_0077185772.html index f57416717..004b9b708 100644 --- a/docs/ces/umn/en-us_topic_0077185772.html +++ b/docs/ces/umn/en-us_topic_0077185772.html @@ -1,10 +1,8 @@

                                                            Viewing Alarm Templates

                                                            -

                                                            Procedure

                                                            1. Log in to the management console.
                                                            2. In the upper left corner, select a region and project.
                                                            3. Click Service List in the upper left corner and select Cloud Eye.
                                                            4. Choose Alarm Management > Alarm Templates.
                                                            -
                                                            -
                                                            On the Alarm Templates page, you can create, view, modify, delete, import, or export custom templates.
                                                            • Viewing the template content: To view details of an alarm template, click the down arrow next to the target alarm template.
                                                            • Searching for an alarm template: You can search for an alarm template by template name or resource type.
                                                            -
                                                            +
                                                            1. Log in to the management console.
                                                            2. In the upper left corner, select a region and project.
                                                            3. Choose Service List > Cloud Eye.
                                                            4. Choose Alarm Management > Alarm Templates.

                                                              On the Alarm Templates page, you can view the default or custom metric or event templates. You can also create, view, modify, delete, import, or export custom templates.

                                                              +

                                                            diff --git a/docs/ces/umn/en-us_topic_0078721772.html b/docs/ces/umn/en-us_topic_0078721772.html index 178f72058..cb6892496 100644 --- a/docs/ces/umn/en-us_topic_0078721772.html +++ b/docs/ces/umn/en-us_topic_0078721772.html @@ -3,15 +3,52 @@

                                                            Introduction to Server Monitoring

                                                            Server monitoring includes basic monitoring, process monitoring, and OS monitoring for servers.

                                                            • Basic monitoring covers metrics automatically reported by ECSs. The data is collected every 5 minutes. For details, see Services Interconnected with Cloud Eye.
                                                            • OS monitoring provides proactive and fine-grained OS monitoring for ECSs or BMSs, and it requires the Agent to be installed on all servers that will be monitored. The data is collected every minute. OS monitoring supports metrics such as CPU usage and memory usage (Linux). For details, see Services Interconnected with Cloud Eye.
                                                            • Process monitoring provides monitoring of active processes on hosts. By default, Cloud Eye collects CPU usage, memory usage, and number of opened files of active processes.
                                                            -
                                                            • For the ECS specifications, use 2 vCPUs and 4 GB memory for a Linux ECS and 4 vCPUs and 8 GB memory or higher specifications for a Windows ECS.
                                                            • The Agent will use the system ports. For details, see descriptions of ClientPort and PortNum in (Optional) Manually Configuring the Agent (Linux). If the Agent port conflicts with a service port, see What Should I Do If the Service Port Is Used by the Agent?
                                                            • To install the Agent in a Linux server, you must have the root permissions. For a Windows server, you must have the administrator permissions.
                                                            +

                                                            Scenarios

                                                            Whether you are using ECSs or BMSs, you can use server monitoring to track various OS metrics, monitor server resource usage, and query monitoring data when faults occur.

                                                            -

                                                            Constraints

                                                            Server monitoring is available only for servers using public images provided by a cloud service platform. If any problem occurs when you use a private image, Cloud Eye will not provide technical support.

                                                            +

                                                            Constraints

                                                            Server monitoring is available only for servers using certain public images provided by a cloud service platform. If any problem occurs when you use a private image, Cloud Eye will not provide technical support. For details about supported public images, see What OSs Does the Agent Support?.

                                                            Monitoring Capabilities

                                                            Server monitoring provides multiple metrics, such as metrics for CPU, memory, disk, and network usage, meeting the basic monitoring and O&M requirements for servers. For details about metrics, see Services Interconnected with Cloud Eye.

                                                            -

                                                            Resource Usage

                                                            The Agent uses considerably less resources. When the Agent is installed on a server, it uses less than 5% of the CPU and less than 100 MB of memory.

                                                            +

                                                            Resource Usage

                                                            The Agent uses very few system resources (no more than 10% of a single-core CPU or no more than 200 MB memory). When the Agent is installed on a server, it uses less than 5% of the single-core CPU and less than 100 MB of memory.

                                                            +
                                                            In some scenarios, the CPU and memory usage of the Agent may increase sharply due to server operations. If the resource usage exceeds the threshold, circuit-breaking will be activated, and the Agent process will then exit. After that, the Agent process will automatically start. However, if resource overuse persists, the Agent keeps shutting down and restarting repeatedly, leading to instability. The following table describes some common scenarios and typical solutions. +
                                                          Table 1 Basic information about metric alarms

                                                          Parameter

                                                          Specifies the name of the topic(s) and/or the Account Contact to which the alarm notification is to be sent.

                                                          Trigger Condition

                                                          +

                                                          Trigger Condition

                                                          Specifies the condition for triggering an alarm notification. The options are Generated alarm and Cleared alarm.

                                                          Notification Window

                                                          Cloud Eye sends notifications only within the notification window specified in the alarm rule.

                                                          -

                                                          For example, if the notification window is set to 00:00–8:00, Cloud Eye will only send notifications from 00:00 to 8:00.

                                                          +

                                                          For example, if the notification window is set to 00:00–8:00, Cloud Eye only sends notifications during this period.
                                                          + + + + + + + + + + + + + + + + +
                                                          Table 1 High Agent resource usage scenarios

                                                          Cause

                                                          +

                                                          Scenario

                                                          +

                                                          Solution

                                                          +

                                                          Too many TCP connections

                                                          +

                                                          By default, the Agent collects only two basic metrics TCP TOTAL and TCP ESTABLISHED, which use a few CPU resources. If you choose to enable any detailed TCP metric by updating the configuration file, the Agent will start collecting all TCP metrics, which will consume a lot of CPU resources.

                                                          +

                                                          Basic TCP metrics: TCP TOTAL and TCP ESTABLISHED

                                                          +

                                                          TCP detailed metrics: TCP SYS_SENT, TCP SYS_RECV, TCP FIN_WAIT1, TCP FIN_WAIT2, TCP TIME_WAIT, TCP CLOSE, TCP CLOSE_WAIT, TCP LAST_ACK, TCP LISTEN, and TCP CLOSING

                                                          +

                                                          Method 1: Modify the configuration file to disable TCP detailed metric collection and reduce the CPU usage. For details, see How Do I Enable or Disable Metric Collection by Modifying the Configuration File?.

                                                          +

                                                          Method 2: Change the Agent resource usage threshold by referring to How Do I Change the Agent Resource Usage Threshold by Modifying the Configuration File?.

                                                          +

                                                          Too many file handles

                                                          +

                                                          While the Agent is running, it monitors all files opened by processes on the host to track and sum the number of file handles. If there are too many file handles, the Agent task will be re-executed, resulting in high CPU usage.

                                                          +

                                                          Method 1: Modify the configuration file to decrease the metric update interval for the Agent process to minimize CPU usage. For details, see How Do I Change the Process Collection Frequency by Modifying the Configuration File?.

                                                          +

                                                          Method 2: Change the Agent resource usage threshold. For details, see How Do I Change the Agent Resource Usage Threshold by Modifying the Configuration File?.

                                                          +

                                                          +

                                                          Too many processes

                                                          +

                                                          When the Agent is running, it scans all processes on the current server and collects process-level metrics by reviewing process information. When there are too many processes, the Agent task is re-executed, leading to high CPU usage.

                                                          +
                                                          +
                                                          +
                                                      diff --git a/docs/ces/umn/en-us_topic_0079332017.html b/docs/ces/umn/en-us_topic_0079332017.html index c1bc73c58..0654c70ba 100644 --- a/docs/ces/umn/en-us_topic_0079332017.html +++ b/docs/ces/umn/en-us_topic_0079332017.html @@ -4,23 +4,23 @@

                                                      Scenarios

                                                      This topic describes how to view server monitoring metrics, including fine-grained OS metrics collected by the Agent and basic ECS metrics.

                                                      For details, see Services Interconnected with Cloud Eye.

                                                      -

                                                      Prerequisites

                                                      You have installed the Agent. For details, see Installing and Configuring the Agent on a Linux ECS or BMS and Installing and Configuring the Agent on a Windows Server.

                                                      +

                                                      Prerequisites

                                                      You have installed the Agent. For details, see Installing and Configuring the Agent on a Linux ECS or BMS and Installing the Agent on a Windows server.

                                                      -

                                                      Procedure

                                                      1. Log in to the management console.
                                                      2. Click Service List in the upper left corner and select Cloud Eye.
                                                      3. View ECS or BMS metrics.
                                                        • To view OS monitoring metrics of an ECS, in the left navigation pane, choose Server Monitoring > Elastic Cloud Server, locate the ECS, and click View Metric in the Operation column.

                                                          +

                                                          Procedure

                                                          1. Log in to the management console.
                                                          2. Choose Service List > Cloud Eye.
                                                          3. View ECS or BMS metrics.
                                                            • To view OS monitoring metrics of an ECS, in the left navigation pane, choose Server Monitoring > Elastic Cloud Server, locate the ECS, and click View Metric in the Operation column.

                                                            • To view basic monitoring metrics of an ECS, in the left navigation pane, choose Server Monitoring > Elastic Cloud Server, locate the ECS, and click View Metric in the Operation column. Click the Basic Monitoring tab.

                                                            • To view OS monitoring metrics of a BMS, in the left navigation pane, choose Server Monitoring > Bare Metal Server, locate the BMS, and click View Metric in the Operation column.
                                                            • To view processing monitoring metrics, in the left navigation pane, choose Server Monitoring > Elastic Cloud Server, locate the ECS, and click View Metric in the Operation column, and then click the Process Monitoring tab.
                                                            -
                                                          4. View metrics.

                                                            In the upper part of the OS Monitoring page, different metric types, such as CPU, memory, and disk metrics are displayed.

                                                            -

                                                            View metric graphs based on raw data from the last 1 hour, last 3 hours, last 12 hours, last 1 day, last 7 days, or last 30 days. Cloud Eye provides the Auto Refresh function at 60-second intervals.

                                                            -
                                                          5. Hover your mouse over a graph. In the upper right corner, click to enlarge the graph for viewing detailed data.

                                                            In the upper left corner, you can see six default monitoring periods: 1h, 3h, 12h, 1d, 7d, and 30d. To view historical monitoring data for any period during the last six months, customize the monitoring period by setting Select Range in the upper right corner.

                                                            +
                                                          6. View metrics.
                                                            • In the upper part of the OS Monitoring page, different metric types, such as CPU, memory, and disk metrics are displayed.

                                                              You can view the monitoring data curves of different metrics. By default, raw metric data is displayed if you select 1h, 3h, 12h, or 1d. For Last 7d and longer time ranges, aggregated data is displayed.

                                                              +
                                                            • Cloud Eye provides the Auto Refresh function at 30-second intervals.
                                                            • Select the Select Date for Comparison check box and select a date to compare the monitoring data of the current date with that of the specified date on a graph.
                                                            +
                                                          7. Hover your mouse over a graph. In the upper right corner, click to enlarge the graph for viewing detailed data.

                                                            In the upper right corner, you can see the following default monitoring periods: 1h, 3h, 12h, 1d, 7d, and 30d. You can also customize a time range (up to six months).

                                                            -
                                                          8. In the upper left corner of the graph, locate Period and configure the aggregation method.
                                                            • If you select 1h, 3h, 12h, or 1d, raw data is displayed by default.
                                                            • If you select 7d or 30d, aggregated data is displayed by default.
                                                            +
                                                          9. In the upper left corner of the graph, locate Period and configure the rollup method.
                                                            • If you select 1h, 3h, 12h, or 1d, raw data is displayed by default.
                                                            • If you select 7d or 30d, aggregated data is displayed by default.
                                                            • After clicking the zoom in icon in the upper right of an enlarged graph, you can drag the mouse to customize a time range.
                                                      -
                                                      Parent topic: Server Monitoring
                                                      +
                                                      Parent topic: Viewing Metrics
                                                      diff --git a/docs/ces/umn/en-us_topic_0084572213.html b/docs/ces/umn/en-us_topic_0084572213.html index f3e074e64..5fd480f8e 100644 --- a/docs/ces/umn/en-us_topic_0084572213.html +++ b/docs/ces/umn/en-us_topic_0084572213.html @@ -3,7 +3,7 @@

                                                      Creating an Alarm Rule

                                                      Cloud Eye allows you to use alarm templates to create alarm rules, making it easy and convenient to add or modify alarm rules for resources or cloud services, especially for a large number of resources and cloud services.

                                                      This topic describes how to create an alarm rule.

                                                      -

                                                      Creating an Alarm Rule

                                                      1. Log in to the management console.
                                                      2. In the upper left corner, select a region and project.
                                                      3. Click Service List in the upper left corner and select Cloud Eye.
                                                      4. In the navigation pane on the left, choose Alarm Management > Alarm Rules.
                                                      5. Click Create Alarm Rule in the upper right corner.
                                                      6. On the Create Alarm Rule page, configure the parameters.
                                                        1. Configure the alarm rule name and description. +

                                                          Creating an Alarm Rule

                                                          1. Log in to the management console.
                                                          2. In the upper left corner, select a region and project.
                                                          3. Choose Service List > Cloud Eye.
                                                          4. In the navigation pane on the left, choose Alarm Management > Alarm Rules.
                                                          5. Click Create Alarm Rule in the upper right corner.
                                                          6. On the Create Alarm Rule page, configure the parameters.
                                                            1. Configure the alarm rule name and description.
                                                              - - - @@ -97,7 +99,7 @@ - - @@ -125,7 +127,7 @@ @@ -172,17 +174,43 @@ + + + + + + + + - + + + + @@ -200,7 +228,7 @@ @@ -216,7 +244,7 @@ - @@ -243,12 +271,12 @@ - - diff --git a/docs/ces/umn/en-us_topic_0092358859.html b/docs/ces/umn/en-us_topic_0092358859.html index 4e04b6fee..e56a08def 100644 --- a/docs/ces/umn/en-us_topic_0092358859.html +++ b/docs/ces/umn/en-us_topic_0092358859.html @@ -1,13 +1,13 @@ -

                                                              Viewing Process Monitoring

                                                              +

                                                              Viewing Process Monitoring Metrics

                                                              Process monitoring is used to monitor active processes on a host. By default, the Agent collects CPU usage, memory usage, and the number of opened files of the active processes. If you have customized process monitoring, the number of processes containing keywords is also monitored.

                                                              The Agent collects process CPU usages once every minute and displays the top 5 processes, ranked by the CPU usage over the last 24 hours.

                                                              To view the process monitoring information, install the Agent.

                                                              Querying the System Processes

                                                              After the Agent is installed, you can check system processes on Cloud Eye.

                                                              To query the number of processes

                                                              -
                                                              1. Log in to the management console.
                                                              2. Click Service List in the upper left corner and select Cloud Eye.
                                                              3. Perform the following operations based on the resources to be viewed:
                                                                • To check the process monitoring of an ECS, choose Server Monitoring > Elastic Cloud Server.
                                                                • To check the process monitoring of a BMS, choose Server Monitoring > Bare Metal Server.
                                                                +
                                                                1. Log in to the management console.
                                                                2. Choose Service List > Cloud Eye.
                                                                3. Perform the following operations based on the resources to be viewed:
                                                                  • To check the process monitoring of an ECS, choose Server Monitoring > Elastic Cloud Server.
                                                                  • To check the process monitoring of a BMS, choose Server Monitoring > Bare Metal Server.
                                                                4. On the Server Monitoring page, locate the ECS and click View Metric to go to the OS Monitoring page.
                                                                5. Select the Process Monitoring tab.
                                                                  In the System Processes area, the process information is displayed. Table 1 describes the metrics of system processes.
                                                              Table 1 Name and Description

                                                              Parameter

                                                              Description

                                                              @@ -56,8 +56,8 @@

                                                              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 you select Specific resources, select one or more resources and click to add them to the box on the right.
                                                              +

                                                              The monitoring scope of an alarm rule can be All resources, Resource groups, or Specific resources.

                                                              +
                                                              NOTE:
                                                              • If you select All resources, an alarm notification will be sent when any instance meets an alarm policy. New resources will automatically apply the existing alarm rule.
                                                              • If Resource groups is selected and any resource in the group meets the alarm policy, an alarm is triggered.
                                                              • If you select Specific resources, click Select Specific Resources and select resources.

                                                              Specific resources

                                                              @@ -65,14 +65,16 @@

                                                              Group

                                                              This parameter is mandatory when Monitoring Scope is set to Resource groups.

                                                              +

                                                              This parameter is mandatory when Monitoring Scope is set to Resource groups.

                                                              N/A

                                                              Method

                                                              There are two options: Use existing template or Configure manually.

                                                              +

                                                              You can select Associate template, Use existing template, or Configure manually as needed.

                                                              +
                                                              NOTE:
                                                              • If you select Associate template, the policies contained in the alarm rule will automatically be modified accordingly after the associated custom template is modified.
                                                              • If you select Associate template or Use existing template, the alarm policies that match the current resource and dimension in the alarm template will be synchronized to the alarm policies of the current alarm rule. If you select Use existing template, you can add alarm policies as needed, or modify or delete the synchronized ones.
                                                              +

                                                              Configure manually

                                                              Metric

                                                              Example:

                                                              +

                                                              Examples:

                                                              • CPU Usage

                                                                CPU usage of the monitored object in percent.

                                                              • Memory Usage

                                                                Memory usage of the monitored object in percent.

                                                                @@ -116,7 +118,7 @@

                                                              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

                                                              This parameter is displayed on the console and can be configured only when the following conditions are met:

                                                              • The monitoring scope is Resource groups or 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.

                                                              +

                                                              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

                                                              Elastic Cloud Server

                                                              Monitoring Scope

                                                              +

                                                              The monitoring scope of an alarm rule can be All resources, Resource groups, or Specific resources.

                                                              +
                                                              NOTE:
                                                              • If you select All resources, an alarm notification will be sent when any instance meets an alarm policy. New resources will automatically apply the existing alarm rule.
                                                              • If you select Resource groups, an alarm will be triggered when the resource usage of the group reaches the preset threshold. Currently, Resource groups is only available for DDS, RDS, or DCS event alarms.
                                                              • If you select Specific resources, click Select Specific Resources and select resources.
                                                              +
                                                              +

                                                              All resources

                                                              +

                                                              Group

                                                              +

                                                              This parameter is mandatory when Monitoring Scope is set to Resource groups.

                                                              +

                                                              N/A

                                                              +

                                                              Method

                                                              The only option is Configure manually.

                                                              +

                                                              You can select Associate template, Use existing template, or Configure manually as needed.

                                                              +
                                                              NOTE:
                                                              • If you select Associate template, the policies contained in the alarm rule will automatically be modified accordingly after the associated custom template is modified.
                                                              • If you select Associate template or Use existing template, the alarm policies that match the current resource and dimension in the alarm template will be synchronized to the alarm policies of the current alarm rule. If you select Use existing template, you can add alarm policies as needed, or modify or delete the synchronized ones.
                                                              +

                                                              Configure manually

                                                              Template

                                                              +

                                                              Specifies the template to be used.

                                                              +

                                                              You can select a default or a custom event template.

                                                              +

                                                              ECS event template

                                                              +

                                                              Alarm Policy

                                                              Specifies the policy for triggering an alarm.

                                                              -

                                                              The event that triggers an alarm is an instant operation. For example, if the event Reboot ECS occurs, an alarm will be triggered.

                                                              +

                                                              The event that triggers an alarm is an instant operation. 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.

                                                              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: An alarm is triggered once an event occurs.
                                                              • Accumulative trigger: An alarm is triggered only when the number of event occurrences reaches the preset threshold.

                                                              Immediate trigger

                                                              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

                                                              Alarm Notification

                                                              Specifies whether to notify users when alarms are triggered. Notifications can be sent by email, SMS message, or HTTP/HTTPS message.

                                                              +

                                                              Specifies whether to notify users when alarms are triggered. Notifications can be sent by email, SMS message, or HTTP/HTTPS request.

                                                              Notification Object

                                                              Specifies the object to which alarm notifications will be sent. You can select the account contact or a topic.

                                                              +

                                                              Specifies the object that receives alarm notifications, which can be an account 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 and add subscriptions to it first. For details, see Creating a Topic and Adding Subscriptions.
                                                              @@ -104,7 +104,7 @@

                                                              To query information about top 5 processes with the highest CPU usages

                                                              -
                                                              1. Log in to the management console.
                                                              2. Click Service List in the upper left corner and select Cloud Eye.
                                                              3. In the navigation pane on the left, choose Server Monitoring.
                                                              4. On the Server Monitoring page, locate the ECS and click View Metric to go to the OS Monitoring page.
                                                              5. Select the Process Monitoring tab.
                                                              6. In the Monitored Processes area, click in the upper right corner to view Top 5 Processes with Highest CPU Usage.
                                                              7. In the displayed TOP 5 Processes with Highest CPU Usage window, enable process monitoring for the processes, and click OK.

                                                                In the Monitored Processes area, the system selects processes in the Running state by default and displays CPU usage curves of those processes in 1h. The displayed data is raw data.

                                                                +
                                                                1. Log in to the management console.
                                                                2. Choose Service List > Cloud Eye.
                                                                3. In the navigation pane on the left, choose Server Monitoring.
                                                                4. On the Server Monitoring page, locate the ECS and click View Metric to go to the OS Monitoring page.
                                                                5. Select the Process Monitoring tab.
                                                                6. In the Monitored Processes area, click in the upper right corner to view Top 5 Processes with Highest CPU Usage.
                                                                7. In the displayed TOP 5 Processes with Highest CPU Usage window, enable process monitoring for the processes, and click OK.

                                                                  In the Monitored Processes area, the system selects processes in the Running state by default and displays CPU usage curves of those processes in 1h. The displayed data is raw data.

                                                                  You can also select the process to be displayed and view its CPU usage curve in 1h.

                                                                  You can click CPU Usage, Memory Usage, or Open Files above the graph to view the curves of different metrics of the currently displayed process. Table 2 lists Process Monitoring metrics.

                                                                  @@ -154,7 +154,7 @@
                                                              @@ -167,14 +167,14 @@
                                                              Table 1 System process metrics

                                                              Metric

                                                              Open Files

                                                              Specifies the number of opened files consumed by the process.

                                                              -

                                                              pHashId (process name and process ID) is the value of md5.

                                                              +

                                                              pHashId (process name and process ID) is the value of md5.

                                                              ≥ 0
                                                              -
                                                            2. Hover your mouse over a graph. In the upper right corner, click to enlarge the graph for viewing detailed data.

                                                              In the upper left corner, you can see six default monitoring periods: 1h, 3h, 12h, 1d, 7d, and 30d. To view historical monitoring data for any period during the last six months, customize the monitoring period by setting Select Range in the upper right corner.

                                                              -

                                                              In the upper left corner of the graph, select a different value for Period to configure the aggregation method.

                                                              +
                                                            3. Hover your mouse over a graph. In the upper right corner, click to enlarge the graph for viewing detailed data.

                                                              In the upper left corner, you can see six default monitoring periods: 1h, 3h, 12h, 1d, 7d, and 30d. You can also set Select Range to customize one to view historical monitoring data for any period during the last six months.

                                                              +

                                                              In the upper left corner of the graph details page, locate Period and configure the rollup method.

                                                      -
                                                      Parent topic: Process Monitoring
                                                      +
                                                      Parent topic: Viewing Metrics
                                                      diff --git a/docs/ces/umn/en-us_topic_0094279601.html b/docs/ces/umn/en-us_topic_0094279601.html index c68b87ca1..ee805b427 100644 --- a/docs/ces/umn/en-us_topic_0094279601.html +++ b/docs/ces/umn/en-us_topic_0094279601.html @@ -2,12 +2,12 @@

                                                      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.

                                                      -

                                                      Viewing Custom Monitoring

                                                      1. Log in to the management console.
                                                      2. Click Service List in the upper left corner and select Cloud Eye.
                                                      3. In the navigation pane on the left, choose Custom Monitoring.
                                                      4. On the Custom Monitoring page, view the data reported by yourself through API requests, including custom services and metrics.

                                                        Only after you add monitoring data through APIs, will those data be displayed on the Cloud Eye console. For details about how to add monitoring data, see section "Adding Monitoring Data" in Cloud Eye API Reference.

                                                        +

                                                        Viewing Custom Monitoring

                                                        1. Log in to the management console.
                                                        2. Choose Service List > Cloud Eye.
                                                        3. In the navigation pane on the left, choose Custom Monitoring.
                                                        4. On the Custom Monitoring page, view the data reported by yourself through API requests, including custom services and metrics.

                                                          Only after you add monitoring data through APIs, will those data be displayed on the Cloud Eye console. For details about how to add monitoring data, see Adding Monitoring Data.

                                                          -
                                                        5. Locate the row containing the cloud resource to be viewed, and click View Metric.

                                                          On the page displayed, you can view graphs based on raw data collected in 1h, 3h, 12h, 1d, and 7d. In the upper right corner of each graph, the maximum and minimum values of the metric in the corresponding time periods are dynamically displayed.

                                                          +
                                                        6. Locate the cloud resource to be viewed, and click View Metric.

                                                          On the page displayed, you can view graphs based on raw data collected in 1h, 3h, 12h, 1d, and 7d. In the upper right corner of each graph, the maximum and minimum values of the metric in the corresponding time periods are dynamically displayed.

                                                        -

                                                        Creating an Alarm Rule

                                                        1. Log in to the management console.
                                                        2. Click Service List in the upper left corner and select Cloud Eye.
                                                        3. In the navigation pane on the left, choose Custom Monitoring.
                                                        4. On the Custom Monitoring page, locate the resource and click Create Alarm Rule in the Operation column.
                                                        5. On the Create Alarm Rule page, follow the prompts to configure the parameters. For details, see Table 1 and Table 4.
                                                        6. Click Create.
                                                        +

                                                        Creating an Alarm Rule

                                                        1. Log in to the management console.
                                                        2. Choose Service List > Cloud Eye.
                                                        3. In the navigation pane on the left, choose Custom Monitoring.
                                                        4. On the Custom Monitoring page, locate the resource and click Create Alarm Rule in the Operation column.
                                                        5. On the Create Alarm Rule page, follow the prompts to configure the parameters. For details, see Table 1 and Table 4.
                                                        6. Click Create.
                                                        diff --git a/docs/ces/umn/en-us_topic_0110258146.html b/docs/ces/umn/en-us_topic_0110258146.html index 12b7d6bf7..67747ce05 100644 --- a/docs/ces/umn/en-us_topic_0110258146.html +++ b/docs/ces/umn/en-us_topic_0110258146.html @@ -1,25 +1,27 @@ -

                                                        Installing and Configuring the Agent on a Windows Server

                                                        +

                                                        Installing the Agent on a Windows server

                                                        Scenarios

                                                        This topic describes how to install the Agent on a Windows ECS.

                                                        -

                                                        Constraints

                                                        The Agent cannot be installed on Windows BMSs.

                                                        +

                                                        Constraints

                                                        • The Agent cannot be installed on Windows BMSs.
                                                        • Some OSs are not supported. For details about which Windows OSs are supported, see What OSs Does the Agent Support?
                                                        -

                                                        Prerequisites

                                                        • You have performed operations described in Modifying the DNS Server Address and Adding Security Group Rules (Windows).
                                                        • Use an administrator account to install the Agent.
                                                        • Ensure that the Telescope process is not stopped by other processes after the installation.
                                                        • You have obtained the Agent installation package (Windows). -
                                                          Table 1 Installation package path

                                                          Name

                                                          +

                                                          Prerequisites

                                                          • You have performed operations described in Modifying the DNS Server Address and Adding Security Group Rules (Windows).
                                                          • You have configured an agency by referring to Configuring an Agency by One Click.
                                                          • Use an administrator account to install the Agent.
                                                          • Ensure that the Telescope process is not stopped by other processes after the installation.
                                                          • You have obtained the Agent installation package (Windows). +
                                                            - - - - - @@ -27,11 +29,13 @@ -

                                                            Procedure

                                                            1. Log in to the Windows ECS as an administrator.
                                                            2. Open a browser, and enter the address of the Agent installation package in the address box to download and save the installation package.
                                                            3. Create a directory for storing the installation package (for example, D:\Agent) and decompress the package to this directory.
                                                            4. Double-click the install.bat script to install and start the Agent.

                                                              If Install service success is displayed, the Agent is successfully installed and started.

                                                              -

                                                              After you configure the Agent, its status is still displayed as Uninstalled because no monitoring data is reported yet. Wait 3 to 5 minutes and refresh the page.

                                                              +

                                                              Procedure

                                                              1. Log in to the Windows ECS as an administrator.
                                                              2. Open a browser, and enter the address of the Agent installation package in the address box to download and save the installation package.
                                                              3. Open Windows PowerShell and go to the directory storing the installation package.
                                                              4. Run the following command to install the Agent:
                                                                EU DE:
                                                                .\install_amd64.exe -r eu-de -u 0.1.9 -t 2.7.2 -d agent.ces.otc.t-systems.com -o otc.t-systems.com
                                                                +
                                                                +
                                                                EU NL:
                                                                .\install_amd64.exe -r eu-nl -u 0.1.9 -t 2.7.2 -d agent.ces.otc.t-systems.com -o otc.t-systems.com
                                                                +
                                                                +
                                                                Wait for 3 to 5 minutes until the Agent starts collecting monitoring data.
                                                                • After you configure the Agent, its status is still displayed as Not installed on the Server Monitoring page because no monitoring data is reported yet. Wait 3 to 5 minutes and refresh the page.
                                                                • If the Agent status is Running and monitoring is enabled, the Agent has been recognized by Cloud Eye and has started to report fine-grained metric data.
                                                                -
                                                              5. On the Server Monitoring page, select the ECS and click Restore Agent Configurations.
                                                              6. In the displayed Restore Agent Configurations dialog box, click One-Click Restore.

                                                                The Agent configuration is completed.

                                                                -

                                                                If the Agent is in the Running state, the Agent has been installed and has started to collect fine-grained metric data.

                                                                +
                                                            diff --git a/docs/ces/umn/en-us_topic_0150354069.html b/docs/ces/umn/en-us_topic_0150354069.html index f5d5e6e0a..30e22f8dd 100644 --- a/docs/ces/umn/en-us_topic_0150354069.html +++ b/docs/ces/umn/en-us_topic_0150354069.html @@ -8,13 +8,13 @@

                                                            Modifying the DNS Server Address (Command Lines)

                                                            The following describes how to add the DNS server address to the resolv.conf file using command lines.

                                                            To use the management console, see Modifying the DNS Server Address (Management Console).

                                                            -
                                                            1. Log in to an ECS as user root.
                                                            2. Run the vi /etc/resolv.conf command to open the file.
                                                            3. Add the DNS server address, for example, nameserver 100.125.4.25 to the file. Enter :wq and press Enter to save the change.
                                                              Figure 1 Adding the DNS server address (Linux)
                                                              +
                                                              1. Log in to an ECS as user root.
                                                              2. Run the vi /etc/resolv.conf command to open the file.
                                                              3. Add the DNS server address, for example, nameserver 100.125.4.25 to the file. Enter :wq and press Enter to save the change.
                                                                Figure 1 Adding the DNS server address (Linux)

                                                            Modifying the DNS Server Address (Management Console)

                                                            The following describes how to modify the DNS server address of an ECS on the management console. This section takes an ECS as an example. The operations for BMSs are similar.

                                                            1. In the upper left corner, select a region and project.
                                                            2. Click Service List in the upper left corner. Under Compute, select Elastic Cloud Server.

                                                              On the ECS console, click the name of the ECS to view its details.

                                                              -
                                                            3. Click the VPC name on the right of VPC to go to the VPC console.
                                                            4. Click the name of the VPC.
                                                            5. In the Networking Components area, click the number following Subnets.

                                                              The Subnets page is displayed.

                                                              -
                                                            6. In the subnet list, click the name of the subnet.
                                                            7. In the Gateway and DNS Information area, click following DNS Server Address.
                                                            8. Change the DNS server address to 100.125.4.25.
                                                            9. Click OK.

                                                              The new DNS server address is applied after the ECS or BMS is restarted.

                                                              +
                                                            10. Click the VPC name on the right of VPC to go to the VPC console.
                                                            11. Click the name of the VPC.
                                                            12. In the Networking Components area, click the number following Subnets.

                                                              The Subnets page is displayed.

                                                              +
                                                            13. In the subnet list, click the name of the subnet.
                                                            14. In the Gateway and DNS Information area, click following DNS Server Address.
                                                            15. Change the DNS server address to 100.125.4.25.
                                                            16. Click OK.

                                                              The new DNS server address is applied after the ECS or BMS is restarted.

                                                            diff --git a/docs/ces/umn/en-us_topic_0150366044.html b/docs/ces/umn/en-us_topic_0150366044.html index 94d6202e1..ddad5f46c 100644 --- a/docs/ces/umn/en-us_topic_0150366044.html +++ b/docs/ces/umn/en-us_topic_0150366044.html @@ -11,8 +11,8 @@

                                                            Modifying the DNS Server Address (Management Console)

                                                            The following describes how to modify the DNS server address of an ECS on the management console. This section takes an ECS as an example. The operations for BMSs are similar.

                                                            1. In the upper left corner, select a region and project.
                                                            2. Click Service List in the upper left corner. Under Compute, select Elastic Cloud Server.

                                                              On the ECS console, click the name of the ECS to view its details.

                                                              -
                                                            3. Click the VPC name on the right of VPC to go to the VPC console.
                                                            4. Click the name of the VPC.
                                                            5. In the Networking Components area, click the number following Subnets.

                                                              The Subnets page is displayed.

                                                              -
                                                            6. In the subnet list, click the name of the subnet.
                                                            7. In the Gateway and DNS Information area, click following DNS Server Address.
                                                            8. Change the DNS server address to 100.125.4.25.
                                                            9. Click OK.

                                                              The new DNS server address is applied after the ECS or BMS is restarted.

                                                              +
                                                            10. Click the VPC name on the right of VPC to go to the VPC console.
                                                            11. Click the name of the VPC.
                                                            12. In the Networking Components area, click the number following Subnets.

                                                              The Subnets page is displayed.

                                                              +
                                                            13. In the subnet list, click the name of the subnet.
                                                            14. In the Gateway and DNS Information area, click following DNS Server Address.
                                                            15. Change the DNS server address to 100.125.4.25.
                                                            16. Click OK.

                                                              The new DNS server address is applied after the ECS or BMS is restarted.

                                                            diff --git a/docs/ces/umn/en-us_topic_0171694487.html b/docs/ces/umn/en-us_topic_0171694487.html new file mode 100644 index 000000000..3a1593bbc --- /dev/null +++ b/docs/ces/umn/en-us_topic_0171694487.html @@ -0,0 +1,31 @@ + + +

                                                            One-Click Monitoring

                                                            +

                                                            Scenarios

                                                            One-click monitoring allows you to quickly enable alarm reporting for all resources. This helps you quickly establish a monitoring and alarm system and receive notifications in a timely manner when resources are abnormal. When one-click monitoring is enabled, the alarm rules you selected are added to the alarm rule list. When one-click monitoring is disabled, these alarm rules are deleted from the alarm rule list.

                                                            +

                                                            This topic describes how to use one-click monitoring to monitor key metrics or events.

                                                            +
                                                            +

                                                            Constraints

                                                            • Once the alarm threshold is reached, one-click monitoring will trigger alarms immediately.
                                                            • Alarm policies cannot be modified in one-click monitoring.
                                                            +
                                                            +

                                                            Enabling One-Click Monitoring

                                                            1. Log in to the management console.
                                                            2. Choose Service List > Cloud Eye.
                                                            3. In the navigation pane on the left, choose Alarm Management > One-Click Monitoring.
                                                            4. Locate the cloud service you want to enable one-click monitoring and turn on the toggle in the One-Click Monitoring column.
                                                              Figure 1 Enabling one-click monitoring
                                                              +
                                                            5. On the Enable Alarm Rule page, all alarm rules are enabled by default. If you do not want to enable one-click monitoring for certain alarm rules, turn off the toggle in the One-Click Monitoring column of those alarm rules.
                                                            6. Configure alarm notification parameters as prompted. For details, see Table 4.
                                                            7. Review and confirm parameter settings. Then, click OK.
                                                            +
                                                            +

                                                            Enabling or Disabling an Alarm Rule

                                                            After one-click monitoring is enabled for a cloud service, you can enable or disable the alarm rules of the cloud service.

                                                            +
                                                            1. Log in to the management console.
                                                            2. Choose Service List > Cloud Eye.
                                                            3. In the navigation pane on the left, choose Alarm Management > One-Click Monitoring.
                                                            4. Click the drop-down button on the left of the cloud service to view the associated alarm rules.
                                                            5. Turn on or off the toggle in the One-Click Monitoring column of the alarm rule to enable or disable the alarm rule.
                                                              Figure 2 Viewing alarm rules
                                                              +
                                                            +
                                                            +

                                                            Enabling or Disabling an Alarm Policy

                                                            When an alarm rule of one-click monitoring is enabled, all alarm policies under the alarm rule are enabled by default. You can enable or disable them as needed.

                                                            +
                                                            1. Log in to the management console.
                                                            2. Choose Service List > Cloud Eye.
                                                            3. In the navigation pane on the left, choose Alarm Management > One-Click Monitoring.
                                                            4. Click the drop-down button on the left of the cloud service to view the associated alarm rules.
                                                            5. Click the drop-down button on the left of the alarm rule to view the associated alarm policies.
                                                            6. Turn on or off the toggle in the One-Click Monitoring column of the alarm policy to enable or disable the alarm policy.
                                                            +
                                                            +

                                                            Batch Modifying Alarm Notifications

                                                            When one-click monitoring is enabled for a cloud service, you can modify alarm notifications in batches. Once modified, the new notification settings are applied to all the alarm rules for that cloud service.

                                                            +
                                                            1. Log in to the management console.
                                                            2. Choose Service List > Cloud Eye.
                                                            3. In the navigation pane on the left, choose Alarm Management > One-Click Monitoring.
                                                            4. Locate the cloud service you want to modify alarm notifications for, and click Batch Modify Alarm Notifications in the Operation column.
                                                            5. In the Batch Modify Alarm Notifications dialog box, set alarm notification parameters. For details, see Table 4.
                                                            6. Click OK.
                                                            +
                                                            +

                                                            Modifying Alarm Notifications of a Specified Alarm Rule

                                                            You can also modify alarm notifications of a specified alarm rule for a cloud service.

                                                            +
                                                            1. Log in to the management console.
                                                            2. Choose Service List > Cloud Eye.
                                                            3. In the navigation pane on the left, choose Alarm Management > One-Click Monitoring.
                                                            4. Click the drop-down button on the left of the cloud service to view the associated alarm rules.
                                                            5. Locate the alarm rule and click Modify Alarm Notifications in the Operation column.
                                                            6. In the Modify Alarm Notifications dialog box, set alarm notification parameters. For details, see Table 4.
                                                            +
                                                            +
                                                            +
                                                            +
                                                            +
                                                            Parent topic: Using the Alarm Function
                                                            +
                                                            +
                                                            + diff --git a/docs/ces/umn/en-us_topic_0202622212.html b/docs/ces/umn/en-us_topic_0202622212.html index 3011fb6ca..4fd913ee7 100644 --- a/docs/ces/umn/en-us_topic_0202622212.html +++ b/docs/ces/umn/en-us_topic_0202622212.html @@ -2,207 +2,246 @@

                                                            Services Interconnected with Cloud Eye

                                                            -
                                                            Table 1 Installation package path

                                                            Name

                                                            Format

                                                            +

                                                            Format

                                                            Download Path

                                                            +

                                                            Download Path

                                                            Installation package for 64-bit Windows

                                                            +

                                                            Installation package for 64-bit Windows

                                                            zip

                                                            +

                                                            zip

                                                            EU-DE: http://telescope-eu-de.obs.eu-de.otc.t-systems.com/agent/telescope_windows_amd64.zip

                                                            -

                                                            EU-NL: http://telescope-eu-nl.obs.eu-nl.otc.t-systems.com/agent/telescope_windows_amd64.zip

                                                            +
                                                            EU DE:
                                                            https://uniagent-eu-de.obs.eu-de.otc.t-systems.com/package/install_amd64.exe
                                                            +
                                                            +
                                                            EU NL:
                                                            https://uniagent-eu-nl.obs.eu-nl.otc.t-systems.com/package/install_amd64.exe
                                                            +

                                                            Category

                                                            +
                                                            - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + - - - + + +
                                                            Table 1 Cloud service metrics

                                                            Category

                                                            Service

                                                            +

                                                            Service

                                                            Namespace

                                                            +

                                                            Namespace

                                                            Reference

                                                            +

                                                            Reference

                                                            Compute

                                                            +

                                                            Compute

                                                            +

                                                            Elastic Cloud Server

                                                            +

                                                            Elastic Cloud Server

                                                            SYS.ECS

                                                            +

                                                            SYS.ECS

                                                            Basic ECS metrics

                                                            +

                                                            Basic ECS metrics

                                                            Bare Metal Server

                                                            +

                                                            Bare Metal Server

                                                            SERVICE.BMS

                                                            +

                                                            SERVICE.BMS

                                                            BMS metrics (with the Agent installed)

                                                            +

                                                            BMS metrics (with the Agent installed)

                                                            Auto Scaling

                                                            +

                                                            Auto Scaling

                                                            SYS.AS

                                                            +

                                                            SYS.AS

                                                            AS metrics

                                                            +

                                                            AS metrics

                                                            Storage

                                                            +

                                                            Storage

                                                            Elastic Volume Service (attached to an ECS or BMS)

                                                            +

                                                            Elastic Volume Service (attached to an ECS or BMS)

                                                            SYS.EVS

                                                            +

                                                            SYS.EVS

                                                            EVS metrics

                                                            +

                                                            EVS metrics

                                                            Object Storage Service

                                                            +

                                                            Object Storage Service

                                                            SYS.OBS

                                                            +

                                                            SYS.OBS

                                                            OBS metrics

                                                            +

                                                            OBS metrics

                                                            Scalable File Service

                                                            +

                                                            Scalable File Service

                                                            SYS.SFS

                                                            +

                                                            SYS.SFS

                                                            SFS metrics

                                                            +

                                                            SFS metrics

                                                            SFS Turbo

                                                            +

                                                            SFS Turbo

                                                            SYS.EFS

                                                            +

                                                            SYS.EFS

                                                            SFS Turbo metrics

                                                            +

                                                            SFS Turbo metrics

                                                            Cloud Backup and Recovery

                                                            +

                                                            Cloud Backup and Recovery

                                                            SYS.CBR

                                                            +

                                                            SYS.CBR

                                                            CBR metrics

                                                            +

                                                            CBR metrics

                                                            Network

                                                            +

                                                            Networking

                                                            Elastic IP and bandwidth

                                                            +

                                                            Elastic IP and bandwidth

                                                            SYS.VPC

                                                            +

                                                            SYS.VPC

                                                            VPC metrics

                                                            +

                                                            VPC metrics

                                                            Elastic Load Balance

                                                            +

                                                            Elastic Load Balance

                                                            SYS.ELB

                                                            +

                                                            SYS.ELB

                                                            ELB metrics

                                                            +

                                                            ELB metrics

                                                            Direct Connect

                                                            +

                                                            Direct Connect

                                                            SYS.DCAAS

                                                            +

                                                            SYS.DCAAS

                                                            Direct Connect metrics

                                                            +

                                                            Direct Connect metrics

                                                            NAT Gateway

                                                            +

                                                            NAT Gateway

                                                            SYS.NAT

                                                            +

                                                            SYS.NAT

                                                            NAT Gateway metrics

                                                            +

                                                            NAT Gateway metrics

                                                            Virtual Private Network

                                                            +

                                                            Virtual Private Network

                                                            SYS.VPN

                                                            +

                                                            SYS.VPN

                                                            VPN metrics

                                                            +

                                                            VPN metrics

                                                            Security

                                                            +

                                                            Security and Compliance

                                                            Web Application Firewall

                                                            +

                                                            Web Application Firewall

                                                            SYS.WAF

                                                            +

                                                            SYS.WAF

                                                            WAF metrics

                                                            +

                                                            WAF metrics

                                                            Application

                                                            +

                                                            Application Services

                                                            Distributed Message Service

                                                            +

                                                            Distributed Message Service

                                                            SYS.DMS

                                                            +

                                                            SYS.DMS

                                                            DMS metrics

                                                            +

                                                            DMS metrics

                                                            Distributed Cache Service

                                                            +

                                                            Distributed Cache Service

                                                            SYS.DCS

                                                            +

                                                            SYS.DCS

                                                            DCS metrics

                                                            +

                                                            DCS metrics

                                                            API Gateway

                                                            +

                                                            API Gateway

                                                            SYS.APIC

                                                            +

                                                            SYS.APIC

                                                            API Gateway metrics

                                                            +

                                                            API Gateway metrics

                                                            Database

                                                            +

                                                            Databases

                                                            Relational Database Service

                                                            +

                                                            Relational Database Service

                                                            SYS.RDS

                                                            +

                                                            SYS.RDS

                                                            RDS for MySQL metrics

                                                            +

                                                            RDS for MySQL metrics

                                                            RDS for PostgreSQL metrics

                                                            RDS for SQL Server metrics

                                                            Document Database Service

                                                            +

                                                            Document Database Service

                                                            SYS.DDS

                                                            +

                                                            SYS.DDS

                                                            DDS metrics

                                                            +

                                                            DDS metrics

                                                            GeminiDB

                                                            +

                                                            GeminiDB

                                                            SYS.NoSQL

                                                            +

                                                            SYS.NoSQL

                                                            GeminiDB metrics

                                                            +

                                                            GeminiDB metrics

                                                            GaussDB(for MySQL)

                                                            +

                                                            TaurusDB

                                                            SYS.GAUSSDB

                                                            +

                                                            SYS.GAUSSDB

                                                            GaussDB(for MySQL) metrics

                                                            +

                                                            TaurusDB metrics

                                                            GaussDB(for openGauss)

                                                            +

                                                            GaussDB(for openGauss)

                                                            SYS.GAUSSDBV5

                                                            +

                                                            SYS.GAUSSDBV5

                                                            GaussDB(for openGauss) metrics

                                                            +

                                                            GaussDB(for openGauss) metrics

                                                            Data analysis

                                                            +

                                                            Distributed Database Middleware

                                                            Data Warehouse Service

                                                            +

                                                            SYS.DDM (DDM 1.0)

                                                            +

                                                            SYS.DDMS (DDM 2.0)

                                                            SYS.DWS

                                                            -

                                                            DWS metrics

                                                            +

                                                            DDM instance metrics

                                                            +

                                                            DDM network metrics

                                                            Cloud Search Service

                                                            +

                                                            Data Analytics

                                                            SYS.ES

                                                            +

                                                            Data Warehouse Service

                                                            CSS metrics

                                                            +

                                                            SYS.DWS

                                                            +

                                                            DWS metrics

                                                            Data Ingestion Service (DIS)

                                                            +

                                                            Cloud Search Service

                                                            SYS.DAYU

                                                            +

                                                            SYS.ES

                                                            DIS Metrics

                                                            +

                                                            CSS metrics

                                                            +
                                                            +
                                                            +

                                                            In addition to the preceding cloud services, the following cloud services also support event monitoring. For details about monitored events, see Events Supported by Event Monitoring.

                                                            + +
                                                            + + + + + + + + + + + + + + + + + diff --git a/docs/ces/umn/index.html b/docs/ces/umn/index.html index aed63ff00..678ba3d2c 100644 --- a/docs/ces/umn/index.html +++ b/docs/ces/umn/index.html @@ -5,14 +5,12 @@
                                                            Table 2 Cloud services that support event monitoring only

                                                            Service

                                                            +

                                                            Namespace

                                                            +

                                                            Cloud Eye (CES)

                                                            +

                                                            SYS.CES

                                                            +

                                                            Host Security Service (HSS)

                                                            +

                                                            SYS.HSS

                                                            +

                                                            Identity and Access Management (IAM)

                                                            +

                                                            SYS.IAM

                                                            +

                                                            Image Management Service (IMS)

                                                            +

                                                            SYS.IMS

                                                            +

                                                            Key Management Service (KMS)

                                                            +

                                                            SYS.KMS