diff --git a/docs/ces/api-ref/ALL_META.TXT.json b/docs/ces/api-ref/ALL_META.TXT.json new file mode 100644 index 000000000..6e9f6bc7d --- /dev/null +++ b/docs/ces/api-ref/ALL_META.TXT.json @@ -0,0 +1,322 @@ +[ + { + "uri":"ces_03_0001.html", + "product_code":"ces", + "code":"1", + "des":"Public cloud APIs comply with the RESTful API design principles. REST-based Web services are organized into resources. Each resource is identified by one or more Uniform ", + "doc_type":"api", + "kw":"API Usage Guidelines,API Reference", + "title":"API Usage Guidelines", + "githuburl":"" + }, + { + "uri":"ces_03_0018.html", + "product_code":"ces", + "code":"2", + "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":"api", + "kw":"API Description", + "title":"API Description", + "githuburl":"" + }, + { + "uri":"ces_03_0019.html", + "product_code":"ces", + "code":"3", + "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":"api", + "kw":"API Version Management", + "title":"API Version Management", + "githuburl":"" + }, + { + "uri":"ces_03_0020.html", + "product_code":"ces", + "code":"4", + "des":"This API is used to query all API versions supported by Cloud Eye.GET /Example requestResponse parametersParameter descriptionParameterTypeDescriptionversionsArray of obj", + "doc_type":"api", + "kw":"Querying All API Versions,API Version Management,API Reference", + "title":"Querying All API Versions", + "githuburl":"" + }, + { + "uri":"ces_03_0021.html", + "product_code":"ces", + "code":"5", + "des":"This API is used to query a specified API version of Cloud Eye.GET /{api_version}Parameter descriptionParameter descriptionParameterMandatoryDescriptionapi_versionYesSpec", + "doc_type":"api", + "kw":"Querying a Specified API Version,API Version Management,API Reference", + "title":"Querying a Specified API Version", + "githuburl":"" + }, + { + "uri":"ces_03_0022.html", + "product_code":"ces", + "code":"6", + "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":"api", + "kw":"Metric Management", + "title":"Metric Management", + "githuburl":"" + }, + { + "uri":"ces_03_0023.html", + "product_code":"ces", + "code":"7", + "des":"This API is used to query the metrics. You can specify the namespace, metric, dimension, sorting order, start records, and the maximum number of records when using this A", + "doc_type":"api", + "kw":"Querying Metrics,Metric Management,API Reference", + "title":"Querying Metrics", + "githuburl":"" + }, + { + "uri":"ces_03_0026.html", + "product_code":"ces", + "code":"8", + "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":"api", + "kw":"Alarm Rule Management", + "title":"Alarm Rule Management", + "githuburl":"" + }, + { + "uri":"ces_03_0027.html", + "product_code":"ces", + "code":"9", + "des":"This API is used to query the alarm rule list. You can specify the paging parameters to limit the number of query results displayed on a page. You can also set the sortin", + "doc_type":"api", + "kw":"Querying Alarm Rules,Alarm Rule Management,API Reference", + "title":"Querying Alarm Rules", + "githuburl":"" + }, + { + "uri":"ces_03_0028.html", + "product_code":"ces", + "code":"10", + "des":"This API is used to query an alarm rule based on the alarm rule ID.GET /V1.0/{project_id}/alarms/{alarm_id}Parameter descriptionParameter descriptionParameterMandatoryDes", + "doc_type":"api", + "kw":"Querying an Alarm Rule,Alarm Rule Management,API Reference", + "title":"Querying an Alarm Rule", + "githuburl":"" + }, + { + "uri":"ces_03_0029.html", + "product_code":"ces", + "code":"11", + "des":"This API is used to enable or disable an alarm rule.PUT /V1.0/{project_id}/alarms/{alarm_id}/actionParameter descriptionParameter descriptionParameterMandatoryDescription", + "doc_type":"api", + "kw":"Enabling or Disabling an Alarm Rule,Alarm Rule Management,API Reference", + "title":"Enabling or Disabling an Alarm Rule", + "githuburl":"" + }, + { + "uri":"ces_03_0030.html", + "product_code":"ces", + "code":"12", + "des":"This API is used to delete an alarm rule.DELETE /V1.0/{project_id}/alarms/{alarm_id}Parameter descriptionParameter descriptionParameterMandatoryDescriptionproject_idYesSp", + "doc_type":"api", + "kw":"Deleting an Alarm Rule,Alarm Rule Management,API Reference", + "title":"Deleting an Alarm Rule", + "githuburl":"" + }, + { + "uri":"ces_03_0031.html", + "product_code":"ces", + "code":"13", + "des":"This API is used to create an alarm rule.POST /V1.0/{project_id}/alarmsParameter descriptionParameter descriptionParameterMandatoryDescriptionproject_idYesSpecifies the p", + "doc_type":"api", + "kw":"Creating an Alarm Rule,Alarm Rule Management,API Reference", + "title":"Creating an Alarm Rule", + "githuburl":"" + }, + { + "uri":"ces_03_0032.html", + "product_code":"ces", + "code":"14", + "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":"api", + "kw":"Monitoring Data Management", + "title":"Monitoring Data Management", + "githuburl":"" + }, + { + "uri":"ces_03_0033.html", + "product_code":"ces", + "code":"15", + "des":"This API is used to query the monitoring data at a specified granularity for a specified metric in a specified period of time. You can specify the dimension of data to be", + "doc_type":"api", + "kw":"Querying Monitoring Data,Monitoring Data Management,API Reference", + "title":"Querying Monitoring Data", + "githuburl":"" + }, + { + "uri":"en-us_topic_0032831274.html", + "product_code":"ces", + "code":"16", + "des":"This API is used to add one or more pieces of custom metric monitoring data to solve the problem that the system metrics cannot meet specific service requirements.POST /V", + "doc_type":"api", + "kw":"Adding Monitoring Data,Monitoring Data Management,API Reference", + "title":"Adding Monitoring Data", + "githuburl":"" + }, + { + "uri":"ces_03_0034.html", + "product_code":"ces", + "code":"17", + "des":"You can query the monitoring data of specified metrics within a specified time range and specified granularities in batches. At present, you can query the monitoring data", + "doc_type":"api", + "kw":"Querying Monitoring Data in Batches,Monitoring Data Management,API Reference", + "title":"Querying Monitoring Data in Batches", + "githuburl":"" + }, + { + "uri":"ces_03_0035.html", + "product_code":"ces", + "code":"18", + "des":"This API is used to query the host configuration for a specified event type in a specified period of time. You can specify the dimension of data to be queried.This API is", + "doc_type":"api", + "kw":"Querying the Host Configuration,Monitoring Data Management,API Reference", + "title":"Querying the Host Configuration", + "githuburl":"" + }, + { + "uri":"ces_03_0036.html", + "product_code":"ces", + "code":"19", + "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":"api", + "kw":"Quota Management", + "title":"Quota Management", + "githuburl":"" + }, + { + "uri":"ces_03_0037.html", + "product_code":"ces", + "code":"20", + "des":"This API is used to query a resource quota and the used amount. The current resource refers to alarm rules only.GET /V1.0/{project_id}/quotasParameter descriptionParamete", + "doc_type":"api", + "kw":"Querying Quotas,Quota Management,API Reference", + "title":"Querying Quotas", + "githuburl":"" + }, + { + "uri":"ces_03_0038.html", + "product_code":"ces", + "code":"21", + "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":"api", + "kw":"Event Monitoring", + "title":"Event Monitoring", + "githuburl":"" + }, + { + "uri":"en-us_topic_0109034020.html", + "product_code":"ces", + "code":"22", + "des":"An API for reporting custom events is provided, which helps you collect and report abnormal events or important change events to Cloud Eye.POST /V1.0/{project_id}/eventsP", + "doc_type":"api", + "kw":"Reporting Events,Event Monitoring,API Reference", + "title":"Reporting Events", + "githuburl":"" + }, + { + "uri":"ces_03_0074.html", + "product_code":"ces", + "code":"23", + "des":"This API is used to query the events, including system events and custom events.GET /V1.0/{project_id}/eventsParameter descriptionParameter descriptionParameterTypeMandat", + "doc_type":"api", + "kw":"Querying Events,Event Monitoring,API Reference", + "title":"Querying Events", + "githuburl":"" + }, + { + "uri":"ces_03_0075.html", + "product_code":"ces", + "code":"24", + "des":"This API is used to query the event details based on the event name.GET /V1.0/{project_id}/event/{event_name}Parameter descriptionParameter descriptionParameterTypeMandat", + "doc_type":"api", + "kw":"Querying Monitoring Details of an Event,Event Monitoring,API Reference", + "title":"Querying Monitoring Details of an Event", + "githuburl":"" + }, + { + "uri":"ces_03_0053.html", + "product_code":"ces", + "code":"25", + "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":"api", + "kw":"Common Parameters", + "title":"Common Parameters", + "githuburl":"" + }, + { + "uri":"ces_03_0055.html", + "product_code":"ces", + "code":"26", + "des":"NormalReturned ValueDescription200 OKThe results of GET and PUT operations are returned as expected.201 CreatedThe results of the POST operation are returned as expected.", + "doc_type":"api", + "kw":"Status Codes,Common Parameters,API Reference", + "title":"Status Codes", + "githuburl":"" + }, + { + "uri":"ErrorCode.html", + "product_code":"ces", + "code":"27", + "des":"If an error occurs during API calling, the system returns error information. This section describes the error codes contained in the error information for Cloud Eye APIs.", + "doc_type":"api", + "kw":"Error Codes,Common Parameters,API Reference", + "title":"Error Codes", + "githuburl":"" + }, + { + "uri":"ces_03_0057.html", + "product_code":"ces", + "code":"28", + "des":"A project ID needs to be specified in the URIs of some APIs. Therefore, you need to obtain the project ID before calling APIs. The following procedure describes how to ob", + "doc_type":"api", + "kw":"Obtaining a Project ID,Common Parameters,API Reference", + "title":"Obtaining a Project ID", + "githuburl":"" + }, + { + "uri":"ces_03_0058.html", + "product_code":"ces", + "code":"29", + "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":"api", + "kw":"Appendix", + "title":"Appendix", + "githuburl":"" + }, + { + "uri":"ces_03_0059.html", + "product_code":"ces", + "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":"api", + "kw":"Services Interconnected with Cloud Eye,Appendix,API Reference", + "title":"Services Interconnected with Cloud Eye", + "githuburl":"" + }, + { + "uri":"ces_01_0054.html", + "product_code":"ces", + "code":"31", + "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", + "doc_type":"api", + "kw":"Events Supported by Event Monitoring,Appendix,API Reference", + "title":"Events Supported by Event Monitoring", + "githuburl":"" + }, + { + "uri":"ces_03_0060.html", + "product_code":"ces", + "code":"32", + "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":"api", + "kw":"Change History,API Reference", + "title":"Change History", + "githuburl":"" + } +] \ No newline at end of file diff --git a/docs/ces/api-ref/CLASS.TXT.json b/docs/ces/api-ref/CLASS.TXT.json new file mode 100644 index 000000000..e6688b5bf --- /dev/null +++ b/docs/ces/api-ref/CLASS.TXT.json @@ -0,0 +1,290 @@ +[ + { + "desc":"Public cloud APIs comply with the RESTful API design principles. REST-based Web services are organized into resources. Each resource is identified by one or more Uniform ", + "product_code":"ces", + "title":"API Usage Guidelines", + "uri":"ces_03_0001.html", + "doc_type":"api", + "p_code":"", + "code":"1" + }, + { + "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":"API Description", + "uri":"ces_03_0018.html", + "doc_type":"api", + "p_code":"", + "code":"2" + }, + { + "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":"API Version Management", + "uri":"ces_03_0019.html", + "doc_type":"api", + "p_code":"2", + "code":"3" + }, + { + "desc":"This API is used to query all API versions supported by Cloud Eye.GET /Example requestResponse parametersParameter descriptionParameterTypeDescriptionversionsArray of obj", + "product_code":"ces", + "title":"Querying All API Versions", + "uri":"ces_03_0020.html", + "doc_type":"api", + "p_code":"3", + "code":"4" + }, + { + "desc":"This API is used to query a specified API version of Cloud Eye.GET /{api_version}Parameter descriptionParameter descriptionParameterMandatoryDescriptionapi_versionYesSpec", + "product_code":"ces", + "title":"Querying a Specified API Version", + "uri":"ces_03_0021.html", + "doc_type":"api", + "p_code":"3", + "code":"5" + }, + { + "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":"Metric Management", + "uri":"ces_03_0022.html", + "doc_type":"api", + "p_code":"2", + "code":"6" + }, + { + "desc":"This API is used to query the metrics. You can specify the namespace, metric, dimension, sorting order, start records, and the maximum number of records when using this A", + "product_code":"ces", + "title":"Querying Metrics", + "uri":"ces_03_0023.html", + "doc_type":"api", + "p_code":"6", + "code":"7" + }, + { + "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":"Alarm Rule Management", + "uri":"ces_03_0026.html", + "doc_type":"api", + "p_code":"2", + "code":"8" + }, + { + "desc":"This API is used to query the alarm rule list. You can specify the paging parameters to limit the number of query results displayed on a page. You can also set the sortin", + "product_code":"ces", + "title":"Querying Alarm Rules", + "uri":"ces_03_0027.html", + "doc_type":"api", + "p_code":"8", + "code":"9" + }, + { + "desc":"This API is used to query an alarm rule based on the alarm rule ID.GET /V1.0/{project_id}/alarms/{alarm_id}Parameter descriptionParameter descriptionParameterMandatoryDes", + "product_code":"ces", + "title":"Querying an Alarm Rule", + "uri":"ces_03_0028.html", + "doc_type":"api", + "p_code":"8", + "code":"10" + }, + { + "desc":"This API is used to enable or disable an alarm rule.PUT /V1.0/{project_id}/alarms/{alarm_id}/actionParameter descriptionParameter descriptionParameterMandatoryDescription", + "product_code":"ces", + "title":"Enabling or Disabling an Alarm Rule", + "uri":"ces_03_0029.html", + "doc_type":"api", + "p_code":"8", + "code":"11" + }, + { + "desc":"This API is used to delete an alarm rule.DELETE /V1.0/{project_id}/alarms/{alarm_id}Parameter descriptionParameter descriptionParameterMandatoryDescriptionproject_idYesSp", + "product_code":"ces", + "title":"Deleting an Alarm Rule", + "uri":"ces_03_0030.html", + "doc_type":"api", + "p_code":"8", + "code":"12" + }, + { + "desc":"This API is used to create an alarm rule.POST /V1.0/{project_id}/alarmsParameter descriptionParameter descriptionParameterMandatoryDescriptionproject_idYesSpecifies the p", + "product_code":"ces", + "title":"Creating an Alarm Rule", + "uri":"ces_03_0031.html", + "doc_type":"api", + "p_code":"8", + "code":"13" + }, + { + "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":"Monitoring Data Management", + "uri":"ces_03_0032.html", + "doc_type":"api", + "p_code":"2", + "code":"14" + }, + { + "desc":"This API is used to query the monitoring data at a specified granularity for a specified metric in a specified period of time. You can specify the dimension of data to be", + "product_code":"ces", + "title":"Querying Monitoring Data", + "uri":"ces_03_0033.html", + "doc_type":"api", + "p_code":"14", + "code":"15" + }, + { + "desc":"This API is used to add one or more pieces of custom metric monitoring data to solve the problem that the system metrics cannot meet specific service requirements.POST /V", + "product_code":"ces", + "title":"Adding Monitoring Data", + "uri":"en-us_topic_0032831274.html", + "doc_type":"api", + "p_code":"14", + "code":"16" + }, + { + "desc":"You can query the monitoring data of specified metrics within a specified time range and specified granularities in batches. At present, you can query the monitoring data", + "product_code":"ces", + "title":"Querying Monitoring Data in Batches", + "uri":"ces_03_0034.html", + "doc_type":"api", + "p_code":"14", + "code":"17" + }, + { + "desc":"This API is used to query the host configuration for a specified event type in a specified period of time. You can specify the dimension of data to be queried.This API is", + "product_code":"ces", + "title":"Querying the Host Configuration", + "uri":"ces_03_0035.html", + "doc_type":"api", + "p_code":"14", + "code":"18" + }, + { + "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":"Quota Management", + "uri":"ces_03_0036.html", + "doc_type":"api", + "p_code":"2", + "code":"19" + }, + { + "desc":"This API is used to query a resource quota and the used amount. The current resource refers to alarm rules only.GET /V1.0/{project_id}/quotasParameter descriptionParamete", + "product_code":"ces", + "title":"Querying Quotas", + "uri":"ces_03_0037.html", + "doc_type":"api", + "p_code":"19", + "code":"20" + }, + { + "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":"Event Monitoring", + "uri":"ces_03_0038.html", + "doc_type":"api", + "p_code":"2", + "code":"21" + }, + { + "desc":"An API for reporting custom events is provided, which helps you collect and report abnormal events or important change events to Cloud Eye.POST /V1.0/{project_id}/eventsP", + "product_code":"ces", + "title":"Reporting Events", + "uri":"en-us_topic_0109034020.html", + "doc_type":"api", + "p_code":"21", + "code":"22" + }, + { + "desc":"This API is used to query the events, including system events and custom events.GET /V1.0/{project_id}/eventsParameter descriptionParameter descriptionParameterTypeMandat", + "product_code":"ces", + "title":"Querying Events", + "uri":"ces_03_0074.html", + "doc_type":"api", + "p_code":"21", + "code":"23" + }, + { + "desc":"This API is used to query the event details based on the event name.GET /V1.0/{project_id}/event/{event_name}Parameter descriptionParameter descriptionParameterTypeMandat", + "product_code":"ces", + "title":"Querying Monitoring Details of an Event", + "uri":"ces_03_0075.html", + "doc_type":"api", + "p_code":"21", + "code":"24" + }, + { + "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":"Common Parameters", + "uri":"ces_03_0053.html", + "doc_type":"api", + "p_code":"", + "code":"25" + }, + { + "desc":"NormalReturned ValueDescription200 OKThe results of GET and PUT operations are returned as expected.201 CreatedThe results of the POST operation are returned as expected.", + "product_code":"ces", + "title":"Status Codes", + "uri":"ces_03_0055.html", + "doc_type":"api", + "p_code":"25", + "code":"26" + }, + { + "desc":"If an error occurs during API calling, the system returns error information. This section describes the error codes contained in the error information for Cloud Eye APIs.", + "product_code":"ces", + "title":"Error Codes", + "uri":"ErrorCode.html", + "doc_type":"api", + "p_code":"25", + "code":"27" + }, + { + "desc":"A project ID needs to be specified in the URIs of some APIs. Therefore, you need to obtain the project ID before calling APIs. The following procedure describes how to ob", + "product_code":"ces", + "title":"Obtaining a Project ID", + "uri":"ces_03_0057.html", + "doc_type":"api", + "p_code":"25", + "code":"28" + }, + { + "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":"Appendix", + "uri":"ces_03_0058.html", + "doc_type":"api", + "p_code":"", + "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.", + "product_code":"ces", + "title":"Services Interconnected with Cloud Eye", + "uri":"ces_03_0059.html", + "doc_type":"api", + "p_code":"29", + "code":"30" + }, + { + "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", + "product_code":"ces", + "title":"Events Supported by Event Monitoring", + "uri":"ces_01_0054.html", + "doc_type":"api", + "p_code":"29", + "code":"31" + }, + { + "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":"Change History", + "uri":"ces_03_0060.html", + "doc_type":"api", + "p_code":"", + "code":"32" + } +] \ No newline at end of file diff --git a/docs/ces/api-ref/ErrorCode.html b/docs/ces/api-ref/ErrorCode.html new file mode 100644 index 000000000..45e8d38d6 --- /dev/null +++ b/docs/ces/api-ref/ErrorCode.html @@ -0,0 +1,312 @@ + + +
If an error occurs during API calling, the system returns error information. This section describes the error codes contained in the error information for Cloud Eye APIs.
+{
+ "code": 400,
+ "element": "Bad Request",
+ "message": "The system received a request which cannot be recognized",
+ "details": {
+ "details": "Some content in message body is not correct",
+ "code": "ces.0014"
+ }
+}
+Glossary + |
+Description + |
+
|---|---|
Cloud Eye + |
+Cloud Eye + |
+
Built-in metric + |
+Each service has its own built-in metrics and dimensions. For example, an ECS (SYS.ECS) supports cpu_util. + |
+
Metric + |
+A metric consists of the namespace, dimension (optional), and metric name. A metric name solely does not identify any object. + |
+
Module + |
+HTTP Status Code + |
+Error Code + |
+Error Code Description + |
+Error Message + |
+Measure + |
+
|---|---|---|---|---|---|
Cloud Eye + |
+500 + |
+ces.0007 + |
+Internal service error + |
+Internal service error. + |
+Contact technical support. + |
+
API + |
+400 + |
+ces.0001 + |
+The request content cannot be empty. + |
+The content must be specified. + |
+Specify the request content. + |
+
400 + |
+ces.0003 + |
+The project ID is left blank or is incorrect. + |
+The tenant ID is left blank or incorrect. + |
+Add or use the correct tenant ID. + |
+|
400 + |
+ces.0004 + |
+The API version is not specified. + |
+The API version must be specified. + |
+Specify the API version in the request URL. + |
+|
400 + |
+ces.0005 + |
+The API version is incorrect. + |
+The API version is incorrect. + |
+Use the correct API version. + |
+|
400 + |
+ces.0006 + |
+The paging address is incorrect. + |
+The paging address is incorrect. + |
+Use correct pagination information. + |
+|
403 + |
+ces.0009 + |
+System metrics cannot be added. + |
+Adding SYS metric is not allowed + |
+Use correct rights to add metrics. + |
+|
403 + |
+ces.0010 + |
+System metrics cannot be deleted. + |
+Deleting SYS metric is not allowed + |
+Use correct rights to delete metrics. + |
+|
400 + |
+ces.0011 + |
+The request is invalid. + |
+The request is invalid. + |
+Check the request. + |
+|
400 + |
+ces.0013 + |
+The URL parameter is invalid or does not exist. + |
+The URL parameter is invalid or does not exist. + |
+Check the URL parameter. + |
+|
400 + |
+ces.0014 + |
+Some content in the message body is correct. + |
+Some content in message body is not correct. + |
+Check the request body parameters. + |
+|
401 + |
+ces.0015 + |
+Authentication fails or valid authentication information is not provided. + |
+Authentication fails or the authentication information is not provided. + |
+Check whether the user name or password (or AK or SK) for obtaining the token is correct. + |
+|
404 + |
+ces.0016 + |
+The requested resource does not exist. + |
+The requested resource does not exist. + |
+Check whether the requested resource exists. + |
+|
403 + |
+ces.0017 + |
+The authentication information is incorrect or the service invoker does not have sufficient rights. + |
+The authentication information is incorrect or the service invoker does not have sufficient rights. + |
+Check whether the user name or password (or AK or SK) or the user rights for obtaining the token are correct. + |
+|
Cassandra + |
+500 + |
+ces.0008 + |
+Database error + |
+Database error. + |
+Contact technical support. + |
+
Kafka + |
+500 + |
+ces.0012 + |
+The message queue is abnormal or is not ready. + |
+The message queue is abnormal or is not ready. + |
+Contact technical support. + |
+
Zookeeper + |
+500 + |
+ces.0021 + |
+Internal locking error + |
+Internal locking error + |
+Contact technical support. + |
+
Blueflood + |
+500 + |
+ces.0019 + |
+The metric processing engine is abnormal. + |
+The metric processing engine is abnormal. + |
+Contact technical support. + |
+
Alarm + |
+400 + |
+ces.0002 + |
+The alarm ID cannot be left blank. + |
+The alarm ID must be specified. + |
+Specify the alarm ID. + |
+
403 + |
+ces.0018 + |
+The number of alarm rules created exceeds the quota. + |
+The number of alarms exceeds the quota + |
+Apply for a higher alarm quota. + |
+|
400 + |
+ces.0028 + |
+The metric and notification type do not match when an alarm rule is created. + |
+The metric does not support the alarm action type. + |
+Modify the metric or notification type according to the parameter description to make them match. + |
+
Events in Event Monitoring come from operations on cloud service resources and are not collected by the Agent in Server Monitoring.
+Event Source + |
+Event Name + |
+Event ID + |
+Event Severity + |
+Description + |
+Solution + |
+Impact + |
+
|---|---|---|---|---|---|---|
ECS + |
+Delete ECS + |
+deleteServer + |
+Major + |
+The ECS was deleted +
|
+Check whether the deletion was performed intentionally by a user. + |
+Services are interrupted. + |
+
Reboot ECS + |
+rebootServer + |
+Minor + |
+The ECS was restarted +
|
+Check whether the restart was performed intentionally by a user. +
|
+Services are interrupted. + |
+|
Resize ECS + |
+resizeServer + |
+Minor + |
+The ECS was resized +
|
+
|
+Services are interrupted. + |
+|
Start auto recovery + |
+startAutoRecovery + |
+Major + |
+ECSs on a faulty host would be automatically migrated to another properly-running host. During the migration, the ECSs was restarted. + |
+Wait for the event to end and check whether services are affected. + |
+Services may be interrupted. + |
+|
Stop auto recovery + |
+endAutoRecovery + |
+Major + |
+The ECS was restored to be normal after the automatic migration. + |
+This event indicates that the ECS has been recovered and been working properly. + |
+None + |
+|
Auto recovery timeout (being processed on the backend) + |
+faultAutoRecovery + |
+Major + |
+Migrating the ECS to a normal host timed out. + |
+Migrate services to other ECSs. + |
+Services are interrupted. + |
+|
Improper ECS running + |
+vmIsRunningImproperly + |
+Major + |
+The ECS was faulty or the ECS NIC was abnormal. + |
+Deploy service applications in HA mode. +After the fault is rectified, check whether services recover. + |
+Services are interrupted. + |
+|
Improper ECS running recovered + |
+vmIsRunningImproperlyRecovery + |
+Major + |
+The ECS was restored to the normal status. + |
+Wait for the ECS status to become normal and check whether services are affected. + |
+None + |
+|
VM faults caused by host process exceptions + |
+VMFaultsByHostProcessExceptions + |
+Critical + |
+The processes of the host accommodating the ECS were abnormal. + |
+Contact O&M personnel. + |
+The ECS is faulty. + |
+|
Restarted GuestOS + |
+RestartGuestOS + |
+Minor + |
+The guest OS was restarted. + |
+Contact O&M personnel. + |
+Services may be interrupted. + |
+
Once a physical host running ECSs breaks down, the ECSs are automatically migrated to a functional physical host. During the migration, the ECSs will be restarted.
+Event Source + |
+Event Name + |
+Event ID + |
+Event Severity + |
+Description + |
+Solution + |
+Impact + |
+
|---|---|---|---|---|---|---|
AAD + |
+DDoS Attack Events + |
+ddosAttackEvents + |
+Major + |
+A DDoS attack occurs in the AAD protected lines. + |
+Judge the impact on services based on the attack traffic and attack type. If the attack traffic exceeds your purchased elastic bandwidth, change to another line or increase your bandwidth. + |
+Services may be interrupted. + |
+
Event Source + |
+Event Name + |
+Event ID + |
+Event Severity + |
+Description + |
+Solution + |
+Impact + |
+
|---|---|---|---|---|---|---|
CBR + |
+Failed to create the backup. + |
+backupFailed + |
+Critical + |
+The backup failed to be created. + |
+Manually create a backup or contact customer service. + |
+Data loss may occur. + |
+
Failed to restore the resource using a backup. + |
+restorationFailed + |
+Critical + |
+The resource failed to be restored using a backup. + |
+Restore the resource using another backup or contact customer service. + |
+Data loss may occur. + |
+|
Failed to delete the backup. + |
+backupDeleteFailed + |
+Critical + |
+The backup failed to be deleted. + |
+Try again later or contact customer service. + |
+Charging may be abnormal. + |
+|
Failed to delete the vault. + |
+vaultDeleteFailed + |
+Critical + |
+The vault failed to be deleted. + |
+Try again later or contact technical support. + |
+Charging may be abnormal. + |
+|
Replication failure + |
+replicationFailed + |
+Critical + |
+The backup failed to be replicated. + |
+Try again later or contact technical support. + |
+Data loss may occur. + |
+|
The backup is created successfully. + |
+backupSucceeded + |
+Major + |
+The backup was created. + |
+None + |
+None + |
+|
Resource restoration using a backup succeeded. + |
+restorationSucceeded + |
+Major + |
+The resource was restored using a backup. + |
+Check whether the data is successfully restored. + |
+None + |
+|
The backup is deleted successfully. + |
+backupDeletionSucceeded + |
+Major + |
+The backup was deleted. + |
+None + |
+None + |
+|
The vault is deleted successfully. + |
+vaultDeletionSucceeded + |
+Major + |
+The vault was deleted. + |
+None + |
+None + |
+|
Replication success + |
+replicationSucceeded + |
+Major + |
+The backup was replicated successfully. + |
+None + |
+None + |
+
Event Source + |
+Event Name + |
+Event ID + |
+Event Severity + |
+Description + |
+Solution + |
+Impact + |
+
|---|---|---|---|---|---|---|
RDS + |
+Full backup failure + |
+fullBackupFailed + |
+Major + |
+A single full backup failure does not affect the files that have been successfully backed up, but prolong the incremental backup time during the point-in-time restore (PITR). + |
+Create a manual backup again. + |
+Backup failed. + |
+
Primary/standby switchover or failover + |
+PrimaryStandbySwitched + |
+Major + |
+This event is reported when a primary/standby switchover or a failover is triggered. + |
+
|
+Downtime occurs during the switchover. + |
+|
Replication status abnormal + |
+abnormalReplicationStatus + |
+Major + |
+The possible causes are as follows: +The replication delay between the primary and standby instances is too long, which usually occurs when a large amount of data is written to databases or a large transaction is processed. During peak hours, data may be blocked. +The network between the primary and standby instances is disconnected. + |
+Submit a service ticket. + |
+Your applications are not affected because this event does not interrupt data read and write. + |
+|
Replication status recovered + |
+replicationStatusRecovered + |
+Major + |
+The replication delay between the primary and standby instances is within the normal range, or the network connection between them has restored. + |
+No action is required. + |
+None + |
+|
DB instance faulty + |
+faultyDBInstance + |
+Major + |
+A single or primary DB instance was faulty due to a disaster or a server failure. + |
+Check whether an automated backup policy has been configured for the DB instance and submit a service ticket. + |
+The database service may be unavailable. + |
+|
DB instance recovered + |
+DBInstanceRecovered + |
+Major + |
+RDS rebuilds the standby DB instance with its high availability. After the instance is rebuilt, this event will be reported. + |
+No action is required. + |
+None + |
+|
Failure of changing single DB instance to primary/standby + |
+singleToHaFailed + |
+Major + |
+A fault occurs when RDS is creating the standby DB instance or configuring replication between the primary and standby DB instances. The fault may occur because resources are insufficient in the data center where the standby DB instance is located. + |
+Submit a service ticket. + |
+Your applications are not affected because this event does not interrupt data read and write of the DB instance. + |
+|
Database process restarted + |
+DatabaseProcessRestarted + |
+Major + |
+The database process is stopped due to insufficient memory or high load. + |
+Log in to the Cloud Eye console. Check whether the memory usage increases sharply, the CPU usage is too high for a long time, or the storage space is insufficient. You can increase the CPU and memory specifications or optimize the service logic. + |
+Downtime occurs. When this happens, RDS automatically restarts the database process and attempts to recover the workloads. + |
+|
Instance storage full + |
+instanceDiskFull + |
+Major + |
+Generally, the cause is that the data space usage is too high. + |
+Scale up the instance. + |
+The DB instance becomes read-only because the storage space is full, and data cannot be written to the database. + |
+|
Instance storage full recovered + |
+instanceDiskFullRecovered + |
+Major + |
+The instance disk is recovered. + |
+No action is required. + |
+Cancel the read-only state of the instance and resume write operations. + |
+|
Read replica promotion failure + |
+activeStandBySwitchFailed + |
+Major + |
+The read replica fails to be promoted to the primary DB instance due to network or server failures. The original primary DB instance takes over workloads quickly. + |
+Submit a service ticket. + |
+The read replica fails to be promoted to the primary DB instance. + |
+
Event Source + |
+Event Name + |
+Event ID + |
+Event Severity + |
+Description + |
+Solution + |
+Impact + |
+
|---|---|---|---|---|---|---|
GaussDB(for MySQL) + |
+Incremental backup failure + |
+TaurusIncrementalBackupInstanceFailed + |
+Major + |
+The network between the instance and the management plane (or the OBS) is disconnected, or the backup environment created for the instance is abnormal. + |
+Submit a service ticket. + |
+Backup jobs fail. + |
+
Read replica creation failure + |
+addReadonlyNodesFailed + |
+Major + |
+The quota is insufficient or underlying resources are exhausted. + |
+Check the read replica quota. Release resources and create read replicas again. + |
+Read replicas fail to be created. + |
+|
DB instance creation failure + |
+createInstanceFailed + |
+Major + |
+The instance quota or underlying resources are insufficient. + |
+Check the instance quota. Release resources and create instances again. + |
+DB instances fail to be created. + |
+|
Read replica promotion failure + |
+activeStandBySwitchFailed + |
+Major + |
+The read replica fails to be promoted to the primary node due to network or server failures. The original primary node takes over services quickly. + |
+Submit a service ticket. + |
+The read replica fails to be promoted to the primary node. + |
+|
Instance specifications change failure + |
+flavorAlterationFailed + |
+Major + |
+The quota is insufficient or underlying resources are exhausted. + |
+Submit a service ticket. + |
+Instance specifications fail to be changed. + |
+|
Faulty DB instance + |
+TaurusInstanceRunningStatusAbnormal + |
+Major + |
+The instance process is faulty or the communications between the instance and the DFV storage are abnormal. + |
+Submit a service ticket. + |
+Services may be affected. + |
+|
DB instance recovered + |
+TaurusInstanceRunningStatusRecovered + |
+Major + |
+The instance is recovered. + |
+Observe the service running status. + |
+None + |
+|
Faulty node + |
+TaurusNodeRunningStatusAbnormal + |
+Major + |
+The node process is faulty or the communications between the node and the DFV storage are abnormal. + |
+Observe the instance and service running statuses. + |
+A read replica may be promoted to the primary node. + |
+|
Node recovered + |
+TaurusNodeRunningStatusRecovered + |
+Major + |
+The node is recovered. + |
+Observe the service running status. + |
+None + |
+|
Read replica deletion failure + |
+TaurusDeleteReadOnlyNodeFailed + |
+Major + |
+The communications between the management plane and the read replica are abnormal or the VM fails to be deleted from IaaS. + |
+Submit a service ticket. + |
+Read replicas fail to be deleted. + |
+|
Password reset failure + |
+TaurusResetInstancePasswordFailed + |
+Major + |
+The communications between the management plane and the instance are abnormal or the instance is abnormal. + |
+Check the instance status and try again. If the fault persists, submit a service ticket. + |
+Passwords fail to be reset for instances. + |
+|
DB instance reboot failure + |
+TaurusRestartInstanceFailed + |
+Major + |
+The network between the management plane and the instance is abnormal or the instance is abnormal. + |
+Check the instance status and try again. If the fault persists, submit a service ticket. + |
+Instances fail to be rebooted. + |
+|
Restoration to new DB instance failure + |
+TaurusRestoreToNewInstanceFailed + |
+Major + |
+The instance quota is insufficient, underlying resources are exhausted, or the data restoration logic is incorrect. + |
+If the new instance fails to be created, check the instance quota, release resources, and try to restore to a new instance again. In other cases, submit a service ticket. + |
+Backup data fails to be restored to new instances. + |
+|
EIP binding failure + |
+TaurusBindEIPToInstanceFailed + |
+Major + |
+The binding task fails. + |
+Submit a service ticket. + |
+EIPs fail to be bound to instances. + |
+|
EIP unbinding failure + |
+TaurusUnbindEIPFromInstanceFailed + |
+Major + |
+The unbinding task fails. + |
+Submit a service ticket. + |
+EIPs fail to be unbound from instances. + |
+|
Parameter modification failure + |
+TaurusUpdateInstanceParameterFailed + |
+Major + |
+The network between the management plane and the instance is abnormal or the instance is abnormal. + |
+Check the instance status and try again. If the fault persists, submit a service ticket. + |
+Instance parameters fail to be modified. + |
+|
Parameter template application failure + |
+TaurusApplyParameterGroupToInstanceFailed + |
+Major + |
+The network between the management plane and instances is abnormal or the instances are abnormal. + |
+Check the instance status and try again. If the fault persists, submit a service ticket. + |
+Parameter templates fail to be applied to instances. + |
+|
Full backup failure + |
+TaurusBackupInstanceFailed + |
+Major + |
+The network between the instance and the management plane (or the OBS) is disconnected, or the backup environment created for the instance is abnormal. + |
+Submit a service ticket. + |
+Backup jobs fail. + |
+|
Primary/standby failover + |
+TaurusActiveStandbySwitched + |
+Major + |
+When the network, physical machine, or database of the primary node is faulty, the system promotes a read replica to primary based on the failover priority to ensure service continuity. + |
+
|
+During the failover, database connection is interrupted for a short period of time. After the failover is complete, you can reconnect to the database. + |
+|
Database read-only + |
+NodeReadonlyMode + |
+Major + |
+The database supports only query operations. + |
+Contact the database technical support team. + |
+After the database becomes read-only, write operations cannot be processed. + |
+|
Database read/write + |
+NodeReadWriteMode + |
+Major + |
+The database supports both write and read operations. + |
+None. + |
+None. + |
+
Event Source + |
+Event Name + |
+Event ID + |
+Event Severity + |
+Description + |
+Solution + |
+Impact + |
+
|---|---|---|---|---|---|---|
GaussDB(for openGauss) + |
+Process status alarm + |
+ProcessStatusAlarm + |
+Major + |
+Key processes exit, including: CMS/CMA, ETCD, GTM, CN, or DN process. + |
+Wait until the process is automatically recovered or a primary/standby failover is automatically performed. Check whether services are recovered. If no, contact SRE engineers. + |
+If processes on primary nodes are faulty, services are interrupted and then rolled back. If processes on standby nodes are faulty, services are not affected. + |
+
Component status alarm + |
+ComponentStatusAlarm + |
+Major + |
+Key components do not respond, including: CMA, ETCD, GTM, CN, or DN component. + |
+Wait until the process is automatically recovered or a primary/standby failover is automatically performed. Check whether services are recovered. If no, contact SRE engineers. + |
+If processes on primary nodes do not respond, neither do the services. If processes on standby nodes are faulty, services are not affected. + |
+|
Cluster status alarm + |
+ClusterStatusAlarm + |
+Major + |
+The cluster status is abnormal. For example, the cluster is read-only; majority of ETCDs are faulty; or the cluster resources are unevenly distributed. + |
+Contact SRE engineers. + |
+If the cluster status is read-only, only read services are processed. +If the majority of ETCDs are fault, the cluster is unavailable. +If resources are unevenly distributed, the instance performance and reliability deteriorate. + |
+|
Hardware resource alarm + |
+HardwareResourceAlarm + |
+Major + |
+A major hardware fault occurs in the instance, such as disk damage or GTM network fault. + |
+Contact SRE engineers. + |
+Some or all services are affected. + |
+|
Status transition alarm + |
+StateTransitionAlarm + |
+Major + |
+The following events occur in the instance: DN build failure, forcible DN promotion, primary/standby DN switchover/failover, or primary/standby GTM switchover/failover. + |
+Wait until the fault is automatically rectified and check whether services are recovered. If no, contact SRE engineers. + |
+Some services are interrupted. + |
+|
Other abnormal alarm + |
+OtherAbnormalAlarm + |
+Major + |
+Disk usage threshold alarm + |
+Focus on service changes and scale up storage space as needed. + |
+If the used storage space exceeds the threshold, storage space cannot be scaled up. + |
+|
Faulty DB instance + |
+TaurusInstanceRunningStatusAbnormal + |
+Major + |
+This event is a key alarm event and is reported when an instance is faulty due to a disaster or a server failure. + |
+Submit a service ticket. + |
+The database service may be unavailable. + |
+|
DB instance recovered + |
+TaurusInstanceRunningStatusRecovered + |
+Major + |
+GaussDB(for openGauss) provides an HA tool for automated or manual rectification of faults. After the fault is rectified, this event is reported. + |
+No further action is required. + |
+None + |
+|
Faulty DB node + |
+TaurusNodeRunningStatusAbnormal + |
+Major + |
+This event is a key alarm event and is reported when a database node is faulty due to a disaster or a server failure. + |
+Check whether the database service is available and submit a service ticket. + |
+The database service may be unavailable. + |
+|
DB node recovered + |
+TaurusNodeRunningStatusRecovered + |
+Major + |
+GaussDB(for openGauss) provides an HA tool for automated or manual rectification of faults. After the fault is rectified, this event is reported. + |
+No further action is required. + |
+None + |
+|
DB instance creation failure + |
+GaussDBV5CreateInstanceFailed + |
+Major + |
+Instances fail to be created because the quota is insufficient or underlying resources are exhausted. + |
+Release the instances that are no longer used and try to provision them again, or submit a service ticket to adjust the quota. + |
+DB instances cannot be created. + |
+|
Node adding failure + |
+GaussDBV5ExpandClusterFailed + |
+Major + |
+The underlying resources are insufficient. + |
+Submit a service ticket. The O&M personnel will coordinate resources in the background, and then you delete the node that failed to be added and add a new node. + |
+None + |
+|
Storage scale-up failure + |
+GaussDBV5EnlargeVolumeFailed + |
+Major + |
+The underlying resources are insufficient. + |
+Submit a service ticket. The O&M personnel will coordinate resources in the background and then you scale up the storage space again. + |
+Services may be interrupted. + |
+|
Reboot failure + |
+GaussDBV5RestartInstanceFailed + |
+Major + |
+The network is abnormal. + |
+Retry the reboot operation or submit a service ticket to the O&M personnel. + |
+The database service may be unavailable. + |
+|
Full backup failure + |
+GaussDBV5FullBackupFailed + |
+Major + |
+The backup files fail to be exported or uploaded. + |
+Submit a service ticket to the O&M personnel. + |
+Data cannot be backed up. + |
+|
Differential backup failure + |
+GaussDBV5DifferentialBackupFailed + |
+Major + |
+The backup files fail to be exported or uploaded. + |
+Submit a service ticket to the O&M personnel. + |
+Data cannot be backed up. + |
+|
Backup deletion failure + |
+GaussDBV5DeleteBackupFailed + |
+Major + |
+This function does not need to be implemented. + |
+N/A + |
+N/A + |
+|
EIP binding failure + |
+GaussDBV5BindEIPFailed + |
+Major + |
+The EIP is bound to another resource. + |
+Submit a service ticket to the O&M personnel. + |
+The instance cannot be accessed from the Internet. + |
+|
EIP unbinding failure + |
+GaussDBV5UnbindEIPFailed + |
+Major + |
+The network is faulty or EIP is abnormal. + |
+Unbind the IP address again or submit a service ticket to the O&M personnel. + |
+IP addresses may be residual. + |
+|
Parameter template application failure + |
+GaussDBV5ApplyParamFailed + |
+Major + |
+Modifying a parameter template times out. + |
+Modify the parameter template again. + |
+None + |
+|
Parameter modification failure + |
+GaussDBV5UpdateInstanceParamGroupFailed + |
+Major + |
+Modifying a parameter template times out. + |
+Modify the parameter template again. + |
+None + |
+|
Backup and restoration failure + |
+GaussDBV5RestoreFromBcakupFailed + |
+Major + |
+The underlying resources are insufficient or backup files fail to be downloaded. + |
+Submit a service ticket. + |
+The database service may be unavailable during the restoration failure. + |
+
Public cloud APIs comply with the RESTful API design principles. REST-based Web services are organized into resources. Each resource is identified by one or more Uniform Resource Identifiers (URIs). An application accesses a resource based on the resource's Unified Resource Locator (URL). A URL is usually in the following format: https://Endpoint/uri. In the URL,uri indicates the resource path, that is, the API access path.
+Public cloud APIs use HTTPS as the transmission protocol. Requests/Responses are transmitted by using JSON messages, with media type represented by Application/json.
+For details about how to use APIs, see API Usage Guidelines.
+An endpoint is the request address for calling an API. Endpoints vary depending on services and regions. For example, the endpoint of the eu-de region is ces.eu-de.otc.t-systems.com. For the endpoints of all services, see Regions and Endpoints.
+This API is used to query all API versions supported by Cloud Eye.
+GET /
+Example request
+GET https://{Cloud Eye endpoint}/
+Parameter + |
+Type + |
+Description + |
+
|---|---|---|
versions + |
+Array of objects + |
+Specifies the list of all versions. +For details, see Table 2. + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
id + |
+String + |
+Specifies the version ID, for example, v1. + |
+
links + |
+Array of objects + |
+Specifies the API URL. +For details, see Table 3. + |
+
version + |
+String + |
+Specifies the API version. If the APIs of this version support microversions, set this parameter to the supported maximum microversion. If the microversion is not supported, leave this parameter blank. + |
+
status + |
+String + |
+Specifies the version status. +CURRENT: indicates a primary version. +SUPPORTED: indicates an old version but is still supported. +DEPRECATED: indicates a deprecated version which may be deleted later. + |
+
updated + |
+String + |
+Specifies the version release time, which must be the UTC time. For example, the release time of v1 is 2014-06-28T12:20:21Z. + |
+
min_version + |
+String + |
+If the APIs of this version support microversions, set this parameter to the supported minimum microversion. If not, leave this parameter blank. + |
+
{
+ "versions": [
+ {
+ "id": "V1.0",
+ "links": [
+ {
+ "href": "https://x.x.x.x/V1.0/",
+ "rel": "self"
+ }
+ ],
+ "min_version": "",
+ "status": "CURRENT",
+ "updated": "2018-09-30T00:00:00Z",
+ "version": ""
+ }
+ ]
+}
+Returned Value + |
+Description + |
+
|---|---|
400 Bad Request + |
+Request error. + |
+
401 Unauthorized + |
+The authentication information is not provided or is incorrect. + |
+
403 Forbidden + |
+Access to the requested page is forbidden. + |
+
408 Request Timeout + |
+The request timed out. + |
+
429 Too Many Requests + |
+Concurrent requests are excessive. + |
+
500 Internal Server Error + |
+Failed to complete the request because of an internal service error. + |
+
503 Service Unavailable + |
+The service is currently unavailable. + |
+
See Error Codes.
+This API is used to query a specified API version of Cloud Eye.
+GET /{api_version}
+Parameter + |
+Mandatory + |
+Description + |
+
|---|---|---|
api_version + |
+Yes + |
+Specifies the API version. + |
+
GET https://{Cloud Eye endpoint}/V1.0\
+None
+Parameter + |
+Type + |
+Description + |
+
|---|---|---|
version + |
+Objects + |
+Specifies the list of all versions. +For details, see Table 3. + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
id + |
+String + |
+Specifies the version ID, for example, v1. + |
+
links + |
+Array of objects + |
+Specifies the API URL. +For details, see Table 4. + |
+
version + |
+String + |
+Specifies the API version. If the APIs of this version support microversions, set this parameter to the supported maximum microversion. If the microversion is not supported, leave this parameter blank. + |
+
status + |
+String + |
+Specifies the version status. +CURRENT: indicates a primary version. +SUPPORTED: indicates an old version but is still supported. +DEPRECATED: indicates a deprecated version which may be deleted later. + |
+
updated + |
+String + |
+Specifies the version release time, which must be the UTC time. For example, the release time of v1 is 2014-06-28T12:20:21Z. + |
+
min_version + |
+String + |
+If the APIs of this version support microversions, set this parameter to the supported minimum microversion. If not, leave this parameter blank. + |
+
{
+ "version": {
+ "id": "V1.0",
+ "links": [
+ {
+ "href": "https://x.x.x.x/V1.0/",
+ "rel": "self"
+ }
+ ],
+ "min_version": "",
+ "status": "CURRENT",
+ "updated": "2018-09-30T00:00:00Z",
+ "version": ""
+ }
+}
+Returned Value + |
+Description + |
+
|---|---|
400 Bad Request + |
+Request error. + |
+
401 Unauthorized + |
+The authentication information is not provided or is incorrect. + |
+
403 Forbidden + |
+Access to the requested page is forbidden. + |
+
408 Request Timeout + |
+The request timed out. + |
+
429 Too Many Requests + |
+Concurrent requests are excessive. + |
+
500 Internal Server Error + |
+Failed to complete the request because of an internal service error. + |
+
503 Service Unavailable + |
+The service is currently unavailable. + |
+
See Error Codes.
+This API is used to query the metrics. You can specify the namespace, metric, dimension, sorting order, start records, and the maximum number of records when using this API to query metrics.
+GET /V1.0/{project_id}/metrics
+Parameter + |
+Mandatory + |
+Description + |
+
|---|---|---|
project_id + |
+Yes + |
+Specifies the project ID. +For details about how to obtain the project ID, see Obtaining a Project ID. + |
+
Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
|---|---|---|---|
namespace + |
+No + |
+String + |
+Query the namespace of a service. For details, see Services Interconnected with Cloud Eye. +The namespace must be in the service.item format and contain 3 to 32 characters. service and item each must start with a letter and contain only letters, digits, and underscores (_). + |
+
metric_name + |
+No + |
+String + |
+Specifies the metric ID. For example, if the monitoring metric of an ECS is CPU usage, metric_name is cpu_util. For details, see Services Interconnected with Cloud Eye. + |
+
dim + |
+No + |
+String + |
+Specifies the dimension. For example, the ECS dimension is instance_id. For details about each service dimension, see Services Interconnected with Cloud Eye. +A maximum of three dimensions are supported, and the dimensions are numbered from 0 in dim.{i}=key,value format. key cannot exceed 32 characters and value cannot exceed 256 characters. +Single dimension: dim.0=instance_id,6f3c6f91-4b24-4e1b-b7d1-a94ac1cb011d +Multiple dimensions: dim.0=key,value&dim.1=key,value + |
+
start + |
+No + |
+String + |
+Specifies the paging start value. +The format is namespace.metric_name.key:value. +Example: start=SYS.ECS.cpu_util.instance_id:d9112af5-6913-4f3b-bd0a-3f96711e004d. + |
+
limit + |
+No + |
+Integer + |
+Supported range: 1 to 1000 (default) +This parameter is used to limit the number of query results. + |
+
order + |
+No + |
+String + |
+Specifies the result sorting method, which is sorted by timestamp. +The default method is desc. +
|
+
GET https://{Cloud Eye endpoint}/V1.0/{project_id}/metrics
+GET https://{Cloud Eye endpoint}/V1.0/{project_id}/metrics?namespace=SYS.ECS&metric_name=cpu_util&dim.0=instance_id,6f3c6f91-4b24-4e1b-b7d1-a94ac1cb011d&limit=10&order=desc
+None
+Parameter + |
+Type + |
+Description + |
+
|---|---|---|
metrics + |
+Array of objects + |
+Specifies the list of metric objects. +For details, see Table 4. + |
+
meta_data + |
+Object + |
+Specifies the metadata of query results, including the pagination information. +For details, see Table 6. + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
namespace + |
+String + |
+Specifies the metric namespace. + |
+
dimensions + |
+Array of objects + |
+Specifies the list of metric dimensions. +For details, see Table 5. + |
+
metric_name + |
+String + |
+Specifies the metric name, such as cpu_util. + |
+
unit + |
+String + |
+Specifies the metric unit. + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
name + |
+String + |
+Specifies the dimension. For example, the ECS dimension is instance_id. For details about the dimension of each service, see the key column in Services Interconnected with Cloud Eye. + |
+
value + |
+String + |
+Specifies the dimension value, for example, an ECS ID. +Enter 1 to 256 characters. + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
count + |
+Integer + |
+Specifies the number of returned results. + |
+
marker + |
+String + |
+Specifies the pagination marker. +For example, you have queried 10 records this time and the tenth record is about cpu_util. In your next query, if start is set to cpu_util, you can start your query from the next metric of cpu_util. + |
+
total + |
+Integer + |
+Specifies the total number of metrics. + |
+
{
+ "metrics": [
+ {
+ "namespace": "SYS.ECS",
+ "dimensions": [
+ {
+ "name": "instance_id",
+ "value": "d9112af5-6913-4f3b-bd0a-3f96711e004d"
+ }
+ ],
+ "metric_name": "cpu_util",
+ "unit": "%"
+ }
+ ],
+ "meta_data": {
+ "count": 1,
+ "marker": "SYS.ECS.cpu_util.instance_id:d9112af5-6913-4f3b-bd0a-3f96711e004d",
+ "total": 7
+ }
+}
+Returned Value + |
+Description + |
+
|---|---|
400 Bad Request + |
+Request error. + |
+
401 Unauthorized + |
+The authentication information is not provided or is incorrect. + |
+
403 Forbidden + |
+Access to the requested page is forbidden. + |
+
408 Request Timeout + |
+The request timed out. + |
+
429 Too Many Requests + |
+Concurrent requests are excessive. + |
+
500 Internal Server Error + |
+Failed to complete the request because of an internal service error. + |
+
503 Service Unavailable + |
+The service is currently unavailable. + |
+
See Error Codes.
+This API is used to query the alarm rule list. You can specify the paging parameters to limit the number of query results displayed on a page. You can also set the sorting order of query results.
+GET /V1.0/{project_id}/alarms
+Parameter + |
+Mandatory + |
+Description + |
+
|---|---|---|
project_id + |
+Yes + |
+Specifies the project ID. +For details about how to obtain the project ID, see Obtaining a Project ID. + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
alarms + |
+Array of objects + |
+Specifies the alarm rule list. +For details, see Table 3. + |
+
Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
|---|---|---|---|
start + |
+No + |
+String + |
+Specifies the first queried alarm to be displayed on a page. +The value is alarm_id. + |
+
limit + |
+No + |
+Integer + |
+Supported range: 1 to 100 (default) +This parameter is used to limit the number of query results. + |
+
order + |
+No + |
+String + |
+Specifies the result sorting method, which is sorted by timestamp. +The default method is desc. +
|
+
GET https://{Cloud Eye endpoint}/V1.0/{project_id}/alarms
+GET https://{Cloud Eye endpoint}/V1.0/{project_id}/alarms?start=al1441967036681YkazZ0deN&limit=10&order=desc
+None
+Parameter + |
+Type + |
+Description + |
+
|---|---|---|
metric_alarms + |
+Array of objects + |
+Specifies the list of alarm objects. +For details, see Table 5. + |
+
meta_data + |
+Object + |
+Specifies the metadata of query results, including the pagination information. +For details, see Table 11. + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
alarm_name + |
+String + |
+Specifies the alarm rule name. + |
+
alarm_description + |
+String + |
+Provides supplementary information about the alarm rule. + |
+
metric + |
+Object + |
+Specifies the alarm metric. +For details, see Table 6. + |
+
condition + |
+Object + |
+Specifies the alarm triggering condition. +For details, see Table 10. + |
+
alarm_enabled + |
+Boolean + |
+Specifies whether to enable the alarm rule. + |
+
alarm_level + |
+Integer + |
+Specifies the alarm severity, which can be 1, 2 (default), 3 or 4, indicating critical, major, minor, and informational, respectively. + |
+
alarm_action_enabled + |
+Boolean + |
+Specifies whether to enable the action to be triggered by an alarm. + |
+
alarm_actions + |
+Array of objects + |
+Specifies the action to be triggered by an alarm. +For details, see Table 8. + |
+
ok_actions + |
+Array of objects + |
+Specifies the action to be triggered after the alarm is cleared. +For details, see Table 9. + |
+
alarm_id + |
+String + |
+Specifies the alarm rule ID. + |
+
update_time + |
+long + |
+Specifies when the alarm status changed. The time is a UNIX timestamp and the unit is ms. + |
+
alarm_state + |
+String + |
+Specifies the alarm status, which can be +
|
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
namespace + |
+String + |
+Query the namespace of a service. For details, see Services Interconnected with Cloud Eye. + |
+
dimensions + |
+Array of objects + |
+Specifies the list of metric dimensions. +For details, see Table 7. + |
+
metric_name + |
+String + |
+Specifies the metric ID. For example, if the monitoring metric of an ECS is CPU usage, metric_name is cpu_util. For details, see Services Interconnected with Cloud Eye. + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
name + |
+String + |
+Specifies the dimension. For example, the ECS dimension is instance_id. For details about the dimension of each service, see the key column in Services Interconnected with Cloud Eye. + |
+
value + |
+String + |
+Specifies the dimension value, for example, an ECS ID. +Enter 1 to 256 characters. + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
type + |
+String + |
+Specifies the alarm notification type.
+
|
+
notificationList + |
+Array of strings + |
+Specifies the list of objects to be notified if the alarm status changes. + NOTE:
+The IDs in the list are strings. + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
type + |
+String + |
+Specifies the notification type when an alarm is triggered.
+
|
+
notificationList + |
+Array of strings + |
+Specifies the ID list of objects to be notified if the alarm status changes. + NOTE:
+The IDs in the list are strings. + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
period + |
+Integer + |
+Specifies the interval (seconds) for checking whether the configured alarm rules are met. + |
+
filter + |
+String + |
+Specifies the data rollup method. The following methods are supported: +
|
+
comparison_operator + |
+String + |
+Specifies the alarm threshold operator, which can be >, =, <, ≥, or ≤. + |
+
value + |
+Double + |
+Specifies the alarm threshold. Supported range: 0 to Number. MAX_VALUE (1.7976931348623157e+108) +For detailed thresholds, see the value range of each metric in the appendix. For example, you can set ECS cpu_util in Services Interconnected with Cloud Eye to 80. + |
+
unit + |
+String + |
+Specifies the data unit. Enter up to 32 characters. + |
+
count + |
+Integer + |
+Specifies the number of consecutive occurrence times that the alarm policy was met. Supported range: 1 to 5 + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
count + |
+Integer + |
+Specifies the number of returned results. + |
+
marker + |
+String + |
+Specifies the pagination marker. +For example, you have queried 10 records this time and alarm_id of the tenth record is 1441967036681YkazZ0deN. In your next query, if start is set to al1441967036681YkazZ0deN, you can start your query from the next alarm rule ID of al1441967036681YkazZ0deN. + |
+
total + |
+Integer + |
+Specifies the total number of query results. + |
+
{
+ "metric_alarms": [
+ {
+ "alarm_name": "alarm-ttttttt",
+ "alarm_description": "",
+ "metric": {
+ "namespace": "SYS.ECS",
+ "dimensions": [
+ {
+ "name": "instance_id",
+ "value": "07814c0e-59a1-4fcd-a6fb-56f2f6923046"
+ }
+ ],
+ "metric_name": "cpu_util"
+ },
+ "condition": {
+ "period": 300,
+ "filter": "average",
+ "comparison_operator": ">=",
+ "value": 0,
+ "unit": "%",
+ "count": 3
+ },
+ "alarm_enabled": true,
+ "alarm_level": 2,
+ "alarm_action_enabled": false,
+ "alarm_id": "al15330507498596W7vmlGKL",
+ "update_time": 1533050749992,
+ "alarm_state": "alarm"
+ },
+ {
+ "alarm_name": "alarm-m5rwxxxxxxx",
+ "alarm_description": "",
+ "metric": {
+ "namespace": "SYS.ECS",
+ "dimensions": [
+ {
+ "name": "instance_id",
+ "value": "30f3858d-4377-4514-9081-be5bdbf1392e"
+ }
+ ],
+ "metric_name": "network_incoming_bytes_aggregate_rate"
+ },
+ "condition": {
+ "period": 300,
+ "filter": "average",
+ "comparison_operator": ">=",
+ "value": 12,
+ "unit": "Byte/s",
+ "count": 3
+ },
+ "alarm_enabled": true,
+ "alarm_level": 2,
+ "alarm_action_enabled": true,
+ "alarm_actions": [
+ {
+ "type": "notification",
+ "notificationList": [
+ "urn:smn:region:68438a86d98e427e907e0097b7e35d48:test0315"
+ ]
+ }
+ ],
+ "ok_actions": [
+ {
+ "type": "notification",
+ "notificationList": [
+ "urn:smn:region:68438a86d98e427e907e0097b7e35d48:test0315"
+ ]
+ }
+ ],
+ "alarm_id": "al1533031226533nKJexAlbq",
+ "update_time": 1533204036276,
+ "alarm_state": "ok"
+ }
+ ],
+ "meta_data": {
+ "count": 2,
+ "marker": "al1533031226533nKJexAlbq",
+ "total": 389
+ }
+}
+Returned Value + |
+Description + |
+
|---|---|
400 Bad Request + |
+Request error. + |
+
401 Unauthorized + |
+The authentication information is not provided or is incorrect. + |
+
403 Forbidden + |
+You are forbidden to access the page requested. + |
+
408 Request Timeout + |
+The request timed out. + |
+
429 Too Many Requests + |
+Concurrent requests are excessive. + |
+
500 Internal Server Error + |
+Failed to complete the request because of an internal service error. + |
+
503 Service Unavailable + |
+The service is currently unavailable. + |
+
See Error Codes.
+This API is used to query an alarm rule based on the alarm rule ID.
+GET /V1.0/{project_id}/alarms/{alarm_id}
+Parameter + |
+Mandatory + |
+Description + |
+
|---|---|---|
project_id + |
+Yes + |
+Specifies the project ID. +For details about how to obtain the project ID, see Obtaining a Project ID. + |
+
alarm_id + |
+Yes + |
+Specifies the alarm rule ID. + |
+
GET https://{Cloud Eye endpoint}/V1.0/{project_id}/alarms/al1441967036681YkazZ0deN
+None
+Parameter + |
+Type + |
+Description + |
+
|---|---|---|
metric_alarms + |
+Array of objects + |
+Specifies the list of alarm objects. +For details, see Table 2. + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
alarm_name + |
+String + |
+Specifies the alarm rule name. + |
+
alarm_description + |
+String + |
+Provides supplementary information about the alarm rule. + |
+
metric + |
+Object + |
+Specifies the alarm metric. +For details, see Table 3. + |
+
condition + |
+Object + |
+Specifies the alarm triggering condition. +For details, see Table 7. + |
+
alarm_enabled + |
+Boolean + |
+Specifies whether to enable the alarm rule. + |
+
alarm_level + |
+Integer + |
+Specifies the alarm severity, which can be 1, 2 (default), 3 or 4, indicating critical, major, minor, and informational, respectively. + |
+
alarm_action_enabled + |
+Boolean + |
+Specifies whether to enable the action to be triggered by an alarm. + |
+
alarm_actions + |
+Array of objects + |
+Specifies the action to be triggered by an alarm. +For details, see Table 5. + |
+
ok_actions + |
+Array of objects + |
+Specifies the action to be triggered after the alarm is cleared. +For details, see Table 6. + |
+
alarm_id + |
+String + |
+Specifies the alarm rule ID. + |
+
update_time + |
+long + |
+Specifies when the alarm status changed. The time is a UNIX timestamp and the unit is ms. + |
+
alarm_state + |
+String + |
+Specifies the alarm status, which can be +
|
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
namespace + |
+String + |
+Query the namespace of a service. For details, see Services Interconnected with Cloud Eye. + |
+
dimensions + |
+Array of objects + |
+Specifies the list of metric dimensions. +For details, see Table 4. + |
+
metric_name + |
+String + |
+Specifies the metric ID. For example, if the monitoring metric of an ECS is CPU usage, metric_name is cpu_util. For details, see Services Interconnected with Cloud Eye. + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
name + |
+String + |
+Specifies the dimension. For example, the ECS dimension is instance_id. For details about the dimension of each service, see the key column in Services Interconnected with Cloud Eye. + |
+
value + |
+String + |
+Specifies the dimension value, for example, an ECS ID. +Enter 1 to 256 characters. + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
type + |
+String + |
+Specifies the alarm notification type.
+
|
+
notificationList + |
+Array of strings + |
+Specifies the list of objects to be notified if the alarm status changes. + NOTE:
+The IDs in the list are strings. + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
type + |
+String + |
+Specifies the notification type when an alarm is triggered.
+
|
+
notificationList + |
+Array of strings + |
+Specifies the list of objects to be notified if the alarm status changes. + NOTE:
+The IDs in the list are strings. + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
period + |
+Integer + |
+Specifies the interval (seconds) for checking whether the configured alarm rules are met. + |
+
filter + |
+String + |
+Specifies the data rollup method. The following methods are supported: +
|
+
comparison_operator + |
+String + |
+Specifies the alarm threshold operator, which can be >, =, <, ≥, or ≤. + |
+
value + |
+Double + |
+Specifies the alarm threshold. Supported range: 0 to Number. MAX_VALUE (1.7976931348623157e+108) +For detailed thresholds, see the value range of each metric in the appendix. For example, you can set ECS cpu_util in Services Interconnected with Cloud Eye to 80. + |
+
unit + |
+String + |
+Specifies the data unit. Enter up to 32 characters. + |
+
count + |
+Integer + |
+Specifies the number of consecutive occurrence times that the alarm policy was met. Supported range: 1 to 5 + |
+
{
+"metric_alarms":
+ [
+ {
+ "alarm_name":"alarm-ipwx",
+ "alarm_description":"",
+ "metric":
+ {
+ "namespace":"SYS.ELB",
+ "dimensions":
+ [
+ {
+ "name":"lb_instance_id",
+ "value":"44d06d10-bce0-4237-86b9-7b4d1e7d5621"
+ }
+ ],
+ "metric_name":"m8_out_Bps"
+ },
+ "condition":
+ {
+ "period":300,
+ "filter":"sum",
+ "comparison_operator":">=",
+ "value":0,
+ "unit":"",
+ "count":1
+ },
+ "alarm_enabled":true,
+ "alarm_level": 2,
+ "alarm_action_enabled":true,
+ "alarm_actions":
+ [
+ {
+ "type":"notification",
+ "notificationList":["urn:smn:region:68438a86d98e427e907e0097b7e35d48:sd"]
+ }
+ ],
+ "ok_actions":
+ [
+ {
+ "type":"notification",
+ "notificationList":["urn:smn:region:68438a86d98e427e907e0097b7e35d48:sd"]
+ }
+ ],
+ "alarm_id":"al1498096535573r8DNy7Gyk",
+ "update_time":1498100100000,
+ "alarm_state":"alarm"
+ }
+ ]
+}
+Returned Value + |
+Description + |
+
|---|---|
400 Bad Request + |
+Request error. + |
+
401 Unauthorized + |
+The authentication information is not provided or is incorrect. + |
+
403 Forbidden + |
+You are forbidden to access the page requested. + |
+
408 Request Timeout + |
+The request timed out. + |
+
429 Too Many Requests + |
+Concurrent requests are excessive. + |
+
500 Internal Server Error + |
+Failed to complete the request because of an internal service error. + |
+
503 Service Unavailable + |
+The service is currently unavailable. + |
+
See Error Codes.
+This API is used to enable or disable an alarm rule.
+PUT /V1.0/{project_id}/alarms/{alarm_id}/action
+Parameter + |
+Mandatory + |
+Description + |
+
|---|---|---|
project_id + |
+Yes + |
+Specifies the project ID. +For details about how to obtain the project ID, see Obtaining a Project ID. + |
+
alarm_id + |
+Yes + |
+Specifies the alarm rule ID. + |
+
PUT https://{Cloud Eye endpoint}/V1.0/{project_id}/alarms/al1441967036681YkazZ0deN/action
+Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
|---|---|---|---|
alarm_enabled + |
+Yes + |
+Boolean + |
+Specifies whether the alarm rule is enabled. +
|
+
{
+ "alarm_enabled":true
+}
+The response has no message body.
+Returned Value + |
+Description + |
+
|---|---|
400 Bad Request + |
+Request error. + |
+
401 Unauthorized + |
+The authentication information is not provided or is incorrect. + |
+
403 Forbidden + |
+Access to the requested page is forbidden. + |
+
408 Request Timeout + |
+The request timed out. + |
+
429 Too Many Requests + |
+Concurrent requests are excessive. + |
+
500 Internal Server Error + |
+Failed to complete the request because of an internal service error. + |
+
503 Service Unavailable + |
+The service is currently unavailable. + |
+
See Error Codes.
+This API is used to delete an alarm rule.
+DELETE /V1.0/{project_id}/alarms/{alarm_id}
+Parameter + |
+Mandatory + |
+Description + |
+
|---|---|---|
project_id + |
+Yes + |
+Specifies the project ID. +For details about how to obtain the project ID, see Obtaining a Project ID. + |
+
alarm_id + |
+Yes + |
+Specifies the alarm rule ID. + |
+
DELETE https://{Cloud Eye endpoint}/V1.0/{project_id}/alarms/al1441967036681YkazZ0deN
+The request has no message body.
+The response has no message body.
+Returned Value + |
+Description + |
+
|---|---|
400 Bad Request + |
+Request error. + |
+
401 Unauthorized + |
+The authentication information is not provided or is incorrect. + |
+
403 Forbidden + |
+Access to the requested page is forbidden. + |
+
408 Request Timeout + |
+The request timed out. + |
+
429 Too Many Requests + |
+Concurrent requests are excessive. + |
+
500 Internal Server Error + |
+Failed to complete the request because of an internal service error. + |
+
503 Service Unavailable + |
+The service is currently unavailable. + |
+
See Error Codes.
+This API is used to create an alarm rule.
+POST /V1.0/{project_id}/alarms
+Parameter + |
+Mandatory + |
+Description + |
+
|---|---|---|
project_id + |
+Yes + |
+Specifies the project ID. +For details about how to obtain the project ID, see Obtaining a Project ID. + |
+
POST https://{Cloud Eye endpoint}/V1.0/{project_id}/alarms
+Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
|---|---|---|---|
alarm_name + |
+Yes + |
+String + |
+Specifies the alarm rule name. +Enter 1 to 128 characters. Only letters, digits, underscores (_), and hyphens (-) are allowed. + |
+
alarm_description + |
+No + |
+String + |
+Provides supplementary information about the alarm rule. Enter 0 to 256 characters. + |
+
metric + |
+Yes + |
+Object + |
+Specifies the alarm metric. +For details, see Table 3. + |
+
condition + |
+Yes + |
+Object + |
+Specifies the alarm triggering condition. +For details, see Table 7. + |
+
alarm_enabled + |
+No + |
+Boolean + |
+Specifies whether to enable the alarm. +The default value is true. + |
+
alarm_action_enabled + |
+No + |
+Boolean + |
+Specifies whether to enable the action to be triggered by an alarm. The default value is true. + NOTE:
+If you set alarm_action_enabled to true, you must specify either alarm_actions or ok_actions. (You do not need to configure the deprecated parameter insufficientdata_actions.) +If alarm_actions and ok_actions coexist, their notificationList must be the same. (You do not need to configure the deprecated parameter insufficientdata_actions.) + |
+
alarm_level + |
+No + |
+Integer + |
+Specifies the alarm severity, which can be 1, 2 (default), 3 or 4, indicating critical, major, minor, and informational, respectively. + |
+
alarm_type + |
+No + |
+String + |
+Specifies the alarm rule type. +EVENT.SYS: The alarm rule is created for system events. EVENT.CUSTOM: The alarm rule is created for custom events. + |
+
alarm_actions + |
+No + |
+Arrays of objects + |
+Specifies the action to be triggered by an alarm. +An example structure is as follows: +{ +"type": "notification","notificationList": ["urn:smn:region:68438a86d98e427e907e0097b7e35d47:sd"] +} +For details, see Table 5. + |
+
ok_actions + |
+No + |
+Arrays of objects + |
+Specifies the action to be triggered after the alarm is cleared. +Its structure is: +{ "type": "notification","notificationList": ["urn:smn:region:68438a86d98e427e907e0097b7e35d47:sd"] } +For details, see Table 6. + |
+
Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
|---|---|---|---|
namespace + |
+Yes + |
+String + |
+Specifies the namespace of a service. For details, see Services Interconnected with Cloud Eye. +The namespace must be in the service.item format and contain 3 to 32 characters. service and item each must start with a letter and contain only letters, digits, and underscores (_). + |
+
dimensions + |
+No + |
+Arrays of objects + |
+Specifies the metric dimension list. When resource_group_id is not used, dimensions is mandatory. +For details, see Table 4. + |
+
metric_name + |
+Yes + |
+String + |
+Specifies the metric name. +Start with a letter. Enter 1 to 64 characters. Only letters, digits, and underscores (_) are allowed. +For details, see the metric name queried in Querying Metrics. + |
+
resource_group_id + |
+No + |
+String + |
+Specifies the resource group ID selected during the alarm rule creation, for example, rg1603786526428bWbVmk4rP. + NOTE:
+If you create alarm rules for resource groups, you must specify resource_group_id and name, enter at least one dimension for dimensions, and set alarm_type to RESOURCE_GROUP. + |
+
Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
|---|---|---|---|
name + |
+Yes + |
+String + |
+Specifies the dimension. For example, the ECS dimension is instance_id. For details about the dimension of each service, see the key column in Services Interconnected with Cloud Eye. +Start with a letter. Enter 1 to 32 characters. Only letters, digits, underscores (_), and hyphens (-) are allowed. + |
+
value + |
+Yes + |
+String + |
+Specifies the dimension value, for example, an ECS ID. +Start with a letter or a digit. Enter 1 to 256 characters. Only letters, digits, underscores (_), and hyphens (-) are allowed. + |
+
Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
|---|---|---|---|
type + |
+Yes + |
+String + |
+Specifies the alarm notification type.
+
|
+
notificationList + |
+Yes + |
+Arrays of strings + |
+Specifies the list of objects to be notified if the alarm status changes. You can configure up to 5 object IDs. You can obtain the topicUrn value from SMN in the following format: urn:smn:([a-z]|[A-Z]|[0-9]|\-){1,32}:([a-z]|[A-Z]|[0-9]){32}:([a-z]|[A-Z]|[0-9]|\-|\_){1,256}. +If you set type to notification, you must specify notificationList. If you set type to autoscaling, you must set notificationList to []. + NOTE:
+
|
+
Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
|---|---|---|---|
type + |
+Yes + |
+String + |
+Specifies the notification type when an alarm is triggered.
+
|
+
notificationList + |
+Yes + |
+Arrays of objects + |
+Specifies the list of objects to be notified if the alarm status changes. You can configure up to 5 object IDs. You can obtain the topicUrn value from SMN in the following format: urn:smn:([a-z]|[A-Z]|[0-9]|\-){1,32}:([a-z]|[A-Z]|[0-9]){32}:([a-z]|[A-Z]|[0-9]|\-|\_){1,256}. + NOTE:
+If you set alarm_action_enabled to true, you must specify either alarm_actions or ok_actions. (You do not need to configure the deprecated parameter insufficientdata_actions.) +If alarm_actions and ok_actions coexist, their notificationList must be the same. (You do not need to configure the deprecated parameter insufficientdata_actions.) + |
+
Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
|---|---|---|---|
period + |
+Yes + |
+Integer + |
+Specifies the period during which Cloud Eye determines whether to trigger an alarm. Unit: second +Possible periods are 1, 300, 1200, 3600, 14400, and 86400. + NOTE:
+
|
+
filter + |
+Yes + |
+String + |
+Specifies the data rollup method. +Possible methods are max, min, average, sum, or variance. + |
+
comparison_operator + |
+Yes + |
+String + |
+Specifies the operator of alarm thresholds. +Possible operators are >, =, <, >=, and <=. + |
+
value + |
+Yes + |
+Double + |
+Specifies the alarm threshold. +Supported range: 0 to Number. MAX_VALUE (1.7976931348623157e+108) +For detailed thresholds, see the value range of each metric in the appendix. For example, you can set ECS cpu_util in Services Interconnected with Cloud Eye to 80. + |
+
unit + |
+No + |
+String + |
+Specifies the data unit. Enter up to 32 characters. + |
+
count + |
+Yes + |
+Integer + |
+Specifies the number of consecutive occurrence times that the alarm policy was met. Supported range: 1 to 5 + |
+
{
+ "alarm_name": "alarm-rp0E",
+ "alarm_description": "",
+ "metric": {
+ "namespace": "SYS.ECS",
+ "dimensions": [
+ {
+ "name": "instance_id",
+ "value": "33328f02-3814-422e-b688-bfdba93d4051"
+ }
+ ],
+ "metric_name": "network_outgoing_bytes_rate_inband"
+ },
+ "condition": {
+ "period": 300,
+ "filter": "average",
+ "comparison_operator": ">=",
+ "value": 6,
+ "unit": "Byte/s",
+ "count": 1
+ },
+ "alarm_enabled": true,
+ "alarm_action_enabled": true,
+ "alarm_level": 2,
+ "alarm_actions": [
+ {
+ "type": "notification",
+ "notificationList": ["urn:smn:region:68438a86d98e427e907e0097b7e35d48:sd"]
+ }
+ ],
+ "ok_actions": [
+ {
+ "type": "notification",
+ "notificationList": ["urn:smn:region:68438a86d98e427e907e0097b7e35d48:sd"]
+ }
+ ]
+}
+Parameter + |
+Type + |
+Description + |
+
|---|---|---|
alarm_id + |
+String + |
+Specifies the alarm rule ID. + |
+
{
+ "alarm_id":"al1450321795427dR8p5mQBo"
+}
+Returned Value + |
+Description + |
+
|---|---|
400 Bad Request + |
+Request error. + |
+
401 Unauthorized + |
+The authentication information is not provided or is incorrect. + |
+
403 Forbidden + |
+Access to the requested page is forbidden. + |
+
408 Request Timeout + |
+The request timed out. + |
+
429 Too Many Requests + |
+Concurrent requests are excessive. + |
+
500 Internal Server Error + |
+Failed to complete the request because of an internal service error. + |
+
503 Service Unavailable + |
+The service is currently unavailable. + |
+
See Error Codes.
+This API is used to query the monitoring data at a specified granularity for a specified metric in a specified period of time. You can specify the dimension of data to be queried.
+GET /V1.0/{project_id}/metric-data?namespace={namespace}&metric_name={metric_name}&dim.{i}=key,value&from={from}&to={to}&period={period}&filter={filter}
+Parameter + |
+Mandatory + |
+Description + |
+
|---|---|---|
project_id + |
+Yes + |
+Specifies the project ID. +For details about how to obtain the project ID, see Obtaining a Project ID. + |
+
Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
|---|---|---|---|
namespace + |
+Yes + |
+String + |
+Specifies the namespace of a service. For details, see Services Interconnected with Cloud Eye. +The namespace must be in the service.item format and contain 3 to 32 characters. service and item each must start with a letter and contain only letters, digits, and underscores (_). + |
+
metric_name + |
+Yes + |
+String + |
+Specifies the metric name. You can obtain the metric names of existing alarm rules by referring to Querying Metrics. + |
+
from + |
+Yes + |
+String + |
+Specifies the start time of the query. The time is a UNIX timestamp and the unit is ms. +Rollup aggregates the raw data generated within a period to the start time of the period. Therefore, if from and to are within a period, the query result will be empty due to the rollup failure. Set from to at least one period earlier than the current time. +Take the 5-minute period as an example. If it is 10:35 now, the raw data generated between 10:30 and 10:35 will be aggregated to 10:30. Therefore, in this example, if period is 5 minutes, from should be 10:30. + NOTE:
+Cloud Eye rounds up from based on the level of granularity required to perform the rollup. + |
+
to + |
+Yes + |
+String + |
+Specifies the end time of the query. +The time is a UNIX timestamp and the unit is ms. +from must be earlier than to. + |
+
period + |
+Yes + |
+Integer + |
+Specifies how often Cloud Eye aggregates data, which can be +
|
+
filter + |
+Yes + |
+String + |
+Specifies the data rollup method, which can be +
NOTE:
+Rollup uses a rollup method to aggregate raw data generated within a specific period. Take the 5-minute period as an example. If it is 10:35 now, the raw data generated between 10:30 and 10:35 will be aggregated to 10:30. + |
+
dim + |
+Yes + |
+String + |
+A maximum of three metric dimensions are supported, and the dimensions are numbered from 0 in the dim.{i}=key,value format. key cannot exceed 32 characters and value cannot exceed 256 characters. +The following dimensions are only examples. For details about whether multiple dimensions are supported, see the dimension description in the monitoring indicator description of each service. +Single dimension: dim.0=instance_id,i-12345 +Multiple dimensions: dim.0=instance_id,i-12345&dim.1=instance_name,i-1234 + |
+
Request example 1: View the CPU usage of ECS whose ID is 6f3c6f91-4b24-4e1b-b7d1-a94ac1cb011d from 2019-04-30 20:00:00 to 2019-04-30 22:00:00. The monitoring interval is 20 minutes.
+GET https://{Cloud Eye endpoint}/V1.0/{project_id}/metric-data?namespace=SYS.ECS&metric_name=cpu_util&dim.0=instance_id,6f3c6f91-4b24-4e1b-b7d1-a94ac1cb011d&from=1556625600000&to=1556632800000&period=1200&filter=min
+None
+Parameter + |
+Type + |
+Description + |
+
|---|---|---|
datapoints + |
+Array of objects + |
+Specifies the metric data list. For details, see Table 4. + +Since Cloud Eye rounds up from based on the level of granularity for data query, datapoints may contain more data points than expected. + |
+
metric_name + |
+String + |
+Specifies the metric ID. For example, if the monitoring metric of an ECS is CPU usage, metric_name is cpu_util. For details, see Services Interconnected with Cloud Eye. + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
average + |
+double + |
+Specifies the average value of metric data within a rollup period. + |
+
max + |
+double + |
+Specifies the maximum value of metric data within a rollup period. + |
+
min + |
+double + |
+Specifies the minimum value of metric data within a rollup period. + |
+
sum + |
+double + |
+Specifies the sum of metric data within a rollup period. + |
+
variance + |
+double + |
+Specifies the variance of metric data within a rollup period. + |
+
timestamp + |
+long + |
+Specifies when the metric is collected. It is a UNIX timestamp in milliseconds. + |
+
unit + |
+String + |
+Specifies the metric unit. + |
+
{
+ "datapoints": [
+ {
+ "average": 0.23,
+ "timestamp": 1442341200000,
+ "unit": "%"
+ }
+ ],
+ "metric_name": "cpu_util"
+}
+{
+ "datapoints": [
+ {
+ "sum": 0.53,
+ "timestamp": 1442341200000,
+ "unit": "%"
+ }
+ ],
+ "metric_name": "cpu_util"
+}
+{
+ "datapoints": [
+ {
+ "max": 0.13,
+ "timestamp": 1442341200000,
+ "unit": "%"
+ }
+ ],
+ "metric_name": "cpu_util"
+}
+Returned Value + |
+Description + |
+
|---|---|
400 Bad Request + |
+Request error. + |
+
401 Unauthorized + |
+The authentication information is not provided or is incorrect. + |
+
403 Forbidden + |
+You are forbidden to access the page requested. + |
+
408 Request Timeout + |
+The request timed out. + |
+
429 Too Many Requests + |
+Concurrent requests are excessive. + |
+
500 Internal Server Error + |
+Failed to complete the request because of an internal service error. + |
+
503 Service Unavailable + |
+The service is currently unavailable. + |
+
See Error Codes.
+You can query the monitoring data of specified metrics within a specified time range and specified granularities in batches. At present, you can query the monitoring data of a maximum of 10 metrics in batches.
+POST /V1.0/{project_id}/batch-query-metric-data
+Parameter + |
+Mandatory + |
+Description + |
+
|---|---|---|
project_id + |
+Yes + |
+Specifies the project ID. +For details about how to obtain the project ID, see Obtaining a Project ID. + |
+
If period is 1, the maximum interval between from and to is 4 hours. If the interval between from and to is longer than 4 hours, adjust the value of from to to - 4*3600*1000.
+If period is 300, the maximum interval between from and to is 1 day. If the interval between from and to is longer than 1 day, adjust the value of from to to - 24*3600*1000.
+If period is 1200, the maximum interval between from and to is 3 days. If the interval between from and to is longer than three days, adjust the value of from to to - 3*24*3600*1000.
+If period is 3600, the maximum interval between from and to is 10 days. If the interval between from and to is longer than 10 days, adjust the value of from to to - 10*24*3600*1000.
+If period is 14400, the maximum interval between from and to is 30 days. If the interval between from and to is longer than 30 days, adjust the value of from to to - 30*24*3600*1000.
+If period is 86400, the maximum interval between from and to is 180 days. If the interval between from and to is longer than 180 days, adjust the value of from to to - 180*24*3600*1000.
+Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
|---|---|---|---|
metrics + |
+Yes + |
+Arrays of objects + |
+Specifies the metric data. The maximum length of the array is 10. +For details, see Table 3. + |
+
from + |
+Yes + |
+long + |
+Specifies the start time of the query. The time is a UNIX timestamp and the unit is ms. Set from to at least one period earlier than the current time. Rollup aggregates the raw data generated within a period to the start time of the period. Therefore, if from and to are within a period, the query result will be empty due to the rollup failure. Set from to at least one period earlier than the current time. Take the 5-minute period as an example. If it is 10:35 now, the raw data generated between 10:30 and 10:35 will be aggregated to 10:30. Therefore, in this example, if period is 5 minutes, from should be 10:30. + NOTE:
+Cloud Eye rounds up from based on the level of granularity required to perform the rollup. + |
+
to + |
+Yes + |
+long + |
+Specifies the end time of the query. The time is a UNIX timestamp and the unit is ms. from must be earlier than to. + |
+
period + |
+Yes + |
+String + |
+Specifies how often Cloud Eye aggregates data, which can be +
|
+
filter + |
+Yes + |
+String + |
+Specifies the data rollup method, which can be +
filter does not affect the query result of raw data. (The period is 1.) + |
+
Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
|---|---|---|---|
namespace + |
+Yes + |
+String + |
+Specifies the metric namespace, which must be in the service.item format and contain 3 to 32 characters. +service and item each must start with a letter and contain only letters, digits, and underscores (_). + |
+
dimensions + |
+Yes + |
+Arrays of objects + |
+Specifies the list of the metric dimensions. +Each dimension is a JSON object, and its structure is as follows: +{ +"name": "instance_id", +"value": "33328f02-3814-422e-b688-bfdba93d4050" +} +For details, see Table 4. + |
+
metric_name + |
+Yes + |
+String + |
+Specifies the metric name. Start with a letter. Enter 1 to 64 characters. Only letters, digits, and underscores (_) are allowed. + |
+
Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
|---|---|---|---|
name + |
+Yes + |
+String + |
+Specifies the dimension. For example, the ECS dimension is instance_id. For details about the dimension of each service, see the key column in Services Interconnected with Cloud Eye. +Start with a letter. Enter 1 to 32 characters. Only letters, digits, underscores (_), and hyphens (-) are allowed. + |
+
value + |
+Yes + |
+String + |
+Specifies the dimension value, for example, an ECS ID. +Start with a letter or a digit. Enter 1 to 256 characters. Only letters, digits, underscores (_), and hyphens (-) are allowed. + |
+
{
+ "metrics": [
+ {
+ "namespace": "SYS.ECS",
+ "dimensions": [
+ {
+ "name": "instance_id",
+ "value": "faea5b75-e390-4e2b-8733-9226a9026070"
+ }
+ ],
+ "metric_name": "cpu_util"
+ },
+ {
+ "namespace": "SYS.ECS",
+ "dimensions": [
+ {
+ "name": "instance_id",
+ "value": "06b4020f-461a-4a52-84da-53fa71c2f42b"
+ }
+ ],
+ "metric_name": "network_vm_connections"
+ }
+ ],
+ "from": 1556625600000,
+ "to": 1556632800000,
+ "period": "1",
+ "filter": "average"
+}
+
+{
+ "metrics": [
+ {
+ "namespace": "SYS.RDS",
+ "dimensions": [
+ {
+ "name": "rds_cluster_id",
+ "value": "3c8cc15614ab46f5b8743317555e0de2in01"
+ }
+ ],
+ "metric_name": "rds021_myisam_buf_usage"
+ },
+ {
+ "namespace": "SYS.RDS",
+ "dimensions": [
+ {
+ "name": "rds_cluster_id",
+ "value": "3b2fa8b55a9b4adca3713962a9d31884in01"
+ }
+ ],
+ "metric_name": "rds021_myisam_buf_usage"
+ }
+ ],
+ "from": 1556625600000,
+ "to": 1556632800000,
+ "period": "1",
+ "filter": "sum"
+}
+{
+ "metrics": [
+ {
+ "namespace": "AGT.ECS",
+ "dimensions": [
+ {
+ "name": "instance_id",
+ "value": "cd841102-f6b1-407d-a31f-235db796dcbb"
+ },
+ {
+ "name": "proc",
+ "value": "b28354b543375bfa94dabaeda722927"
+ }
+ ],
+ "metric_name": "proc_specified_count"
+ }
+ ],
+ "from": 1556625600000,
+ "to": 1556632800000,
+ "period": "1200",
+ "filter": "min"
+}
+Parameter + |
+Type + |
+Description + |
+
|---|---|---|
metrics + |
+Arrays of objects + |
+Specifies the metric data. +For details, see Table 6. + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
unit + |
+String + |
+Specifies the metric unit. + |
+
datapoints + |
+Arrays of objects + |
+Specifies the metric data list. Since Cloud Eye rounds up from based on the level of granularity for data query, datapoints may contain more data points than expected. +For details, see Table 8. + |
+
namespace + |
+String + |
+Specifies the metric namespace, which must be in the service.item format and contain 3 to 32 characters. service and item each must start with a letter and contain only letters, digits, and underscores (_). + |
+
dimensions + |
+Arrays of objects + |
+Specifies the list of metric dimensions. +Each dimension is a JSON object, and its structure is as follows: +{ +"name": "instance_id", +"value": "33328f02-3814-422e-b688-bfdba93d4050" +} +For details, see Table 7. + |
+
metric_name + |
+String + |
+Specifies the metric name. Start with a letter. Enter 1 to 64 characters. Only letters, digits, and underscores (_) are allowed. + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
name + |
+String + |
+Specifies the dimension. For example, the ECS dimension is instance_id. For details about the dimension of each service, see the key column in Services Interconnected with Cloud Eye. +Start with a letter. Enter 1 to 32 characters. Only letters, digits, underscores (_), and hyphens (-) are allowed. + |
+
value + |
+String + |
+Specifies the dimension value, for example, an ECS ID. +Start with a letter or a digit. Enter 1 to 256 characters. Only letters, digits, underscores (_), and hyphens (-) are allowed. + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
average + |
+double + |
+Specifies the average value of metric data within a rollup period. + |
+
max + |
+double + |
+Specifies the maximum value of metric data within a rollup period. + |
+
min + |
+double + |
+Specifies the minimum value of metric data within a rollup period. + |
+
sum + |
+double + |
+Specifies the sum of metric data within a rollup period. + |
+
variance + |
+double + |
+Specifies the variance of metric data within a rollup period. + |
+
timestamp + |
+long + |
+Specifies when the metric is collected. It is a UNIX timestamp in milliseconds. + |
+
{
+ "metrics": [
+ {
+ "namespace": "SYS.ECS",
+ "metric_name": "cpu_util",
+ "dimensions": [
+ {
+ "name": "instance_id",
+ "value": "faea5b75-e390-4e2b-8733-9226a9026070"
+ }
+ ],
+ "datapoints": [
+ {
+ "average": 0.69,
+ "timestamp": 1556625610000
+ },
+ {
+ "average": 0.7,
+ "timestamp": 1556625715000
+ }
+ ],
+ "unit": "%"
+ },
+ {
+ "namespace": "SYS.ECS",
+ "metric_name": "network_vm_connections",
+ "dimensions": [
+ {
+ "name": "instance_id",
+ "value": "06b4020f-461a-4a52-84da-53fa71c2f42b"
+ }
+ ],
+ "datapoints": [
+ {
+ "average": 1,
+ "timestamp": 1556625612000
+ },
+ {
+ "average": 3,
+ "timestamp": 1556625717000
+ }
+ ],
+ "unit": "count"
+ }
+ ]
+}
+{
+ "metrics": [
+ {
+ "unit": "Ratio",
+ "datapoints": [
+ {
+ "sum": 0.07,
+ "timestamp": 1556625628000
+ },
+ {
+ "sum": 0.07,
+ "timestamp": 1556625688000
+ }
+ ],
+ "namespace": "SYS.RDS",
+ "dimensions": [
+ {
+ "name": "rds_cluster_id",
+ "value": "3c8cc15614ab46f5b8743317555e0de2in01"
+ }
+ ],
+ "metric_name": "rds021_myisam_buf_usage"
+ },
+ {
+ "unit": "Ratio",
+ "datapoints": [
+ {
+ "sum": 0.06,
+ "timestamp": 1556625614000
+ },
+ {
+ "sum": 0.07,
+ "timestamp": 1556625674000
+ }
+ ],
+ "namespace": "SYS.RDS",
+ "dimensions": [
+ {
+ "name": "rds_cluster_id",
+ "value": "3b2fa8b55a9b4adca3713962a9d31884in01"
+ }
+ ],
+ "metric_name": "rds021_myisam_buf_usage"
+ }
+ ]
+}
+{
+ "metrics": [
+ {
+ "unit": "Ratio",
+ "datapoints": [
+ {
+ "min": 0,
+ "timestamp": 1556625612000
+ },
+ {
+ "min": 0,
+ "timestamp": 1556625672000
+ }
+ ],
+ "namespace": "AGT.ECS",
+ "dimensions": [
+ {
+ "name": "instance_id",
+ "value": "cd841102-f6b1-407d-a31f-235db796dcbb"
+ },
+ {
+ "name": "proc",
+ "value": "b28354b543375bfa94dabaeda722927f"
+ }
+ ],
+ "metric_name": "rds021_myisam_buf_usage"
+ }
+ ]
+}
+Returned Value + |
+Description + |
+
|---|---|
400 Bad Request + |
+Request error. + |
+
401 Unauthorized + |
+The authentication information is not provided or is incorrect. + |
+
403 Forbidden + |
+Access to the requested page is forbidden. + |
+
408 Request Timeout + |
+The request timed out. + |
+
429 Too Many Requests + |
+Concurrent requests are excessive. + |
+
500 Internal Server Error + |
+Failed to complete the request because of an internal service error. + |
+
503 Service Unavailable + |
+The service is currently unavailable. + |
+
See Error Codes.
+This API is used to query the host configuration for a specified event type in a specified period of time. You can specify the dimension of data to be queried.
+
This API is provided for SAP Monitor in the HANA scenario to query the host configuration. In other scenarios, the host configuration cannot be queried with this API.
+GET /V1.0/{project_id}/event-data
+Parameter + |
+Mandatory + |
+Description + |
+
|---|---|---|
project_id + |
+Yes + |
+Specifies the project ID. +For details about how to obtain the project ID, see Obtaining a Project ID. + |
+
Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
|---|---|---|---|
namespace + |
+Yes + |
+String + |
+Query the namespace of a service. For details, see Services Interconnected with Cloud Eye. +The namespace must be in the service.item format and contain 3 to 32 characters. service and item each must start with a letter and contain only letters, digits, and underscores (_). + |
+
type + |
+Yes + |
+String + |
+Specifies the event type. +It can contain only letters, underscores (_), and hyphens (-). It must start with a letter and cannot exceed 64 characters, for example, instance_host_info. + |
+
from + |
+Yes + |
+String + |
+Specifies the start time of the query. +The time is a UNIX timestamp and the unit is ms. + |
+
to + |
+Yes + |
+String + |
+Specifies the end time of the query. +The time is a UNIX timestamp and the unit is ms. +from must be earlier than to. + |
+
dim + |
+Yes + |
+String + |
+Specifies the dimension. For example, the ECS dimension is instance_id. For details about the dimensions corresponding to the monitoring metrics of each service, see the monitoring metrics description of the corresponding service in Services Interconnected with Cloud Eye. +Specifies the dimension. A maximum of three dimensions are supported, and the dimensions are numbered from 0 in dim.{i}=key,value format. key cannot exceed 32 characters and value cannot exceed 256 characters. +Example: dim.0=instance_id,i-12345 + |
+
GET https://{Cloud Eye endpoint}/V1.0/{project_id}/event-data?namespace=SYS.ECS&dim.0=instance_id,33328f02-3814-422e-b688-bfdba93d4051&type=instance_host_info&from=1450234543422&to=1450320943422
+None
+Parameter + |
+Type + |
+Description + |
+
|---|---|---|
datapoints + |
+Array of objects + |
+Specifies the configuration list. +If the corresponding configuration information does not exist, datapoints is an empty array and is []. +For details, see Table 3. + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
type + |
+String + |
+Specifies the event type, for example, instance_host_info. + |
+
timestamp + |
+long + |
+Specifies when the event is reported. It is a UNIX timestamp and the unit is ms. + |
+
value + |
+String + |
+Specifies the host configuration information. + |
+
{
+ "datapoints": [
+ {
+ "type": "instance_host_info",
+ "timestamp": 1450231200000,
+ "value": "xxx"
+ },
+ {
+ "type": "instance_host_info",
+ "timestamp": 1450231800000,
+ "value": "xxx"
+ }
+ ]
+}
+Returned Value + |
+Description + |
+
|---|---|
400 Bad Request + |
+Request error. + |
+
401 Unauthorized + |
+The authentication information is not provided or is incorrect. + |
+
403 Forbidden + |
+You are forbidden to access the page requested. + |
+
408 Request Timeout + |
+The request timed out. + |
+
429 Too Many Requests + |
+Concurrent requests are excessive. + |
+
500 Internal Server Error + |
+Failed to complete the request because of an internal service error. + |
+
503 Service Unavailable + |
+The service is currently unavailable. + |
+
See Error Codes.
+This API is used to query a resource quota and the used amount. The current resource refers to alarm rules only.
+GET /V1.0/{project_id}/quotas
+Parameter + |
+Mandatory + |
+Description + |
+
|---|---|---|
project_id + |
+Yes + |
+Specifies the project ID. +For details about how to obtain the project ID, see Obtaining a Project ID. + |
+
GET https://{Cloud Eye endpoint}/V1.0/{project_id}/quotas
+None
+Parameter + |
+Type + |
+Description + |
+
|---|---|---|
quotas + |
+Object + |
+Specifies the quota list. +For details, see Table 3. + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
resources + |
+Array of objects + |
+Specifies the resource quota list. +For details, see Table 4. + |
+
Parameter + |
+Type + |
+Description + |
+
|---|---|---|
type + |
+String + |
+Specifies the quota type. +alarm indicates the alarm rule. + |
+
used + |
+Integer + |
+Specifies the used amount of the quota. + |
+
unit + |
+String + |
+Specifies the quota unit. + |
+
quota + |
+Integer + |
+Specifies the total amount of the quota. + |
+
{
+"quotas":
+ {
+ "resources": [
+ {
+ "unit":"",
+ "type":"alarm",
+ "quota":1000,
+ "used":10
+ }
+ ]
+ }
+}
+Returned Value + |
+Description + |
+
|---|---|
400 Bad Request + |
+Request error. + |
+
401 Unauthorized + |
+The authentication information is not provided or is incorrect. + |
+
403 Forbidden + |
+Access to the requested page is forbidden. + |
+
408 Request Timeout + |
+The request timed out. + |
+
429 Too Many Requests + |
+Concurrent requests are excessive. + |
+
500 Internal Server Error + |
+Failed to complete the request because of an internal service error. + |
+
503 Service Unavailable + |
+The service is currently unavailable. + |
+
See Error Codes.
+Returned Value + |
+Description + |
+
|---|---|
200 OK + |
+The results of GET and PUT operations are returned as expected. + |
+
201 Created + |
+The results of the POST operation are returned as expected. + |
+
202 Accepted + |
+The request has been accepted for processing. + |
+
204 No Content + |
+The results of the DELETE operation are returned as expected. + |
+
Returned Value + |
+Description + |
+
|---|---|
400 Bad Request + |
+The server failed to process the request. + |
+
401 Unauthorized + |
+You must enter a username and password to access the requested page. + |
+
403 Forbidden + |
+You are forbidden to access the requested page. + |
+
404 Not Found + |
+The server cannot find the requested page. + |
+
405 Method Not Allowed + |
+You are not allowed to use the method specified in the request. + |
+
406 Not Acceptable + |
+The response generated by the server cannot be accepted by the client. + |
+
407 Proxy Authentication Required + |
+You must use the proxy server for authentication so that the request can be processed. + |
+
408 Request Timeout + |
+The request timed out. + |
+
409 Conflict + |
+The request could not be processed due to a conflict. + |
+
500 Internal Server Error + |
+Failed to complete the request because of a service error. + |
+
501 Not Implemented + |
+Failed to complete the request because the server does not support the requested function. + |
+
502 Bad Gateway + |
+Failed to complete the request because the request is invalid. + |
+
503 Service Unavailable + |
+Failed to complete the request. The service is unavailable. + |
+
504 Gateway Timeout + |
+A gateway timeout error occurred. + |
+
On the My Credentials page, view project IDs in the project list.
+
In multi-project scenarios, expand the region, and obtain your sub-project ID from the Project ID column.
+Category + |
+Service + |
+Namespace + |
+Reference + |
+
|---|---|---|---|
Compute + |
+Elastic Cloud Server + |
+SYS.ECS + |
++ | +
Bare Metal Server + |
+SERVICE.BMS + |
++ | +|
Auto Scaling + |
+SYS.AS + |
++ | +|
Storage + |
+Elastic Volume Service (attached to an ECS or BMS) + |
+SYS.EVS + |
++ | +
Scalable File Service + |
+SYS.SFS + |
++ | +|
SFS Turbo + |
+SYS.EFS + |
++ | +|
Cloud Backup and Recovery + |
+SYS.CBR + |
++ | +|
Network + |
+Elastic IP and bandwidth + |
+SYS.VPC + |
++ | +
Elastic Load Balance + |
+SYS.ELB + |
++ | +|
NAT Gateway + |
+SYS.NAT + |
++ | +|
Security + |
+Web Application Firewall + |
+SYS.WAF + |
++ | +
Application + |
+Distributed Message Service + |
+SYS.DMS + |
++ | +
Distributed Cache Service + |
+SYS.DCS + |
++ | +|
Database + |
+Relational Database Service + |
+SYS.RDS + |
++ + + | +
Document Database Service + |
+SYS.DDS + |
++ | +|
GaussDB NoSQL + |
+SYS.NoSQL + |
++ | +|
GaussDB(for MySQL) + |
+SYS.GAUSSDB + |
++ | +|
GaussDB(for openGauss) + |
+SYS.GAUSSDBV5 + |
++ | +|
Data analysis + |
+Data Warehouse Service + |
+SYS.DWS + |
++ | +
Cloud Search Service + |
+SYS.ES + |
++ | +
Released On + |
+Description + |
+
|---|---|
2022-10-10 + |
+This release incorporates the following change: +Added section "Events Supported by Event Monitoring". + |
+
2021-02-19 + |
+Accepted for RM-3379. + |
+
2020-08-15 + |
+Accepted for RM-389. + |
+
2020-03-06 + |
+This release incorporates the following changes: +
|
+
2019-08-31 + |
+This release incorporates the following change: +Added Event Monitoring. + |
+
2019-03-30 + |
+This release incorporates the following changes: +
|
+
2018-12-30 + |
+This release incorporates the following changes: +
Added +Interconnected with Document Database Service (DDS). + |
+
2018-09-30 + |
+This release incorporates the following changes: +
|
+
2018-08-30 + |
+This release incorporates the following change: +Interconnected with Cloud Search Service (CSS). + |
+
2018-06-30 + |
+This release incorporates the following change: +Added metrics for the enhanced load balancer and enhanced load balancer listener. + |
+
2018-05-30 + |
+This release incorporates the following change: +Accepted in OTC 3.1. + |
+
2018-03-30 + |
+This release incorporates the following change: +Added Virtual Private Cloud (VPC) traffic metrics. + |
+
2018-02-28 + |
+This release incorporates the following change: +Updated Virtual Private Cloud (VPC) metrics. + |
+
2017-12-30 + |
+This release incorporates the following changes: +
|
+
2017-11-30 + |
+This release incorporates the following change: +Added Auto Scaling (AS) metrics. + |
+
2017-10-30 + |
+This release incorporates the following changes: +
|
+
2017-10-09 + |
+This release incorporates the following change: +Added the API for querying the host configuration. + |
+
2017-07-30 + |
+This release incorporates the following changes:
+
|
+
2017-05-26 + |
+This release incorporates the following change: +Added Distributed Message Service (DMS) metrics. + |
+
2017-04-28 + |
+This release incorporates the following change: +Added Virtual Private Cloud (VPC) traffic metrics. + |
+
2017-02-27 + |
+This release incorporates the following change: +Added the setting description for the from parameter. + |
+
2016-12-30 + |
+This release incorporates the following change: +Added Relational Database Service (RDS) metrics. + |
+
2016-10-29 + |
+This release incorporates the following change: +Added Elastic Load Balance (ELB) metrics. + |
+
2016-10-19 + |
+This release incorporates the following change: +Deleted Resource Template Service (RTS) metrics. + |
+
2016-9-30 + |
+This release incorporates the following change: +Added Resource Template Service (RTS) metrics. + |
+
2016-8-25 + |
+This release incorporates the following changes: +
|
+
2016-07-30 + |
+This release incorporates the following changes: +
|
+
2016-04-14 + |
+This release incorporates the following changes: +
|
+
2016-03-09 + |
+This issue is the first official release. + |
+
This API is used to query the events, including system events and custom events.
+GET /V1.0/{project_id}/events
+Parameter + |
+Type + |
+Mandatory + |
+Description + |
+
|---|---|---|---|
project_id + |
+String + |
+Yes + |
+Specifies the project ID. +For details about how to obtain the project ID, see Obtaining a Project ID. + |
+
event_type + |
+String + |
+No + |
+Specifies the event type. Possible types are EVENT.SYS (system event) and EVENT.CUSTOM (custom event). + |
+
event_name + |
+String + |
+No + |
+Specifies the event name. The name can be a system event name or a custom event name. + |
+
from + |
+Integer + |
+No + |
+Specifies the start time of the query. The time is a UNIX timestamp and the unit is ms. Example: 1605952700911 + |
+
to + |
+Integer + |
+No + |
+Specifies the end time of the query. The time is a UNIX timestamp and the unit is ms. from must be smaller than to. For example, set to to 1606557500911. + |
+
start + |
+Integer + |
+No + |
+Specifies the start value of pagination. The value is an integer. The default value is 0. + |
+
limit + |
+Integer + |
+No + |
+Specifies the maximum number of events that can be queried at a time. Supported range: 1 to 100 (default) + |
+
GET https://{Cloud Eye endpoint}/V1.0/{project_id}/events
+None
+Parameter + |
+Type + |
+Mandatory + |
+Description + |
+
|---|---|---|---|
events + |
+Array of Events objects + |
+No + |
+Specifies one or more pieces of event data. +For details, see Table 3. + |
+
meta_data + |
+MetaData object + |
+No + |
+Specifies the number of metadata records in the query result. +For details, see Table 4. + |
+
Parameter + |
+Type + |
+Mandatory + |
+Description + |
+
|---|---|---|---|
event_name + |
+String + |
+No + |
+Specifies the event name. + |
+
event_type + |
+String + |
+No + |
+Specifies the event type. + |
+
event_count + |
+Integer + |
+No + |
+Specifies the number of occurrences of this event within the specified query time range. + |
+
latest_occur_time + |
+Long + |
+No + |
+Specifies when the event last occurred. + |
+
latest_event_source + |
+String + |
+No + |
+Specifies the event source. If the event is a system event, the value is the namespace of each service. To view the namespace of each service, see Services Interconnected with Cloud Eye. +If the event is a custom event, the event source is defined by the user. + |
+
{
+ "events": [
+ {
+ "event_name": "rebootServer",
+ "event_type": "EVENT.SYS",
+ "event_count": 5,
+ "latest_occur_time": 1606302400000,
+ "latest_event_source": "SYS.ECS"
+ },
+ {
+ "event_name": "deleteVolume",
+ "event_type": "EVENT.SYS",
+ "event_count": 6,
+ "latest_occur_time": 1606300359126,
+ "latest_event_source": "SYS.EVS"
+ },
+ {
+ "event_name": "event_001",
+ "event_type": "EVENT.CUSTOM",
+ "event_count": 4,
+ "latest_occur_time": 1606499035522,
+ "latest_event_source": "TEST.System"
+ }
+ ],
+ "meta_data": {
+ "total": 10
+ }
+}
+Returned Value + |
+Description + |
+
|---|---|
400 Bad Request + |
+Request error. + |
+
401 Unauthorized + |
+The authentication information is not provided or is incorrect. + |
+
403 Forbidden + |
+Access to the requested page is forbidden. + |
+
408 Request Timeout + |
+The request timed out. + |
+
429 Too Many Requests + |
+Concurrent requests are excessive. + |
+
500 Internal Server Error + |
+Failed to complete the request because of an internal service error. + |
+
503 Service Unavailable + |
+The service is currently unavailable. + |
+
See Error Codes.
+This API is used to query the event details based on the event name.
+GET /V1.0/{project_id}/event/{event_name}
+Parameter + |
+Type + |
+Mandatory + |
+Description + |
+
|---|---|---|---|
project_id + |
+String + |
+Yes + |
+Specifies the project ID. +For details about how to obtain the project ID, see Obtaining a Project ID. + |
+
event_name + |
+String + |
+Yes + |
+Specifies the event name. + |
+
event_type + |
+String + |
+Yes + |
+Specifies the event type. Possible types are EVENT.SYS (system event) and EVENT.CUSTOM (custom event). + |
+
event_source + |
+String + |
+No + |
+Specifies the event name. The name can be a system event name or a custom event name. + |
+
event_level + |
+String + |
+No + |
+Specifies the event severity. Possible severities are Critical, Major, Minor, and Info. + |
+
event_user + |
+String + |
+No + |
+Specifies the name of the user who reports the event monitoring data. It can also be a project ID. + |
+
event_state + |
+String + |
+No + |
+Specifies the event status. Possible statuses are normal, warning, or incident. + |
+
from + |
+Integer + |
+No + |
+Specifies the start time of the query. The time is a UNIX timestamp and the unit is ms. Example: 1605952700911 + |
+
to + |
+Integer + |
+No + |
+No +Specifies the end time of the query. The time is a UNIX timestamp and the unit is ms. The from value must be smaller than the to value. + |
+
start + |
+Integer + |
+No + |
+Specifies the start value of pagination. The value is an integer. The default value is 0. + |
+
limit + |
+Integer + |
+No + |
+Specifies the maximum number of records that can be queried at a time. Supported range: 1 to 100 (default) + |
+
GET https://{Cloud Eye endpoint}/V1.0/{project_id}/event/{event_name}
+None
+Parameter + |
+Type + |
+Mandatory + |
+Description + |
+
|---|---|---|---|
event_name + |
+string + |
+No + |
+Specifies the event name. The name can be a system event name or a custom event name. + |
+
event_type + |
+string + |
+No + |
+Specifies the event type. Possible types are EVENT.SYS (system event) and EVENT.CUSTOM (custom event). + |
+
event_users + |
+Array of strings + |
+No + |
+Specifies the name of the user who reports the event. It can also be a project ID. + |
+
event_sources + |
+Array of strings + |
+No + |
+Specifies the event source. If the event is a system event, the source is the namespace of each service. To view the namespace of each service, see Services Interconnected with Cloud Eye. If the event is a custom event, the event source is defined by the user. + |
+
event_info + |
+Array of objects + |
+No + |
+Specifies details about one or more events. +For details, see Table 3. + |
+
meta_data + |
+MetaData object + |
+No + |
+Specifies the number of metadata records in the query result. +For details, see Table 5. + |
+
Parameter + |
+Type + |
+Mandatory + |
+Description + |
+
|---|---|---|---|
event_name + |
+string + |
+Yes + |
+Specifies the event name. Start with a letter. Enter 1 to 64 characters. Only letters, digits, and underscores (_) are allowed. + |
+
event_source + |
+string + |
+No + |
+Specifies the event source in the format of service.item. service and item each must start with a letter and contain 3 to 32 characters, including only letters, digits, and underscores (_). + |
+
time + |
+long + |
+Yes + |
+Specifies when the event occurred, which is a UNIX timestamp (ms). Since there is a latency between the client and the server, the data timestamp to be inserted should be within the period that starts from one hour before the current time plus 20s to 10 minutes after the current time minus 20s. In this way, the timestamp will be inserted to the database without being affected by the latency. + |
+
detail + |
+Detail object + |
+Yes + |
+Specifies the event details. +For details, see Table 4. + |
+
event_id + |
+string + |
+No + |
+Specifies the event ID. + |
+
Parameter + |
+Type + |
+Mandatory + |
+Description + |
+
|---|---|---|---|
content + |
+string + |
+No + |
+Specifies the event content. Enter up to 4096 characters. + |
+
group_id + |
+string + |
+No + |
+Specifies the resource group the event belongs to. This ID must be an existing resource group ID. + |
+
resource_id + |
+string + |
+No + |
+Specifies the resource ID, which can contain a maximum of 128 characters. + |
+
resource_name + |
+string + |
+No + |
+Specifies the resource name, which can contain a maximum of 128 characters. + |
+
event_state + |
+string + |
+No + |
+Specifies the event status. +Valid value can be normal, warning, or incident. + |
+
event_level + |
+string + |
+No + |
+Specifies the event severity. +Its value can be Critical, Major, Minor, or Info. + |
+
event_user + |
+string + |
+No + |
+Specifies the event user. Enter up to 64 characters. + |
+
event_type + |
+string + |
+No + |
+Specifies the event type. +Possible types are EVENT.SYS (system event) and EVENT.CUSTOM (custom event). + |
+
{
+ "event_name": "rebootServer",
+ "event_type": "EVENT.SYS",
+ "event_users": [
+ ""
+ ],
+ "event_sources": [
+ "SYS.ECS"
+ ],
+ "event_info": [
+ {
+ "event_id": "ev1606302402256R6doP5YeZ",
+ "event_name": "rebootServer",
+ "event_source": "SYS.ECS",
+ "time": 1606302400000,
+ "detail": {
+ "content": "{\"resourceSpecCode\":\"kc1.4xlarge.2.linux\",\"enterpriseProjectId\":\"6efb843e-391a-46a8-afc8-7fe51c9dd575\"}",
+ "group_id": "",
+ "resource_id": "ef8dad27-0488-4de7-bb43-1a0df9806d90",
+ "resource_name": "CES-POROS-0001",
+ "event_state": "normal",
+ "event_level": "Minor",
+ "event_user": "",
+ "event_type": "EVENT.SYS"
+ }
+ },
+ {
+ "event_id": "ev1606296088071wGoAOxVYa",
+ "event_name": "rebootServer",
+ "event_source": "SYS.ECS",
+ "time": 1606296086000,
+ "detail": {
+ "content": "{\"resourceSpecCode\":\"kc1.4xlarge.2.linux\",\"enterpriseProjectId\":\"6efb843e-391a-46a8-afc8-7fe51c9dd575\"}",
+ "group_id": "",
+ "resource_id": "ef8dad27-0488-4de7-bb43-1a0df9806d90",
+ "resource_name": "CES-POROS-0001",
+ "event_state": "normal",
+ "event_level": "Minor",
+ "event_user": "",
+ "event_type": "EVENT.SYS"
+ }
+ },
+ {
+ "event_id": "ev1604654426090g7g37E6Yb",
+ "event_name": "rebootServer",
+ "event_source": "SYS.ECS",
+ "time": 1604654425000,
+ "detail": {
+ "content": "{\"resourceSpecCode\":\"c6.4xlarge.2.linux\",\"enterpriseProjectId\":\"129559eb-f795-4b5f-9e46-cbd43a462362\"}",
+ "group_id": "",
+ "resource_id": "0bfa63ee-31f5-40a9-b992-50992c80c58a",
+ "resource_name": "ndrv2-pod-ops-0001",
+ "event_state": "normal",
+ "event_level": "Minor",
+ "event_user": "",
+ "event_type": "EVENT.SYS"
+ }
+ }
+ ],
+ "meta_data": {
+ "total": 5
+ }
+}
+Returned Value + |
+Description + |
+
|---|---|
400 Bad Request + |
+Request error. + |
+
401 Unauthorized + |
+The authentication information is not provided or is incorrect. + |
+
403 Forbidden + |
+Access to the requested page is forbidden. + |
+
408 Request Timeout + |
+The request timed out. + |
+
429 Too Many Requests + |
+Concurrent requests are excessive. + |
+
500 Internal Server Error + |
+Failed to complete the request because of an internal service error. + |
+
503 Service Unavailable + |
+The service is currently unavailable. + |
+
See Error Codes.
+This API is used to add one or more pieces of custom metric monitoring data to solve the problem that the system metrics cannot meet specific service requirements.
+POST /V1.0/{project_id}/metric-data
+Parameter + |
+Mandatory + |
+Description + |
+
|---|---|---|
project_id + |
+Yes + |
+Specifies the project ID. +For details about how to obtain the project ID, see Obtaining a Project ID. + |
+
Parameter + |
+Type + |
+Mandatory + |
+Description + |
+
|---|---|---|---|
Array elements + |
+Array of objects + |
+Yes + |
+Specifies whether to add one or more pieces of custom metric monitoring data. +For details, see Table 3. + |
+
Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
|---|---|---|---|
metric + |
+Yes + |
+Object + |
+Specifies the metric data. +For details, see Table 4. + |
+
ttl + |
+Yes + |
+Integer + |
+Specifies the data validity period. The unit is second. +Supported range: 1 to 604800 +If the validity period expires, the data will be automatically deleted. + |
+
collect_time + |
+Yes + |
+long + |
+Specifies when the data was collected. +The time is UNIX timestamp (ms) format. + NOTE:
+Since there is a latency between the client and the server, the data timestamp to be inserted should be within the period that starts from three days before the current time plus 20s to 10 minutes after the current time minus 20s. In this way, the timestamp will be inserted to the database without being affected by the latency. + |
+
value + |
+Yes + |
+double + |
+Specifies the monitoring metric data to be added, which can be an integer or a floating point number. + |
+
unit + |
+No + |
+String + |
+Specifies the data unit. +Enter a maximum of 32 characters. + |
+
type + |
+No + |
+String + |
+Specifies the enumerated type. +Possible types: +
|
+
Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
|---|---|---|---|
namespace + |
+Yes + |
+String + |
+Specifies the customized namespace. For details, see Services Interconnected with Cloud Eye. +The namespace must be in the service.item format and contain 3 to 32 characters. service and item each must start with a letter and contain only letters, digits, and underscores (_). In addition, service cannot start with SYS, AGT, or SRE, and namespace cannot be SERVICE.BMS because this namespace has been used by the system. +You can leave this parameter blank when you set alarm_type to (EVENT.SYS| EVENT.CUSTOM). + |
+
dimensions + |
+Yes + |
+Array of objects + |
+Specifies the metric dimension. A maximum of three dimensions are supported. +For details, see Table 5. + |
+
metric_name + |
+Yes + |
+String + |
+Specifies the metric ID. For example, if the monitoring metric of an ECS is CPU usage, metric_name is cpu_util. For details, see Services Interconnected with Cloud Eye. + |
+
Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
|---|---|---|---|
name + |
+Yes + |
+String + |
+Specifies the dimension. For example, the ECS dimension is instance_id. For details about the dimension of each service, see the key column in Services Interconnected with Cloud Eye. +Start with a letter. Enter 1 to 32 characters. Only letters, digits, underscores (_), and hyphens (-) are allowed. + |
+
value + |
+Yes + |
+String + |
+Specifies the dimension value, for example, an ECS ID. +Start with a letter or a digit. Enter 1 to 256 characters. Only letters, digits, underscores (_), and hyphens (-) are allowed. + |
+
[
+ {
+ "metric": {
+ "namespace": "MINE.APP",
+ "dimensions": [
+ {
+ "name": "instance_id",
+ "value": "6f3c6f91-4b24-4e1b-b7d1-a94ac1cb011d"
+ }
+ ],
+ "metric_name": "cpu_util"
+ },
+ "ttl": 172800,
+ "collect_time": 1463598260000,
+ "type": "float",
+ "value": 0.09,
+ "unit": "%"
+ },
+ {
+ "metric": {
+ "namespace": "MINE.APP",
+ "dimensions": [
+ {
+ "name": "instance_id",
+ "value": "6f3c6f91-4b24-4e1b-b7d1-a94ac1cb011d"
+ }
+ ],
+ "metric_name": "cpu_util"
+ },
+ "ttl": 172800,
+ "collect_time": 1463598270000,
+ "type": "float",
+ "value": 0.12,
+ "unit": "%"
+ }
+]
+[
+ {
+ "metric": {
+ "namespace": "SYS.RDS",
+ "dimensions": [
+ {
+ "name": "rds_cluster_id",
+ "value": "3c8cc15614ab46f5b8743317555e0de2in01"
+ }
+ ],
+ "metric_name": "rds021_myisam_buf_usage"
+ },
+ "ttl": 172800,
+ "collect_time": 1463598260000,
+ "type": "float",
+ "value": 0.01,
+ "unit": "Ratio"
+ }
+]
+The response has no message body.
+Returned Value + |
+Description + |
+
|---|---|
400 Bad Request + |
+Request error. + |
+
401 Unauthorized + |
+The authentication information is not provided or is incorrect. + |
+
403 Forbidden + |
+You are forbidden to access the page requested. + |
+
408 Request Timeout + |
+The request timed out. + |
+
429 Too Many Requests + |
+Concurrent requests are excessive. + |
+
500 Internal Server Error + |
+Failed to complete the request because of an internal service error. + |
+
503 Service Unavailable + |
+The service is currently unavailable. + |
+
See Error Codes.
+An API for reporting custom events is provided, which helps you collect and report abnormal events or important change events to Cloud Eye.
+POST /V1.0/{project_id}/events
+Parameter + |
+Mandatory + |
+Description + |
+
|---|---|---|
project_id + |
+Yes + |
+Specifies the project ID. +For details about how to obtain the project ID, see Obtaining a Project ID. + |
+
POST https://{Cloud Eye endpoint}/V1.0/{project_id}/events
+Parameter + |
+Type + |
+Mandatory + |
+Description + |
+
|---|---|---|---|
Array elements + |
+Arrays of objects + |
+Yes + |
+Specifies the event list. +For details, see Table 3. + |
+
Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
|---|---|---|---|
event_name + |
+Yes + |
+String + |
+Specifies the event name. +Start with a letter. Enter 1 to 64 characters. Only letters, digits, and underscores (_) are allowed. + |
+
event_source + |
+Yes + |
+String + |
+Specifies the event source. +The format is service.item. Set this parameter based on the site requirements. +service and item each must be a string that starts with a letter and contains 3 to 32 characters, including only letters, digits, and underscores (_). + |
+
time + |
+Yes + |
+long + |
+Specifies when the event occurred, which is a UNIX timestamp (ms). + NOTE:
+Since there is a latency between the client and the server, the data timestamp to be inserted should be within the period that starts from one hour before the current time plus 20s to 10 minutes after the current time minus 20s. In this way, the timestamp will be inserted to the database without being affected by the latency. +For example, if the current time is 2020.01.30 12:00:30, the timestamp inserted must be within the range [2020.01.30 11:00:50, 2020.01.30 12:10:10]. The corresponding UNIX timestamp is [1580353250, 1580357410]. + |
+
detail + |
+Yes + |
+Arrays of objects + |
+Specifies the event details. +For details, see Table 4. + |
+
Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
|---|---|---|---|
content + |
+No + |
+String + |
+Specifies the event content. Enter up to 4096 characters. + |
+
resource_id + |
+No + |
+String + |
+Specifies the resource ID. Enter up to 128 characters, including letters, digits, underscores (_), hyphens (-), and colon (:). +Example: 6a69bf28-ee62-49f3-9785-845dacd799ec +To query the resource ID, perform the following steps: +
|
+
resource_name + |
+No + |
+String + |
+Specifies the resource name. Enter up to 128 characters, including letters, digits, underscores (_), and hyphens (-). + |
+
event_state + |
+No + |
+String + |
+Specifies the event status. +Valid value can be normal, warning, or incident. + |
+
event_level + |
+No + |
+String + |
+Specifies the event severity. +Its value can be Critical, Major, Minor, or Info. + |
+
event_user + |
+No + |
+String + |
+Specifies the event user. +Enter up to 64 characters, including letters, digits, underscores (_), hyphens (-), slashes (/), and spaces. + |
+
[{
+ "event_name":"systemInvaded",
+ "event_source":"financial.System",
+ "time":1522121194000,
+ "detail":{
+ "content":"The financial system was invaded",
+ "group_id":"rg15221211517051YWWkEnVd",
+ "resource_id":"1234567890sjgggad",
+ "resource_name":"ecs001",
+ "event_state":"normal",
+ "event_level":"Major",
+ "event_user":"xiaokong"
+ }
+},
+{
+ "event_name":"systemInvaded",
+ "event_source":"financial.System",
+ "time":1522121194020,
+ "detail":{
+ "content":"The financial system was invaded",
+ "group_id":"rg15221211517051YWWkEnVd",
+ "resource_id":"1234567890sjgggad",
+ "resource_name":"ecs001",
+ "event_state":"normal",
+ "event_level":"Major",
+ "event_user":"xihong"
+ }
+}]
+Parameter + |
+Type + |
+Description + |
+
|---|---|---|
Array elements + |
+Arrays of objects + |
+Specifies the event list. +For details, see Table 6. + |
+
Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
|---|---|---|---|
event_id + |
+Yes + |
+String + |
+Specifies the event ID. + |
+
event_name + |
+Yes + |
+String + |
+Specifies the event name. +Start with a letter. Enter 1 to 64 characters. Only letters, digits, and underscores (_) are allowed. + |
+
[
+ {
+ "event_id":"evdgiqwgedkkcvhdjcdu346",
+ "event_name":"systemInvaded"
+ },
+ {
+ "event_id":"evdgiqwgedkkcvhdjcdu347",
+ "event_name":"systemParalysis"
+ }
+]
+Returned Value + |
+Description + |
+
|---|---|
400 Bad Request + |
+Request error. + |
+
401 Unauthorized + |
+The authentication information is not provided or is incorrect. + |
+
403 Forbidden + |
+Access to the requested page is forbidden. + |
+
408 Request Timeout + |
+The request timed out. + |
+
429 Too Many Requests + |
+Concurrent requests are excessive. + |
+
500 Internal Server Error + |
+Failed to complete the request because of an internal service error. + |
+
503 Service Unavailable + |
+The service is currently unavailable. + |
+
See Error Codes.
+