diff --git a/docs/cts/api-ref/ALL_META.TXT.json b/docs/cts/api-ref/ALL_META.TXT.json new file mode 100644 index 00000000..669ccc5f --- /dev/null +++ b/docs/cts/api-ref/ALL_META.TXT.json @@ -0,0 +1,212 @@ +[ + { + "uri":"en-us_topic_0168602179.html", + "product_code":"cts", + "code":"1", + "des":"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 Resourc", + "doc_type":"api", + "kw":"API Usage Guidelines,API Reference", + "title":"API Usage Guidelines", + "githuburl":"" + }, + { + "uri":"en-us_topic_0168602260.html", + "product_code":"cts", + "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":"en-us_topic_0168602231.html", + "product_code":"cts", + "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":"en-us_topic_0168602247.html", + "product_code":"cts", + "code":"4", + "des":"This API is used to query all API versions supported by Cloud Trace Service (CTS).GET /NoneParameter descriptionParameters in the responseParameterMandatoryTypeDescriptio", + "doc_type":"api", + "kw":"Querying All API Versions,API Version Management,API Reference", + "title":"Querying All API Versions", + "githuburl":"" + }, + { + "uri":"en-us_topic_0168602243.html", + "product_code":"cts", + "code":"5", + "des":"This API is used to query a specified API version of CTS.GET/{api_version}The URI parameters are described in Table 1.Parameters in the URIParameterMandatoryDescriptionap", + "doc_type":"api", + "kw":"Querying a Specified API Version,API Version Management,API Reference", + "title":"Querying a Specified API Version", + "githuburl":"" + }, + { + "uri":"en-us_topic_0168602232.html", + "product_code":"cts", + "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":"Tracker Management", + "title":"Tracker Management", + "githuburl":"" + }, + { + "uri":"en-us_topic_0168602251.html", + "product_code":"cts", + "code":"7", + "des":"All API URLs described in this section are case-sensitive.This API is used to create a tracker.A tracker will be automatically created when CTS is enabled. All traces rec", + "doc_type":"api", + "kw":"Creating a Tracker,Tracker Management,API Reference", + "title":"Creating a Tracker", + "githuburl":"" + }, + { + "uri":"en-us_topic_0168602227.html", + "product_code":"cts", + "code":"8", + "des":"CTS allows you to modify configuration parameters of a created tracker, including parameters related to Transfer to OBS and Trace Analysis. You can also change tracker st", + "doc_type":"api", + "kw":"Modifying a Tracker,Tracker Management,API Reference", + "title":"Modifying a Tracker", + "githuburl":"" + }, + { + "uri":"en-us_topic_0168602253.html", + "product_code":"cts", + "code":"9", + "des":"This API is used to query the details of a tracker. The details include the name of the tracker, name of the OBS bucket for storing traces, and prefix of the trace files ", + "doc_type":"api", + "kw":"Querying a Tracker,Tracker Management,API Reference", + "title":"Querying a Tracker", + "githuburl":"" + }, + { + "uri":"en-us_topic_0168602223.html", + "product_code":"cts", + "code":"10", + "des":"This API is used to delete a tracker. Deleting a tracker has no impact on the operation records that have been generated. When you enable CTS again, you can still view th", + "doc_type":"api", + "kw":"Deleting a Tracker,Tracker Management,API Reference", + "title":"Deleting a Tracker", + "githuburl":"" + }, + { + "uri":"en-us_topic_0168602178.html", + "product_code":"cts", + "code":"11", + "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":"Trace Management", + "title":"Trace Management", + "githuburl":"" + }, + { + "uri":"en-us_topic_0168602225.html", + "product_code":"cts", + "code":"12", + "des":"This API is used to query records of operations on resources in the last seven days.GET /v1.0/{project_id}/{tracker_name}/trace{?trace_id,service_type,resource_type,resou", + "doc_type":"api", + "kw":"Querying Traces (v1.0),Trace Management,API Reference", + "title":"Querying Traces (v1.0)", + "githuburl":"" + }, + { + "uri":"en-us_topic_0168602252.html", + "product_code":"cts", + "code":"13", + "des":"This API is used to query records of operations on resources in the last seven days. In v2.0, the request parameter trace_rating is changed to trace_status, and the type ", + "doc_type":"api", + "kw":"Querying Traces (v2.0),Trace Management,API Reference", + "title":"Querying Traces (v2.0)", + "githuburl":"" + }, + { + "uri":"topic_300000003.html", + "product_code":"", + "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":"Key Event Notification Management", + "title":"Key Event Notification Management", + "githuburl":"" + }, + { + "uri":"cts_api_0312.html", + "product_code":"", + "code":"15", + "des":"SMS, email, or HTTP/HTTPS notifications can be sent through pre-configured SMN topics to subscribers when key operations occur. This helps you detect high-risk operations", + "doc_type":"api", + "kw":"Creating a Key Event Notification,Key Event Notification Management,API Reference", + "title":"Creating a Key Event Notification", + "githuburl":"" + }, + { + "uri":"cts_api_0313.html", + "product_code":"", + "code":"16", + "des":"This API is used to modify a key event notification. The notification ID carried in the request must be valid.PUT /v3/{project_id}/notificationsStatus code: 200Status cod", + "doc_type":"api", + "kw":"Modifying a Key Event Notification,Key Event Notification Management,API Reference", + "title":"Modifying a Key Event Notification", + "githuburl":"" + }, + { + "uri":"cts_api_0314.html", + "product_code":"", + "code":"17", + "des":"This API is used to delete a key event notification.DELETE /v3/{project_id}/notificationsNoneStatus code: 400NoneNoneSee Error Codes.", + "doc_type":"api", + "kw":"Deleting a Key Event Notification,Key Event Notification Management,API Reference", + "title":"Deleting a Key Event Notification", + "githuburl":"" + }, + { + "uri":"cts_api_0315.html", + "product_code":"", + "code":"18", + "des":"This API is used to query a key event notification.GET /v3/{project_id}/notifications/{notification_type}NoneStatus code: 200Status code: 400NoneStatus code: 200The query", + "doc_type":"api", + "kw":"Querying a Key Event Notification,Key Event Notification Management,API Reference", + "title":"Querying a Key Event Notification", + "githuburl":"" + }, + { + "uri":"en-us_topic_0168602233.html", + "product_code":"cts", + "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":"Public Parameters", + "title":"Public Parameters", + "githuburl":"" + }, + { + "uri":"en-us_topic_0168602259.html", + "product_code":"cts", + "code":"20", + "des":"This section explains the meanings of error codes returned by CTS APIs.{\"error_code\": \"CTS.0003\",\"error_msg\": \"Invalid message body. The message body is empty or invalid.", + "doc_type":"api", + "kw":"Error Codes,Public Parameters,API Reference", + "title":"Error Codes", + "githuburl":"" + }, + { + "uri":"en-us_topic_0168602228.html", + "product_code":"cts", + "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":"Change History,API Reference", + "title":"Change History", + "githuburl":"" + } +] \ No newline at end of file diff --git a/docs/cts/api-ref/CLASS.TXT.json b/docs/cts/api-ref/CLASS.TXT.json new file mode 100644 index 00000000..38cb0350 --- /dev/null +++ b/docs/cts/api-ref/CLASS.TXT.json @@ -0,0 +1,191 @@ +[ + { + "desc":"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 Resourc", + "product_code":"cts", + "title":"API Usage Guidelines", + "uri":"en-us_topic_0168602179.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":"cts", + "title":"API Description", + "uri":"en-us_topic_0168602260.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":"cts", + "title":"API Version Management", + "uri":"en-us_topic_0168602231.html", + "doc_type":"api", + "p_code":"2", + "code":"3" + }, + { + "desc":"This API is used to query all API versions supported by Cloud Trace Service (CTS).GET /NoneParameter descriptionParameters in the responseParameterMandatoryTypeDescriptio", + "product_code":"cts", + "title":"Querying All API Versions", + "uri":"en-us_topic_0168602247.html", + "doc_type":"api", + "p_code":"3", + "code":"4" + }, + { + "desc":"This API is used to query a specified API version of CTS.GET/{api_version}The URI parameters are described in Table 1.Parameters in the URIParameterMandatoryDescriptionap", + "product_code":"cts", + "title":"Querying a Specified API Version", + "uri":"en-us_topic_0168602243.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":"cts", + "title":"Tracker Management", + "uri":"en-us_topic_0168602232.html", + "doc_type":"api", + "p_code":"2", + "code":"6" + }, + { + "desc":"All API URLs described in this section are case-sensitive.This API is used to create a tracker.A tracker will be automatically created when CTS is enabled. All traces rec", + "product_code":"cts", + "title":"Creating a Tracker", + "uri":"en-us_topic_0168602251.html", + "doc_type":"api", + "p_code":"6", + "code":"7" + }, + { + "desc":"CTS allows you to modify configuration parameters of a created tracker, including parameters related to Transfer to OBS and Trace Analysis. You can also change tracker st", + "product_code":"cts", + "title":"Modifying a Tracker", + "uri":"en-us_topic_0168602227.html", + "doc_type":"api", + "p_code":"6", + "code":"8" + }, + { + "desc":"This API is used to query the details of a tracker. The details include the name of the tracker, name of the OBS bucket for storing traces, and prefix of the trace files ", + "product_code":"cts", + "title":"Querying a Tracker", + "uri":"en-us_topic_0168602253.html", + "doc_type":"api", + "p_code":"6", + "code":"9" + }, + { + "desc":"This API is used to delete a tracker. Deleting a tracker has no impact on the operation records that have been generated. When you enable CTS again, you can still view th", + "product_code":"cts", + "title":"Deleting a Tracker", + "uri":"en-us_topic_0168602223.html", + "doc_type":"api", + "p_code":"6", + "code":"10" + }, + { + "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":"cts", + "title":"Trace Management", + "uri":"en-us_topic_0168602178.html", + "doc_type":"api", + "p_code":"2", + "code":"11" + }, + { + "desc":"This API is used to query records of operations on resources in the last seven days.GET /v1.0/{project_id}/{tracker_name}/trace{?trace_id,service_type,resource_type,resou", + "product_code":"cts", + "title":"Querying Traces (v1.0)", + "uri":"en-us_topic_0168602225.html", + "doc_type":"api", + "p_code":"11", + "code":"12" + }, + { + "desc":"This API is used to query records of operations on resources in the last seven days. In v2.0, the request parameter trace_rating is changed to trace_status, and the type ", + "product_code":"cts", + "title":"Querying Traces (v2.0)", + "uri":"en-us_topic_0168602252.html", + "doc_type":"api", + "p_code":"11", + "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":"cts", + "title":"Key Event Notification Management", + "uri":"topic_300000003.html", + "doc_type":"api", + "p_code":"2", + "code":"14" + }, + { + "desc":"SMS, email, or HTTP/HTTPS notifications can be sent through pre-configured SMN topics to subscribers when key operations occur. This helps you detect high-risk operations", + "product_code":"cts", + "title":"Creating a Key Event Notification", + "uri":"cts_api_0312.html", + "doc_type":"api", + "p_code":"14", + "code":"15" + }, + { + "desc":"This API is used to modify a key event notification. The notification ID carried in the request must be valid.PUT /v3/{project_id}/notificationsStatus code: 200Status cod", + "product_code":"cts", + "title":"Modifying a Key Event Notification", + "uri":"cts_api_0313.html", + "doc_type":"api", + "p_code":"14", + "code":"16" + }, + { + "desc":"This API is used to delete a key event notification.DELETE /v3/{project_id}/notificationsNoneStatus code: 400NoneNoneSee Error Codes.", + "product_code":"cts", + "title":"Deleting a Key Event Notification", + "uri":"cts_api_0314.html", + "doc_type":"api", + "p_code":"14", + "code":"17" + }, + { + "desc":"This API is used to query a key event notification.GET /v3/{project_id}/notifications/{notification_type}NoneStatus code: 200Status code: 400NoneStatus code: 200The query", + "product_code":"cts", + "title":"Querying a Key Event Notification", + "uri":"cts_api_0315.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":"cts", + "title":"Public Parameters", + "uri":"en-us_topic_0168602233.html", + "doc_type":"api", + "p_code":"", + "code":"19" + }, + { + "desc":"This section explains the meanings of error codes returned by CTS APIs.{\"error_code\": \"CTS.0003\",\"error_msg\": \"Invalid message body. The message body is empty or invalid.", + "product_code":"cts", + "title":"Error Codes", + "uri":"en-us_topic_0168602259.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":"cts", + "title":"Change History", + "uri":"en-us_topic_0168602228.html", + "doc_type":"api", + "p_code":"", + "code":"21" + } +] \ No newline at end of file diff --git a/docs/cts/api-ref/PARAMETERS.txt b/docs/cts/api-ref/PARAMETERS.txt new file mode 100644 index 00000000..6da8d5f0 --- /dev/null +++ b/docs/cts/api-ref/PARAMETERS.txt @@ -0,0 +1,3 @@ +version="" +language="en-us" +type="" \ No newline at end of file diff --git a/docs/cts/api-ref/cts_api_0312.html b/docs/cts/api-ref/cts_api_0312.html new file mode 100644 index 00000000..6c1d675b --- /dev/null +++ b/docs/cts/api-ref/cts_api_0312.html @@ -0,0 +1,484 @@ + + +
SMS, email, or HTTP/HTTPS notifications can be sent through pre-configured SMN topics to subscribers when key operations occur. This helps you detect high-risk operations promptly. Notifications can also be used as triggers for specific operations or to connect to your own audit system.
+POST /v3/{project_id}/notifications
+ +Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
---|---|---|---|
project_id + |
+Yes + |
+String + |
+Project ID. For details, see section "Obtaining the Account ID and Project ID" in Cloud Trace Service API Reference. + |
+
Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
---|---|---|---|
notification_name + |
+Yes + |
+String + |
+Notification name. + |
+
operation_type + |
+Yes + |
+String + |
+Operation type. Possible options include complete and customized. If you choose complete, you do not need to specify operations and notify_user_list, and notifications will be sent when any supported operations occur on any of the connected cloud services. If you choose customized, notifications will be sent when operations defined in operations occur. +Enumerated values: +
|
+
operations + |
+No + |
+Array of Operations objects + |
+Operation list. + |
+
notify_user_list + |
+No + |
+Array of NotificationUsers objects + |
+List of users whose operations will trigger notifications. Currently, up to 50 users in 10 user groups can be configured. + |
+
topic_id + |
+No + |
+String + |
+Topic URN. +
|
+
Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
---|---|---|---|
service_type + |
+Yes + |
+String + |
+Cloud service. The value must be the acronym of a cloud service that has been connected with CTS. It is a word composed of uppercase letters. For cloud services that can be connected with CTS, see section "Supported Services and Operations" in the Cloud Trace Service User Guide. + |
+
resource_type + |
+Yes + |
+String + |
+Resource type. + |
+
trace_names + |
+Yes + |
+Array of strings + |
+Trace name. + |
+
Status code: 201
+ +Parameter + |
+Type + |
+Description + |
+
---|---|---|
notification_name + |
+String + |
+Notification name. + |
+
operation_type + |
+String + |
+Operation type. Possible options include complete and customized. +Enumerated values: +
|
+
operations + |
+Array of Operations objects + |
+Operation list. + |
+
notify_user_list + |
+Array of NotificationUsers objects + |
+List of users whose operations will trigger notifications. Currently, up to 50 users in 10 user groups can be configured. + |
+
status + |
+String + |
+Notification status. Possible options include enabled and disabled. +Enumerated values: +
|
+
topic_id + |
+String + |
+Unique resource ID of an SMN topic. You can obtain the ID by querying the topic list. + |
+
notification_id + |
+String + |
+Unique notification ID. + |
+
notification_type + |
+String + |
+Notification type. +Enumerated value: +
|
+
project_id + |
+String + |
+Project ID. + |
+
create_time + |
+Long + |
+Time when a notification rule was created. + |
+
Parameter + |
+Type + |
+Description + |
+
---|---|---|
service_type + |
+String + |
+Cloud service. The value must be the acronym of a cloud service that has been connected with CTS. It is a word composed of uppercase letters. For cloud services that can be connected with CTS, see section "Supported Services and Operations" in the Cloud Trace Service User Guide. + |
+
resource_type + |
+String + |
+Resource type. + |
+
trace_names + |
+Array of strings + |
+Trace name. + |
+
Parameter + |
+Type + |
+Description + |
+
---|---|---|
user_group + |
+String + |
+IAM user group. + |
+
user_list + |
+Array of strings + |
+IAM user. + |
+
Status code: 400
+ +Parameter + |
+Type + |
+Description + |
+
---|---|---|
error_code + |
+String + |
+Error code. Format: CTS.XXX. + |
+
error_msg + |
+String + |
+Error description. + |
+
POST https://{endpoint}/v3/{project_id}/notifications + +{ + "notification_name": "keyOperate_info_cfwy", + "operation_type": "customized", + "operations": [{ + "service_type": "CTS", + "resource_type": "tracker", + "trace_names": [ + "createTracker", + "deleteTraceker" + ] + }, { + "service_type": "CTS", + "resource_type": "notification", + "trace_names": [ + "deleteNotification", + "updateNotification" + ] + }, { + "service_type": "AOM", + "resource_type": "pe", + "trace_names": [ + "deletePolicyGroup", + "updatePolicyGroup", + "createPolicyGroup" + ] + } + ], + "notify_user_list": [{ + "user_group": "admin", + "user_list": [ + "test1", + "test2" + ] + }, { + "user_group": "CTS view", + "user_list": [ + "test3", + "test4" + ] + } + ], + "topic_id": "urn:smn:{regionid}:24edf66e79d04187acb99a463e610764:test" +}+
POST https://{endpoint}/v3/{project_id}/notifications + +{ + "notification_name": "test", + "operation_type": "complete", + "topic_id": "urn:smn:{regionid}:24edf66e79d04187acb99a463e610764:test" +}+
Status code: 201
+The creation is successful.
+{ + "create_time" : 1634001495876, + "notification_id" : "cda8fd83-d08c-46f0-b914-1453a6a85c00", + "notification_name" : "keyOperate_info_cfwy", + "notification_type" : "smn", + "notify_user_list" : [ { + "user_group" : "admin", + "user_list" : [ "test1", "test2" ] + }, { + "user_group" : "CTS view", + "user_list" : [ "test3", "test4" ] + } ], + "operation_type" : "customized", + "operations" : [ { + "resource_type" : "tracker", + "service_type" : "CTS", + "trace_names" : [ "createTracker", "deleteTraceker" ] + }, { + "resource_type" : "notification", + "service_type" : "CTS", + "trace_names" : [ "deleteNotification", "updateNotification" ] + }, { + "resource_type" : "pe", + "service_type" : "AOM", + "trace_names" : [ "deletePolicyGroup", "updatePolicyGroup", "createPolicyGroup" ] + } ], + "project_id" : "24edf66e79d04187acb99a463e610764", + "status" : "enabled", + "topic_id" : "urn:smn:{regionid}:24edf66e79d04187acb99a463e610764:test" +}+
Status Code + |
+Description + |
+
---|---|
201 + |
+The creation is successful. + |
+
400 + |
+The server failed to process the request. + |
+
401 + |
+The request is rejected due to authentication failure. + |
+
403 + |
+The server understood the request but refused to authorize it. + |
+
404 + |
+The server failed to find the requested resource or some key event notifications failed to be deleted. + |
+
500 + |
+The request failed to be executed or some trackers failed to be deleted. + |
+
503 + |
+The requested service is unavailable. The client should not repeat the request without modifications. + |
+
See Error Codes.
+This API is used to modify a key event notification. The notification ID carried in the request must be valid.
+PUT /v3/{project_id}/notifications
+ +Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
---|---|---|---|
project_id + |
+Yes + |
+String + |
+Project ID. For details, see section "Obtaining the Account ID and Project ID" in Cloud Trace Service API Reference. + |
+
Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
---|---|---|---|
notification_name + |
+Yes + |
+String + |
+Notification name. + |
+
operation_type + |
+Yes + |
+String + |
+Operation type. Possible options include complete and customized. If you choose complete, notifications will be sent when any supported operation occurs on any of the connected cloud services. If you choose customized, notifications will be sent when operations defined in operations occur. +Enumerated values: +
|
+
operations + |
+No + |
+Array of Operations objects + |
+Operation list. + |
+
notify_user_list + |
+No + |
+Array of NotificationUsers objects + |
+List of users whose operations will trigger notifications. Currently, up to 50 users in 10 user groups can be configured. + |
+
status + |
+Yes + |
+String + |
+Notification status. Possible options include enabled and disabled. +Enumerated values: +
|
+
topic_id + |
+No + |
+String + |
+Topic URN. This parameter is mandatory when status is set to enabled. +
|
+
notification_id + |
+Yes + |
+String + |
+Notification ID. + |
+
Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
---|---|---|---|
service_type + |
+Yes + |
+String + |
+Cloud service. The value must be the acronym of a cloud service that has been connected with CTS. It is a word composed of uppercase letters. For cloud services that can be connected with CTS, see section "Supported Services and Operations" in the Cloud Trace Service User Guide. + |
+
resource_type + |
+Yes + |
+String + |
+Resource type. + |
+
trace_names + |
+Yes + |
+Array of strings + |
+Trace name. + |
+
Status code: 200
+ +Parameter + |
+Type + |
+Description + |
+
---|---|---|
notification_name + |
+String + |
+Notification name. + |
+
operation_type + |
+String + |
+Operation type. Possible options include complete and customized. If you choose complete, notifications will be sent when any supported operation occurs on any of the connected cloud services. If you choose customized, notifications will be sent when operations defined in operations occur. +Enumerated values: +
|
+
operations + |
+Array of Operations objects + |
+Operation list. + |
+
notify_user_list + |
+Array of NotificationUsers objects + |
+List of users whose operations will trigger notifications. Currently, up to 50 users in 10 user groups can be configured. + |
+
status + |
+String + |
+Notification status. Possible options include enabled and disabled. +Enumerated values: +
|
+
topic_id + |
+String + |
+Topic URN. +
|
+
notification_id + |
+String + |
+Unique notification ID. + |
+
notification_type + |
+String + |
+Notification type. +Enumerated value: +
|
+
project_id + |
+String + |
+Project ID. + |
+
create_time + |
+Long + |
+Timestamp when a notification was created. + |
+
Parameter + |
+Type + |
+Description + |
+
---|---|---|
service_type + |
+String + |
+Cloud service. The value must be the acronym of a cloud service that has been connected with CTS. It is a word composed of uppercase letters. For cloud services that can be connected with CTS, see section "Supported Services and Operations" in the Cloud Trace Service User Guide. + |
+
resource_type + |
+String + |
+Resource type. + |
+
trace_names + |
+Array of strings + |
+Trace name. + |
+
Parameter + |
+Type + |
+Description + |
+
---|---|---|
user_group + |
+String + |
+IAM user group. + |
+
user_list + |
+Array of strings + |
+IAM user. + |
+
Status code: 400
+ +Parameter + |
+Type + |
+Description + |
+
---|---|---|
error_code + |
+String + |
+Error code. Format: CTS.XXX. + |
+
error_msg + |
+String + |
+Error description. + |
+
Modifying a key event notification
+PUT https://{endpoint}/v3/{project_id}/notifications + +{ + "notification_id" : "6d4a09bb-aa8e-40db-9e87-0d5e203823a8", + "notification_name" : "keyOperate_info_cfwy", + "operation_type" : "customized", + "operations" : [ { + "service_type" : "CTS", + "resource_type" : "tracker", + "trace_names" : [ "createTracker", "deleteTraceker" ] + }, { + "service_type" : "CTS", + "resource_type" : "notification", + "trace_names" : [ "deleteNotification", "updateNotification" ] + }, { + "service_type" : "AOM", + "resource_type" : "pe", + "trace_names" : [ "deletePolicyGroup", "updatePolicyGroup", "createPolicyGroup" ] + } ], + "notify_user_list" : [ { + "user_group" : "admin", + "user_list" : [ "test", "test1" ] + }, { + "user_group" : "CTS view", + "user_list" : [ "test2", "test3" ] + } ], + "status" : "enabled", + "topic_id" : "urn:smn:{regionid}:24edf66e79d04187acb99a463e610764:foo" +}+
Status code: 200
+The notification is modified.
+{ + "notification_id" : "6d4a09bb-aa8e-40db-9e87-0d5e203823a8", + "notification_name" : "keyOperate_info_cfwy", + "operation_type" : "customized", + "operations" : [ { + "service_type" : "CTS", + "resource_type" : "tracker", + "trace_names" : [ "createTracker", "deleteTraceker" ] + }, { + "service_type" : "CTS", + "resource_type" : "notification", + "trace_names" : [ "deleteNotification", "updateNotification" ] + }, { + "service_type" : "AOM", + "resource_type" : "pe", + "trace_names" : [ "deletePolicyGroup", "updatePolicyGroup", "createPolicyGroup" ] + } ], + "notify_user_list" : [ { + "user_group" : "admin", + "user_list" : [ "test", "test1" ] + }, { + "user_group" : "CTS view", + "user_list" : [ "test2", "test3" ] + } ], + "status" : "enabled", + "project_id" : "24edf66e79d04187acb99a463e610764", + "notification_type" : "smn", + "create_time" : 1634001495876, + "topic_id" : "urn:smn:{regionid}:24edf66e79d04187acb99a463e610764:foo" +}+
Status Code + |
+Description + |
+
---|---|
200 + |
+The notification is modified. + |
+
400 + |
+The server failed to process the request. + |
+
401 + |
+The request is rejected due to authentication failure. + |
+
403 + |
+The server understood the request but refused to authorize it. + |
+
404 + |
+The server failed to find the requested resource or some key event notifications failed to be deleted. + |
+
500 + |
+The request failed to be executed or some trackers failed to be deleted. + |
+
503 + |
+The requested service is unavailable. The client should not repeat the request without modifications. + |
+
See Error Codes.
+This API is used to delete a key event notification.
+DELETE /v3/{project_id}/notifications
+ +Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
---|---|---|---|
project_id + |
+Yes + |
+String + |
+Project ID. For details, see section "Obtaining the Account ID and Project ID" in Cloud Trace Service API Reference. + |
+
Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
---|---|---|---|
notification_id + |
+Yes + |
+String + |
+Notification ID. To batch delete notifications, enter multiple notification IDs separated by commas (,), for example, notification_id="xxx1,ccc2". + |
+
None
+Status code: 400
+ +Parameter + |
+Type + |
+Description + |
+
---|---|---|
error_code + |
+String + |
+Error code. Format: CTS.XXX. + |
+
error_msg + |
+String + |
+Error description. + |
+
None
+None
+Status Code + |
+Description + |
+
---|---|
204 + |
+The deletion is successful. + |
+
400 + |
+The server failed to process the request. + |
+
401 + |
+The request is rejected due to authentication failure. + |
+
403 + |
+The server understood the request but refused to authorize it. + |
+
404 + |
+The server failed to find the requested resource or some key event notifications failed to be deleted. + |
+
500 + |
+The request failed to be executed or some trackers failed to be deleted. + |
+
503 + |
+The requested service is unavailable. The client should not repeat the request without modifications. + |
+
See Error Codes.
+This API is used to query a key event notification.
+GET /v3/{project_id}/notifications/{notification_type}
+ +Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
---|---|---|---|
project_id + |
+Yes + |
+String + |
+Project ID. For details, see section "Obtaining the Account ID and Project ID" in Cloud Trace Service API Reference. + |
+
notification_type + |
+Yes + |
+String + |
+Notification type. +Enumerated value: +
|
+
Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
---|---|---|---|
notification_name + |
+No + |
+String + |
+Notification name. If this parameter is not specified, all key event notifications configured in the current tenant account are returned. + |
+
None
+Status code: 200
+ +Parameter + |
+Type + |
+Description + |
+
---|---|---|
notifications + |
+Array of NotificationsResponseBody objects + |
+Notification list. + |
+
Parameter + |
+Type + |
+Description + |
+
---|---|---|
notification_name + |
+String + |
+Notification name. + |
+
operation_type + |
+String + |
+Operation type. Possible options include complete and customized. If you choose complete, notifications will be sent when any supported operation occurs on any of the connected cloud services. If you choose customized, notifications will be sent when operations defined in operations occur. +Enumerated values: +
|
+
operations + |
+Array of Operations objects + |
+Operation list. + |
+
notify_user_list + |
+Array of NotificationUsers objects + |
+List of users whose operations will trigger notifications. Currently, up to 50 users in 10 user groups can be configured. + |
+
status + |
+String + |
+Notification status. Possible options include enabled and disabled. +Enumerated values: +
|
+
topic_id + |
+String + |
+Topic URN. +
|
+
notification_id + |
+String + |
+Unique notification ID. + |
+
notification_type + |
+String + |
+Notification type. +Enumerated value: +
|
+
project_id + |
+String + |
+Project ID. + |
+
create_time + |
+Long + |
+Timestamp when a notification was created. + |
+
Parameter + |
+Type + |
+Description + |
+
---|---|---|
service_type + |
+String + |
+Cloud service. The value must be the acronym of a cloud service that has been connected with CTS. It is a word composed of uppercase letters. For cloud services that can be connected with CTS, see section "Supported Services and Operations" in the Cloud Trace Service User Guide. + |
+
resource_type + |
+String + |
+Resource type. + |
+
trace_names + |
+Array of strings + |
+Trace name. + |
+
Parameter + |
+Type + |
+Description + |
+
---|---|---|
user_group + |
+String + |
+IAM user group. + |
+
user_list + |
+Array of strings + |
+IAM user. + |
+
Status code: 400
+ +Parameter + |
+Type + |
+Description + |
+
---|---|---|
error_code + |
+String + |
+Error code. Format: CTS.XXX. + |
+
error_msg + |
+String + |
+Error description. + |
+
None
+Status code: 200
+The query is successful.
+{ + "notifications" : [ { + "create_time" : 1633933167385, + "notify_user_list" : [ { + "user_group" : "admin", + "user_list" : [ "test1", "test2" ] + }, { + "user_group" : "CTS view", + "user_list" : [ "test3", "test4" ] + } ], + "notification_id" : "0b98e1c2-2fd6-4e33-a355-f9e12eaab88a", + "notification_name" : "test2", + "notification_type" : "smn", + "operation_type" : "customized", + "operations" : [ { + "resource_type" : "tracker", + "service_type" : "CTS", + "trace_names" : [ "createTracker" ] + }, { + "resource_type" : "notification", + "service_type" : "CTS", + "trace_names" : [ "deleteNotification", "updateNotification" ] + }, { + "resource_type" : "pe", + "service_type" : "AOM", + "trace_names" : [ "createPolicyGroup", "updatePolicyGroup", "deletePolicyGroup" ] + } ], + "project_id" : "24edf66e79d04187acb99a463e610764", + "status" : "enabled", + "topic_id" : "urn:smn:{regionid}:24edf66e79d04187acb99a463e610764:test" + }, { + "create_time" : 1633924057706, + "notify_user_list" : [ { + "user_group" : "admin", + "user_list" : [ "test1", "test2" ] + }, { + "user_group" : "CTS view", + "user_list" : [ "test3", "test4" ] + } ], + "notification_id" : "6d4a09bb-aa8e-40db-9e87-0d5e203823a8", + "notification_name" : "test1", + "notification_type" : "smn", + "operation_type" : "complete", + "operations" : [ ], + "project_id" : "24edf66e79d04187acb99a463e610764", + "status" : "disabled" + } ] +}+
Status Code + |
+Description + |
+
---|---|
200 + |
+The query is successful. + |
+
400 + |
+The server failed to process the request. + |
+
401 + |
+The request is rejected due to authentication failure. + |
+
403 + |
+The server understood the request but refused to authorize it. + |
+
404 + |
+The server failed to find the requested resource or some key event notifications failed to be deleted. + |
+
500 + |
+The request failed to be executed or some trackers failed to be deleted. + |
+
503 + |
+The requested service is unavailable. The client should not repeat the request without modifications. + |
+
See Error Codes.
+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.
+Cloud APIs use HTTPS as the transmission protocol. Requests/Responses are transmitted using JSON messages, with the media type represented by Application/json.
+For details about how to use APIs, see API Usage Guidelines.
+This API is used to delete a tracker. Deleting a tracker has no impact on the operation records that have been generated. When you enable CTS again, you can still view those records.
+DELETE /v1.0/{project_id}/tracker?tracker_name={tracker_name}
+DELETE /v1.0/{project_id}/tracker?tracker_name=system+
Returned Value + |
+Description + |
+
---|---|
204 + |
+The tracker is deleted successfully. + |
+
Returned Value + |
+Description + |
+
---|---|
400 + |
+The server failed to process the request. + |
+
404 + |
+The server failed to find the requested resource or deleting some trackers failed. + |
+
500 + |
+The request failed to be executed or some trackers failed to be deleted. + |
+
401 + |
+Your access request is rejected. + |
+
403 + |
+You are forbidden to access the requested page. + |
+
This API is used to query records of operations on resources in the last seven days.
+GET /v1.0/{project_id}/{tracker_name}/trace{?trace_id,service_type,resource_type,resource_id,resource_name,trace_name,trace_rating,user,limit,from,to,next}
+Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
---|---|---|---|
service_type + |
+No + |
+String + |
+Type of a service whose traces are to be queried. The value must be the abbreviation of a cloud service that has been interconnected with CTS. It is a word composed of uppercase letters. For the interconnected cloud services, see section "Supported Services" in the Cloud Trace Service User Guide. + |
+
resource_type + |
+No + |
+String + |
+Type of a resource whose traces are to be queried. The value can contain 1 to 64 characters, including letters, numbers, hyphens (-), underscores (_), and periods (.). It must start with a letter. For the interconnected cloud services, see section "Supported Services" in the Cloud Trace Service User Guide. + |
+
resource_id + |
+No + |
+String + |
+ID of a resource whose traces are to be queried + |
+
resource_name + |
+No + |
+String + |
+Name of a resource whose traces are to be queried + |
+
trace_name + |
+No + |
+String + |
+Trace name. It indicates the operation recorded by this trace. The value can contain 1 to 64 characters, including letters, numbers, hyphens (-), underscores (_), and periods (.). It must start with a letter. + |
+
limit + |
+No + |
+String + |
+Number of traces returned in the trace list. The default value is 50 and the maximum value is 200. + |
+
next + |
+No + |
+String + |
+This parameter is used to query traces generated earlier than its specified value. The value can be that of marker in Table 5. +next can be used with the parameters from and to. +Traces generated in the overlap of the two time ranges specified respectively by next and by from and to will be returned. + |
+
from + |
+No + |
+String + |
+UTC timestamp of the start time of the query time range. The value is in milliseconds and contains 13 numbers. Traces generated on the specified timestamp are not returned. The parameters from and to should be used together. + |
+
to + |
+No + |
+String + |
+UTC timestamp of the end time of the query time range. The value is in milliseconds and contains 13 numbers. Traces generated on the specified timestamp are not returned. The parameters to and from should be used together. + |
+
trace_id + |
+No + |
+String + |
+ID of a trace. +If this parameter is specified, other query criteria will not take effect. + |
+
trace_rating + |
+No + |
+String + |
+Status of a trace. The value can be normal, warning, or incident. + |
+
user + |
+No + |
+String + |
+Name of the user whose traces are to be queried + NOTE:
+The username is case sensitive. + |
+
GET /v1.0/{project_id}/{tracker_name}/trace?limit=11&to=1479095278000&from=1478490478000&trace_name=createTracker&resource_type=tracker&service_type=CTS+
Parameter + |
+Type + |
+Description + |
+
---|---|---|
traces + |
+array + |
+List of returned traces + |
+
meta_data + |
+Structure + |
+Extended parameter. The value can be count (number of traces in the response) or marker (ID of the last trace in the trace list). + |
+
Parameter + |
+Type + |
+Description + |
+
---|---|---|
resource_id + |
+String + |
+ID of a resource on which an operation was performed + |
+
trace_name + |
+String + |
+Name of a trace. The value will contain 1 to 64 characters, including letters, numbers, hyphens (-), underscores (_), and periods (.). It will also start with a letter. + |
+
trace_rating + |
+String + |
+Status of a trace. The value can be normal, warning, or incident. + |
+
trace_type + |
+String + |
+Type of a source trace. The value can be ApiCall, ConsoleAction, or SystemAction. + |
+
request + |
+String + |
+Request of an operation on resources + |
+
response + |
+String + |
+Response to a user request, that is, the returned information for an operation on resources. + |
+
code + |
+String + |
+HTTP status code returned by the associated API + |
+
api_version + |
+String + |
+Version of the API + |
+
message + |
+String + |
+Remarks added by other cloud services to a trace + |
+
record_time + |
+Long + |
+Timestamp when an operation was recorded by CTS + |
+
trace_id + |
+String + |
+ID of a trace. The value is the UUID generated by the system. + |
+
time + |
+Long + |
+Timestamp when an operation occurred + |
+
user + |
+String + |
+Information of the user who performed the operation that triggered the trace. + |
+
service_type + |
+String + |
+Type of a service whose traces were queried. The value is the abbreviation of a cloud service that has been interconnected with CTS. It is a word composed of uppercase letters. + |
+
resource_type + |
+String + |
+Type of a resource whose traces were queried. The value will contain 1 to 64 characters, including letters, numbers, hyphens (-), underscores (_), and periods (.). It will also start with a letter. + |
+
source_ip + |
+String + |
+IP address of the user who performed the operation that triggered the trace. + |
+
resource_name + |
+String + |
+Name of a resource whose traces were queried + |
+
request_id + |
+String + |
+Request ID + |
+
location_info + |
+String + |
+Additional information required for fault locating after a request error + |
+
endpoint + |
+String + |
+Endpoint in the detail page URL of the cloud resource on which the recorded operation was performed + |
+
resource_url + |
+String + |
+Detail page URL (excluding the endpoint) of the cloud resource on which the recorded operation was performed + |
+
Parameter + |
+Type + |
+Description + |
+
---|---|---|
count + |
+Integer + |
+Number of traces returned in the trace list + |
+
marker + |
+String + |
+ID of the last trace in the trace list. The value of this parameter can be used as the next value. If the value of marker is null, all traces have been returned. + |
+
{ + "traces" : [ { + "time" : 1472148708232, + "user" : "{\"name\":\"xxx\",\"domain\":{\"name\":\"xxx\",\"id\":\"ded649d814464428ba89d04d7955c93e\"},\"assumedBy\":{\"user\":{\"name\":\"bss_bm_admin\",\"id\":\"c5140af45b5d4b399dea8f900f1dcf1b\",\"domain\":{\"name\":\"op_service\",\"id\":\"71ce673175024d0495664e525e52bac0\"}}}}", + "response" : "{\"code\":\"VPC.0514\",\"message\":\"Update port fail.\"}", + "code" : 200, + "service_type" : "VPC", + "resource_type" : "eip", + "resource_name" : "192.144.163.1", + "resource_id" : "d502809d-0d1d-41ce-9690-784282142ccc", + "trace_name" : "deleteEip", + "trace_rating" : "warning", + "trace_type" : "ConsoleAction", + "api_version" : "2.0", + "record_time" : 1481066128032, + "trace_id" : "e001ccb9-bc09-11e6-b00b-4b2a61338db6" + "request_id" : "a0001c1b9-bctt-2136-c12b-4b2a611116" + "location_info" : "resource has been deleted" + "endpoint" : "https://*****/vpc?agencyId=***®ion=***&locale=zh-cn#" + "resource_url" : "/vpc/vpcmanager/vpcs?vpcid=*****" + }, { + "time" : 1472148708232, + "user" : "{\"name\":\"xxx\",\"domain\":{\"name\":\"xxx\",\"id\":\"ded649d814464428ba89d04d7955c93e\"},\"assumedBy\":{\"user\":{\"name\":\"bss_bm_admin\",\"id\":\"c5140af45b5d4b399dea8f900f1dcf1b\",\"domain\":{\"name\":\"op_service\",\"id\":\"71ce673175024d0495664e525e52bac0\"}}}}", + "response" : "{\"code\":\"VPC.0514\",\"message\":\"Update port fail.\"}", + "code" : 200, + "service_type" : "VPC", + "resource_type" : "eip", + "resource_name" : "192.144.163.1", + "resource_id" : "d502809d-0d1d-41ce-9690-784282142ccc", + "trace_name" : "deleteEip", + "trace_rating" : "warning", + "trace_type" : "ConsoleAction", + "api_version" : "2.0", + "record_time" : 1481066128032, + "trace_id" : "e001ccb8-bc09-11e6-b2cc-2640a43cc6e8" + "request_id" : "a0001c1b9-bctt-2136-c12b-4b2a611116" + "location_info" : "resource has been deleted" + "endpoint" : "https://*****/vpc?agencyId=***®ion=***&locale=zh-cn#" + "resource_url" : "/vpc/vpcmanager/vpcs?vpcid=*****" + } ], + "meta_data" : { + "count" : 2, + "marker" : "e001ccb8-bc09-11e6-b2cc-2640a43cc6e8" + } +}+
Returned Value + |
+Description + |
+
---|---|
200 + |
+The request is successful and the query result is returned. + |
+
Returned Value + |
+Description + |
+
---|---|
400 + |
+The query parameters are abnormal. + |
+
500 + |
+Failed to complete the request because of an internal service error. + |
+
401 + |
+Your access request is rejected. + |
+
403 + |
+You are forbidden to access the requested page. + |
+
404 + |
+The requested trace does not exist. + |
+
CTS allows you to modify configuration parameters of a created tracker, including parameters related to Transfer to OBS and Trace Analysis. You can also change tracker status by clicking Enable or Disable in the Operation column. Modifying tracker parameters does not affect the existing operation records. After the modification is complete, the system will immediately start recording operations based on the new rule.
+PUT /v1.0/{project_id}/tracker/{tracker_name}
+Parameter + |
+Sub-Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
---|---|---|---|---|
bucket_name + |
+N/A + |
+Yes + |
+String + |
+OBS bucket name. It starts with a number or lowercase letter and contains 3 to 63 characters, including lowercase letters, numbers, hyphens (-), and periods (.) + |
+
file_prefix_name + |
+N/A + |
+No + |
+String + |
+Prefix of trace files that need to be stored in OBS buckets. The value contains 0 to 64 characters, including letters, numbers, hyphens (-), underscores (_), and periods (.) + |
+
status + |
+N/A + |
+No + |
+String + |
+Status of a tracker. The value can be enabled or disabled. If you change the value to disabled, the tracker stops recording traces. + |
+
lts + |
+is_lts_enabled + |
+Yes + |
+Boolean + |
+Whether trace analysis is enabled. + NOTE:
+When you enable trace analysis, a log group named CTS and a log stream named system-trace are created in LTS. + |
+
PUT /v1.0/{project_id}/tracker/system +{ + "bucket_name" : "my_created_bucket", + "file_prefix_name" : "some_folder", + "lts" : { + "is_lts_enabled" : true, + }, + "status" : "disabled" +}+
Parameter + |
+Sub-Parameter + |
+Type + |
+Description + |
+
---|---|---|---|
tracker_name + |
+N/A + |
+String + |
+Tracker name. It is set as system by default. + |
+
bucket_name + |
+N/A + |
+String + |
+OBS bucket name. It starts with a number or lowercase letter and contains 3 to 63 characters, including lowercase letters, numbers, hyphens (-), and periods (.) + |
+
file_prefix_name + |
+N/A + |
+String + |
+Prefix of trace files that need to be stored in OBS buckets. + |
+
status + |
+N/A + |
+String + |
+Status of a tracker. The value can be enabled or disabled. + |
+
lts + |
+is_lts_enabled + |
+Boolean + |
+Whether trace analysis is enabled. + |
+
log_group_name + |
+String + |
+Name of the LTS log group. + |
+|
log_topic_name + |
+String + |
+Name of the LTS log stream. + |
+
{ + "bucket_name" : "my_created_bucket", + "tracker_name" : "system", + "file_prefix_name" : "some_folder", + "lts" : { + "is_lts_enabled" : true, + "log_group_name" : "CTS", + "log_topic_name" : "system-trace" + }, + "status" : "disabled" + "bucket_name" : "1214", + "tracker_name" : "system", +}+
Returned Value + |
+Description + |
+
---|---|
200 + |
+The request is successfully processed. + |
+
Returned Value + |
+Description + |
+
---|---|
400 + |
+The server failed to process the request. + |
+
404 + |
+The server failed to find the requested resource. + |
+
500 + |
+Failed to complete the request because of an internal service error. + |
+
401 + |
+Your access request is rejected. + |
+
403 + |
+You are forbidden to access the requested page. + |
+
Released On + |
+Description + |
+
---|---|
2022-10-30 + |
+
|
+
2022-07-21 + |
+This release incorporates the following changes: +Added Creating a Key Event Notification. +Added Modifying a Key Event Notification. + + + |
+
2021-02-25 + |
+This release incorporates the following changes: +
|
+
2020-04-30 + |
+This release incorporates the following changes: +Added descriptions of the parameters domain_id, is_support_trace_files_encryption, create_time, and message to the Parameter in the response table in Creating a Tracker, Modifying a Tracker, and Querying a Tracker. Deleted SMN-related content. + |
+
2018-09-30 + |
+This release incorporates the following changes: +Added section API Version Management to support the queries of API versions. + |
+
2018-05-10 + |
+This release incorporates the following changes: +Accepted in OTC 3.1. + |
+
2018-04-08 + |
+This release incorporates the following changes: +Optimized descriptions of the parameter tracker_name in sections Tracker Management and Trace Management. + |
+
2018-03-15 + |
+This release incorporates the following changes: +Optimized the parameter description in sections Creating a Tracker, Modifying a Tracker, and Querying a Tracker. + |
+
2018-02-25 + |
+This release incorporates the following changes: +In sections Creating a Tracker, Modifying a Tracker, and Querying a Tracker, added the parameters related to the new feature in Key Event Notifications, which is notifications of login activities of specified users. + |
+
2018-01-30 + |
+This release incorporates the following changes: +
|
+
2017-12-30 + |
+This release incorporates the following changes: +Added descriptions of notifications of native OpenStack API calls in sections Creating a Tracker, Modifying a Tracker, and Querying a Tracker. + |
+
2017-11-30 + |
+This release incorporates the following changes: +Added parameters in sections Creating a Tracker and Modifying a Tracker. These parameters can be configured to enable notifications of user login activities. + |
+
2017-10-30 + |
+This release incorporates the following changes: +Added parameters in sections Creating a Tracker and Modifying a Tracker. These parameters can be configured to support the search of management traces using LTS. + |
+
2017-09-30 + |
+This release incorporates the following changes: +
|
+
2017-08-30 + |
+This release incorporates the following changes: +
|
+
2017-05-26 + + |
+This release incorporates the following changes: +In section Querying a Tracker, added the description of API responses. + |
+
2017-04-28 + |
+This release incorporates the following changes: +In section Trace Management, added the description of Querying Traces v2.0. + |
+
2017-02-27 + |
+This release incorporates the following changes: +
|
+
2017-02-08 + |
+This release incorporates the following changes: +
|
+
2017-02-03 + |
+This release incorporates the following changes: +
|
+
2017-01-20 + |
+This release incorporates the following changes: +Added the servicetype parameter to the trace query API. + |
+
2016-12-30 + |
+This issue is the first official release. + |
+
This API is used to query a specified API version of CTS.
+None
+Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
---|---|---|---|
version + |
+Yes + |
+Array + |
+Information of the API version. + |
+
id + |
+Yes + |
+String + |
+Version ID (version number), for example, v1. + |
+
links + |
+Yes + |
+String + |
+API URL + |
+
href + |
+Yes + |
+String + |
+Reference address of the current API version + |
+
rel + |
+Yes + |
+String + |
+Relationship between the current API version and the referenced address + |
+
version + |
+Yes + |
+String + |
+If microversions are supported by the APIs of the given version, the maximum microversion supported will be displayed. If microversions are not supported, this parameter will be left blank. + |
+
status + |
+Yes + |
+String + |
+Version status. The value will be one of the following: +CURRENT: The version is the primary version. +SUPPORTED: The version is an old version, but it is still supported. +DEPRECATED: The version is a deprecated version, which may be deleted later. + |
+
updated + |
+Yes + |
+String + |
+Version release time, which is the Coordinated Universal time (UTC). For example, the release time of v1 is 2014-06-28T12:20:21Z. + |
+
min_version + |
+No + |
+String + |
+If microversions are supported by the APIs of the given version, the minimum microversion supported will be displayed. If microversions are not supported, this parameter will be left 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 + |
+The request was forbidden. + |
+
404 Not Found + |
+The server failed to find the requested resource. + |
+
408 Request Timeout + |
+The request timed out. + |
+
429 Too Many Requests + |
+The number of requests exceeded the upper limit. + |
+
500 Internal Server Error + |
+Failed to complete the request because of an internal service error. + |
+
503 Service Unavailable + |
+The service is currently unavailable. + |
+
This API is used to query all API versions supported by Cloud Trace Service (CTS).
+GET /
+None
+Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
---|---|---|---|
version + |
+Yes + |
+Array + |
+List of all API versions + |
+
id + |
+Yes + |
+String + |
+Version ID (version number), for example, v1. + |
+
links + |
+Yes + |
+String + |
+API URL + |
+
href + |
+Yes + |
+String + |
+Reference address of the current API version + |
+
rel + |
+Yes + |
+String + |
+Relationship between the current API version and the referenced address + |
+
version + |
+Yes + |
+String + |
+If microversions are supported by the APIs of the given version, the maximum microversion supported will be displayed. If microversions are not supported, this parameter will be left blank. + |
+
status + |
+Yes + |
+String + |
+Version status. The value will be one of the following: +CURRENT: The version is the primary version. +SUPPORTED: The version is an old version, but it is still supported. +DEPRECATED: The version is a deprecated version, which may be deleted later. + |
+
updated + |
+Yes + |
+String + |
+Version release time, which is the Coordinated Universal time (UTC). For example, the release time of v1 is 2014-06-28T12:20:21Z. + |
+
min_version + |
+No + |
+String + |
+If microversions are supported by the APIs of the given version, the minimum microversion supported will be displayed. If microversions are not supported, this parameter will be left 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": "" + } + { + "id": "v2.0", + "links": [ + { + "href": "https://x.x.x.x/v2.0/", + "rel": "self" + } + ], + "min_version": "", + "status": "SUPPORTED", + "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 + |
+The request was forbidden. + |
+
404 Not Found + |
+The server failed to find the requested resource. + |
+
408 Request Timeout + |
+The request timed out. + |
+
429 Too Many Requests + |
+The number of requests exceeded the upper limit. + |
+
500 Internal Server Error + |
+Failed to complete the request because of an internal service error. + |
+
503 Service Unavailable + |
+The service is currently unavailable. + |
+
All API URLs described in this section are case-sensitive.
+This API is used to create a tracker.
+A tracker will be automatically created when CTS is enabled. All traces recorded by CTS are associated with the tracker. Currently, only one tracker can be created for each tenant in a region.
+Traces are retained in the CTS console for seven days. For long-term storage, you can enable Object Storage Service (OBS) and deliver real-time operation records to OBS buckets.
+POST /v1.0/{project_id}/tracker
+Parameter + |
+Sub-Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
---|---|---|---|---|
bucket_name + |
+N/A + |
+Yes + |
+String + |
+OBS bucket name. The value contains 3 to 63 characters and must start with a digit or lowercase letter. Only lowercase letters, digits, hyphens (-), and periods (.) are allowed. + |
+
file_prefix_name + |
+N/A + |
+No + |
+String + |
+Prefix of trace files that need to be stored in OBS buckets. The value can contain 0 to 64 characters, including letters, digits, hyphens (-), underscores (_), and periods (.). + |
+
lts + |
+is_lts_enabled + |
+No + |
+Boolean + |
+Whether trace analysis is enabled. + NOTE:
+When you enable trace analysis, a log group named CTS and a log stream named system-trace are created in LTS. + |
+
{ + "bucket_name" : "obs-f1da", + "file_prefix_name" : "yO8Q", + "lts" : { + "is_lts_enabled" : true + } +}+
Parameter + |
+Sub-Parameter + |
+Type + |
+Description + |
+
---|---|---|---|
bucket_name + |
+N/A + |
+String + |
+OBS bucket name. The value contains 3 to 63 characters and must start with a digit or lowercase letter. Only lowercase letters, digits, hyphens (-), and periods (.) are allowed. + |
+
file_prefix_name + |
+N/A + |
+String + |
+Prefix of trace files that need to be stored in OBS buckets. + |
+
status + |
+N/A + |
+String + |
+Status of a tracker. The value is enabled. + |
+
tracker_name + |
+N/A + |
+String + |
+Tracker name. The default value is system. + |
+
lts + + + |
+is_lts_enabled + |
+Boolean + |
+Whether trace analysis is enabled. + |
+
log_group_name + |
+String + |
+Name of the Log Tank Service (LTS) log group. + |
+|
log_topic_name + |
+String + |
+Name of the LTS log stream. + |
+
{ + "bucket_name" : "obs-f1da", + "file_prefix_name" : "yO8Q", + "lts" : { + "is_lts_enabled" : true, + "log_group_name" : "CTS", + "log_topic_name" : "system-trace" + }, + "bucket_name" : "1214", + "tracker_name" : "system", + "file_prefix_name" : "", + "status" : "enabled", + "tracker_type" : "system" +}+
Returned Value + |
+Description + |
+
---|---|
201 + |
+The request is successful. + |
+
Returned Value + |
+Description + |
+
---|---|
400 + |
+The server failed to process the request. + |
+
403 + |
+The server understood the request but refused to authorize it. + |
+
500 + |
+Failed to complete the request because of an internal service error. + |
+
401 + |
+The request is rejected due to authentication failure. + |
+
400 + |
+The requested OBS bucket does not exist. + |
+
This API is used to query records of operations on resources in the last seven days. In v2.0, the request parameter trace_rating is changed to trace_status, and the type of response parameter user is changed to Structure.
+GET /v2.0/{project_id}/{tracker_name}/trace{?trace_id,service_type,resource_type,resource_id,resource_name,trace_name,trace_status,user,limit,from,to,next}
+Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
---|---|---|---|
service_type + |
+No + |
+String + |
+Type of a service whose traces are to be queried. The value must be the acronym of a cloud service that has been connected with CTS. It is a word composed of uppercase letters. +For cloud services that can be connected with CTS, see section "Supported Services and Operations" in the Cloud Trace Service User Guide. + |
+
resource_type + |
+No + |
+String + |
+Type of a resource whose traces are to be queried. The value can contain 1 to 64 characters, including letters, digits, hyphens (-), underscores (_), and periods (.). It must start with a letter. For cloud services that can be connected with CTS, see section "Supported Services and Operations" in the Cloud Trace Service User Guide. + |
+
resource_id + |
+No + |
+String + |
+ID of a cloud resource whose traces are to be queried. + |
+
resource_name + |
+No + |
+String + |
+Name of a resource whose traces are to be queried. + NOTE:
+The resource name is case sensitive. + |
+
trace_name + |
+No + |
+String + |
+Trace name. It indicates the operation recorded by this trace. + NOTE:
+The trace name is case sensitive. + |
+
limit + |
+No + |
+String + |
+Number of traces returned in the trace list. The default value is 50 and the maximum value is 200. + |
+
next + |
+No + |
+String + |
+This parameter is used to query traces generated earlier than its specified value. The value can be that of marker in Table 5. +next can be used with from and to. +Traces generated in the overlap of the two time ranges specified respectively by next and by from and to will be returned. + |
+
from + |
+No + |
+String + |
+UTC timestamp of the start time of the query time range. The value is in milliseconds and contains 13 digits. Traces generated on the specified timestamp are not returned. The parameters from and to should be used together. + |
+
to + |
+No + |
+String + |
+UTC timestamp of the end time of the query time range. The value is in milliseconds and contains 13 digits. Traces generated on the specified timestamp are not returned. The parameters to and from should be used together. + |
+
trace_id + |
+No + |
+String + |
+Trace ID. +If this parameter is specified, other query criteria will not take effect. + |
+
trace_status + |
+No + |
+String + |
+Status of a trace. The value can be normal, warning, or incident. + |
+
user + |
+No + |
+String + |
+Name of the user whose traces are to be queried. + NOTE:
+The username is case sensitive. + |
+
GET +/v2.0/{project_id}/{tracker_name}/trace?limit=11&to=1479095278000&from=1478490478000&trace_name=createTracker&resource_type=tracker&service_type=CTS+
Parameter + |
+Type + |
+Description + |
+
---|---|---|
traces + |
+array + |
+List of returned traces. + |
+
meta_data + |
+Structure + |
+Extended parameter. The value can be count (number of traces in the response) or marker (ID of the last trace in the trace list). + |
+
Parameter + |
+Type + |
+Description + |
+
---|---|---|
resource_id + |
+String + |
+ID of a cloud resource on which the recorded operation was performed. + |
+
trace_name + |
+String + |
+Name of a trace. The value can contain 1 to 64 characters, including letters, digits, hyphens (-), underscores (_), and periods (.). It must start with a letter. + |
+
trace_status + |
+String + |
+Trace status. The value can be normal, warning, or incident. + |
+
trace_type + |
+String + |
+Trace source. The value can be ApiCall, ConsoleAction, or SystemAction. + |
+
request + |
+String + |
+Request of an operation on resources. + |
+
response + |
+String + |
+Response to a user request, that is, the returned information for an operation on resources. + |
+
code + |
+String + |
+HTTP status code returned by the associated API. + |
+
api_version + |
+String + |
+Version of the API. + |
+
message + |
+String + |
+Remarks added by other cloud services to a trace. + |
+
record_time + |
+Long + |
+Timestamp when an operation was recorded by CTS. + |
+
trace_id + |
+String + |
+Trace ID. The value is the UUID generated by the system. + |
+
time + |
+Long + |
+Timestamp when a trace was generated. + |
+
user + |
+Structure + |
+Information of the user who performed the operation that triggered the trace. + |
+
service_type + |
+String + |
+Type of a service whose traces are to be queried. The value must be the acronym of a cloud service that has been connected with CTS. It is a word composed of uppercase letters. + |
+
resource_type + |
+String + |
+Type of a resource whose traces are to be queried. The value can contain 1 to 64 characters, including letters, digits, hyphens (-), underscores (_), and periods (.). It must start with a letter. + |
+
source_ip + |
+String + |
+IP address of the tenant who performed the operation that triggered the trace. + |
+
resource_name + |
+String + |
+Name of a resource on which the recorded operation was performed. + |
+
request_id + |
+String + |
+Request ID. + |
+
location_info + |
+String + |
+Additional information required for fault locating after a request error. + |
+
endpoint + |
+String + |
+Endpoint in the details page URL of the cloud resource on which the recorded operation was performed. + |
+
resource_url + |
+String + |
+Details page URL (excluding the endpoint) of the cloud resource on which the recorded operation was performed. + |
+
Parameter + |
+Type + |
+Description + |
+
---|---|---|
count + |
+Integer + |
+Number of returned traces. + |
+
marker + |
+String + |
+ID of the last trace in the returned trace list. The value of this parameter can be used as the next value. If the value of marker is null, all traces have been returned. + |
+
{ + "traces" : [ { + "time" : 1472148708232, + "user" : "{\"name\":\"xxx\",\"id\":\"a2e899190fcd444084a68fc0ac2sc1e9\",\"domain\":{\"name\":\"xxx\",\"id\":\"05b2598d69bc4a209f9ac5eeeb1f91ad\"}}", + "response" : "{\"code\":\"VPC.0514\",\"message\":\"Update port fail.\"}", + "code" : 200, + "service_type" : "VPC", + "resource_type" : "eip", + "resource_name" : "192.144.163.1", + "resource_id" : "d502809d-0d1d-41ce-9690-784282142ccc", + "trace_name" : "deleteEip", + "trace_status " : "warning", + "trace_type" : "ConsoleAction", + "api_version" : "2.0", + "record_time" : 1481066128032, + "trace_id" : "e001ccb9-bc09-11e6-b00b-4b2a61338db6" + "request_id" : "a0001c1b9-bctt-2136-c12b-4b2a611116" + "location_info" : "resource has been deleted" + "endpoint" : "https://*****/vpc?agencyId=***®ion=***&locale=zh-cn#" + "resource_url" : "/vpc/vpcmanager/vpcs?vpcid=*****" + }, { + "time" : 1472148708232, + "user" : "{\"name\":\"xxx\",\"domain\":{\"name\":\"xxx\",\"id\":\"ded649d814464428ba89d04d7955c93e\"},\"assumedBy\":{\"user\":{\"name\":\"bss_bm_admin\",\"id\":\"c5140af45b5d4b399dea8f900f1dcf1b\",\"domain\":{\"name\":\"op_service\",\"id\":\"71ce673175024d0495664e525e52bac0\"}}}}", + "response" : "{\"code\":\"VPC.0514\",\"message\":\"Update port fail.\"}", + "code" : 200, + "service_type" : "VPC", + "resource_type" : "eip", + "resource_name" : "192.144.163.1", + "resource_id" : "d502809d-0d1d-41ce-9690-784282142ccc", + "trace_name" : "deleteEip", + "trace_status" : "warning", + "trace_type" : "ConsoleAction", + "api_version" : "2.0", + "record_time" : 1481066128032, + "trace_id" : "e001ccb8-bc09-11e6-b2cc-2640a43cc6e8" + "request_id" : "a0001c1b9-bctt-2136-c12b-4b2a611116" + "location_info" : "resource has been deleted" + "endpoint" : "https://*****/vpc?agencyId=***®ion=***&locale=zh-cn#" + "resource_url" : "/vpc/vpcmanager/vpcs?vpcid=*****" + + } ], + "meta_data" : { + "count" : 2, + "marker" : "e001ccb8-bc09-11e6-b2cc-2640a43cc6e8" + } +}+ +
Returned Value + |
+Description + |
+
---|---|
200 + |
+The request is successful and the query result is returned. + |
+
Returned Value + |
+Description + |
+
---|---|
400 + |
+The query parameters are abnormal. + |
+
500 + |
+Failed to complete the request because of an internal service error. + |
+
401 + |
+The request is rejected due to authentication failure. + |
+
403 + |
+The server understood the request but refused to authorize it. + |
+
404 + |
+The requested trace does not exist. + |
+
This API is used to query the details of a tracker. The details include the name of the tracker, name of the OBS bucket for storing traces, and prefix of the trace files stored in the OBS bucket.
+GET /v1.0/{project_id}/tracker?tracker_name={tracker_name}
+Parameter + |
+Mandatory + |
+Type + |
+Description + |
+
---|---|---|---|
project_id + |
+Yes + |
+String + |
+Project ID + |
+
tracker_name + |
+No + |
+String + |
+Tracker name. +If this parameter is not specified, all trackers will be queried. +Currently, only one tracker is allowed for each tenant. The tracker name is system. + |
+
It is expected that CTS can support multiple trackers in the future. In this case, if you send a request where the parameter tracker_name is not specified (GET /v1.0/{project_id}/tracker), the response will be in array format. Otherwise, the response will be in object format.
+GET /v1.0/{project_id}/tracker?tracker_name=system+
Parameter + |
+Sub-Parameter + |
+Type + |
+Description + |
+
---|---|---|---|
tracker_name + |
+- + |
+String + |
+Tracker name. It is set as system by default. + |
+
bucket_name + |
+- + |
+String + |
+OBS bucket name. It starts with a number or lowercase letter and contains 3 to 63 characters, including lowercase letters, numbers, hyphens (-), and periods (.) + |
+
file_prefix_name + |
+- + |
+String + |
+Prefix of trace files that need to be stored in OBS buckets + |
+
status + |
+- + |
+String + |
+Status of a tracker. The value can be enabled or disabled. + |
+
detail + |
+- + |
+String + |
+This parameter is returned only when the tracker status is abnormal. It specifies the cause of the exception. The value will be checkBucketExistFailed, which indicates the failure to check the bucket, or noBucket, which indicates that the bucket does not exist. + |
+
+ lts + + |
+is_lts_enabled + |
+Boolean + |
+Whether trace analysis is enabled + |
+
log_group_name + |
+String + |
+Name of the LTS log group + |
+|
log_topic_name + |
+String + |
+Name of the LTS log stream + |
+
{ + "bucket_name" : "my_created_bucket", + "tracker_name" : "system", + "detail" : "noBucket", + "file_prefix_name" : "some_folder", + "status" : "disabled", + "lts" : { + "is_lts_enabled" : true, + "log_group_name" : "CTS", + "log_topic_name" : "tracker" + }, + "bucket_name" : "1214", + "tracker_name" : "system", + +}+
Returned Value + |
+Description + |
+
---|---|
200 + |
+The request is successful and the query result is returned. + |
+
Returned Value + |
+Description + |
+
---|---|
400 + |
+The server failed to process the request. + |
+
500 + |
+Failed to complete the request because of an internal service error. + |
+
401 + |
+Your access request is rejected. + |
+
403 + |
+You are forbidden to access the requested page. + |
+
This section explains the meanings of error codes returned by CTS APIs.
+{
+"error_code": "CTS.0003",
+"error_msg": "Invalid message body. The message body is empty or invalid."
+}
+Status Code + |
+Error Code + |
+Error Message + |
+Description + |
+Solution + |
+
---|---|---|---|---|
400 + |
+CTS.0001 + |
+IAM or OBS exception, please check. + |
+The IAM or OBS service is abnormal. + |
+Contact technical support. + |
+
403 + |
+CTS.0002 + |
+The user fails the authentication or does not have permission to this operation. + |
+Authentication failed or you do not have the permissions required. + |
+Check your permissions. + |
+
400 + |
+CTS.0003 + |
+Invalid message body. The message body is empty or invalid. + |
+The message body is empty or invalid. + |
+Check the body content and format. + |
+
500 + |
+CTS.0004 + |
+Data write exception. + |
+Failed to write data. + |
+Contact technical support. + |
+
500 + |
+CTS.0005 + |
+Data read exception. + |
+Failed to read data. + |
+Contact technical support. + |
+
403 + |
+CTS.0012 + |
+Invalid project ID. Check whether the project ID is correct. + |
+The project ID is invalid. + |
+Check whether the project ID is correct. + |
+
400 + |
+CTS.0056 + |
+Failed to create lts trace analysis. + |
+Failed to enable trace analysis. + |
+Contact technical support. + |
+
404 + |
+CTS.0100 + |
+CTS does not support API interface version query. + |
+API version query is not supported in CTS. + |
+Contact technical support. + |
+
400 + |
+CTS.0200 + |
+Tracker number is Maximum. + |
+The number of trackers has reached the upper limit. + |
+Delete or modify unnecessary trackers. + |
+
400 + |
+CTS.0201 + |
+A management tracker has been created. + |
+A management tracker has been created. + |
+Check whether the management tracker is available. + |
+
400 + |
+CTS.0202 + |
+Invalid message body. Tracker tracker_type must be either system or data. + |
+The value of tracker_type is invalid. + |
+Change its value to system or data. + |
+
400 + |
+CTS.0203 + |
+Invalid message body. The tracker_name is a string of 1 to 32 characters and cannot start with underscores or hyphens. + |
+The value of tracker_name is invalid. + |
+Modify its value by referring to the parameter descriptions. + |
+
400 + |
+CTS.0204 + |
+The tracker_name parameter of a management tracker can only be set to system. + |
+The tracker_name parameter of a management tracker must be set to system. + |
+Modify its value by referring to the parameter descriptions. + |
+
400 + |
+CTS.0205 + |
+Invalid message body. Tracker status is required and value must be either enabled or disabled. + |
+The status parameter can only be set to enabled or disabled. + |
+Change its value to enabled or disabled. + |
+
400 + |
+CTS.0206 + |
+Invalid message body. The data_bucket is not need. + |
+The data_bucket parameter cannot be included in the message body for a management tracker. + |
+Delete the data_bucket parameter. + |
+
400 + |
+CTS.0207 + |
+Invalid message body. The tracker_name value cannot be system or system-trace. + |
+The tracker_name parameter in the message body cannot be set to system for a data tracker. + |
+Change the value of tracker_name to a value other than system. + |
+
400 + |
+CTS.0208 + |
+The tracker already exists. + |
+The tracker already exists. + |
+Check whether the tracker already exists. + |
+
400 + |
+CTS.0209 + |
+You cannot create different trackers to record the same type of operations on the same OBS bucket. + |
+A type of operations on an OBS bucket can be tracked by only one tracker. + |
+Change the tracker configurations. + |
+
400 + |
+CTS.0210 + |
+Invalid message body. The OBS bucket for which data operations are to be recorded can not be empty. + |
+The OBS bucket to be tracked cannot be empty. + |
+Select another bucket or ensure that the bucket is not empty. + |
+
400 + |
+CTS.0211 + |
+Check bucket failed.The bucket is not exist. + |
+The OBS bucket to be tracked does not exist. + |
+Check whether bucket_name is correctly set. + |
+
400 + |
+CTS.0212 + |
+The tracked OBS bucket can not be modify. + |
+The tracked OBS bucket cannot be modified. + |
+Withdraw the changes on the OBS bucket. + |
+
400 + |
+CTS.0213 + |
+Invalid message body. The OBS bucket for which data operations are to be recorded and the OBS bucket configured for storing transferred traces cannot be the same. + |
+The OBS bucket used for trace transfer cannot be the tracked OBS bucket. + |
+Select another OBS bucket for trace transfer. + |
+
404 + |
+CTS.0214 + |
+The tracker does not exist. + |
+The tracker does not exist. + |
+Check whether the tracker has been deleted. + |
+
400 + |
+CTS.0215 + |
+Check bucket failed.The bucket is already exist. + |
+The OBS bucket already exists. + |
+Change the value of bucket_name. + |
+
400 + |
+CTS.0216 + |
+Create bucket failed. + |
+Failed to create a bucket. + |
+Contact technical support. + |
+
400 + |
+CTS.0217 + |
+Set bucket life cycle failed. Contact O&M personnel. + |
+Failed to set a lifecycle rule for the OBS bucket. + |
+Contact technical support. + |
+
400 + |
+CTS.0218 + |
+Invalid message body. The file_prefix_name is a string of 0 to 64 characters and can only contain uppercase letters, lowercase letters, digits, hyphens, underscores and periods. + |
+The value of file_prefix_name is invalid. + |
+Modify its value by referring to the parameter descriptions. + |
+
400 + |
+CTS.0219 + |
+The bucket operation cannot be empty. + |
+The operation type cannot be empty. + |
+Select at least one operation type to track. + |
+
400 + |
+CTS.0220 + |
+KMS is not supported. + |
+KMS is not supported. + |
+Contact technical support. + |
+
400 + |
+CTS.0221 + |
+The KMS ID is empty. + |
+The KMS ID is empty. + |
+Check whether the KMS ID is correct. + |
+
400 + |
+CTS.0222 + |
+Failed to obtain key list from KMS. + |
+KMS verification failed. + |
+Check whether the KMS ID is correct. + |
+
400 + |
+CTS.0225 + |
+The Bucket operation must be WRITE or READ or WRITE,READ. + |
+The bucket operation must be write, read, or read/write. + |
+Enter a correct parameter. + |
+
400 + |
+CTS.0231 + |
+Invalid bucket name. A bucket name must be a string of 3 to 63 characters, including only lowercase letters, digits, hyphens (-), or periods (.). It must start with a digit or a lowercase letter. + |
+Invalid bucket name. A bucket name must contain 3 to 63 characters and start with a digit or a lowercase letter. Only lowercase letters, digits, hyphens (-), and periods (.) are allowed. + |
+Check whether the bucket name is correct. + |
+
400 + |
+CTS.0300 + |
+Query data failed. + |
+Query failed. + |
+Try again later or contact technical support. + |
+
400 + |
+CTS.0400 + |
+Notification name is existed already. + |
+The key event notification name already exists. + |
+Check whether the key event notification already exists. + |
+
400 + |
+CTS.0401 + |
+Invalid message body. The operations parameter value is invalid. + |
+The operations parameter is invalid. + |
+Check whether the operation parameter is correct. + |
+
400 + |
+CTS.0402 + |
+The Smn topic does not exist. + |
+The SMN topic does not exist. + |
+Check whether the SMN topic exists. + |
+
404 + |
+CTS.0403 + |
+The notification does not exist. + |
+The key event notification does not exist. + |
+Check whether the key event notification has been deleted. + |
+
400 + |
+CTS.0404 + |
+State setting failed, check if topicId exists. + |
+Failed to enable the key event notification. Check whether the SMN topic has been configured. + |
+Check whether the SMN topic has been configured. + |
+
400 + |
+CTS.0407 + |
+The quantity has exceeded the maximum quantity limit. + |
+The number of key event notifications exceeds the upper limit. + |
+Check whether the number of key event notifications exceeds the quota. + |
+
400 + |
+CTS.0410 + |
+The notification_type must be smn. + |
+The key event notification type can only be smn. + |
+Check the key operation notification type. + |
+
400 + |
+CTS.0411 + |
+The notification_name invalid. + |
+The notification name is invalid. + |
+Check whether the notification name is correct. + |
+