Currently, CTS only sends notifications for some key operations on ECS, EVS, VPC, KMS, IAM, and native OpenStack. This feature currently supports creation, deletion, login, and native OpenStack API operations. This function is still being improved and will support more services and operation types in the future. For details, see Configuring a Tracker.
CTS sends notifications of all key operations on services including ECS, EVS, VPC, DEW, native OpenStack, and IAM. These operations include creation, deletion, login, and native OpenStack API calls.
diff --git a/docs/cts/umn/cts_faq_017.html b/docs/cts/umn/cts_faq_017.html
index 5a8e8a19..979b39fd 100644
--- a/docs/cts/umn/cts_faq_017.html
+++ b/docs/cts/umn/cts_faq_017.html
@@ -1,11 +1,11 @@
OBS provides three storage classes of buckets for storage, respectively standard access, infrequent access, or archive. You must select a standard OBS bucket because CTS needs to frequently access the OBS bucket that stores traces.
+
How Can I Store Trace Files for a Long Time?
+
CTS only retains traces for seven days. To store traces for a long time, configure your tracker to transfer traces to OBS buckets. For details, see Configuring a Tracker.
diff --git a/docs/cts/umn/cts_faq_019.html b/docs/cts/umn/cts_faq_019.html
deleted file mode 100644
index 6d211a48..00000000
--- a/docs/cts/umn/cts_faq_019.html
+++ /dev/null
@@ -1,12 +0,0 @@
-
-
-
Why Are user and source_ip Empty for Some Traces with trace_type as systemAction?
-
The trace_type field indicates the request resource. This field can be ConsoleAction, ApiCall, and SystemAction.
-
SystemAction indicates that the operations are not triggered by users, such as automatic alarms, elastic scaling, scheduled backup tasks, and secondary invocations generated within the system to respond to the user's request. In this case, no user or device that triggers an operation exists. Therefore, user and source_ip are both empty.
-
-
-
diff --git a/docs/cts/umn/cts_faq_020.html b/docs/cts/umn/cts_faq_020.html
deleted file mode 100644
index b6abaf93..00000000
--- a/docs/cts/umn/cts_faq_020.html
+++ /dev/null
@@ -1,12 +0,0 @@
-
-
-
What Are the Meanings of the Three Trace Statuses?
-
The trace status is defined based on
trace_status information recorded in a trace. Different fields have different meanings as follows:
- normal: indicates that this operation succeeded.
- warning: indicates that this operation failed.
- incident: indicates that this operation causes a more serious consequence than a failure, for example, causing a node failure or service interruption.
-
-
-
-
diff --git a/docs/cts/umn/cts_faq_0912.html b/docs/cts/umn/cts_faq_0912.html
new file mode 100644
index 00000000..130e407c
--- /dev/null
+++ b/docs/cts/umn/cts_faq_0912.html
@@ -0,0 +1,18 @@
+
+
+
How Can I Find Out Who Created a Specific ECS?
+
Solution
To identify the user who created a specific ECS, you can view traces recorded by CTS.
+
+
Prerequisites
- You have enabled CTS.
- You have obtained the resource ID of the ECS.
+
+
Procedure
Log in to the CTS console, choose Trace List, and select ECS for Trace Source. In the displayed traces, look for the createServer trace with the obtained resource ID, and expand the trace details.
+
The user field shows details of the IAM user who created the ECS. The format is {"name": "Account name", "id": "Account ID", "domain"{"name": "IAM user name", "id": "IAM user ID"}}. If the ECS was created by an account, the IAM user name and the account name are the same.
+
+
+
+
+
diff --git a/docs/cts/umn/cts_faq_0913.html b/docs/cts/umn/cts_faq_0913.html
new file mode 100644
index 00000000..a7319e50
--- /dev/null
+++ b/docs/cts/umn/cts_faq_0913.html
@@ -0,0 +1,18 @@
+
+
+
How Can I Find Out the Login IP Address of an IAM User?
+
Solution
If you want to check if there are security risks in your account by examining the login IP addresses and login time of IAM users, you can view traces recorded by CTS.
+
+
Prerequisites
You have enabled CTS.
+
+
Procedure
- Log in to the CTS console, select IAM for Trace Source, select a time range, and click Query.
+
- Click View Trace in the Operation column of a trace to view its details. source_ip indicates the login IP address, and record_time indicates the login time.
+
+
+
+
+
diff --git a/docs/cts/umn/cts_faq_0915.html b/docs/cts/umn/cts_faq_0915.html
new file mode 100644
index 00000000..3472f459
--- /dev/null
+++ b/docs/cts/umn/cts_faq_0915.html
@@ -0,0 +1,11 @@
+
+
+
Why Are Two deleteMetadata Traces Generated When I Buy an ECS?
+
During ECS creation, metadata is used to store temporary information. When the creation is finished, the information is automatically deleted. Thus, two traces named deleteMetadata are generated.
+
+
+
diff --git a/docs/cts/umn/cts_faq_0918.html b/docs/cts/umn/cts_faq_0918.html
new file mode 100644
index 00000000..6e7bd8b5
--- /dev/null
+++ b/docs/cts/umn/cts_faq_0918.html
@@ -0,0 +1,16 @@
+
+
+
What Can I Do If I Cannot Query Traces?
+
Background
Traces cannot be queried on the CTS console.
+
+
Solution
- Check whether you have configured a proper query time range.
+
- Check whether you have configured filters correctly.
+
- If you still cannot query traces after the preceding steps, submit a service ticket for technical support.
+
+
+
+
diff --git a/docs/cts/umn/cts_faq_0919.html b/docs/cts/umn/cts_faq_0919.html
new file mode 100644
index 00000000..cdf9bf31
--- /dev/null
+++ b/docs/cts/umn/cts_faq_0919.html
@@ -0,0 +1,21 @@
+
+
+
Can I Disable CTS?
+
You can use the basic functions of CTS for free, including enabling a tracker, tracking traces, as well as storing and querying traces of the last seven days. Only value-added services, such as trace transfer, are charged. If you only use the basic services, you do not need to disable CTS since no fees are generated.
+
If you do need to disable CTS, you can do it in the following two ways:
+
- Delete or disable existing trackers. (The system tracker created by CTS can only be disabled and cannot be deleted.) No traces will be generated.
- Delete the CTS agency from the IAM agency list. CTS will become unavailable.
+
+
+
+
+
+
\ No newline at end of file
diff --git a/docs/cts/umn/en-us_cts_01_0001.html b/docs/cts/umn/en-us_cts_01_0001.html
deleted file mode 100644
index e27263dc..00000000
--- a/docs/cts/umn/en-us_cts_01_0001.html
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-
Configuring Key Event Notifications
-
Scenarios
You can configure key event notifications on CTS so that Simple Message Notification (SMN) can send messages to notify you of key operations. This function is triggered by CTS, but notifications are sent by SMN. This function is used in the following scenarios:
- Real-time detection and confirmation of high-risk operations (such as VM restart and security configuration changes), cost-sensitive operations (such as creating and deleting expensive resources), and service-sensitive operations (such as network configuration changes)
- Detection and confirmation of unauthorized operations and operations such as logging in with high permissions
- Interconnecting with your own audit system: All audit logs are synchronized to your audit system in real time for analysis of API calling success rate, unauthorized operations, security, and costs.
-
-
-
Note
- Key event notifications are sent to subscribers by SMN. Therefore, before using CTS, you need to know how to create topics and add subscriptions on the SMN console.
- Currently, you can create 100 key event notifications in CTS and specify key operations, users, and topics for each notification.
- You can configure a maximum of 50 users in 10 user groups in key event notifications. For each notification, you can select multiple users in a same user group.
- You can select a maximum of 1000 key operations of 100 cloud services for each notification.
- Key event notification is an upgraded version of the original notification function. It is more powerful and provides more configuration items.
-
-
Procedure
- Log in to the management console.
- Click
in the upper left corner to select the desired project. - Click Service List and choose Management & Deployment > Cloud Trace Service.
- In the navigation pane on the left, choose Key Event Notifications.
- Click Create Key Event Notification in the upper right corner of the page. On the displayed page, specify required parameters.
- Enter a key event notification name in the Basic Information area.
Notification Name: Identifies key event notifications. This parameter is mandatory. The value contains a maximum of 64 characters, and only letters, numbers, and underscores (_) are allowed.
- - Configure key operations.
Select
Typical,
All, or
Custom based on your actual requirements:
- Typical: This option is suitable for enterprise routine auditing. Notifications will be sent when your specified operations occur, such as creating or deleting core resources of ECS, Virtual Private Cloud (VPC), EVS, or Key Management Service (KMS), and logging in as an Identity and Access Management (IAM) user.
- All: This option is suitable if you have connected CTS to your own audit systems. When All is chosen, you cannot deselect operations because all operations on all cloud services that have connected with CTS will trigger notifications. You are advised to use an SMN topic for which HTTPS is selected.
- Custom: This option is suitable for enterprises that require detection of high-risk, cost-sensitive, service-sensitive, and unauthorized operations. You can connect CTS with your own audit systems for log analysis. Select the operations that will trigger notifications. Up to 1000 operations of 100 services can be added for each notification. For details, see Supported Services and Operation Lists.
-
- Configure users.
Specify users. SMN messages will be sent to subscribers when specified users perform key operations.
-- If you select All users, SMN will notify subscribers of key operations initiated by all users.
- If you select Specified users and specify users, SMN will notify subscribers of key operations initiated by these users. You can configure a maximum of 50 users in 10 user groups. For each notification, you can select multiple users in a same user group.
- - Configure an SMN topic.
- If you select Yes for Send Notification, you can select an existing topic or click Topic to create one on the SMN console.
- If you select No for Send Notification, no further action is required.
- - Click Create Now. The Key Event Notifications page is displayed, showing all created key event notifications.
-
-
-
-
diff --git a/docs/cts/umn/en-us_cts_01_0002.html b/docs/cts/umn/en-us_cts_01_0002.html
deleted file mode 100644
index fe636b1a..00000000
--- a/docs/cts/umn/en-us_cts_01_0002.html
+++ /dev/null
@@ -1,192 +0,0 @@
-
-
-
Key Operations on SDRS
-
Storage Disaster Recovery Service (SDRS) provides disaster recovery (DR) services for many cloud services, such as Elastic Cloud Server (ECS), Elastic Volume Service (EVS), and Dedicated Distributed Storage Service (DSS). SDRS uses multiple technologies, such as storage replication, data redundancy, and cache acceleration, to provide high data reliability and service continuity for users.
-
With CTS, you can record operations associated with SDRS for later query, audit, and backtracking.
-
-
Table 1 SDRS operations that can be recorded by CTSOperation
- |
-Resource Type
- |
-Trace Name
- |
-
|---|
-
-Creating a protection group
- |
-protectionGroup
- |
-createProtectionGroup
- |
-
-Deleting a protection group
- |
-protectionGroup
- |
-deleteProtectionGroup
- |
-
-Updating a protection group
- |
-protectionGroup
- |
-updateProtectionGroup
- |
-
-Enabling protection for a protection group (when the protection group is in the available state)
- |
-protectionGroup
- |
-startProtectionGroup
- |
-
-Enabling protection for a protection group (when the protection group is in the failed-over state)
- |
-protectionGroup
- |
-reprotectProtectionGroup
- |
-
-Disabling protection for a protection group
- |
-protectionGroup
- |
-stopProtectionGroup
- |
-
-Performing a failover for a protection group
- |
-protectionGroup
- |
-failoverProtectionGroup
- |
-
-Performing a planned failover
- |
-protectionGroup
- |
-reverseProtectionGroup
- |
-
-An action performed when a job is not submitted by a protection group
- |
-protectionGroup
- |
-protectionGroupAction
- |
-
-Creating a protected instance
- |
-protectedInstance
- |
-createProtectedInstance
- |
-
-Deleting a protected instance
- |
-protectedInstance
- |
-deleteProtectedInstance
- |
-
-Updating a protected instance
- |
-protectedInstance
- |
-updateProtectedInstance
- |
-
-Attaching a replication pair to a protected instance
- |
-protectedInstance
- |
-attachReplicationPair
- |
-
-Detaching a replication pair from a protected instance
- |
-protectedInstance
- |
-detachReplicationPair
- |
-
-Adding a NIC to a protected instance
- |
-protectedInstance
- |
-addNic
- |
-
-Deleting a NIC from a protected instance
- |
-protectedInstance
- |
-deleteNic
- |
-
-Modifying the specifications of a protected instance
- |
-protectedInstance
- |
-resizeProtectedInstance
- |
-
-Creating a replication pair
- |
-replicationPair
- |
-createReplicationPair
- |
-
-Deleting a replication pair
- |
-replicationPair
- |
-deleteReplicationPair
- |
-
-Updating a replication pair
- |
-replicationPair
- |
-updateReplicationPair
- |
-
-Expanding the capacity of a replication pair
- |
-replicationPair
- |
-expandReplicationPair
- |
-
-Creating a DR drill
- |
-disasterRecoveryDrill
- |
-createDrDrill
- |
-
-Deleting a DR drill
- |
-disasterRecoveryDrill
- |
-deleteDrDrill
- |
-
-Updating a DR drill
- |
-disasterRecoveryDrill
- |
-updateDrDrill
- |
-
-
-
-
-
-
-
diff --git a/docs/cts/umn/en-us_cts_03_0011.html b/docs/cts/umn/en-us_cts_03_0011.html
deleted file mode 100644
index 99fa5766..00000000
--- a/docs/cts/umn/en-us_cts_03_0011.html
+++ /dev/null
@@ -1,185 +0,0 @@
-
-
-
Key Operations on GaussDB(for MySQL)
-
GaussDB(for MySQL) is a MySQL-compatible, enterprise-class distributed database service.
-
With CTS, you can record operations associated with GaussDB(for MySQL) for future query, audit, and backtracking.
-
-
Table 1 GaussDB(for MySQL) operations recorded by CTSOperation
- |
-Resource Type
- |
-Trace Name
- |
-
|---|
-
-Creating a DB instance
- |
-instance
- |
-createInstance
- |
-
-Creating a read replica
- |
-instance
- |
-addNodes
- |
-
-Deleting a read replica
- |
-instance
- |
-deleteNode
- |
-
-Rebooting a DB instance
- |
-instance
- |
-restartInstance
- |
-
-Changing a database port
- |
-instance
- |
-changeInstancePort
- |
-
-Changing a security group
- |
-instance
- |
-modifySecurityGroup
- |
-
-Promoting a read replica to the primary node
- |
-instance
- |
-instanceSwitchOver
- |
-
-Binding or unbinding an EIP
- |
-instance
- |
-setOrResetPublicIP
- |
-
-Deleting a DB instance
- |
-instance
- |
-deleteInstance
- |
-
-Renaming a DB instance
- |
-instance
- |
-renameInstance
- |
-
-Changing a failover priority
- |
-instance
- |
-modifyPriority
- |
-
-Modifying specifications
- |
-instance
- |
-instanceAction
- |
-
-Resetting a password
- |
-instance
- |
-resetPassword
- |
-
-Restoring data to a new DB instance
- |
-instance
- |
-restoreInstance
- |
-
-Creating a backup
- |
-backup
- |
-createManualSnapshot
- |
-
-Deleting a backup
- |
-backup
- |
-deleteManualSnapshot
- |
-
-Creating a parameter template
- |
-parameterGroup
- |
-createParameterGroup
- |
-
-Modifying parameters in a parameter template
- |
-parameterGroup
- |
-updateParameterGroup
- |
-
-Deleting a parameter template
- |
-parameterGroup
- |
-deleteParameterGroup
- |
-
-Replicating a parameter template
- |
-parameterGroup
- |
-copyParameterGroup
- |
-
-Resetting a parameter template
- |
-parameterGroup
- |
-resetParameterGroup
- |
-
-Comparing parameter templates
- |
-parameterGroup
- |
-compareParameterGroup
- |
-
-Applying a parameter template
- |
-parameterGroup
- |
-applyParameterGroup
- |
-
-
-
-
-
-
-
diff --git a/docs/cts/umn/en-us_cts_03_0012.html b/docs/cts/umn/en-us_cts_03_0012.html
deleted file mode 100644
index d90a751c..00000000
--- a/docs/cts/umn/en-us_cts_03_0012.html
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
Enterprise Intelligence
-
-
-
diff --git a/docs/cts/umn/en-us_cts_03_0013.html b/docs/cts/umn/en-us_cts_03_0013.html
deleted file mode 100644
index 3ed2b51b..00000000
--- a/docs/cts/umn/en-us_cts_03_0013.html
+++ /dev/null
@@ -1,419 +0,0 @@
-
-
-
Key Operations on ModelArts
-
ModelArts is a one-stop development platform for AI developers. With data preprocessing, semi-automated data labeling, distributed training, automated model building, and model deployment on the device, edge, and cloud, ModelArts helps AI developers build models quickly and manage the lifecycle of AI development.
-
With CTS, you can record operations associated with ModelArts for later query, audit, and backtracking.
-
-
Table 1 Key operations that can be audited for data managementOperation
- |
-Resource Type
- |
-Trace Name
- |
-
|---|
-
-Creating a dataset
- |
-dataset
- |
-createDataset
- |
-
-Deleting a dataset
- |
-dataset
- |
-deleteDataset
- |
-
-Updating a dataset
- |
-dataset
- |
-updateDataset
- |
-
-Publishing a version of a dataset
- |
-dataset
- |
-publishDatasetVersion
- |
-
-Deleting a dataset version
- |
-dataset
- |
-deleteDatasetVersion
- |
-
-Synchronizing the data source
- |
-dataset
- |
-syncDataSource
- |
-
-Exporting a dataset
- |
-dataset
- |
-exportDataFromDataset
- |
-
-Importing samples to a dataset
- |
-dataset
- |
-importSamplesToDataset
- |
-
-Creating a dataset label
- |
-dataset
- |
-createLabel
- |
-
-Updating a dataset label
- |
-dataset
- |
-updateLabel
- |
-
-Deleting a dataset label
- |
-dataset
- |
-deleteLabel
- |
-
-Deleting a dataset label and its samples
- |
-dataset
- |
-deleteLabelWithSamples
- |
-
-Adding samples
- |
-dataset
- |
-uploadSamples
- |
-
-Deleting samples
- |
-dataset
- |
-deleteSamples
- |
-
-
-
-
-
Key Operations Recorded for Development Environments
-
-
Table 2 Key operations that can be audited in the development environmentOperation
- |
-Resource Type
- |
-Trace Name
- |
-
|---|
-
-Creating a notebook instance
- |
-Notebook
- |
-create_instance
- |
-
-Deleting a notebook instance
- |
-Notebook
- |
-delete_instance
- |
-
-Starting a notebook instance
- |
-Notebook
- |
-change_instance_status
- |
-
-Stopping a notebook instance
- |
-Notebook
- |
-change_instance_status
- |
-
-
-
-
-
Key Operations Recorded for Training Jobs
-
-
Table 3 Key operations that can be audited in a training jobOperation
- |
-Resource Type
- |
-Trace Name
- |
-
|---|
-
-Creating a training job
- |
-ModelArtsTrainJob
- |
-createModelArtsTrainJob
- |
-
-Creating a version of a training job
- |
-ModelArtsTrainJob
- |
-createModelArtsTrainVersion
- |
-
-Stopping a training job
- |
-ModelArtsTrainJob
- |
-stopModelArtsTrainVersion
- |
-
-Modifying the description of a training job
- |
-ModelArtsTrainJob
- |
-updateModelArtsTrainDesc
- |
-
-Deleting a training job version
- |
-ModelArtsTrainJob
- |
-deleteModelArtsTrainVersion
- |
-
-Deleting a training job
- |
-ModelArtsTrainJob
- |
-deleteModelArtsTrainJob
- |
-
-Creating a training job configuration
- |
-ModelArtsTrainConfig
- |
-createModelArtsTrainConfig
- |
-
-Modifying a training job configuration
- |
-ModelArtsTrainConfig
- |
-updateModelArtsTrainConfig
- |
-
-Deleting a training job configuration
- |
-ModelArtsTrainConfig
- |
-deleteModelArtsTrainConfig
- |
-
-Creating a visualization job
- |
-ModelArtsTensorboardJob
- |
-createModelArtsTensorboardJob
- |
-
-Deleting a visualization job
- |
-ModelArtsTensorboardJob
- |
-deleteModelArtsTensorboardJob
- |
-
-Modifying the description of a visualization job
- |
-ModelArtsTensorboardJob
- |
-updateModelArtsTensorboardDesc
- |
-
-Stopping a visualization job
- |
-ModelArtsTensorboardJob
- |
-stopModelArtsTensorboardJob
- |
-
-Restarting a visualization job
- |
-ModelArtsTensorboardJob
- |
-restartModelArtsgTensorboardJob
- |
-
-
-
-
-
Key Operations Recorded for AI Application Management
-
-
Table 4 Key operations that can be audited for AI application managementOperation
- |
-Resource Type
- |
-Trace Name
- |
-
|---|
-
-Creating an AI Application
- |
-model
- |
-addModel
- |
-
-Updating an AI application
- |
-model
- |
-updateModel
- |
-
-Deleting an AI application
- |
-model
- |
-deleteModel
- |
-
-Adding a model conversion task
- |
-convert
- |
-addConvert
- |
-
-Updating a model conversion task
- |
-convert
- |
-updateConvert
- |
-
-Deleting a model conversion task
- |
-convert
- |
-deleteConvert
- |
-
-
-
-
-
Key Operations Recorded for Service Management
-
-
Table 5 Key operations that can be audited for service managementOperation
- |
-Resource Type
- |
-Trace Name
- |
-
|---|
-
-Deploying a model as a service
- |
-service
- |
-addService
- |
-
-Deleting a service
- |
-service
- |
-deleteService
- |
-
-Updating a service
- |
-service
- |
-updateService
- |
-
-Starting/stopping a service
- |
-service
- |
-startOrStopService
- |
-
-Adding an access key
- |
-service
- |
-addAkSk
- |
-
-Deleting an access key
- |
-service
- |
-deleteAkSk
- |
-
-Creating a dedicated resource pool
- |
-cluster
- |
-createCluster
- |
-
-Deleting a dedicated resource pool
- |
-cluster
- |
-deleteCluster
- |
-
-Adding a node to a dedicated resource pool
- |
-cluster
- |
-addClusterNode
- |
-
-Deleting a node from a dedicated resource pool
- |
-cluster
- |
-deleteClusterNode
- |
-
-Getting a result from the dedicated resource pool creation
- |
-cluster
- |
-createClusterResult
- |
-
-
-
-
-
-
-
diff --git a/docs/cts/umn/en-us_image_0000001186930850.png b/docs/cts/umn/en-us_image_0000001186930850.png
new file mode 100644
index 00000000..582b1618
Binary files /dev/null and b/docs/cts/umn/en-us_image_0000001186930850.png differ
diff --git a/docs/cts/umn/en-us_image_0000001187249376.png b/docs/cts/umn/en-us_image_0000001187249376.png
new file mode 100644
index 00000000..582b1618
Binary files /dev/null and b/docs/cts/umn/en-us_image_0000001187249376.png differ
diff --git a/docs/cts/umn/en-us_image_0000001187470664.png b/docs/cts/umn/en-us_image_0000001187470664.png
new file mode 100644
index 00000000..582b1618
Binary files /dev/null and b/docs/cts/umn/en-us_image_0000001187470664.png differ
diff --git a/docs/cts/umn/en-us_image_0000001187630634.png b/docs/cts/umn/en-us_image_0000001187630634.png
new file mode 100644
index 00000000..582b1618
Binary files /dev/null and b/docs/cts/umn/en-us_image_0000001187630634.png differ
diff --git a/docs/cts/umn/en-us_image_0000001187789198.png b/docs/cts/umn/en-us_image_0000001187789198.png
new file mode 100644
index 00000000..582b1618
Binary files /dev/null and b/docs/cts/umn/en-us_image_0000001187789198.png differ
diff --git a/docs/cts/umn/en-us_image_0000001187949118.png b/docs/cts/umn/en-us_image_0000001187949118.png
new file mode 100644
index 00000000..582b1618
Binary files /dev/null and b/docs/cts/umn/en-us_image_0000001187949118.png differ
diff --git a/docs/cts/umn/en-us_image_0000001231522936.png b/docs/cts/umn/en-us_image_0000001231522936.png
new file mode 100644
index 00000000..359a8e20
Binary files /dev/null and b/docs/cts/umn/en-us_image_0000001231522936.png differ
diff --git a/docs/cts/umn/en-us_image_0000001232728809.png b/docs/cts/umn/en-us_image_0000001232728809.png
new file mode 100644
index 00000000..582b1618
Binary files /dev/null and b/docs/cts/umn/en-us_image_0000001232728809.png differ
diff --git a/docs/cts/umn/en-us_image_0000001232728979.png b/docs/cts/umn/en-us_image_0000001232728979.png
new file mode 100644
index 00000000..582b1618
Binary files /dev/null and b/docs/cts/umn/en-us_image_0000001232728979.png differ
diff --git a/docs/cts/umn/en-us_image_0000001232870297.png b/docs/cts/umn/en-us_image_0000001232870297.png
new file mode 100644
index 00000000..582b1618
Binary files /dev/null and b/docs/cts/umn/en-us_image_0000001232870297.png differ
diff --git a/docs/cts/umn/en-us_image_0000001232950241.png b/docs/cts/umn/en-us_image_0000001232950241.png
new file mode 100644
index 00000000..582b1618
Binary files /dev/null and b/docs/cts/umn/en-us_image_0000001232950241.png differ
diff --git a/docs/cts/umn/en-us_image_0000001251736595.png b/docs/cts/umn/en-us_image_0000001251736595.png
new file mode 100644
index 00000000..41123ac5
Binary files /dev/null and b/docs/cts/umn/en-us_image_0000001251736595.png differ
diff --git a/docs/cts/umn/en-us_image_0000001366287882.png b/docs/cts/umn/en-us_image_0000001366287882.png
new file mode 100644
index 00000000..582b1618
Binary files /dev/null and b/docs/cts/umn/en-us_image_0000001366287882.png differ
diff --git a/docs/cts/umn/en-us_image_0000001366607830.png b/docs/cts/umn/en-us_image_0000001366607830.png
new file mode 100644
index 00000000..582b1618
Binary files /dev/null and b/docs/cts/umn/en-us_image_0000001366607830.png differ
diff --git a/docs/cts/umn/en-us_image_0000001381965089.jpg b/docs/cts/umn/en-us_image_0000001381965089.jpg
deleted file mode 100644
index b8e79a0e..00000000
Binary files a/docs/cts/umn/en-us_image_0000001381965089.jpg and /dev/null differ
diff --git a/docs/cts/umn/en-us_image_0237950263.png b/docs/cts/umn/en-us_image_0000001410476944.png
similarity index 100%
rename from docs/cts/umn/en-us_image_0237950263.png
rename to docs/cts/umn/en-us_image_0000001410476944.png
diff --git a/docs/cts/umn/en-us_image_0000001410575694.png b/docs/cts/umn/en-us_image_0000001410575694.png
new file mode 100644
index 00000000..c988aba1
Binary files /dev/null and b/docs/cts/umn/en-us_image_0000001410575694.png differ
diff --git a/docs/cts/umn/en-us_image_0000001417089185.png b/docs/cts/umn/en-us_image_0000001417089185.png
new file mode 100644
index 00000000..582b1618
Binary files /dev/null and b/docs/cts/umn/en-us_image_0000001417089185.png differ
diff --git a/docs/cts/umn/en-us_image_0000001417288029.png b/docs/cts/umn/en-us_image_0000001417288029.png
new file mode 100644
index 00000000..582b1618
Binary files /dev/null and b/docs/cts/umn/en-us_image_0000001417288029.png differ
diff --git a/docs/cts/umn/en-us_image_0000001460694917.png b/docs/cts/umn/en-us_image_0000001460694917.png
new file mode 100644
index 00000000..e4fcbfa9
Binary files /dev/null and b/docs/cts/umn/en-us_image_0000001460694917.png differ
diff --git a/docs/cts/umn/en-us_image_0237950267.png b/docs/cts/umn/en-us_image_0000001467612717.png
similarity index 100%
rename from docs/cts/umn/en-us_image_0237950267.png
rename to docs/cts/umn/en-us_image_0000001467612717.png
diff --git a/docs/cts/umn/en-us_image_0000001525454037.png b/docs/cts/umn/en-us_image_0000001525454037.png
new file mode 100644
index 00000000..26b6def9
Binary files /dev/null and b/docs/cts/umn/en-us_image_0000001525454037.png differ
diff --git a/docs/cts/umn/en-us_image_0168422564.png b/docs/cts/umn/en-us_image_0168422564.png
deleted file mode 100644
index f1403c1d..00000000
Binary files a/docs/cts/umn/en-us_image_0168422564.png and /dev/null differ
diff --git a/docs/cts/umn/en-us_image_0179639495.png b/docs/cts/umn/en-us_image_0179639495.png
new file mode 100644
index 00000000..2ff31567
Binary files /dev/null and b/docs/cts/umn/en-us_image_0179639495.png differ
diff --git a/docs/cts/umn/en-us_image_0179639581.jpg b/docs/cts/umn/en-us_image_0179639581.jpg
new file mode 100644
index 00000000..fac6892b
Binary files /dev/null and b/docs/cts/umn/en-us_image_0179639581.jpg differ
diff --git a/docs/cts/umn/en-us_image_0179741594.png b/docs/cts/umn/en-us_image_0179741594.png
new file mode 100644
index 00000000..5f0e5bb1
Binary files /dev/null and b/docs/cts/umn/en-us_image_0179741594.png differ
diff --git a/docs/cts/umn/en-us_image_0179741687.png b/docs/cts/umn/en-us_image_0179741687.png
new file mode 100644
index 00000000..3c358d85
Binary files /dev/null and b/docs/cts/umn/en-us_image_0179741687.png differ
diff --git a/docs/cts/umn/en-us_image_0237950264.png b/docs/cts/umn/en-us_image_0237950264.png
deleted file mode 100644
index 67163576..00000000
Binary files a/docs/cts/umn/en-us_image_0237950264.png and /dev/null differ
diff --git a/docs/cts/umn/en-us_image_0237950265.png b/docs/cts/umn/en-us_image_0237950265.png
deleted file mode 100644
index 19ed01d9..00000000
Binary files a/docs/cts/umn/en-us_image_0237950265.png and /dev/null differ
diff --git a/docs/cts/umn/en-us_image_0237950266.png b/docs/cts/umn/en-us_image_0237950266.png
deleted file mode 100644
index f1403c1d..00000000
Binary files a/docs/cts/umn/en-us_image_0237950266.png and /dev/null differ
diff --git a/docs/cts/umn/en-us_image_0237964513.png b/docs/cts/umn/en-us_image_0237964513.png
deleted file mode 100644
index f1403c1d..00000000
Binary files a/docs/cts/umn/en-us_image_0237964513.png and /dev/null differ
diff --git a/docs/cts/umn/en-us_image_0237964518.png b/docs/cts/umn/en-us_image_0237964518.png
deleted file mode 100644
index f1403c1d..00000000
Binary files a/docs/cts/umn/en-us_image_0237964518.png and /dev/null differ
diff --git a/docs/cts/umn/en-us_image_0238416168.png b/docs/cts/umn/en-us_image_0238416168.png
deleted file mode 100644
index ae6bdb3d..00000000
Binary files a/docs/cts/umn/en-us_image_0238416168.png and /dev/null differ
diff --git a/docs/cts/umn/en-us_image_0295789897.png b/docs/cts/umn/en-us_image_0295789897.png
new file mode 100644
index 00000000..0ab7bc82
Binary files /dev/null and b/docs/cts/umn/en-us_image_0295789897.png differ
diff --git a/docs/cts/umn/en-us_image_0296237505.png b/docs/cts/umn/en-us_image_0296237505.png
new file mode 100644
index 00000000..3c358d85
Binary files /dev/null and b/docs/cts/umn/en-us_image_0296237505.png differ
diff --git a/docs/cts/umn/en-us_topic_0000001317721642.html b/docs/cts/umn/en-us_topic_0000001317721642.html
deleted file mode 100644
index a7a281eb..00000000
--- a/docs/cts/umn/en-us_topic_0000001317721642.html
+++ /dev/null
@@ -1,122 +0,0 @@
-
-
-
Key Operations on CBR
-
Cloud Backup and Recovery (CBR) backup for Elastic Volume Service (EVS), Elastic Cloud Server (ECS), and Bare Metal Server (BMS), ensuring data security and correctness as well as service security.
-
With CTS, you can record operations associated with CBR for later query, audit, and backtracking.
-
-
Table 1 CBR operations that can be recorded by CTSOperation
- |
-Resource Type
- |
-Trace Name
- |
-
|---|
-
-Creating a policy
- |
-policy
- |
-createPolicy
- |
-
-Updating a policy
- |
-policy
- |
-updatePolicy
- |
-
-Deleting a policy
- |
-policy
- |
-deletePolicy
- |
-
-Setting a vault policy
- |
-vault
- |
-associatePolicy
- |
-
-Removing a policy from a vault
- |
-vault
- |
-dissociatePolicy
- |
-
-Creating a vault
- |
-vault
- |
-createVault
- |
-
-Modifying a vault
- |
-vault
- |
-updateVault
- |
-
-Deleting a vault
- |
-vault
- |
-deleteVault
- |
-
-Removing resources
- |
-vault
- |
-removeResources
- |
-
-Adding resources
- |
-vault
- |
-addResources
- |
-
-Performing a backup
- |
-vault
- |
-createVaultBackup
- |
-
-Creating a backup
- |
-backup
- |
-createBackup
- |
-
-Deleting a backup
- |
-backup
- |
-deleteBackup
- |
-
-Restoring a backup
- |
-backup
- |
-restoreBackup
- |
-
-
-
-
-
-
-
diff --git a/docs/cts/umn/en-us_topic_0000001410799284.html b/docs/cts/umn/en-us_topic_0000001410799284.html
new file mode 100644
index 00000000..b7540fdf
--- /dev/null
+++ b/docs/cts/umn/en-us_topic_0000001410799284.html
@@ -0,0 +1,41 @@
+
+
+
FAQs
+
+
+
diff --git a/docs/cts/umn/en-us_topic_0030579718.html b/docs/cts/umn/en-us_topic_0030579718.html
index b5c0816b..088906da 100644
--- a/docs/cts/umn/en-us_topic_0030579718.html
+++ b/docs/cts/umn/en-us_topic_0030579718.html
@@ -1,16 +1,20 @@
-
Overview
-
+
Service Overview
+
diff --git a/docs/cts/umn/en-us_topic_0030581457.html b/docs/cts/umn/en-us_topic_0030581457.html
index 38cfd523..61481658 100644
--- a/docs/cts/umn/en-us_topic_0030581457.html
+++ b/docs/cts/umn/en-us_topic_0030581457.html
@@ -1,16 +1,20 @@
-
Getting Started
-
+
+
Getting Started
+
+
+
diff --git a/docs/cts/umn/en-us_topic_0030581459.html b/docs/cts/umn/en-us_topic_0030581459.html
deleted file mode 100644
index a1ef3b58..00000000
--- a/docs/cts/umn/en-us_topic_0030581459.html
+++ /dev/null
@@ -1,13 +0,0 @@
-
-
-
Trace References
-
-
-
diff --git a/docs/cts/umn/en-us_topic_0030594187.html b/docs/cts/umn/en-us_topic_0030594187.html
index 3e14ae4c..e5b7187e 100644
--- a/docs/cts/umn/en-us_topic_0030594187.html
+++ b/docs/cts/umn/en-us_topic_0030594187.html
@@ -1,14 +1,22 @@
-
CTS
-
Log audit is core to information security audit. It is an essential part of security risk control for information systems in enterprises and public sectors. As more information systems are migrating to the cloud, standards on information security have been released around the globe, such as ISO/IEC 27000, GB/T 20945-2013, ITIL, and NIST SP 800.
-
Cloud Trace Service (CTS) is a log audit service for cloud security. It allows you to collect, store, and query resource operation records. You can use these records to perform security analysis, track resource changes, audit compliance, and locate faults.
-
CTS provides the following functions:
- Operation recording: CTS records action taken on the console, API calls, and system-triggered actions.
- Trace query: You can query traces of the last seven days on the CTS console by multiple filters, such as trace source, resource type, operator, and trace status.
- Trace transfer: traces can be transferred to Object Storage Service (OBS) buckets periodically. During transfer, traces are compressed into trace files by service.
+
What Is Cloud Trace Service
+
The log audit module is a core component necessary for information security audit and an important part for the information systems of enterprises and public institutions to provide security risk management and control.
+
Cloud Trace Service (CTS) is a log audit service for security. It allows you to collect, store, and query resource operation records. You can use these records to perform security analysis, track resource changes, audit compliance, and locate faults.
+
Figure 1 CTS service diagram
+
CTS provides the following functions:
- Trace recording: CTS records operations performed on the management console or by calling APIs, as well as operations triggered by each interconnected service.
- Trace query: Operation records of the last seven days can be queried on the management console from multiple dimensions, such as the trace type, trace source, resource type, filter, operator and trace status.
- Trace transfer: Traces are transferred to Object Storage Service (OBS) buckets on a regular basis for long-term storage. In this process, traces are compressed into trace files by service.
+
+
\ No newline at end of file
diff --git a/docs/cts/umn/en-us_topic_0030598498.html b/docs/cts/umn/en-us_topic_0030598498.html
index b95bd1f8..6874e9ff 100644
--- a/docs/cts/umn/en-us_topic_0030598498.html
+++ b/docs/cts/umn/en-us_topic_0030598498.html
@@ -1,46 +1,36 @@
-
Enabling CTS
-
Scenarios
You need to enable CTS before using it. A tracker is automatically created when CTS is enabled. All traces recorded by CTS are associated with the tracker. Currently, only one tracker is available in a project for a tenant.
-
Trace files must be stored in OBS buckets. Therefore, before enabling CTS, you must enable OBS and have full permissions of the OBS bucket you are going to use. By default, only the owner who has enabled OBS can access OBS buckets and all objects contained, but the owner can grant permissions to other services and users by configuring an access policy.
-
A tracker created in a multi-project scenario can only track resources under the current project. If tracking cloud resources under another project is required, you need to create a tracker under the project.
-
This section describes how to enable CTS.
+
Basic Concepts
+
Trackers
When you enable CTS for the first time, a management tracker named system is created automatically.
+
Th management tracker identifies and associates with all cloud services your tenant account is using, and records all operations of your tenant account.
+
Currently, only one tracker can be created for each tenant.
-
Prerequisites
You have created an OBS bucket and have the required permissions.
+
Traces
Traces are operation logs of cloud service resources and are captured and stored by CTS. You can view traces to get to know details of operations performed on specific resources.
+
Traces: management traces reported by cloud services.
-
Procedure
- Log in to the management console.
- Click
in the upper left corner to select the desired project. - Click Service List and choose Management & Deployment > Cloud Trace Service.
- Click Tracker in the left navigation pane.
- Click Enable CTS.
- Click Configure in the Operation column to set OBS Bucket and File Prefix. Table 1 lists the parameters.
-
Table 1 Parameter descriptionParameter
- |
-Description
- |
-Example Value
- |
-
|---|
-
-OBS Bucket
- |
-Name of the OBS bucket in which trace files are to be stored.
- |
-bucket-001
- |
-
-File Prefix
- |
-Used for identifying the trace files stored in the OBS bucket. This parameter is optional. The value can contain 0 to 64 characters. Only letters, numbers, hyphens (-), underscores (_), and periods (.) are supported. If a tracker is created, a value will be generated automatically in the same way as you specify the value manually.
- |
-None
- |
-
-
-
+
Trace List
The trace list displays traces generated in the last seven days. These traces record operations (in the last hour by default) on cloud service resources, including creation, modification, and deletion, but do not record query operations.
+
- Management traces: record details about creating, modifying, and deleting cloud service resources in your tenant account.
-
- Click OK.
-
After CTS is enabled, you can view details of the created tracker on the Tracker page.
+
Trace Files
A trace file is a collection of traces. CTS generates trace files based on services and transfer cycle and send these files to your specified OBS bucket in real time. In most cases, all traces of a service generated in a transfer cycle are compressed into one trace file. However, if there are a large number of traces, CTS will adjust the number of traces contained in each trace file.
+
Traces files are in JSON format. Figure 1 shows an example of a trace file.
+
Figure 1 Trace file example
+
+
Verifying Trace File Integrity
The authenticity of operation records during a security incident investigation is often affected by trace files being deleted or tampered with. The records therefore cannot be used as an effective basis for investigation. Therefore, CTS provides trace file integrity verification to help you ensure the authenticity of trace files.
+
The verification function for trace file integrity adopts industry standard algorithms and generates a Hash value for each trace file. This Hash value changes when the trace file is modified or deleted. Therefore, by tracking the Hash value, you can confirm whether the trace file is modified. In addition, the RSA algorithm is used to sign on the digest file to ensure that the file is not modified. In this way, any operations of modifying or deleting trace files are recorded by CTS.
+
After the verification function for trace file integrity is enabled, CTS generates a digest file for Hash values of all trace files recorded in the past hour and synchronizes the digest file to an OBS bucket configured for the current tracker.
+
CTS signs on each digest file using public and private keys. You can verify the digest file using the public key after the file is stored to the OBS bucket.
Querying Traces on the CTS Console
-Scenarios
When you enable CTS, the system starts recording operations on cloud resources. Operation records of the last seven days are stored on the CTS console.
-
This section describes how to query or export operation records of the last seven days on the CTS console.
+
Querying Real-Time Traces
+
Scenarios
After CTS is enabled, the tracker starts recording operations on cloud resources. CTS stores operation records for the last seven days.
+
This section describes how to query operation records of the last seven days on the CTS console.
-
Procedure
- Log in to the management console.
- Click in the upper left corner to select the desired project.
- Click Service List and choose Management & Deployment > Cloud Trace Service.
- Choose Trace List in the navigation pane on the left.
- Set filters to search for desired traces. The following filters are available:
- Trace Source, Resource Type, and Search By.
Select the desired content from the drop-down lists one by one.
-When you select Trace name for Search By, you need to select a trace name.
-When you select Resource ID for Search By, you need to enter a resource ID.
-When you select Resource name, you also need to select or enter a resource name.
-
Options are available in the Search By drop-down list only when Trace Source and Resource Type are specified.
-
- Operator: Select a user.
- Trace Status: Select All trace statuses, normal, warning, or incident.
- In the upper right corner, choose Last 1 hour, Last 1 day, or Last 1 week, or specify a custom time range.
- - On the right of the filter box, click Export. CTS exports a CSV file listing query results.
- Click
on the left of the required trace to expand its details.Figure 1 Expanded trace details
-
- - Click View Trace in the Operation column. In the View Trace dialog box, the trace structure details are displayed.
Figure 2 Viewing a trace
-For details on key fields in traces, see Trace Structure and Example Traces.
+Procedure
- Log in to the management console.
- Click
in the upper left corner and choose Management & Deployment > Cloud Trace Service. The CTS console is displayed. - In the navigation pane on the left, choose Trace List.
- Set filters to search for your desired traces, as shown in Figure 1. The following filters are available:
Figure 1 Filters
+- Trace Source, Resource Type, and Search By
Select a filter from the drop-down list.
+If you select Resource ID for Search By, specify a resource ID.
+ - Operator: Select a user.
- Trace Status: Select All trace statuses, Normal, Warning, or Incident.
- Time range: You can query traces generated during any time range in the last few days.
+
- Click Export on the right to export all traces in the query result as a CSV file. The file can contain up to 5000 records.
- Click
on the left of a trace to expand its details.
+
+
+ - Click View Trace in the Operation column. The trace details are displayed.
+
+For details about key fields in the trace structure, see Trace Structure and Example Traces.
@@ -24,3 +24,10 @@
+
+
\ No newline at end of file
diff --git a/docs/cts/umn/en-us_topic_0030598500.html b/docs/cts/umn/en-us_topic_0030598500.html
deleted file mode 100644
index 9a416069..00000000
--- a/docs/cts/umn/en-us_topic_0030598500.html
+++ /dev/null
@@ -1,224 +0,0 @@
-
-
-
Trace Structure
-
Multiple key fields are included in CTS traces, as shown in Table 1.
-
- Formats of some fields displayed on the management console are optimized for easy understanding.
- This section describes the key fields of traces displayed on the management console.
-
-
-
Table 1 Key fields of tracesField
- |
-Mandatory
- |
-Type
- |
-Description
- |
-
|---|
-
-time
- |
-Yes
- |
-Date
- |
-The time when a trace occurred. The time is displayed in the local standard time (GMT+local time zone). In the API, this field is transmitted and stored in the timestamp format. The timestamp is the number of seconds elapsed since January 1, 1970 (midnight UTC/GMT), regardless of leap seconds.
-For example, 2022-08-19 18:46:33 GMT+02:00, is displayed as 1660927593570.
- |
-
-user
- |
-Yes
- |
-Structure
- |
-Cloud account used to perform the recorded operation.
-The value is also displayed in the Operator column on the Trace List page.
-This field is transmitted and stored in the API in the form of a string.
- |
-
-request
- |
-No
- |
-Structure
- |
-Requested operation.
-This field is transmitted and stored in the API in the form of a string.
- |
-
-response
- |
-No
- |
-Structure
- |
-Response to the request.
-This field is transmitted and stored in the API in the form of a string.
- |
-
-service_type
- |
-Yes
- |
-String
- |
-Operation source.
- |
-
-resource_type
- |
-Yes
- |
-String
- |
-Resource type.
- |
-
-resource_name
- |
-No
- |
-String
- |
-Resource name.
- |
-
-resource_id
- |
-No
- |
-String
- |
-Unique resource ID.
- |
-
-source_ip
- |
-Yes
- |
-String
- |
-IP address of the user that performed the operation.
-The value of this field is empty if the operation was triggered by system.
- |
-
-trace_name
- |
-Yes
- |
-String
- |
-Operation name.
- |
-
-trace_rating
- |
-Yes
- |
-String
- |
-Trace status. The value can be normal, warning, or incident.
- |
-
-trace_type
- |
-Yes
- |
-String
- |
-Operation type.
-There are three types of operations:
-- ConsoleAction: operations performed on the management console
- SystemAction: operations triggered by the system
- ApiCall: operations triggered by calling API Gateway
- |
-
-api_version
- |
-No
- |
-String
- |
-Version of the cloud service API which was called to perform the operation.
- |
-
-message
- |
-No
- |
-StructureString
- |
-Supplementary information.
- |
-
-record_time
- |
-Yes
- |
-Number
- |
-Time when the operation was recorded, in the form of a timestamp.
- |
-
-trace_id
- |
-Yes
- |
-String
- |
-Unique operation ID.
- |
-
-code
- |
-No
- |
-Number
- |
-HTTP return code, for example, 200 or 400.
- |
-
-request_id
- |
-No
- |
-String
- |
-ID of the recorded request.
- |
-
-location_info
- |
-No
- |
-String
- |
-Additional information required for fault locating after a request error.
- |
-
-endpoint
- |
-No
- |
-String
- |
-Endpoint of the page that displays details of cloud resources involved in this operation.
- |
-
-resource_url
- |
-No
- |
-String
- |
-Access link (excluding the endpoint) of the page that displays details of cloud resources involved in this operation.
- |
-
-
-
-
-
-
-
diff --git a/docs/cts/umn/en-us_topic_0030598636.html b/docs/cts/umn/en-us_topic_0030598636.html
deleted file mode 100644
index be349235..00000000
--- a/docs/cts/umn/en-us_topic_0030598636.html
+++ /dev/null
@@ -1,28 +0,0 @@
-
-
-
Querying Archived Traces
-
Scenarios
CTS periodically compresses recorded traces into trace files and delivers them to OBS buckets. A trace file is a collection of traces. CTS generates trace files based on services and transfer periods. If there are a large number of traces, the system will adjust the number of traces contained in each trace file as needed.
-
This section describes how to obtain historical operation records from the trace files downloaded from OBS buckets.
-
-
Procedure
- Log in to the management console.
- Click in the upper left corner to select the desired project.
- Click Service List and choose Management & Deployment > Cloud Trace Service.
- Choose Tracker List in the left navigation pane.
- Click an OBS bucket name in the OBS Bucket column. You will be redirected to the bucket's details page on the OBS console.
Figure 1 Selecting an OBS bucket
-
- Select the target trace by choosing in sequence an OBS bucket, the CloudTraces directory, a region, a year, a month, a day, a tracker name, and a service directory. Click Download in the Operation column to download the trace file to the default path. To download the trace file to a customized path, click More > Download As.
-
- The trace file naming format is as follows:
Trace file prefix_CloudTrace_Region/Region-project_Time when the trace file was uploaded to OBS: Year-Month-DayTHour-Minute-SecondZ_Character randomly generated.json.gz
-Example: File Prefix_CloudTrace_region_2016-05-30T16-20-56Z_21d36ced8c8af71e.json.gz
-
- The OBS bucket name and trace file prefix are customized and other parameters are automatically generated.
-
-For details on key fields in traces, see Trace Structure and Example Traces.
-Figure 2 Viewing a trace file
- - Decompress the downloaded package to obtain a JSON file with the same name as the package. Open the JSON file using a text file editor to view traces.
-
-
-
-
diff --git a/docs/cts/umn/en-us_topic_0030628003.html b/docs/cts/umn/en-us_topic_0030628003.html
index e378c2b0..e0941604 100644
--- a/docs/cts/umn/en-us_topic_0030628003.html
+++ b/docs/cts/umn/en-us_topic_0030628003.html
@@ -1,13 +1,22 @@
-
Managing a Tracker
-
A tracker is used to record management traces, which are logs of operations on all cloud resources, such as creation, login, and deletion. When you enable CTS, a tracker is created automatically.
-
+
User Guide
+
diff --git a/docs/cts/umn/en-us_topic_0030930181.html b/docs/cts/umn/en-us_topic_0030930181.html
deleted file mode 100644
index 5c0f51b0..00000000
--- a/docs/cts/umn/en-us_topic_0030930181.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
Disabling or Enabling a Tracker
-
Scenarios
This section describes how to disable or enable a tracker on the CTS console. After a tracker is disabled, it will stop recording operations, but you can still view operation records that have been collected.
-
This section describes how to disable or enable a tracker.
-
-
Prerequisites
You have created a tracker on the CTS console.
-
-
Procedure
- Log in to the management console.
- Click in the upper left corner to select the desired project.
- Click Service List and choose Management & Deployment > Cloud Trace Service.
- Click Tracker in the left navigation pane.
- Click Disable in the same row as the target tracker in the Operation column.
- Click Yes.
After the tracker is disabled, the Disable button changes to Enable. To enable the tracker, click Enable and then click Yes. The tracker will start recording operations again.
-
-
-
-
-
diff --git a/docs/cts/umn/en-us_topic_0030932518.html b/docs/cts/umn/en-us_topic_0030932518.html
deleted file mode 100644
index 7b22e9ce..00000000
--- a/docs/cts/umn/en-us_topic_0030932518.html
+++ /dev/null
@@ -1,39 +0,0 @@
-
-
-
FAQs
-
-
-
diff --git a/docs/cts/umn/en-us_topic_0043371376.html b/docs/cts/umn/en-us_topic_0043371376.html
deleted file mode 100644
index 43b76712..00000000
--- a/docs/cts/umn/en-us_topic_0043371376.html
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
Application Examples
-
-
-
diff --git a/docs/cts/umn/en-us_topic_0043371377.html b/docs/cts/umn/en-us_topic_0043371377.html
deleted file mode 100644
index 5d03deca..00000000
--- a/docs/cts/umn/en-us_topic_0043371377.html
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-
Security Auditing
-
Scenarios
You can query operation records matching specified conditions and check whether operations have been performed by authorized users for security analysis.
-
-
Prerequisites
You have enabled CTS and the tracker is running properly. For details on how to enable CTS, see Enabling CTS.
-
-
Procedure
The following shows how you can review records of EVS disk creation and deletion over the last two weeks.
-
- Log in to the management console as an administrator.
- Click
in the upper left corner to select the desired project. - Click Service List and choose Management & Deployment > Cloud Trace Service.
- Choose Trace List in the navigation pane on the left.
- Set filters in sequence: Trace Source > Resource Type > Search By > Operator > Trace Status. Then click Query to view the result.
Select evs for Trace Source, evs for Resource Type, Trace name for Search By, and select createVolume or deleteVolume. Then, click Query to search for all EVS creation or deletion operations of the last seven days.
-
- - Choose Tracker in the left navigation pane to obtain an OBS bucket name.
- Download traces older than seven days or all traces by following the instructions in Querying Archived Traces.
- In the downloaded file, locate required operation records by searching for keywords createVolume and deleteVolume.
- Check the traces obtained in steps 5 and 8 to see whether there are any unauthorized operations or operations that do not conform to security rules.
-
-
-
-
diff --git a/docs/cts/umn/en-us_topic_0043371378.html b/docs/cts/umn/en-us_topic_0043371378.html
deleted file mode 100644
index 14980347..00000000
--- a/docs/cts/umn/en-us_topic_0043371378.html
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-
Resource Tracking
-
Scenarios
You can view operation records of a cloud resource throughout its lifecycle.
-
-
Prerequisites
You have enabled CTS and the tracker is running properly. For details on how to enable CTS, see Enabling CTS.
-
-
Procedure
The following takes the records of all operations on an ECS as an example.
-
- Log in to the management console as an administrator.
- Click in the upper left corner to select the desired project.
- Click Service List and choose Management & Deployment > Cloud Trace Service.
- Choose Trace List in the navigation pane on the left.
- Set filters in sequence: Trace Source > Resource Type > Search By. Then click Query to view the result.
Select ecs for Trace Source, ecs for Resource Type, Resource ID for Search By, and enter the ID of the VM. Click Query to obtain the traces generated in the last seven days.
-
- - Choose Tracker in the left navigation pane to obtain an OBS bucket name.
- Download traces older than seven days or all traces by following the instructions in Querying Archived Traces.
- Check all the traces obtained in steps 5 and 7.
-
-
-
-
diff --git a/docs/cts/umn/en-us_topic_0043371379.html b/docs/cts/umn/en-us_topic_0043371379.html
deleted file mode 100644
index d8d36634..00000000
--- a/docs/cts/umn/en-us_topic_0043371379.html
+++ /dev/null
@@ -1,21 +0,0 @@
-
-
-
Fault Locating
-
Scenarios
If a resource or an action encounters an exception, you can query operation records for the resource or action in a specified time period and view the requests and responses to facilitate troubleshooting.
-
-
Prerequisites
You have enabled CTS and the tracker is running properly. For details on how to enable CTS, see Enabling CTS.
-
-
Procedure
To locate an ECS fault which occurred in the morning:
-
- Log in to the management console as an administrator.
- Click
in the upper left corner to select the desired project. - Click Service List and choose Management & Deployment > Cloud Trace Service.
- Choose Trace List in the navigation pane on the left.
- Set filters in sequence: Trace Source > Resource Type > Search By. Then click Query to view the result.
Select ecs for Trace Source, ecs for Resource Type, and Resource ID for Search By. Enter the ID of the faulty virtual machine (VM), and select a time range from 06:00:00 to 12:00:00 on the day when the fault occurred in the upper right corner. Then click Query.
-
- - Check the returned traces, especially the request type and response of each trace. Note any traces whose status is warning or incident, and any traces whose response indicates a failure.
-
To locate a fault after an ECS server failed to be created:
- Log in to the management console as an administrator.
- Click in the upper left corner to select the desired project.
- Click Service List and choose Management & Deployment > Cloud Trace Service.
- Choose Trace List in the navigation pane on the left.
- Select esc for Trace Source, ecs for Resource Type, and warning for Trace Status. In the returned traces, locate the trace named createSingleServer.
- Check the trace details and locate the fault based on the error code or error message.
-
-
-
-
-
diff --git a/docs/cts/umn/en-us_topic_0043877274.html b/docs/cts/umn/en-us_topic_0043877274.html
deleted file mode 100644
index 062f16a7..00000000
--- a/docs/cts/umn/en-us_topic_0043877274.html
+++ /dev/null
@@ -1,27 +0,0 @@
-
-
-
Concepts
-
-
-
diff --git a/docs/cts/umn/en-us_topic_0043877275.html b/docs/cts/umn/en-us_topic_0043877275.html
deleted file mode 100644
index f2079118..00000000
--- a/docs/cts/umn/en-us_topic_0043877275.html
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
Tracker
-
Before using CTS, you need to enable it. A tracker will be created automatically when CTS is enabled. The tracker will identify and associate with all cloud services used, and record all operations on the cloud services.
-
-
-
diff --git a/docs/cts/umn/en-us_topic_0043877276.html b/docs/cts/umn/en-us_topic_0043877276.html
deleted file mode 100644
index 3a56106e..00000000
--- a/docs/cts/umn/en-us_topic_0043877276.html
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
Trace
-
Traces, also referred to as management traces, are operation records of cloud services tracked by CTS. You can view traces to check what operations were performed, who started the operations, and what resources were involved.
-
-
-
diff --git a/docs/cts/umn/en-us_topic_0043877277.html b/docs/cts/umn/en-us_topic_0043877277.html
deleted file mode 100644
index 257a3593..00000000
--- a/docs/cts/umn/en-us_topic_0043877277.html
+++ /dev/null
@@ -1,11 +0,0 @@
-
-
-
Trace List
-
The trace list displays traces generated in the last seven days. You can view the trace list to check details of operations on cloud service resources, including creation, modification, and deletion.
-
-
-
diff --git a/docs/cts/umn/en-us_topic_0043877298.html b/docs/cts/umn/en-us_topic_0043877298.html
deleted file mode 100644
index 4c02c16b..00000000
--- a/docs/cts/umn/en-us_topic_0043877298.html
+++ /dev/null
@@ -1,13 +0,0 @@
-
-
-
Trace File
-
A trace file is a collection of traces and is in JSON format. CTS generates trace files based on services and transfer periods. Then the trace files are transferred to specified OBS buckets.
-
Generally, all traces generated by a service during a transfer period are compressed into a trace file. However, if there are a large number of traces, the system will adjust the number of traces contained in each trace file as needed.
-
Trace files can be obtained only from OBS. For details about how to obtain, see Querying Archived Traces. For details about key fields in traces, see Trace Structure.
-
-
-
diff --git a/docs/cts/umn/en-us_topic_0043877299.html b/docs/cts/umn/en-us_topic_0043877299.html
deleted file mode 100644
index 783445e7..00000000
--- a/docs/cts/umn/en-us_topic_0043877299.html
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-
Working Principle
-
CTS directly connects to other cloud services, records operations on the cloud resources and the results, and stores these records in the form of trace files to OBS buckets in real time.
-
Before enabling CTS, you need to create an OBS bucket. When CTS is enabled, a tracker is created automatically. The tracker will generate trace files and send them to your specified OBS bucket.
-
The following operations can be performed on trace files:
-
- Trace file creation and storage
- When operations, such as addition, deletion, and modification, are performed on the services connected with CTS, the services will record the operations in specified formats and send the records to CTS. Such services include Elastic Cloud Server (ECS), Elastic Volume Service (EVS), and Image Management Service (IMS).
- CTS keeps the operation records for seven days, and periodically delivers the records to your specified OBS buckets for long-term storage.
-
-
- Trace file query
- You can query operation records in the last seven days on the Trace List page by time and other filters.
- To check operation records older than seven days, download trace files from OBS buckets.
- You can enable, disable, delete, or modify a tracker on the Tracker page on the CTS console.
-Let's use image creation as an example to show how CTS works. If you create an image in IMS, IMS will report a trace that records the operation to CTS. You can then view the trace on the CTS console. For long-term storage, CTS will transfer the trace to an OBS bucket.
-Figure 1 CTS working principle
-
-
-
-
diff --git a/docs/cts/umn/en-us_topic_0043877300.html b/docs/cts/umn/en-us_topic_0043877300.html
deleted file mode 100644
index dd0dff94..00000000
--- a/docs/cts/umn/en-us_topic_0043877300.html
+++ /dev/null
@@ -1,20 +0,0 @@
-
-
-
Application Scenarios
-
CTS is used in the following scenarios:
-
- Compliance audit
CTS tracks operations and allows you to query the records. This is essential for organizations, especially financial and payment enterprises, to obtain certifications such as PCI DSS and COSO certificate.
- - Data Value Mining
CTS allows you to mine data in audit logs to provide support for service health analysis, risk analysis, resource tracking, and cost analysis. In addition, you can obtain audit data from CTS and explore data value yourself.
-An audit log contains 19 fields, including time, operator, operation device IP address, operated resource, operation details, and other information. Each audit log is worth mining.
-CTS allows you to synchronize audit logs to your own system for analysis by configuring HTTP or HTTPS notifications. CTS has been interconnected with Cloud Eye and Log Tank Service (LTS) to help you track high-risk operations, analyze unauthorized operations, and check resource usage. The interconnection also provides data for analysis of service health and costs. For details on Cloud Eye, see Cloud Eye User Guide.
- - Key Event Notifications
CTS works with FunctionGraph to send notifications to natural persons or service APIs when any key operation is performed. The following are some usage examples:
-- CTS allows you to configure HTTP or HTTPS notifications targeted at your independent audit systems and synchronize audit logs received by CTS to these audit systems for auditing.
- CTS allows you to select a type of log as a trigger (such as file upload) in FunctionGraph to trigger a preset workflow (such as file format conversion). This simplifies service deployment and O&M, avoiding problems and risks.
- - Fault Locating and Analysis
If a fault occurs when you use cloud services, you can use filters to quickly search for unusual operations, and send the related traces to customer service or O&M engineers to handle the issue. This accelerates troubleshooting and reduces manpower requirements.
-You can search by filters such as trace source, resource type, operator, and trace status. Each trace contains the request and response of an operation.
-
-
-
-
diff --git a/docs/cts/umn/en-us_topic_0044019595.html b/docs/cts/umn/en-us_topic_0044019595.html
deleted file mode 100644
index f5aab7cd..00000000
--- a/docs/cts/umn/en-us_topic_0044019595.html
+++ /dev/null
@@ -1,66 +0,0 @@
-
-
-
Example Traces
-
This section provides two example traces and describes their key fields to help you better understand traces. You can read other traces in a similar way as shown below.
-
For details on the fields in a trace, see Trace Structure.
-
ECS Server Creation
{
- "time": "12/01/2016 11:07:28 GMT+08:00",
- "user": {
- "name": "aaa/op_service",
- "id": "f2fe9fac63414a35a7d03108d5f1ea73",
- "domain": {
- "name": "aaa",
- "id": "1f9b9ba51f6b4061bd5c1736b28469f8"
- }
- },
- "request": "{\"server\":{\"name\":\"as-config-15f1_XWO68TFC\",\"imageRef\":\"b2b2c7dc-bbb0-4d6b-81dd-f0904023d54f\",\"flavorRef\":\"m1.tiny\",\"personality\":[],\"vpcid\":\"e4c374b9-3675-482c-9b81-4acd59745c2b\",\"nics\":[{\"subnet_id\":\"fff89132-88d4-4e5b-9e27-d9001167d24f\",\"nictype\":null,\"ip_address\":null,\"binding:profile\":null,\"extra_dhcp_opts\":null}],\"adminPass\":\"********\",\"count\":1,\"metadata\":{\"op_svc_userid\":\"26e96eda18034ae9a44130bacb967b96\"},\"availability_zone\":\"az1.dc1\",\"root_volume\":{\"volumetype\":\"SATA\",\"extendparam\":{\"resourceSpecCode\":\"SATA\"},\"size\":40},\"data_volumes\":[],\"security_groups\":[{\"id\":\"dd597fd7-d119-4994-a22c-891fcfc54be1\"}],\"key_name\":\"KeyPair-3e51\"}}",
- "response": "{\"status\":\"SUCCESS\",\"entities\":{\"server_id\":\"42d39b4a-19b7-4ee2-b01b-a9f1353b4c54\"},\"job_id\":\"4010b39d58b855980158b8574b270018\",\"job_type\":\"createSingleServer\",\"begin_time\":\"2016-12-01T03:04:38.437Z\",\"end_time\":\"2016-12-01T03:07:26.871Z\",\"error_code\":null,\"fail_reason\":null}",
- "service_type": "ECS",
- "resource_type": "ecs",
- "resource_name": "as-config-15f1_XWO68TFC",
- "resource_id": "42d39b4a-19b7-4ee2-b01b-a9f1353b4c54",
- "source_ip": "",
- "trace_name": "createSingleServer",
- "trace_status": "normal",
- "trace_type": "SystemAction",
- "api_version": "1.0",
- "record_time": "12/01/2016 11:07:28 GMT+08:00",
- "trace_id": "4abc3a67-b773-11e6-8412-8f0ed3cc97c6"
-}
-
Note the following fields:
-
- time indicates the time when the trace occurred. In this example, the time is 11:07:28 on December 1.
- user indicates the user who performed the operation. In this example, the user (name field) is displayed under the enterprise account aaa (domain field).
- request indicates the request to create an ECS server. It contains basic information about the server, such as its name (as-config-15f1_XWO68TFC) and ID (e4c374b9-3675-482c-9b81-4acd59745c2b).
- response indicates the response to the ECS creation request. It contains status (SUCCESS in this example), error_code (null in this example), and fail_reason (null in this example).
-
-
EVS Disk Creation
{
- "time": "12/01/2016 11:24:04 GMT+08:00",
- "user": {
- "name": "aaa",
- "id": "26e96eda18034ae9a44130bacb967b96",
- "domain": {
- "name": "aaa",
- "id": "1f9b9ba51f6b4061bd5c1736b28469f8"
- }
- },
- "request": "{\"volumes\":[{\"id\":\"49b52508-7cd1-4642-ade5-dfecb853c8a0\"},{\"id\":\"8aa423db-052b-4ecf-a748-53eab02d4cf0\"},{\"id\":\"4b1ee16f-a469-47eb-9433-4fac2a2f959a\"},{\"id\":\"edc7f193-8fd8-44b3-812b-63cb57fd7932\"},{\"id\":\"4094a2c3-9d62-4a24-bb2e-0f417d27834a\"}]}",,
- "response": "{\"job_id\":\"ff808082814cc2ee01828d0a608067c7\",\"job_type\":\"deleteVolume\",\"begin_time\":\"2022-08-11T13:14:03.775Z\",\"end_time\":\"2022-08-11T13:14:07.458Z\",\"status\":\"SUCCESS\",\"error_code\":null,\"fail_reason\":null,\"entities\":{\"volume_type\":\"SAS\",\"volume_id\":\"edc7f193-8fd8-44b3-812b-63cb57fd7932\",\"size\":10,\"name\":\"volume-8631-lxrtest-0002\"}}",
- "service_type": "EVS",
- "resource_type": "evs",
- "resource_name": "volume-39bc",
- "resource_id": "229142c0-2c2e-4f01-a1b4-2dfdf1c678c7",
- "source_ip": "10.146.230.124",
- "trace_name": "deleteVolume",
- "trace_status": "normal",
- "trace_type": "ConsoleAction",
- "api_version": "1.0",
- "record_time": "1660223647458765184",
- "trace_id": "c529254f-bcf5-11e6-a89a-7fc778a6c92c"
-}
-
Note the following fields:
-
- time indicates the time when the trace occurred. In this example, the time is 11:24:04 on December 1.
- user indicates the user who performed the operation. In this example, the user (name field) is displayed under the enterprise account aaa (domain field).
- request is optional. It is null in this example.
- response is optional. It is null in this example.
- trace_status indicates the trace status. This field can replace the response field to indicate the operation results. In this example, the value is normal, indicating that the operation was successful according to Trace Structure.
-
-
-
-
diff --git a/docs/cts/umn/en-us_topic_0045053541.html b/docs/cts/umn/en-us_topic_0045053541.html
index 74273f65..9e857124 100644
--- a/docs/cts/umn/en-us_topic_0045053541.html
+++ b/docs/cts/umn/en-us_topic_0045053541.html
@@ -1,180 +1,204 @@
Change History
-
-
Released On
+
+ Table 1 Released On
|
-Description
+ | Description
|
|---|
-2022-10-30
+ | 2023-09-01
|
-This release incorporates the following changes:
-
+ | Incorporated the following changes:
+Optimized Configuring Key Event Notifications.
|
-2020-04-30
+ | 2023-03-30
|
-This release incorporates the following change:
-Modified parameters on the Configure Tracker page in Configuring a Tracker.
+ | Incorporated the following changes:
+
|
-2020-03-19
+ | 2023-02-08
|
-This release incorporates the following change:
-Added the description of the region and global filter conditions in Querying Traces on the CTS Console.
+ | Incorporated the following changes:
+
|
-2019-08-27
+ | 2022-10-30
|
-This release incorporates the following change:
-Added Key Operations on SWR.
+ | Incorporated the following changes:
+- Updated the parameters and descriptions in Table 1.
- Updated supported services and operations.
|
-2019-05-15
+ | 2021-03-15
|
-This release incorporates the following changes:
-
+ | Incorporated the following changes:
+Resolved issues found in the UAT testing.
|
-2019-04-30
+ | 2020-04-30
|
-This release incorporates the following changes:
-
+ | Incorporated the following changes:
+Modified parameters on the Configure Tracker page in Configuring a Tracker.
|
-2019-03-30
+ | 2020-03-19
|
-This release incorporates the following changes:
-
+ | Incorporated the following changes:
+Added the description of the region and global filter conditions in Querying Real-Time Traces.
|
-2019-01-30
+ | 2019-08-27
|
-This release incorporates the following changes:
-- Interconnected with CSS.
- Interconnected with WAF.
+ | Incorporated the following change:
+Added key operations on SWR.
|
-2018-12-05
+ | 2019-05-15
|
-This release incorporates the following change:
+ | Incorporated the following changes:
+- Modified key operations on DCS.
- Modified key operations on VPC.
+ |
+
+2019-04-30
+ |
+Incorporated the following changes:
+- Modified trace names of key operations on ELB.
- Modified resource types of key operations on DC.
- Modified trace names of key operations on DeH.
+ |
+
+2019-03-30
+ |
+Incorporated the following changes:
+- Updated restrictions on notification rules and operation types in Configuring Key Event Notifications.
- Added the data tracker function on the page of key operations on OBS.
- Modified key operations on VPC.
+ |
+
+2019-01-30
+ |
+Incorporated the following changes:
+- Interconnected with Cloud Search Service (CSS).
- Interconnected with Web Application Firewall (WAF).
+ |
+
+2018-12-05
+ |
+Incorporated the following changes:
Added the log description about how to create an OBS bucket as follows:
-
+
|
-2018-11-12
+ | 2018-11-12
|
-This release incorporates the following change:
-Interconnected with SDRS.
+ | Incorporated the following changes:
+Interconnected with Storage Disaster Recovery Service (SDRS).
|
-2018-08-30
+ | 2018-08-30
|
-This release incorporates the following change:
+ | Incorporated the following changes:
Supported exporting traces received in the last seven days in CSV format.
|
-2018-06-28
+ | 2018-06-28
|
-This release incorporates the following change:
+ | Incorporated the following changes:
Accepted in OTC 3.1
|
-2018-05-30
+ | 2018-05-30
|
-This release incorporates the following changes:
-
+ | Incorporated the following changes:
+
|
-2018-05-21
+ | 2018-05-21
|
-This release incorporates the following change:
-Added an FAQ "What Are the Meanings of Trace Statuses normal, warning, and incident?"
+ | Incorporated the following changes:
+Added FAQ "What Are the Meanings of Trace Statuses normal, warning, and incident?"
|
-2018-04-25
+ | 2018-04-25
|
-This release incorporates the following change:
+ | Incorporated the following changes:
Interconnected with OBS to support notifications for key operations of OBS.
|
-2018-03-09
+ | 2018-03-09
|
-This release incorporates the following change:
-Optimized Supported Services.
+ | Incorporated the following changes:
+Optimized supported services.
|
-2018-01-30
+ | 2018-01-30
|
-This release incorporates the following changes:
-- Added All for Key Event Notification, as well as function and configuration description in Configuring a Tracker.
- Interconnected with DESS.
+ | Incorporated the following changes:
+- Added All for Key Event Notification, as well as function and configuration description in Configuring a Tracker.
- Interconnected with Dedicated Enterprise Storage Service (DESS).
|
-2017-12-30
+ | 2017-12-30
|
-This release incorporates the following changes:
-- Added the Key Event Notification feature for the native OpenStack API.
- Interconnected with SFS.
- Added the description that only standard OBS buckets can be selected for transferring traces.
+ | Incorporated the following changes:
+- Added the Key Event Notification feature for the native OpenStack API.
- Interconnected with Scalable File Service (SFS).
- Added the description that only standard OBS buckets can be selected for transferring traces.
|
-2017-11-30
+ | 2017-11-30
|
-This release incorporates the following change:
-Added the "User Login" function under Key Event Notification.
+ | Incorporated the following changes:
+Added the "User Login" function under Key Event Notification.
|
-2017-08-30
+ | 2017-08-30
|
-This release incorporates the following changes:
-- Added Region.
- Added Project.
- Added the operations to select a region and project.
-
+ | Incorporated the following changes:
+- Added the operations to select a region and project.
+- Interconnected with Data Warehouse Service (DWS).
- Added description of the notification of key traces to Configuring a Tracker.
|
-2017-07-27
+ | 2017-07-27
|
-This release incorporates the following change:
+ | Incorporated the following changes:
Interconnected CTS with Object Storage Migration Service.
|
-2017-06-14
+ | 2017-06-14
|
-This release incorporates the following change:
-Added DeH.
+ | Incorporated the following changes:
+Added Dedicated Host (DeH).
|
-2017-03-30
+ | 2017-03-30
|
-This release incorporates the following change:
-Interconnected with RTS.
+ | Incorporated the following changes:
+Interconnected with Resource Template Service (RTS).
|
-2017-02-27
+ | 2017-02-27
|
-This release incorporates the following changes:
-
+ | Incorporated the following changes:
+
|
-2017-02-08
+ | 2017-02-08
|
-This release incorporates the following changes:
-
+ | Incorporated the following changes:
+
|
-2017-02-03
+ | 2017-02-03
|
-This release incorporates the following changes:
-- Added Why Do Some Operation Records Occur Twice in the Trace List? to provide a description of asynchronous operation scenarios.
- Added the description: The subscription information deletion operation in the topic deletion operation in the SMN service is not recorded by CTS.
- Modified the description in Enabling CTS to: The tracker records trace creation operations on cloud resources performed by the user.
- Modified descriptions of parameters user, request, and response in Trace Structure.
+ | Incorporated the following changes:
+- Added an FAQ "Why Do Some Operation Records Occur Twice in the Trace List?" to provide a description of the asynchronous operation scenarios.
- Added the description: The subscription information deletion operation in the topic deletion operation in the SMN service is not recorded by CTS.
- Modified the description in Enabling CTS to: The tracker records trace creation operations on cloud resources performed by the user.
- Modified descriptions of parameters user, request, and response in Trace Structure.
|
-2017-01-20
+ | 2017-01-20
|
-This release incorporates the following changes:
-- Interconnected with ELB, VBS, CCE, and MRS
- Added redirection to the resource page of the VBS and IMS console through the hyperlink in the Resource ID column on the Trace List page.
+ | Incorporated the following changes:
+- Interconnected with ELB, VBS, CCE, and MRS
- Added redirection to the resource page of the VBS and IMS console through the hyperlink in the Resource ID column on the Trace List page.
|
-2016-12-30
+ | 2016-12-30
|
-This issue is the first official release.
+ | This issue is the first official release.
|
diff --git a/docs/cts/umn/en-us_topic_0059288681.html b/docs/cts/umn/en-us_topic_0059288681.html
deleted file mode 100644
index 054b0470..00000000
--- a/docs/cts/umn/en-us_topic_0059288681.html
+++ /dev/null
@@ -1,29 +0,0 @@
-
-
-Configuring a Tracker
-ScenariosYou can configure parameters in the Transfer to OBS area for a created tracker on the Configure Tracker page.
- If you configure an OBS bucket for a tracker, CTS automatically attaches transferring policies to the OBS bucket so that trace files can be delivered to the OBS bucket for storage. File Prefix can be customized to mark trace files to be transferred. The specified prefix will be automatically added in front of the name of a transferred file, helping you quickly find required files. You must select a standard OBS bucket because CTS needs to frequently access the OBS bucket which traces are transferred to.
-
-
- After a tracker is configured, new rules take effect immediately.
- This section describes how to configure a tracker.
-
- PrerequisitesYou have enabled CTS.
-
- Procedure- Log in to the management console.
- Click in the upper left corner to select the desired project.
- Click Service List and choose Management & Deployment > Cloud Trace Service.
- Click Tracker in the left navigation pane.
- Click Configure in the same row as the target tracker in the Operation column.
- Set related parameters on the Configure Tracker page.
- Basic Information
- Tracker Name: The default value is system.
- Trace Analysis: Enable this function.
- Trace Analysis Path.
After trace analysis is enabled, traces will be synchronized to LTS.
-
-
- - Transfer to OBS
CTS allows you to store traces of the last seven days. You can also configure an OBS bucket to deliver traces to it for long-term storage.
-
-- OBS Bucket: Select an existing OBS bucket.
- File Prefix: The prefix is used to mark a transferred trace file. The specified prefix will be automatically added in front of the name of a transferred file, helping you quickly find required files.
-
- - Click OK.
After the tracker is configured, you can view its details on the Tracker page.
-
-
- Region
-A region refers to a geographic area where the server for installing CTS is located. Availability zones (AZs) in the same geographic area can communicate with each other through internal network.
- Cloud data centers are deployed in different regions around the world, such as the regions eu-de and eu-nl.
- Project
-A project is used to group and isolate resources, including computing, storage, and network resources. Multiple projects can be created by a tenant, and a project can be a department or a project team.
- Supported Services
-Once you enable CTS, the system automatically identifies cloud services enabled on the cloud platform, captures key operations on the services, and reports audit logs of these operations to CTS.
- Key operations triggered by calling IaaS OpenStack APIs are shown in Relationship Between Operations Triggered by IaaS OpenStack and Native OpenStack APIs.
- For details on key operations supported by CTS, see Supported Services and Operation Lists.
- Supported Services and Operation Lists
-
-
-
diff --git a/docs/cts/umn/en-us_topic_0100236046.html b/docs/cts/umn/en-us_topic_0100236046.html
deleted file mode 100644
index 5662f109..00000000
--- a/docs/cts/umn/en-us_topic_0100236046.html
+++ /dev/null
@@ -1,94 +0,0 @@
-
-
-Key Operations on ECS
-An ECS is a computing server that consists of CPUs, memory, images, and EVS disks and allows on-demand allocation and elastic scaling. ECS integrates VPC, virtual firewall, and multi-data-copy capabilities to build an efficient, reliable, and secure computing environment to ensure stable and continuous running of your services.
- With CTS, you can record operations associated with ECS for future query, audit, and backtrack operations.
-
- Table 1 ECS operations that can be recorded by CTSOperation
- |
-Resource Type
- |
-Trace Name
- |
-
|---|
-
-Starting an ECS
- |
-ecs
- |
-startServer
- |
-
-Restarting an ECS
- |
-ecs
- |
-rebootServer
- |
-
-Stopping an ECS
- |
-ecs
- |
-stopServer
- |
-
-Attaching a disk to an ECS (on the EVS console)
- |
-ecs
- |
-attachVolume2
- |
-
-Reinstalling the OS
- |
-ecs
- |
-reinstallOs
- |
-
-Changing the OS
- |
-ecs
- |
-changeOs
- |
-
-Modifying ECS specifications
- |
-ecs
- |
-resizeServer
- |
-
-Adding an automatic recovery tag to a VM
- |
-ecs
- |
-addAutoRecovery
- |
-
-Deleting an automatic recovery tag from a VM
- |
-ecs
- |
-deleteAutoRecovery
- |
-
-Creating a security group
- |
-ecs
- |
-createSecurityGroup
- |
-
-
-
-
- Key Operations on IMS
-IMS provides easy-to-use and self-service image management. You can use a public or private image to create an ECS. You can also create a private image using an existing ECS or an external image file.
- With CTS, you can record operations associated with IMS for future query, audit, and backtrack operations.
-
- Table 1 IMS operations that can be recorded by CTSOperation
- |
-Resource Type
- |
-Trace Name
- |
-
|---|
-
-Creating an image
- |
-ims
- |
-createImage
- |
-
-Updating an image
- |
-ims
- |
-updateImage
- |
-
-Deleting images in batches
- |
-ims
- |
-deleteImage
- |
-
-Copying an image
- |
-ims
- |
-copyImage
- |
-
-Exporting an image
- |
-ims
- |
-exportImage
- |
-
-Adding a member
- |
-ims
- |
-addMember
- |
-
-Updating members in batches
- |
-ims
- |
-updateMember
- |
-
-Deleting members in batches
- |
-ims
- |
-deleteMember
- |
-
-
-
-
- Key Operations on BMS
-A Bare Metal Server (BMS) is a physical server dedicated for individual tenants. It provides remarkable compute performance and stability for running key applications. The BMS service can be used in conjunction with other cloud services, such as Virtual Private Cloud (VPC), allowing you to enjoy the stable performance of server hosting and the high scalability of cloud resources together.
- With CTS, you can record operations associated with BMS for future query, audit, and backtrack operations.
-
- Table 1 BMS operations that can be recorded by CTSOperation
- |
-Resource Type
- |
-Trace Name
- |
-
|---|
-
-Creating a BMS
- |
-bms
- |
-createBareMetalServers
- |
-
-Deleting a BMS
- |
-bms
- |
-deleteBareMetalServers
- |
-
-Starting a BMS
- |
-bms
- |
-startBareMetalServers
- |
-
-Stopping a BMS
- |
-bms
- |
-stopBareMetalServers
- |
-
-Restarting a BMS
- |
-bms
- |
-rebootBareMetalServers
- |
-
-
-
-
- Key Operations on AS
-Auto Scaling (AS) is a service that automatically adjusts computing resources based on your requirements and configured AS policies to ensure proper service running.
- With CTS, you can record operations associated with AS for future query, audit, and backtrack operations.
-
- Table 1 AS operations that can be recorded by CTSOperation
- |
-Resource Type
- |
-Trace Name
- |
-
|---|
-
-Creating an AS group
- |
-scaling_group
- |
-createScalingGroup
- |
-
-Modifying an AS group
- |
-scaling_group
- |
-modifyScalingGroup
- |
-
-Deleting an AS group
- |
-scaling_group
- |
-deleteScalingGroup
- |
-
-Enabling an AS group
- |
-scaling_group
- |
-enableScalingGroup
- |
-
-Disabling an AS group
- |
-scaling_group
- |
-disableScalingGroup
- |
-
-Creating an AS configuration
- |
-scaling_configuration
- |
-createScalingConfiguration
- |
-
-Deleting an AS configuration
- |
-scaling_configuration
- |
-deleteScalingConfiguration
- |
-
-Batch deleting AS configurations
- |
-scaling_configuration
- |
-batchDeleteScalingConfiguration
- |
-
-Creating an AS policy
- |
-scaling_policy
- |
-createScalingPolicy
- |
-
-Modifying an AS policy
- |
-scaling_policy
- |
-modifyScalingPolicy
- |
-
-Deleting an AS policy
- |
-scaling_policy
- |
-deleteScalingPolicy
- |
-
-Enabling an AS policy
- |
-scaling_policy
- |
-enableScalingPolicy
- |
-
-Disabling an AS policy
- |
-scaling_policy
- |
-disableScalingPolicy
- |
-
-Executing an AS policy
- |
-scaling_policy
- |
-executeScalingPolicy
- |
-
-Removing an instance
- |
-scaling_instance
- |
-removeInstance
- |
-
-Batch removing instances from an AS group
- |
-scaling_instance
- |
-batchRemoveInstances
- |
-
-Batch adding instances to an AS group
- |
-scaling_instance
- |
-batchAddInstances
- |
-
-Batch enabling instance protection
- |
-scaling_instance
- |
-batchProtectInstances
- |
-
-Batch disabling instance protection
- |
-scaling_instance
- |
-batchUnprotectInstances
- |
-
-
-
-
- Key Operations on OBS
-OBS is a stable, secure, efficient, and easy-to-use cloud storage service. With the Representational State Transfer (REST) application programming interface (API), OBS is able to store any amount and form of unstructured data.
- With CTS, you can record operations associated with OBS for future query, audit, and backtrack operations.
- Table 1 OBS operations that can be recorded by CTSOperation
- |
-Resource Type
- |
-Trace Name
- |
-
|---|
-
-Deleting a bucket
- |
-bucket
- |
-deleteBucket
- |
-
-Deleting the bucket CORS configuration
- |
-bucket
- |
-deleteBucketCors
- |
-
-Deleting the custom domain configuration
- |
-bucket
- |
-deleteBucketCustomdomain
- |
-
-Deleting the bucket lifecycle configuration
- |
-bucket
- |
-deleteBucketLifecycle
- |
-
-Deleting the bucket policy configuration
- |
-bucket
- |
-deleteBucketPolicy
- |
-
-Deleting the bucket cross-region replication configuration
- |
-bucket
- |
-deleteBucketReplication
- |
-
-Deleting the bucket tagging configuration
- |
-bucket
- |
-deleteBucketTagging
- |
-
-Deleting the bucket website configuration
- |
-bucket
- |
-deleteBucketWebsite
- |
-
-Deleting bucket data
- |
-bucket
- |
-deleteBucketdata
- |
-
-Creating a bucket
- |
-bucket
- |
-createBucket
- |
-
-Setting the bucket ACL
- |
-bucket
- |
-setBucketAcl
- |
-
-Setting the bucket CORS
- |
-bucket
- |
-setBucketCors
- |
-
-Setting a custom domain name of a bucket
- |
-bucket
- |
-setBucketCustomdomain
- |
-
-Setting the bucket lifecycle
- |
-bucket
- |
-setBucketLifecycle
- |
-
-Setting the bucket logging
- |
-bucket
- |
-setBucketLogging
- |
-
-Setting the bucket notification
- |
-bucket
- |
-setBucketNotification
- |
-
-Setting the bucket policy
- |
-bucket
- |
-setBucketPolicy
- |
-
-Setting the bucket quota
- |
-bucket
- |
-setBucketQuota
- |
-
-Setting a cross-domain replication of a bucket
- |
-bucket
- |
-setBucketReplication
- |
-
-Setting the bucket storage class
- |
-bucket
- |
-setBucketStorageclass
- |
-
-Setting a bucket tag
- |
-bucket
- |
-setBucketTagging
- |
-
-Setting bucket versioning
- |
-bucket
- |
-setBucketVersioning
- |
-
-Setting a static domain name of a bucket
- |
-bucket
- |
-setBucketWebsite
- |
-
-
-
-
-
- Key Operations on CTS
-CTS provides records of operations on cloud service resources. With CTS, you can query, audit, and backtrack these operations.
- With CTS, you can record operations associated with CTS itself for future query, audit, and backtrack operations.
-
- Table 1 CTS operations that can be recorded by itselfOperation
- |
-Resource Type
- |
-Trace Name
- |
-
|---|
-
-Creating a tracker
- |
-tracker
- |
-createTracker
- |
-
-Modifying a tracker
- |
-tracker
- |
-updateTracker
- |
-
-Disabling a tracker
- |
-tracker
- |
-updateTracker
- |
-
-Enabling a tracker
- |
-tracker
- |
-updateTracker
- |
-
-Deleting a tracker
- |
-tracker
- |
-deleteTracker
- |
-
-Creating a key event notification
- |
-notification
- |
-createNotification
- |
-
-Deleting a key event notification
- |
-notification
- |
-deleteNotification
- |
-
-Modifying a key event notification
- |
-notification
- |
-updateNotification
- |
-
-Changing the status of a key event notification
- |
-notification
- |
-updateNotificationStatus
- |
-
-
-
-
- Key Operations on Cloud Eye
-Cloud Eye is an open monitoring platform. It provides monitoring, alarm reporting, and alarm notification for your resources in near-real time.
- With CTS, you can record operations associated with Cloud Eye for future query, audit, and backtrack operations.
-
- Table 1 Cloud Eye operations that can be recorded by CTSOperation
- |
-Resource Type
- |
-Trace Name
- |
-
|---|
-
-Creating an alarm rule
- |
-alarm_rule
- |
-createAlarmRule
- |
-
-Creating alarm rules in batches
- |
-alarm_rule
- |
-batchCreateAlarmRule
- |
-
-Deleting an alarm rule
- |
-alarm_rule
- |
-deleteAlarmRule
- |
-
-Disabling an alarm rule
- |
-alarm_rule
- |
-disableAlarmRule
- |
-
-Enabling an alarm rule
- |
-alarm_rule
- |
-enableAlarmRule
- |
-
-Modifying an alarm rule
- |
-alarm_rule
- |
-updateAlarmRule
- |
-
-Updating the alarm status to alarm
- |
-alarm_rule
- |
-alarmStatusChangeToAlarm
- |
-
-Updating the alarm status to insufficient data
- |
-alarm_rule
- |
-alarmStatusChangeToInsufficientData
- |
-
-Updating the alarm status to normal
- |
-alarm_rule
- |
-alarmStatusChangeToOk
- |
-
-Creating a custom alarm template
- |
-alarm_template
- |
-createAlarmTemplate
- |
-
-Deleting a custom alarm template
- |
-alarm_template
- |
-deleteAlarmTemplate
- |
-
-Modifying a custom alarm template
- |
-alarm_template
- |
-updateAlarmTemplate
- |
-
-Creating a monitoring panel
- |
-dashboard
- |
-createDashboard
- |
-
-Deleting a monitoring panel
- |
-dashboard
- |
-deleteDashboard
- |
-
-Modifying a monitoring panel
- |
-dashboard
- |
-updateDashboard
- |
-
-Adding monitoring data
- |
-metric
- |
-addMetricData
- |
-
-Exporting monitoring data
- |
-metric
- |
-downloadMetricsReport
- |
-
-
-
-
- Key Operations on IAM
-IAM enables you to centrally manage authentication information, including your authenticated email, phone number, and password. When you invoke an API to apply for an ECS, manage cloud resources, or log in to the cloud platform in multi-tenant mode, you can query the required project ID, AK/SK, and username in real time.
- With CTS, you can record operations associated with IAM for later query, audit, and backtracking.
-
- Table 1 IAM operations that can be recorded by CTSOperation
- |
-Resource Type
- |
-Trace Name
- |
-
|---|
-
-Creating a token
- |
-token
- |
-createTokenByPwd
- |
-
-Creating a token
- |
-token
- |
-createTokenByHwAccessKey
- |
-
-Creating a token
- |
-token
- |
-createTokenByToken
- |
-
-Creating a token
- |
-token
- |
-createTokenByAssumeRole
- |
-
-User login
- |
-user
- |
-login
- |
-
-Login failure
- |
-user
- |
-loginFailed
- |
-
-User logout
- |
-user
- |
-logout
- |
-
-Changing a user password
- |
-user
- |
-changePassword
- |
-
-Creating a user
- |
-user
- |
-createUser
- |
-
-Modifying user information
- |
-user
- |
-updateUser
- |
-
-Deleting a user
- |
-user
- |
-deleteUser
- |
-
-Changing a user password
- |
-user
- |
-updateUserPwd
- |
-
-Creating an AK/SK
- |
-user
- |
-addCredential
- |
-
-Deleting an AK/SK
- |
-user
- |
-deleteCredential
- |
-
-Changing an email address
- |
-user
- |
-modifyUserEmail
- |
-
-Changing a mobile phone number
- |
-user
- |
-modifyUserMobile
- |
-
-Changing a password
- |
-user
- |
-modifyUserPassword
- |
-
-Uploading a user picture
- |
-user
- |
-modifyUserPicture
- |
-
-Setting a password for a user (by the administrator)
- |
-user
- |
-setPasswordByAdmin
- |
-
-Creating a user group
- |
-userGroup
- |
-createUserGroup
- |
-
-Updating a user group
- |
-userGroup
- |
-updateUserGroup
- |
-
-Deleting a user group
- |
-userGroup
- |
-deleteUserGroup
- |
-
-Adding a user to a user group
- |
-userGroup
- |
-addUserToGroup
- |
-
-Deleting a user from a user group
- |
-userGroup
- |
-removeUserFromGroup
- |
-
-Creating a project
- |
-project
- |
-createProject
- |
-
-Changing a project
- |
-project
- |
-updateProject
- |
-
-Updating the project status
- |
-project
- |
-updateProjectStatus
- |
-
-Creating an agency
- |
-agency
- |
-createAgency
- |
-
-Modifying an agency
- |
-agency
- |
-updateAgency
- |
-
-Deleting an agency
- |
-agency
- |
-deleteAgency
- |
-
-Switching a role
- |
-user
- |
-switchRole
- |
-
-Registering an identity provider
- |
-identityProvider
- |
-createIdentityProvider
- |
-
-Modifying an identity provider
- |
-identityProvider
- |
-updateIdentityProvider
- |
-
-Deleting an identity provider
- |
-identityProvider
- |
-deleteIdentityProvider
- |
-
-Creating a mapping
- |
-mapping
- |
-createMapping
- |
-
-Updating a mapping
- |
-mapping
- |
-updateMapping
- |
-
-Deleting a mapping
- |
-mapping
- |
-deleteMapping
- |
-
-Creating a protocol
- |
-protocol
- |
-createProtocol
- |
-
-Changing a protocol
- |
-protocol
- |
-updateProtocol
- |
-
-Deleting a protocol
- |
-protocol
- |
-deleteProtocol
- |
-
-Granting permissions to a user group of a tenant
- |
-roleGroupDomain
- |
-assignRoleToGroupOnDomain
- |
-
-Deleting permissions of a specified user group of a tenant
- |
-roleGroupDomain
- |
-unassignRoleToGroupOnDomain
- |
-
-Assigning permissions to a user group corresponding to a project
- |
-roleGroupProject
- |
-assignRoleToGroupOnProject
- |
-
-Revoking permissions from a user group corresponding to a project
- |
-roleGroupProject
- |
-unassignRoleToGroupOnProject
- |
-
-Updating the login authentication policy
- |
-domain
- |
-updateSecurityPolicies
- |
-
-Updating a password policy
- |
-domain
- |
-updatePasswordPolicies
- |
-
-Modifying an ACL policy
- |
-domain
- |
-updateACLPolicies
- |
-
-Binding a virtual MFA device
- |
-MFA
- |
-BindMFA
- |
-
-Unbinding a virtual MFA device
- |
-MFA
- |
-UnBindMFA
- |
-
-
-
-
- Key Operations on CCE
-Cloud Container Engine (CCE) is a high-performance, high-reliability service through which enterprises can manage containerized applications. CCE supports native Kubernetes applications and tools, allowing you to easily set up a container runtime environment on the cloud.
- With CTS, you can record operations associated with CCE for future query, audit, and backtrack operations.
-
- Table 1 CCE operations supported by CTSOperation
- |
-Resource Type
- |
-Event Name
- |
-
|---|
-
-Creating an agency
- |
-Cluster
- |
-createUserAgencies
- |
-
-Creating a cluster
- |
-Cluster
- |
-createCluster
- |
-
-Updating the description of a cluster
- |
-Cluster
- |
-updateCluster
- |
-
-Upgrading a cluster
- |
-Cluster
- |
-clusterUpgrade
- |
-
-Deleting a cluster
- |
-Cluster
- |
-claimCluster/deleteCluster
- |
-
-Downloading a cluster certificate
- |
-Cluster
- |
-getClusterCertByUID
- |
-
-Binding and unbinding an EIP
- |
-Cluster
- |
-operateMasterEIP
- |
-
-Waking up a cluster and resetting node management (V2)
- |
-Cluster
- |
-operateCluster
- |
-
-Hibernating a cluster (V3)
- |
-Cluster
- |
-hibernateCluster
- |
-
-Waking up a cluster (V3)
- |
-Cluster
- |
-awakeCluster
- |
-
-Changing the specifications of a cluster
- |
-Cluster
- |
-resizeCluster
- |
-
-Modifying configurations of a cluster
- |
-Cluster
- |
-updateConfiguration
- |
-
-Creating a node pool
- |
-Node pool
- |
-createNodePool
- |
-
-Updating a node pool
- |
-Node pool
- |
-updateNodePool
- |
-
-Deleting a node pool
- |
-Node pool
- |
-claimNodePool
- |
-
-Migrating a node pool
- |
-Node pool
- |
-migrateNodepool
- |
-
-Modifying node pool configurations
- |
-Node pool
- |
-updateConfiguration
- |
-
-Creating a node
- |
-Node
- |
-createNode
- |
-
-Deleting all the nodes from a specified cluster
- |
-Node
- |
-deleteAllHosts
- |
-
-Deleting a single node
- |
-Node
- |
-deleteOneHost/claimOneHost
- |
-
-Updating the description of a node
- |
-Node
- |
-updateNode
- |
-
-Creating an add-on instance
- |
-Add-on instance
- |
-createAddonInstance
- |
-
-Deleting an add-on instance
- |
-Add-on instance
- |
-deleteAddonInstance
- |
-
-Uploading a chart
- |
-Chart
- |
-uploadChart
- |
-
-Updating a chart
- |
-Chart
- |
-updateChart
- |
-
-Deleting a chart
- |
-Chart
- |
-deleteChart
- |
-
-Creating a release
- |
-Release
- |
-createRelease
- |
-
-Upgrading a release
- |
-Release
- |
-updateRelease
- |
-
-Deleting a release
- |
-Release
- |
-deleteRelease
- |
-
-Creating a ConfigMap
- |
-Kubernetes resource
- |
-createConfigmaps
- |
-
-Creating a DaemonSet
- |
-Kubernetes resource
- |
-createDaemonsets
- |
-
-Creating a Deployment
- |
-Kubernetes resource
- |
-createDeployments
- |
-
-Creating an event
- |
-Kubernetes resource
- |
-createEvents
- |
-
-Creating an Ingress
- |
-Kubernetes resource
- |
-createIngresses
- |
-
-Creating a job
- |
-Kubernetes resource
- |
-createJobs
- |
-
-Creating a namespace
- |
-Kubernetes resource
- |
-createNamespaces
- |
-
-Creating a node
- |
-Kubernetes resource
- |
-createNodes
- |
-
-Creating a PersistentVolumeClaim
- |
-Kubernetes resource
- |
-createPersistentvolumeclaims
- |
-
-Creating a pod
- |
-Kubernetes resource
- |
-createPods
- |
-
-Creating a replica set
- |
-Kubernetes resource
- |
-createReplicasets
- |
-
-Creating a resource quota
- |
-Kubernetes resource
- |
-createResourcequotas
- |
-
-Creating a secret
- |
-Kubernetes resource
- |
-createSecrets
- |
-
-Creating a service
- |
-Kubernetes resource
- |
-createServices
- |
-
-Creating a StatefulSet
- |
-Kubernetes resource
- |
-createStatefulsets
- |
-
-Creating a volume
- |
-Kubernetes resource
- |
-createVolumes
- |
-
-Deleting a ConfigMap
- |
-Kubernetes resource
- |
-deleteConfigmaps
- |
-
-Deleting a DaemonSet
- |
-Kubernetes resource
- |
-deleteDaemonsets
- |
-
-Deleting a Deployment
- |
-Kubernetes resource
- |
-deleteDeployments
- |
-
-Deleting an event
- |
-Kubernetes resource
- |
-deleteEvents
- |
-
-Deleting an Ingress
- |
-Kubernetes resource
- |
-deleteIngresses
- |
-
-Deleting a job
- |
-Kubernetes resource
- |
-deleteJobs
- |
-
-Deleting a namespace
- |
-Kubernetes resource
- |
-deleteNamespaces
- |
-
-Deleting a node
- |
-Kubernetes resource
- |
-deleteNodes
- |
-
-Deleting a Pod
- |
-Kubernetes resource
- |
-deletePods
- |
-
-Deleting a replica set
- |
-Kubernetes resource
- |
-deleteReplicasets
- |
-
-Deleting a resource quota
- |
-Kubernetes resource
- |
-deleteResourcequotas
- |
-
-Deleting a secret
- |
-Kubernetes resource
- |
-deleteSecrets
- |
-
-Deleting a service
- |
-Kubernetes resource
- |
-deleteServices
- |
-
-Deleting a StatefulSet
- |
-Kubernetes resource
- |
-deleteStatefulsets
- |
-
-Deleting volumes
- |
-Kubernetes resource
- |
-deleteVolumes
- |
-
-Replacing a specified ConfigMap
- |
-Kubernetes resource
- |
-updateConfigmaps
- |
-
-Replacing a specified DaemonSet
- |
-Kubernetes resource
- |
-updateDaemonsets
- |
-
-Replacing a specified Deployment
- |
-Kubernetes resource
- |
-updateDeployments
- |
-
-Replacing a specified event
- |
-Kubernetes resource
- |
-updateEvents
- |
-
-Replacing a specified ingress
- |
-Kubernetes resource
- |
-updateIngresses
- |
-
-Replacing a specified job
- |
-Kubernetes resource
- |
-updateJobs
- |
-
-Replacing a specified namespace
- |
-Kubernetes resource
- |
-updateNamespaces
- |
-
-Replacing a specified node
- |
-Kubernetes resource
- |
-updateNodes
- |
-
-Replacing a specified PersistentVolumeClaim
- |
-Kubernetes resource
- |
-updatePersistentvolumeclaims
- |
-
-Replacing a specified pod
- |
-Kubernetes resource
- |
-updatePods
- |
-
-Replacing a specified replica set
- |
-Kubernetes resource
- |
-updateReplicasets
- |
-
-Replacing a specified resource quota
- |
-Kubernetes resource
- |
-updateResourcequotas
- |
-
-Replacing a specified secret
- |
-Kubernetes resource
- |
-updateSecrets
- |
-
-Replacing a specified service
- |
-Kubernetes resource
- |
-updateServices
- |
-
-Replacing a specified StatefulSet
- |
-Kubernetes resource
- |
-updateStatefulsets
- |
-
-Replacing the specified status
- |
-Kubernetes resource
- |
-updateStatus
- |
-
-Uploading a chart
- |
-Kubernetes resource
- |
-uploadChart
- |
-
-Updating a component template
- |
-Kubernetes resource
- |
-updateChart
- |
-
-Deleting a chart
- |
-Kubernetes resource
- |
-deleteChart
- |
-
-Creating a template application
- |
-Kubernetes resource
- |
-createRelease
- |
-
-Updating a template application
- |
-Kubernetes resource
- |
-updateRelease
- |
-
-Deleting a template application
- |
-Kubernetes resource
- |
-deleteRelease
- |
-
-
-
-
- Key Operations on VPC
-VPC enables you to provision logically isolated, configurable, and manageable virtual networks for ECSs, improving the security of resources in enterprise clouds and simplifying network deployment.
- With CTS, you can record operations associated with VPC for future query, audit, and backtrack operations.
-
- Table 1 VPC operations that can be recorded by CTSOperation
- |
-Resource Type
- |
-Trace Name
- |
-
|---|
-
-Modifying the bandwidth
- |
-bandwidth
- |
-modifyBandwidth
- |
-
-Creating an EIP
- |
-eip
- |
-createEip
- |
-
-Releasing an EIP
- |
-eip
- |
-deleteEip
- |
-
-Binding an EIP
- |
-eip
- |
-bindEip
- |
-
-Unbinding an EIP
- |
-eip
- |
-unbindEip
- |
-
-Assigning a private IP address
- |
-privateIps
- |
-createPrivateIp
- |
-
-Releasing a private IP address
- |
-privateIps
- |
-deletePrivateIp
- |
-
-Creating a security group
- |
-security_group
- |
-createSecurityGroup
- |
-
-Modifying a security group
- |
-security_group
- |
-modifySecurityGroup
- |
-
-Creating a subnet
- |
-subnet
- |
-createSubnet
- |
-
-Deleting a subnet
- |
-subnet
- |
-deleteSubnet
- |
-
-Modifying a subnet
- |
-subnet
- |
-modifySubnet
- |
-
-Creating a VPC
- |
-vpc
- |
-createVpc
- |
-
-Deleting a VPC
- |
-vpc
- |
-deleteVpc
- |
-
-Modifying a VPC
- |
-vpc
- |
-modifyVpc
- |
-
-Creating a VPN
- |
-vpn
- |
-createVpn
- |
-
-Deleting a VPN
- |
-vpn
- |
-deleteVpn
- |
-
-Modifying a VPN
- |
-vpn
- |
-modifyVpn
- |
-
-Creating a NAT gateway
- |
-natgateway
- |
-createNatGateway
- |
-
-Updating a NAT gateway
- |
-natgateway
- |
-updateNatGateway
- |
-
-Deleting a NAT gateway
- |
-natgateway
- |
-deleteNatGateway
- |
-
-Creating an SNAT rule
- |
-snatrule
- |
-createSnatRule
- |
-
-Deleting an SNAT rule
- |
-snatrule
- |
-deleteSnatRule
- |
-
-Creating a DNAT rule
- |
-dnatrule
- |
-createDnatRule
- |
-
-Deleting a DNAT rule
- |
-dnatrule
- |
-deleteDnatRule
- |
-
-
-
-
- Key Operations on DC
-Direct Connect (DC) allows you to establish a private, dedicated network connection from your data center, office, or collocation environment to the cloud platform. It reduces your network latency and provides a more consistent network experience than Internet-based connections.
- With CTS, you can record operations associated with DC for later query, audit, and backtracking.
-
- Table 1 DC operations that can be recorded by CTSOperation
- |
-Resource Type
- |
-Trace Name
- |
-
|---|
-
-Modifying a direct connection
- |
-dcaasConnection
- |
-modifyConnection
- |
-
-
-
-
- Key Operations on ELB
-Elastic Load Balancing (ELB) is a service that automatically distributes access traffic to multiple ECSs to balance their service load. ELB enables you to achieve higher levels of fault tolerance in your applications and expand application service capabilities.
- With a web-based console, you can create load balancers, configure the ports required for listening, and add backend ECSs for load balancers. ELB helps eliminate single points of failure (SPOFs), improving availability of the whole system.
- With CTS, you can record operations associated with ELB for future query, audit, and backtrack operations.
-
- Table 1 ELB operations that can be recorded by CTSOperation
- |
-Resource Type
- |
-Trace Name
- |
-
|---|
-
-Creating a certificate
- |
-certificate
- |
-createCertificate
- |
-
-Updating a certificate
- |
-certificate
- |
-updateCertificate
- |
-
-Deleting a certificate
- |
-certificate
- |
-deleteCertificate
- |
-
-Creating a health check
- |
-healthmonitor
- |
-createHealthMonitor
- |
-
-Updating a health check
- |
-healthmonitor
- |
-updateHealthMonitor
- |
-
-Deleting a health check
- |
-healthmonitor
- |
-deleteHealthMonitor
- |
-
-Creating a forwarding policy
- |
-l7policy
- |
-createL7policy
- |
-
-Updating a forwarding policy
- |
-l7policy
- |
-updateL7policy
- |
-
-Deleting a forwarding policy
- |
-l7policy
- |
-deleteL7policy
- |
-
-Creating a forwarding rule
- |
-l7rule
- |
-createl7rule
- |
-
-Updating a forwarding rule
- |
-l7rule
- |
-updateL7rule
- |
-
-Deleting a forwarding rule
- |
-l7rule
- |
-deleteL7rule
- |
-
-Creating a listener
- |
-listener
- |
-createListener
- |
-
-Updating a listener
- |
-listener
- |
-updateListener
- |
-
-Deleting a listener
- |
-listener
- |
-deleteListener
- |
-
-Creating a load balancer
- |
-loadbalancer
- |
-createLoadbalancer
- |
-
-Updating a load balancer
- |
-loadbalancer
- |
-updateLoadbalancer
- |
-
-Deleting a load balancer
- |
-loadbalancer
- |
-deleteLoadbalancer
- |
-
-Adding a backend ECS
- |
-member
- |
-createMember
- |
-
-Updating a backend ECS
- |
-member
- |
-updateMember
- |
-
-Removing a backend ECS
- |
-member
- |
-batchUpdateMember
- |
-
-Creating a backend server group
- |
-pool
- |
-createPool
- |
-
-Updating a backend server group
- |
-pool
- |
-updatPool
- |
-
-Deleting a backend server group
- |
-pool
- |
-deletePool
- |
-
-
-
-
- Key Operations on DNS
-Domain Name Service (DNS) provides highly available and scalable authoritative DNS services and domain name management services. It translates domain names or application resources into IP addresses required for network connection. By doing so, visitors' access requests are directed to the desired resources.
- With CTS, you can record operations associated with DNS for future query, audit, and backtrack operations.
- DNS operations that can be recorded by CTS are listed in Table 1 and Table 2.
-
- Table 1 DNS operations that can be recorded by CTS (global level)Operation
- |
-Resource Type
- |
-Trace Name
- |
-
|---|
-
-Creating a record set in a public zone
- |
-publicRecordSet
- |
-createPublicRecordSet
- |
-
-Deleting a record set in a public zone
- |
-publicRecordSet
- |
-deletePublicRecordSet
- |
-
-Modifying a record set in a public zone
- |
-publicRecordSet
- |
-updatePublicRecordSet
- |
-
-Creating a public zone
- |
-publicZone
- |
-createPublicZone
- |
-
-Modifying a public zone
- |
-publicZone
- |
-updatePublicZone
- |
-
-Deleting a public zone
- |
-publicZone
- |
-deletePublicZone
- |
-
-Adding tags to a public zone
- |
-publicZoneTag
- |
-createPublicZoneTag
- |
-
-Deleting tags of a public zone
- |
-publicZoneTag
- |
-deletePublicZoneTag
- |
-
-Adding tags to a record set in a public zone
- |
-publicRecordSetTag
- |
-createPublicRecordSetTag
- |
-
-Deleting tags of a record set in a public zone
- |
-publicRecordSetTag
- |
-deletePublicRecordSetTag
- |
-
-Adding tags to a private zone
- |
-privateZoneTag
- |
-createPrivateZoneTag
- |
-
-Deleting tags of a private zone
- |
-privateZoneTag
- |
-deletePrivateZoneTag
- |
-
-Adding tags to a record set in a private zone
- |
-privateRecordSetTag
- |
-createPrivateRecordSetTag
- |
-
-Deleting tags of a record set in a private zone
- |
-privateRecordSetTag
- |
-deletePrivateRecordSetTag
- |
-
-Adding tags to a PTR record
- |
-ptrRecordTag
- |
-createPTRRecordSetTag
- |
-
-Deleting tags of a PTR record
- |
-ptrRecordTag
- |
-deletePTRRecordTag
- |
-
-
-
-
-
- Table 2 DNS operations that can be recorded by CTS (region level)Operation
- |
-Resource Type
- |
-Trace Name
- |
-
|---|
-
-Creating a private record set
- |
-privateRecordSet
- |
-createPrivateRecordSet
- |
-
-Deleting a private record set
- |
-privateRecordSet
- |
-deletePrivateRecordSet
- |
-
-Modifying a private record set
- |
-privateRecordSet
- |
-updatePrivateRecordSet
- |
-
-Creating a private zone
- |
-privateZone
- |
-createPrivateZone
- |
-
-Modifying a private zone
- |
-privateZone
- |
-updatePrivateZone
- |
-
-Deleting a private zone
- |
-privateZone
- |
-deletePrivateZone
- |
-
-Associating a VPC
- |
-privateZone
- |
-associateRouter
- |
-
-Disassociating a VPC
- |
-privateZone
- |
-disassociateRouter
- |
-
-Configuring a PTR record
- |
-ptrRecord
- |
-setPTRRecord
- |
-
-Unsetting a PTR record
- |
-ptrRecord
- |
-resetPTRRecord
- |
-
-
-
-
- Key Operations on EVS
-An EVS disk is a virtual block storage service that is based on distributed architecture and can elastically scale up and down. EVS disks can be operated online. Using them is similar to using common server hard disks. Compared with common server hard disks, EVS disks have higher data reliability and I/O throughput capabilities. They are also easier to use. EVS disks apply to file systems, databases, or system software or other applications that require block storage devices.
- With CTS, you can record operations associated with EVS for future query, audit, and backtrack operations.
- Table 1 EVS operations that can be recorded by CTSOperation
- |
-Resource Type
- |
-Trace Name
- |
-
|---|
-
-Creating an EVS disk
- |
-evs
- |
-createVolume
- |
-
-Updating an EVS disk
- |
-evs
- |
-updateVolume
- |
-
-Expanding an EVS disk
- |
-evs
- |
-extendVolume
- |
-
-Deleting an EVS disk
- |
-evs
- |
-deleteVolume
- |
-
-
-
-
-
- Key Operations on TMS
-Tag Management Service (TMS) is a visualized service for fast, unified tag management that enables you to control your resource permissions and billing more efficiently. It allows you to tag and categorize cloud services across regions, and it can be accessed through the TMS console or using APIs.
- With CTS, you can record operations associated with TMS for future query, audit, and backtrack operations.
-
- Table 1 TMS operations that can be recorded by CTSOperation
- |
-Resource Type
- |
-Trace Name
- |
-
|---|
-
-Adding a predefined tag
- |
-predefineTag
- |
-addPredefineTag
- |
-
-Deleting a predefined tag
- |
-predefineTag
- |
-deletePredefineTag
- |
-
-Modifying a predefined tag
- |
-predefineTag
- |
-modifyPredefineTag
- |
-
-Creating a resource tag
- |
-application
- |
-createResourceTag
- |
-
-Deleting a resource tag
- |
-application
- |
-deleteResourceTag
- |
-
-
-
-
- Key Operations on SMN
-Simple Message Notification (SMN) is a type of web service that a user can easily construct and maintain. SMN sends notifications from a cloud.
- With CTS, you can record operations associated with SMN for future query, audit, and backtrack operations.
- In SMN, deleting a topic will delete all subscription information associated with the topic, and the subscription information deletion operation will not be recorded by CTS.
-
-
- Table 1 SMN operations that can be recorded by CTSOperation
- |
-Resource Type
- |
-Trace Name
- |
-
|---|
-
-Creating a topic
- |
-topic
- |
-createTopic
- |
-
-Deleting a topic
- |
-topic
- |
-deleteTopic
- |
-
-Updating a topic
- |
-topic
- |
-updateTopic
- |
-
-Updating attributes of a topic
- |
-topic
- |
-updateTopicAttribute
- |
-
-Deleting all topic attributes
- |
-topic
- |
-deleteTopicAttributes
- |
-
-Deleting a specified topic attribute
- |
-topic
- |
-deleteTopicAttributeByName
- |
-
-Adding a subscription
- |
-subscription
- |
-subscribe
- |
-
-Deleting a subscription
- |
-subscription
- |
-unsubscribe
- |
-
-Creating a message template
- |
-message_template
- |
-createMessageTemplate
- |
-
-Creating message templates in batches
- |
-message_template
- |
-batchCreateMessageTemplate
- |
-
-Modifying a message template
- |
-message_template
- |
-updateMessageTemplate
- |
-
-Deleting a message template
- |
-message_template
- |
-deleteMessageTemplate
- |
-
-
-
-
- Key Operations on DMS
-Distributed Message Service (DMS) is a Kafka-based and high-performance message service that allows multi-user and concurrent access and message queue isolation.
- With CTS, you can record operations associated with DMS for future query, audit, and backtrack operations.
-
- Table 1 DMS operations that can be recorded by CTSOperation
- |
-Resource Type
- |
-Trace Name
- |
-
|---|
-
-Successfully deleting a background task
- |
-kafka
- |
-deleteDMSBackendJobSuccess
- |
-
-Failing to delete a background task
- |
-kafka
- |
-deleteDMSBackendJobFailure
- |
-
-Successfully creating an order for creating an instance
- |
-kafka
- |
-createDMSInstanceOrderSuccess
- |
-
-Failing to create an order for creating an instance
- |
-kafka
- |
-createDMSInstanceOrderFailure
- |
-
-Successfully submitting a request to modify an instance order
- |
-kafka
- |
-modifyDMSInstanceOrderSuccess
- |
-
-Failing to submit a request to modify an instance order
- |
-kafka
- |
-modifyDMSInstanceOrderFailure
- |
-
-Successfully submitting a request to scale up an instance
- |
-kafka
- |
-extendDMSInstanceSuccess
- |
-
-Failing to submit a request to scale up an instance
- |
-kafka
- |
-extendDMSInstanceFailure
- |
-
-Successfully submitting a request to reset instance password
- |
-kafka
- |
-resetDMSInstancePasswordSuccess
- |
-
-Failing to submit a request to reset instance password
- |
-kafka
- |
-resetDMSInstancePasswordFailure
- |
-
-Successfully creating a topic for a Kafka instance
- |
-kafka
- |
-Kafka_platinum_create_topicSuccess
- |
-
-Failing to create a topic for a Kafka instance
- |
-kafka
- |
-Kafka_platinum_create_topicFailure
- |
-
-Successfully deleting a topic from a Kafka instance
- |
-kafka
- |
-Kafka_platinum_delete_topicsSuccess
- |
-
-Failing to delete a topic for a Kafka instance
- |
-kafka
- |
-Kafka_platinum_delete_topicsFailure
- |
-
-Successfully deleting an instance that failed to be created
- |
-kafka
- |
-deleteDMSCreateFailureInstancesSuccess
- |
-
-Failing to delete an instance that failed to be created
- |
-kafka
- |
-deleteDMSCreateFailureInstancesFailure
- |
-
-Successfully submitting a request to restart an instance
- |
-kafka
- |
-restartDMSInstanceSuccess
- |
-
-Failing to submit a request to restart an instance
- |
-kafka
- |
-restartDMSInstanceFailure
- |
-
-Successfully submitting a request to delete multiple instances at a time
- |
-kafka
- |
-batchDeleteDMSInstanceSuccess
- |
-
-Failing to submit a request to delete multiple instances at a time
- |
-kafka
- |
-batchDeleteDMSInstanceFailure
- |
-
-Successfully submitting a request to restart multiple instances at a time
- |
-kafka
- |
-batchRestartDMSInstanceSuccess
- |
-
-Failing to submit a request to restart multiple instances at a time
- |
-kafka
- |
-batchRestartDMSInstanceFailure
- |
-
-Successfully submitting a request to modify instance information
- |
-kafka
- |
-modifyDMSInstanceInfoSuccess
- |
-
-Failing to submit a request to modify instance information
- |
-kafka
- |
-modifyDMSInstanceInfoFailure
- |
-
-Successfully deleting an instance
- |
-kafka
- |
-deleteDMSInstanceTaskSuccess
- |
-
-Failing to delete an instance
- |
-kafka
- |
-deleteDMSInstanceTaskFailure
- |
-
-Successfully creating an instance
- |
-kafka
- |
-createDMSInstanceTaskSuccess
- |
-
-Failing to create an instance
- |
-kafka
- |
-createDMSInstanceTaskFailure
- |
-
-Successfully scaling up an instance
- |
-kafka
- |
-extendDMSInstanceTaskSuccess
- |
-
-Failing to scale up an instance
- |
-kafka
- |
-extendDMSInstanceTaskFailure
- |
-
-Successfully restarting an instance
- |
-kafka
- |
-restartDMSInstanceTaskSuccess
- |
-
-Failing to restart an instance
- |
-kafka
- |
-restartDMSInstanceTaskFailure
- |
-
-Successfully restarting multiple instances at a time
- |
-kafka
- |
-batchRestartDMSInstanceTaskSuccess
- |
-
-Failing to restart multiple instances at a time
- |
-kafka
- |
-batchRestartDMSInstanceTaskFailure
- |
-
-Successfully modifying instance information
- |
-kafka
- |
-modifyDMSInstanceInfoTaskSuccess
- |
-
-Failing to modify instance information
- |
-kafka
- |
-modifyDMSInstanceInfoTaskFailure
- |
-
-
-
-
- Key Operations on KMS
-Key Management Service (KMS) is a secure and reliable key hosting service used to provide central management of users' masker keys.
- With CTS, you can record operations associated with KMS for later query, audit, and backtracking.
-
- Key Operations on Anti-DDoS
-Anti-DDoS is a network security service that defends IP addresses against distributed denial of service (DDoS) attacks.
- Anti-DDoS monitors traffic directed to specified IP addresses in real time and detects access traffic at network egresses to discover DDoS attacks as soon as possible. It then cleans abnormal traffic according to user-configured defense policies so that services run as normal. It also generates reports to present users with a clear evaluation of network security.
- With CTS, you can record operations associated with Anti-DDoS for future query, audit, and backtrack operations.
- Table 1 Anti-DDoS operations that can be recorded by CTSOperation
- |
-Resource Type
- |
-Trace Name
- |
-
|---|
-
-Enabling Anti-DDoS
- |
-anti-ddos
- |
-openAntiddos
- |
-
-Disabling Anti-DDoS
- |
-anti-ddos
- |
-deleteAntiddos
- |
-
-Updating Anti-DDoS
- |
-anti-ddos
- |
-updateAntiddos
- |
-
-
-
-
-
- Key Operations on WAF
-Web Application Firewall (WAF) is designed to keep web services stable and secure in combination with years of experience in security protection. It examines all HTTP and HTTPS requests to detect and block attacks such as Structure Query Language (SQL) injections, cross-site scripting (XSS), webshell upload, third-party vulnerability exploits, CC attacks, and malicious crawlers.
- With CTS, you can record operations associated with WAF for future query, audit, and backtrack operations.
-
- Table 1 WAF operations recorded by CTSOperation
- |
-Resource Type
- |
-Trace Name
- |
-
|---|
-
-Creating a WAF instance
- |
-instance
- |
-createInstance
- |
-
-Deleting a WAF instance
- |
-instance
- |
-deleteInstance
- |
-
-Modifying a WAF instance
- |
-instance
- |
-modifyInstance
- |
-
-Modifying the protection status of a WAF instance
- |
-instance
- |
-modifyProtectStatus
- |
-
-Modifying the connection status of a WAF instance
- |
-instance
- |
-modifyAccessStatus
- |
-
-Creating a policy
- |
-policy
- |
-createPolicy
- |
-
-Applying a policy
- |
-policy
- |
-applyToPolicy
- |
-
-Modifying a policy
- |
-policy
- |
-modifyPolicy
- |
-
-Deleting a policy
- |
-policy
- |
-deletePolicy
- |
-
-Modifying alarm notification settings
- |
-alertNoticeConfig
- |
-modifyAlertNoticeConfig
- |
-
-Creating a certificate
- |
-certificate
- |
-createCertificate
- |
-
-Changing the name of a certificate
- |
-certificate
- |
-modifyCertificate
- |
-
-Deleting a certificate
- |
-certificate
- |
-deleteCertificate
- |
-
-Creating a CC attack protection rule
- |
-policy
- |
-createCc
- |
-
-Modifying a CC attack protection rule
- |
-policy
- |
-modifyCc
- |
-
-Deleting a CC attack protection rule
- |
-policy
- |
-deleteCc
- |
-
-Creating a precise protection rule
- |
-policy
- |
-createCustom
- |
-
-Modifying a precise protection rule
- |
-policy
- |
-modifyCustom
- |
-
-Deleting a precise protection rule
- |
-policy
- |
-deleteCustom
- |
-
-Adding a blacklist or whitelist rule
- |
-policy
- |
-createWhiteblackip
- |
-
-Modifying a blacklist or whitelist rule
- |
-policy
- |
-modifyWhiteblackip
- |
-
-Deleting a blacklist or whitelist rule
- |
-policy
- |
-deleteWhiteblackip
- |
-
-Adding a web tamper protection rule
- |
-policy
- |
-createAntitamper
- |
-
-Updating a web tamper protection rule
- |
-policy
- |
-refreshAntitamper
- |
-
-Deleting a web tamper protection rule
- |
-policy
- |
-deleteAntitamper
- |
-
-Adding a false alarm masking rule
- |
-policy
- |
-createIgnore
- |
-
-Deleting a false alarm masking rule
- |
-policy
- |
-deleteIgnore
- |
-
-Creating a data masking rule
- |
-policy
- |
-createPrivacy
- |
-
-Modifying a data masking rule
- |
-policy
- |
-modifyPrivacy
- |
-
-Deleting a data masking rule
- |
-policy
- |
-deletePrivacy
- |
-
-
-
-
-
- Key Operations on DeH
-Dedicated Host (DeH) is a service that provides dedicated physical hosts. You can create ECSs on a DeH to enhance isolation, security, and performance of your ECSs. When you migrate services to a DeH, you can continue to use your server software licenses used before the migration. That is, you can use the Bring Your Own License (BYOL) feature on the DeH to reduce costs and independently manage your ECSs.
- With CTS, you can record operations associated with DeH for future query, audit, and backtrack operations.
-
- Table 1 DeH operations that can be recorded by CTSOperation
- |
-Resource Type
- |
-Trace Name
- |
-
|---|
-
-Creating a DeH
- |
-dedicatedHosts
- |
-createDedicatedHosts
- |
-
-Updating a DeH
- |
-dedicatedHosts
- |
-updateDedicatedHosts
- |
-
-Deleting a DeH
- |
-dedicatedHosts
- |
-releaseDedicatedHosts
- |
-
-
-
-
- Key Operations on DCS
-Distributed Cache Service (DCS) is an online distributed database service that is based on the cloud computing platform, available immediately after it is enabled, stable and reliable, scalable online, and easy to manage.
- With CTS, you can record operations associated with DCS for future query, audit, and backtrack operations.
-
- Table 1 DCS operations that can be recorded by CTSOperation
- |
-Resource Type
- |
-Trace Name
- |
-
|---|
-
-Creating an instance
- |
-Redis
- |
-createDCSInstance
- |
-
-Submitting an instance creation request
- |
-Redis
- |
-submitCreateDCSInstanceRequest
- |
-
-Batch deleting instances
- |
-Redis
- |
-batchDeleteDCSInstance
- |
-
-Deleting an instance
- |
-Redis
- |
-deleteDCSInstance
- |
-
-Modifying the information about a DCS instance
- |
-Redis
- |
-modifyDCSInstanceInfo
- |
-
-Modifying the configurations of a DCS instance
- |
-Redis
- |
-modifyDCSInstanceConfig
- |
-
-Changing the password of a DCS instance
- |
-Redis
- |
-modifyDCSInstancePassword
- |
-
-Restarting an instance
- |
-Redis
- |
-restartDCSInstance
- |
-
-Submitting an instance restarting request
- |
-Redis
- |
-submitRestartDCSInstanceRequest
- |
-
-Starting an instance
- |
-Redis
- |
-startDCSInstance
- |
-
-Submitting an instance starting request
- |
-Redis
- |
-submitStartDCSInstanceRequest
- |
-
-Clearing instance data
- |
-Redis
- |
-flushDCSInstance
- |
-
-Restarting instances in batches
- |
-Redis
- |
-batchRestartDCSInstance
- |
-
-Submitting a request to restart instances in batches
- |
-Redis
- |
-submitBatchRestartDCSInstanceRequest
- |
-
-Starting instances in batches
- |
-Redis
- |
-batchStartDCSInstance
- |
-
-Submitting a request to start instances in batches
- |
-Redis
- |
-submitBatchStartDCSInstanceRequest
- |
-
-Restoring instance data
- |
-Redis
- |
-restoreDCSInstance
- |
-
-Submitting a request to restore instance data
- |
-Redis
- |
-submitRestoreDCSInstanceRequest
- |
-
-Backing up instance data
- |
-Redis
- |
-backupDCSInstance
- |
-
-Submitting a request to back up instance data
- |
-Redis
- |
-submitBackupDCSInstanceRequest
- |
-
-Deleting instance backup files
- |
-Redis
- |
-deleteInstanceBackupFile
- |
-
-Deleting background tasks
- |
-Redis
- |
-deleteDCSInstanceJobRecord
- |
-
-Modifying instance specifications
- |
-Redis
- |
-modifySpecification
- |
-
-Submitting a request to modify instance specifications
- |
-Redis
- |
-submitModifySpecificationRequest
- |
-
-Creating an instance subscription order
- |
-Redis
- |
-createInstanceOrder
- |
-
-Switching between master and standby nodes
- |
-Redis
- |
-masterStandbySwitchover
- |
-
-Resetting an instance password
- |
-Redis
- |
-resetDCSInstancePassword
- |
-
-Submitting a request to clear instance data
- |
-Redis
- |
-submitFlushDCSInstanceRequest
- |
-
-
-
-
- Key Operations on RDS
-Relational Database Service (RDS) is a cloud-based web service that is reliable, scalable, easy to manage, and immediately ready for use.
- With CTS, you can record operations associated with RDS for future query, audit, and backtrack operations.
-
- Table 1 RDS operations recorded by CTSOperation
- |
-Resource Type
- |
-Trace Name
- |
-
|---|
-
-Creating a DB instance or a read replica, or restoring data to a new DB instance
- |
-instance
- |
-createInstance
- |
-
-Scaling up storage space and changing instance class
- |
-instance
- |
-instanceAction
- |
-
-Rebooting a DB instance
- |
-instance
- |
-instanceRestart
- |
-
-Restoring data to the original DB instance
- |
-instance
- |
-instanceRestore
- |
-
-Renaming a DB instance
- |
-instance
- |
-instanceRename
- |
-
-Resetting a password
- |
-instance
- |
-resetPassword
- |
-
-Setting database version parameters
- |
-instance
- |
-setDBParameters
- |
-
-Resetting database version parameters
- |
-instance
- |
-resetDBParameters
- |
-
-Enabling, modifying, or disabling a backup policy
- |
-instance
- |
-setBackupPolicy
- |
-
-Changing a database port
- |
-instance
- |
-changeInstancePort
- |
-
-Binding or unbinding an EIP
- |
-instance
- |
-setOrResetPublicIP
- |
-
-Modifying a security group
- |
-instance
- |
-modifySecurityGroup
- |
-
-Deleting a DB instance
- |
-instance
- |
-deleteInstance
- |
-
-Performing a primary/standby switchover
- |
-instance
- |
-instanceFailOver
- |
-
-Changing the replication mode
- |
-instance
- |
-instanceFailOverMode
- |
-
-Changing a failover priority
- |
-instance
- |
-instanceFailOverStrategy
- |
-
-Changing a DB instance type from single to primary/standby
- |
-instance
- |
-modifySingleToHaInstance
- |
-
-Downloading a backup (using OBS)
- |
-backup
- |
-downLoadSnapshot
- |
-
-Downloading a backup (using a browser)
- |
-backup
- |
-backupsDownLoad
- |
-
-Deleting a backup
- |
-backup
- |
-deleteManualSnapshot
- |
-
-Downloading a merged backup
- |
-backup
- |
-packBackupsDownLoad
- |
-
-Creating a parameter template
- |
-parameterGroup
- |
-createParameterGroup
- |
-
-Modifying parameters in a parameter template
- |
-parameterGroup
- |
-updateParameterGroup
- |
-
-Deleting a parameter template
- |
-parameterGroup
- |
-deleteParameterGroup
- |
-
-Replicating a parameter template
- |
-parameterGroup
- |
-copyParameterGroup
- |
-
-Resetting a parameter template
- |
-parameterGroup
- |
-resetParameterGroup
- |
-
-Applying a parameter template
- |
-parameterGroup
- |
-applyParameterGroup
- |
-
-Saving parameters in a parameter template
- |
-parameterGroup
- |
-saveParameterGroup
- |
-
-
-
-
- Key Operations on DRS
-Data Replication Service (DRS) is an easy-to-use, stable, and efficient cloud service used for database migration and synchronization. DRS makes data flow between databases simple, greatly reducing data transfer costs. DRS enables you to quickly transfer data between databases in different scenarios.
- With CTS, you can record operations associated with DRS for future query, audit, and backtrack operations.
-
- Table 1 DRS operations that can be recorded by CTSOperation
- |
-Resource Type
- |
-Trace Name
- |
-
|---|
-
-Creating a task
- |
-job
- |
-createJob
- |
-
-Editing a task
- |
-job
- |
-modifyJob
- |
-
-Deleting a task
- |
-job
- |
-deleteJob
- |
-
-Cloning a task
- |
-job
- |
-cloneJob
- |
-
-Starting a task
- |
-job
- |
-startJob
- |
-
-Retrying a task
- |
-job
- |
-retryJob
- |
-
-
-
-
- Key Operations on DDS
-Document Database Service (DDS) is compatible with the MongoDB protocol and is secure, highly available, reliable, scalable, and easy to use. It provides DB instance creation, scaling, redundancy, backup, restoration, monitoring, and alarm reporting functions with just a few clicks on the DDS console.
- With CTS, you can record operations associated with DDS for future query, audit, and backtrack operations.
-
- Table 1 DDS operations recorded by CTSOperation
- |
-Resource Type
- |
-Trace Name
- |
-
|---|
-
-Restoring data to a new DB instance
- |
-instance
- |
-ddsRestoreToNewInstance
- |
-
-Creating a DB instance
- |
-instance
- |
-ddsCreateInstance
- |
-
-Deleting a DB instance
- |
-instance
- |
-ddsDeleteInstance
- |
-
-Restarting a DB instance
- |
-instance
- |
-ddsRestartInstance
- |
-
-Scaling up a DB instance
- |
-instance
- |
-ddsGrowInstance
- |
-
-Scaling up storage space
- |
-instance
- |
-ddsExtendInstanceVolume
- |
-
-Resetting the database password
- |
-instance
- |
-ddsResetPassword
- |
-
-Renaming a DB instance
- |
-instance
- |
-ddsRenameInstance
- |
-
-Modifying a DB instance port
- |
-instance
- |
-ddsModifyInstancePort
- |
-
-Creating a backup
- |
-backup
- |
-ddsCreateBackup
- |
-
-Deleting a backup
- |
-backup
- |
-ddsDeleteBackup
- |
-
-Setting a backup policy
- |
-backup
- |
-ddsSetBackupPolicy
- |
-
-Applying a parameter group
- |
-parameterGroup
- |
-ddsApplyConfigurations
- |
-
-Replicating a parameter group
- |
-parameterGroup
- |
-ddsCopyConfigurations
- |
-
-Resetting a parameter group
- |
-parameterGroup
- |
-ddsResetConfigurations
- |
-
-Creating a parameter group
- |
-parameterGroup
- |
-ddsCreateConfigurations
- |
-
-Deleting a parameter group
- |
-parameterGroup
- |
-ddsDeleteConfigurations
- |
-
-Updating a parameter group
- |
-parameterGroup
- |
-ddsUpdateConfigurations
- |
-
-Binding an EIP
- |
-instance
- |
-ddsBindEIP
- |
-
-Unbinding an EIP
- |
-instance
- |
-ddsUnbindEIP
- |
-
-Rolling back upon scaling-up failure
- |
-instance
- |
-ddsDeleteExtendedDdsNode
- |
-
-Changing DB instance classes
- |
-instance
- |
-ddsResizeInstance
- |
-
-
-
-
- Key Operations on MRS
-MapReduce Service (MRS) is a data processing and analysis service that is based on a cloud computing platform. It is stable, reliable, scalable, and easy to manage.
- With CTS, you can record operations associated with MRS for future query, audit, and backtrack operations.
-
- Table 1 MRS operations that can be recorded by CTSOperation
- |
-Resource Type
- |
-Trace Name
- |
-
|---|
-
-Creating a cluster
- |
-cluster_mrs
- |
-createCluster
- |
-
-Deleting a cluster
- |
-cluster_mrs
- |
-deleteCluster
- |
-
-Expanding a cluster
- |
-cluster_mrs
- |
-scaleOutCluster
- |
-
-Shrinking a cluster
- |
-cluster_mrs
- |
-scaleInCluster
- |
-
-
-
-
- Key Operations on DIS
-Data Ingestion Service (DIS) solves the problems of transmitting external data into cloud services. With DIS, you can build customized applications to process or analyze stream data to meet specific demands.
- With CTS, you can record operations associated with DIS for future query, audit, and backtrack operations.
-
- Table 1 DIS operations that can be recorded by CTSOperation
- |
-Resource Type
- |
-Trace Name
- |
-
|---|
-
-Creating a stream
- |
-stream
- |
-createStream
- |
-
-Deleting a stream
- |
-stream
- |
-deleteStream
- |
-
-Creating an app
- |
-app
- |
-createApp
- |
-
-Deleting an app
- |
-app
- |
-deleteApp
- |
-
-
-
-
- Relationship Between Operations Triggered by IaaS OpenStack and Native OpenStack APIs
-
- Table 1 Relationship between operations triggered by IaaS OpenStack and native OpenStack APIsOperation
- |
-Trace Name
- |
-Service Type
- |
-Resource Type
- |
-OpenStack Component
- |
-
|---|
-
-Enabling an ECS
- |
-enableService
- |
-ECS
- |
-computeService
- |
-nova
- |
-
-Disabling an ECS
- |
-disableService
- |
-ECS
- |
-computeService
- |
-nova
- |
-
-Adding the cause of disabling an ECS
- |
-logDisabledInfo
- |
-ECS
- |
-computeService
- |
-nova
- |
-
-Deleting an ECS
- |
-deleteService
- |
-ECS
- |
-computeService
- |
-nova
- |
-
-Creating a flavor
- |
-createFlavor
- |
-ECS
- |
-flavor
- |
-nova
- |
-
-Deleting a flavor
- |
-deleteFlavor
- |
-ECS
- |
-flavor
- |
-nova
- |
-
-Adding/Deleting permissions of a tenant to access specifications
- |
-operateFlavorAccess
- |
-ECS
- |
-flavor
- |
-nova
- |
-
-Creating extra specifications
- |
-createExtraSpecs
- |
-ECS
- |
-flavor
- |
-nova
- |
-
-Updating specified extra specifications
- |
-updateExtraSpec
- |
-ECS
- |
-flavor
- |
-nova
- |
-
-Deleting specified extra specifications
- |
-deleteExtraSpec
- |
-ECS
- |
-flavor
- |
-nova
- |
-
-Creating a host group
- |
-createAggregate
- |
-ECS
- |
-hostAggregates
- |
-nova
- |
-
-Updating a host group
- |
-updateAggregate
- |
-ECS
- |
-hostAggregates
- |
-nova
- |
-
-Deleting a host group
- |
-deleteAggregate
- |
-ECS
- |
-hostAggregates
- |
-nova
- |
-
-Adding a host to a host group/Removing a host from a host group/Setting metadata of a host group
- |
-operateAggregate
- |
-ECS
- |
-hostAggregates
- |
-nova
- |
-
-Creating a key pair
- |
-createKeypair
- |
-ECS
- |
-keypair
- |
-nova
- |
-
-Deleting a key pair
- |
-deleteKeypair
- |
-ECS
- |
-keypair
- |
-nova
- |
-
-Updating the quota
- |
-updateQuotas
- |
-ECS
- |
-quotaSets
- |
-nova
- |
-
-Deleting the quota
- |
-revertQuotasToDefaults
- |
-ECS
- |
-quotaSets
- |
-nova
- |
-
-Creating a VM
- |
-createServer
- |
-ECS
- |
-server
- |
-nova
- |
-
-Updating a VM
- |
-updateServer
- |
-ECS
- |
-server
- |
-nova
- |
-
-Deleting a VM
- |
-deleteServer
- |
-ECS
- |
-server
- |
-nova
- |
-
-Operating a VM
- |
-operateServer
- |
-ECS
- |
-server
- |
-nova
- |
-
-Setting metadata
- |
-setMetadata
- |
-ECS
- |
-server
- |
-nova
- |
-
-Updating metadata/Setting metadata of a specified key
- |
-updateMetadata
- |
-ECS
- |
-server
- |
-nova
- |
-
-Deleting metadata of a specified key
- |
-deleteMetadata
- |
-ECS
- |
-server
- |
-nova
- |
-
-Adding an NIC to a VM
- |
-createInterface
- |
-ECS
- |
-server
- |
-nova
- |
-
-Detaching an NIC from a VM
- |
-detachInterface
- |
-ECS
- |
-server
- |
-nova
- |
-
-Clearing the password (DB) of a specified VM
- |
-clearAdminPassword
- |
-ECS
- |
-server
- |
-nova
- |
-
-Attaching a volume to a VM
- |
-attachVolume
- |
-ECS
- |
-server
- |
-nova
- |
-
-Detaching a volume from a VM
- |
-detachVolume
- |
-ECS
- |
-server
- |
-nova
- |
-
-Creating a VM group
- |
-createServerGroup
- |
-ECS
- |
-serverGroup
- |
-nova
- |
-
-Deleting a VM group
- |
-deleteServerGroup
- |
-ECS
- |
-serverGroup
- |
-nova
- |
-
-Creating a VM
- |
-createServerVolumesBoot
- |
-ECS
- |
-server
- |
-nova
- |
-
-Creating a console
- |
-createServerRemoteConsoles
- |
-ECS
- |
-server
- |
-nova
- |
-
-Resetting the password
- |
-resetServerPassword
- |
-ECS
- |
-server
- |
-nova
- |
-
-Creating a floating IP address
- |
-createFloatingip
- |
-VPC
- |
-floatingips
- |
-neutron
- |
-
-Updating a floating IP address
- |
-updateFloatingip
- |
-VPC
- |
-floatingips
- |
-neutron
- |
-
-Deleting a floating IP address
- |
-deleteFloatingip
- |
-VPC
- |
-floatingips
- |
-neutron
- |
-
-Creating a firewall group
- |
-createFirewallGroup
- |
-VPC
- |
-FWaaS v2
- |
-neutron
- |
-
-Updating a firewall group
- |
-updateFirewallGroup
- |
-VPC
- |
-FWaaS v2
- |
-neutron
- |
-
-Deleting a firewall group
- |
-deleteFirewallGroup
- |
-VPC
- |
-FWaaS v2
- |
-neutron
- |
-
-Creating a firewall policy
- |
-createFirewallPolicy
- |
-VPC
- |
-FWaaS v2
- |
-neutron
- |
-
-Updating a firewall policy
- |
-updateFirewallPolicy
- |
-VPC
- |
-FWaaS v2
- |
-neutron
- |
-
-Deleting a firewall policy
- |
-deleteFirewallPolicy
- |
-VPC
- |
-FWaaS v2
- |
-neutron
- |
-
-Inserting a firewall rule into a firewall policy
- |
-insertFirewallPolicyRule
- |
-VPC
- |
-FWaaS v2
- |
-neutron
- |
-
-Removing a firewall rule from a firewall policy
- |
-removeFirewallPolicyRule
- |
-VPC
- |
-FWaaS v2
- |
-neutron
- |
-
-Creating a firewall rule
- |
-createFirewallRule
- |
-VPC
- |
-FWaaS v2
- |
-neutron
- |
-
-Updating a firewall rule
- |
-updateFirewallRule
- |
-VPC
- |
-FWaaS v2
- |
-neutron
- |
-
-Deleting a firewall rule
- |
-deleteFirewallRule
- |
-VPC
- |
-FWaaS v2
- |
-neutron
- |
-
-Creating a NAT gateway
- |
-createNatGateway
- |
-VPC-OpenStack
- |
-natgateways
- |
-neutron
- |
-
-Updating a NAT gateway
- |
-updateNatGateway
- |
-VPC-OpenStack
- |
-natgateways
- |
-neutron
- |
-
-Deleting a NAT gateway
- |
-deleteNatGateway
- |
-VPC-OpenStack
- |
-natgateways
- |
-neutron
- |
-
-Creating an SNAT rule
- |
-createSnatRule
- |
-VPC-OpenStack
- |
-snatrules
- |
-neutron
- |
-
-Deleting an SNAT rule
- |
-deleteSnatRule
- |
-VPC-OpenStack
- |
-snatrules
- |
-neutron
- |
-
-Creating a DNAT rule
- |
-createDnatRule
- |
-VPC-OpenStack
- |
-dnatrules
- |
-neutron
- |
-
-Deleting a DNAT rule
- |
-deleteDnatRule
- |
-VPC-OpenStack
- |
-dnatrules
- |
-neutron
- |
-
-Creating a VPC
- |
-createNetwork
- |
-VPC
- |
-networks
- |
-neutron
- |
-
-Updating a VPC
- |
-updateNetwork
- |
-VPC
- |
-networks
- |
-neutron
- |
-
-Deleting a VPC
- |
-deleteNetwork
- |
-VPC
- |
-networks
- |
-neutron
- |
-
-Creating a virtual port
- |
-createPort
- |
-VPC
- |
-ports
- |
-neutron
- |
-
-Updating a virtual port
- |
-updatePort
- |
-VPC
- |
-ports
- |
-neutron
- |
-
-Deleting a virtual port
- |
-deletePort
- |
-VPC
- |
-ports
- |
-neutron
- |
-
-Creating a vRouter
- |
-createRouter
- |
-VPC
- |
-routes
- |
-neutron
- |
-
-Updating a vRouter
- |
-updateRouter
- |
-VPC
- |
-routes
- |
-neutron
- |
-
-Deleting a vRouter
- |
-deleteRouter
- |
-VPC
- |
-routes
- |
-neutron
- |
-
-Adding a vRouter API
- |
-addRouterInterface
- |
-VPC
- |
-routes
- |
-neutron
- |
-
-Deleting a vRouter API
- |
-removeRouterInterface
- |
-VPC
- |
-routes
- |
-neutron
- |
-
-Adding an extra route to the current vRouter
- |
-addExtraRoute
- |
-VPC
- |
-routes
- |
-neutron
- |
-
-Deleting a specified extra route from the current vRouter
- |
-removeExtraRoute
- |
-VPC
- |
-routes
- |
-neutron
- |
-
-Creating a security group rule
- |
-createSecurity-group-rule
- |
-VPC
- |
-security-group-rules
- |
-neutron
- |
-
-Deleting a security group rule
- |
-deleteSecurity-group-rule
- |
-VPC
- |
-security-group-rules
- |
-neutron
- |
-
-Creating a security group
- |
-createSecurity-group
- |
-VPC
- |
-security-groups
- |
-neutron
- |
-
-Deleting a security group
- |
-deleteSecurity-group
- |
-VPC
- |
-security-groups
- |
-neutron
- |
-
-Updating a security group
- |
-updateSecurity-group
- |
-VPC
- |
-security-groups
- |
-neutron
- |
-
-Creating a virtual subnet
- |
-createSubnet
- |
-VPC
- |
-subnets
- |
-neutron
- |
-
-Updating a virtual subnet
- |
-updateSubnet
- |
-VPC
- |
-subnets
- |
-neutron
- |
-
-Deleting a virtual subnet
- |
-deleteSubnet
- |
-VPC
- |
-subnets
- |
-neutron
- |
-
-Creating a VPN
- |
-createVpnService
- |
-VPC
- |
-vpn
- |
-neutron
- |
-
-Updating a VPN
- |
-updateVpnService
- |
-VPC
- |
-vpn
- |
-neutron
- |
-
-Deleting a VPN
- |
-deleteVpnService
- |
-VPC
- |
-vpn
- |
-neutron
- |
-
-Creating a private key exchange policy
- |
-createVpnIkepolicy
- |
-VPC
- |
-vpn
- |
-neutron
- |
-
-Updating a private key exchange policy
- |
-updateVpnIkepolicy
- |
-VPC
- |
-vpn
- |
-neutron
- |
-
-Deleting an IKE policy specified by the tenant
- |
-deleteVpnIkepolicy
- |
-VPC
- |
-vpn
- |
-neutron
- |
-
-Creating an IPsec policy
- |
-createVpnIpsecpolicy
- |
-VPC
- |
-vpn
- |
-neutron
- |
-
-Updating a specified IPsec policy
- |
-updateVpnIpsecpolicy
- |
-VPC
- |
-vpn
- |
-neutron
- |
-
-Deleting a specified IPsec policy
- |
-deleteVpnIpsecpolicy
- |
-VPC
- |
-vpn
- |
-neutron
- |
-
-Creating an IPsec connection
- |
-createVpnIpsec-site-connection
- |
-VPC
- |
-vpn
- |
-neutron
- |
-
-Updating an IPsec connection
- |
-updateVpnIpsec-site-connection
- |
-VPC
- |
-vpn
- |
-neutron
- |
-
-Deleting a specified IPsec connection
- |
-deleteVpnIpsec-site-connection
- |
-VPC
- |
-vpn
- |
-neutron
- |
-
-Creating an image
- |
-createImage
- |
-IMS
- |
-image
- |
-glance
- |
-
-Modifying information about an image/Uploading an image
- |
-updateImage
- |
-IMS
- |
-image
- |
-glance
- |
-
-Deleting an image
- |
-deleteImage
- |
-IMS
- |
-image
- |
-glance
- |
-
-Adding a tag
- |
-addTag
- |
-IMS
- |
-image
- |
-glance
- |
-
-Deleting a tag
- |
-deleteTag
- |
-IMS
- |
-image
- |
-glance
- |
-
-Adding an image member
- |
-addMember
- |
-IMS
- |
-image
- |
-glance
- |
-
-Modifying information about an image member
- |
-updateMember
- |
-IMS
- |
-image
- |
-glance
- |
-
-Deleting an image member
- |
-deleteMember
- |
-IMS
- |
-image
- |
-glance
- |
-
-Creating a configuration
- |
-createSoftwareConfigs
- |
-RTS
- |
-software_configs
- |
-heat
- |
-
-Deleting a configuration
- |
-deleteSoftwareConfigs
- |
-RTS
- |
-software_configs
- |
-heat
- |
-
-Creating a deployment
- |
-createSoftwareDeployments
- |
-RTS
- |
-software_deployments
- |
-heat
- |
-
-Deleting a deployment
- |
-deleteSoftwareDeployments
- |
-RTS
- |
-software_deployments
- |
-heat
- |
-
-Updating a deployment
- |
-updateSoftwareDeployments
- |
-RTS
- |
-software_deployments
- |
-heat
- |
-
-Stack management actions, such as canceling stack update or checking stack resources
- |
-createStacksActions
- |
-RTS
- |
-stacks
- |
-heat
- |
-
-Sending a signal to resources in a stack
- |
-createStacksResourcesSignal
- |
-RTS
- |
-stacks
- |
-heat
- |
-
-Creating a stack
- |
-createStacks
- |
-RTS
- |
-stacks
- |
-heat
- |
-
-Deleting a stack
- |
-deleteStacks
- |
-RTS
- |
-stacks
- |
-heat
- |
-
-Updating a stack
- |
-updateStacks
- |
-RTS
- |
-stacks
- |
-heat
- |
-
-Previewing a stack
- |
-createStacksPreview
- |
-RTS
- |
-stacks
- |
-heat
- |
-
-Identifying a resource as unhealthy
- |
-patchStacksResource
- |
-RTS
- |
-stacks
- |
-heat
- |
-
-Validating a template
- |
-createValidate
- |
-RTS
- |
-validate
- |
-heat
- |
-
-Creating a backup
- |
-createBackup
- |
-EVS
- |
-backup
- |
-Cinder
- |
-
-Importing volume backup information
- |
-import_recordBackup
- |
-EVS
- |
-backup
- |
-Cinder
- |
-
-Restoring a volume backup
- |
-restoreBackup
- |
-EVS
- |
-backup
- |
-Cinder
- |
-
-Deleting a backup
- |
-deleteBackup
- |
-EVS
- |
-backup
- |
-Cinder
- |
-
-Deleting a consistent group of snapshots
- |
-deleteCgsnapshot
- |
-EVS
- |
-cgsnapshot
- |
-Cinder
- |
-
-Creating a consistent group of snapshots
- |
-createCgsnapshot
- |
-EVS
- |
-cgsnapshot
- |
-Cinder
- |
-
-Creating a consistent group
- |
-createConsistencygroup
- |
-EVS
- |
-consistencygroup
- |
-Cinder
- |
-
-Deleting a consistent group
- |
-deleteConsistencygroup
- |
-EVS
- |
-consistencygroup
- |
-Cinder
- |
-
-Updating a consistent group
- |
-updateConsistencygroup
- |
-EVS
- |
-consistencygroup
- |
-Cinder
- |
-
-Updating the quota level of a tenant
- |
-updateQuota-class
- |
-EVS
- |
-quota-class
- |
-Cinder
- |
-
-Updating the quota of a tenant
- |
-updateQuota
- |
-EVS
- |
-quota
- |
-Cinder
- |
-
-Creating a volume transfer
- |
-createVolume-transfer
- |
-EVS
- |
-volume-transfer
- |
-Cinder
- |
-
-Deleting a volume transfer
- |
-deleteVolume-transfer
- |
-EVS
- |
-volume-transfer
- |
-Cinder
- |
-
-Accepting a volume transfer
- |
-acceptVolume-transfer
- |
-EVS
- |
-volume-transfer
- |
-Cinder
- |
-
-Creating qos-specs
- |
-createQos-specs
- |
-EVS
- |
-qos-specs
- |
-Cinder
- |
-
-Deleting qos-specs
- |
-deleteQos-specs
- |
-EVS
- |
-qos-specs
- |
-Cinder
- |
-
-Creating a snapshot
- |
-createSnapshot
- |
-EVS
- |
-snapshot
- |
-Cinder
- |
-
-Adding pieces of snapshot metadata
- |
-createSnapshotMetadata
- |
-EVS
- |
-snapshot
- |
-Cinder
- |
-
-Forcibly deleting a snapshot
- |
-force_deleteSnapshot
- |
-EVS
- |
-snapshot
- |
-Cinder
- |
-
-Deleting a snapshot
- |
-deleteSnapshot
- |
-EVS
- |
-snapshot
- |
-Cinder
- |
-
-Deleting a single piece of snapshot metadata
- |
-deleteSnapshotSingleMetadata
- |
-EVS
- |
-snapshot
- |
-Cinder
- |
-
-Updating snapshot information
- |
-updateSnapshot
- |
-EVS
- |
-snapshot
- |
-Cinder
- |
-
-Replacing pieces of snapshot metadata
- |
-updateSnapshotMetadata
- |
-EVS
- |
-snapshot
- |
-Cinder
- |
-
-Updating a single piece of snapshot metadata
- |
-updateSnapshotSingleMetadata
- |
-EVS
- |
-snapshot
- |
-Cinder
- |
-
-Rolling back a snapshot
- |
-rollbackSnapshot
- |
-EVS
- |
-snapshot
- |
-Cinder
- |
-
-Activating a snapshot
- |
-activeSnapshot
- |
-EVS
- |
-snapshot
- |
-Cinder
- |
-
-Creating a volume type
- |
-createType
- |
-EVS
- |
-type
- |
-Cinder
- |
-
-Creating extra specifications for a volume type
- |
-createTypeExtra-specs
- |
-EVS
- |
-type
- |
-Cinder
- |
-
-Deleting a volume type
- |
-deleteType
- |
-EVS
- |
-type
- |
-Cinder
- |
-
-Creating a volume
- |
-createVolume
- |
-EVS
- |
-volume
- |
-Cinder
- |
-
-Adding pieces of volume metadata
- |
-createVolumeMetadata
- |
-EVS
- |
-volume
- |
-Cinder
- |
-
-Forcibly deleting a volume
- |
-force_deleteVolume
- |
-EVS
- |
-volume
- |
-Cinder
- |
-
-Attaching a volume
- |
-attachVolume
- |
-EVS
- |
-volume
- |
-Cinder
- |
-
-Detaching a volume
- |
-detachVolume
- |
-EVS
- |
-volume
- |
-Cinder
- |
-
-Reserving a volume
- |
-reserveVolume
- |
-EVS
- |
-volume
- |
-Cinder
- |
-
-Pre-detaching a volume
- |
-begin_detachingVolume
- |
-EVS
- |
-volume
- |
-Cinder
- |
-
-Rolling back the volume pre-detaching
- |
-roll_detachingVolume
- |
-EVS
- |
-volume
- |
-Cinder
- |
-
-Initializing the connection for attaching a volume
- |
-initialize_connectionVolume
- |
-EVS
- |
-volume
- |
-Cinder
- |
-
-Terminating the connection for detaching a volume
- |
-terminate_connectionVolume
- |
-EVS
- |
-volume
- |
-Cinder
- |
-
-Uploading a volume image
- |
-Upload_imageVolume
- |
-EVS
- |
-volume
- |
-Cinder
- |
-
-Expanding the capacity of a volume
- |
-extendVolume
- |
-EVS
- |
-volume
- |
-Cinder
- |
-
-Unreserving a volume
- |
-unreserveVolume
- |
-EVS
- |
-volume
- |
-Cinder
- |
-
-Setting the state of a volume to read-only
- |
-update_readonly_flagVolume
- |
-EVS
- |
-volume
- |
-Cinder
- |
-
-Changing the type of a volume
- |
-retypeVolume
- |
-EVS
- |
-volume
- |
-Cinder
- |
-
-Setting the state of a volume to bootable
- |
-set_bootableVolume
- |
-EVS
- |
-volume
- |
-Cinder
- |
-
-Deleting a volume
- |
-deleteVolume
- |
-EVS
- |
-volume
- |
-Cinder
- |
-
-Deleting a single piece of volume metadata
- |
-deleteVolumeSingleMetadata
- |
-EVS
- |
-volume
- |
-Cinder
- |
-
-Updating a volume
- |
-updateVolume
- |
-EVS
- |
-volume
- |
-Cinder
- |
-
-Replacing pieces of volume metadata
- |
-updateVolumeMetadata
- |
-EVS
- |
-volume
- |
-Cinder
- |
-
-Updating a single piece of volume metadata
- |
-updateVolumeSingleMetadata
- |
-EVS
- |
-volume
- |
-Cinder
- |
-
-Creating volume tags
- |
-createVolume-tags
- |
-EVS
- |
-volume-tags
- |
-Cinder
- |
-
-Updating volume tags
- |
-updateVolume-tags
- |
-EVS
- |
-volume-tags
- |
-Cinder
- |
-
-Batch deleting volume tags
- |
-bulkDeleteVolume-tags
- |
-EVS
- |
-volume-tags
- |
-Cinder
- |
-
-Deleting a single volume tag
- |
-deleteVolume-tagsSingleTag
- |
-EVS
- |
-volume-tags
- |
-Cinder
- |
-
-Updating a single volume tag
- |
-updateVolume-tagsSingleTag
- |
-EVS
- |
-volume-tags
- |
-Cinder
- |
-
-Creating snapshot tags
- |
-createSnapshot-tags
- |
-EVS
- |
-snapshot-tags
- |
-Cinder
- |
-
-Updating snapshot tags
- |
-updateSnapshot-tags
- |
-EVS
- |
-snapshot-tags
- |
-Cinder
- |
-
-Batch deleting snapshot tags
- |
-bulkDeleteSnapshot-tags
- |
-EVS
- |
-snapshot-tags
- |
-Cinder
- |
-
-Deleting a single snapshot tag
- |
-deleteSnapshot-tagsSingleTag
- |
-EVS
- |
-snapshot-tags
- |
-Cinder
- |
-
-Updating a single snapshot tag
- |
-updateSnapshot-tagsSingleTag
- |
-EVS
- |
-snapshot-tags
- |
-Cinder
- |
-
-Batch creating volume tags
- |
-createVolume-tags
- |
-EVS
- |
-volume-tags
- |
-Cinder
- |
-
-Batch deleting volume tags
- |
-deleteVolume-tags
- |
-EVS
- |
-volume-tags
- |
-Cinder
- |
-
-
-
-
- Key Operations on DWS
-Data Warehouse Service (DWS) is an online data processing database based on the cloud infrastructure and platform and helps you mine and analyze massive data.
- With CTS, you can record operations associated with DWS for later query, audit, and backtracking.
-
- Table 1 DWS operations that can be recorded by CTSOperation
- |
-Resource Type
- |
-Trace Name
- |
-
|---|
-
-Creating/Restoring a cluster
- |
-cluster
- |
-createCluster
- |
-
-Deleting a cluster
- |
-cluster
- |
-deleteCluster
- |
-
-Expanding the cluster capacity
- |
-cluster
- |
-growCluster
- |
-
-Restarting a cluster
- |
-cluster
- |
-rebootCluster
- |
-
-Creating a snapshot
- |
-backup
- |
-createBackup
- |
-
-Deleting a snapshot
- |
-backup
- |
-deleteBackup
- |
-
-Setting security parameters
- |
-configurations
- |
-updateConfigurations
- |
-
-Creating an MRS data source
- |
-dataSource
- |
-createExtDataSource
- |
-
-Deleting an MRS data source
- |
-dataSource
- |
-deleteExtDataSource
- |
-
-Updating an MRS data source
- |
-dataSource
- |
-updateExtDataSource
- |
-
-
-
-
- Key Operations on CSS
-Cloud Search Service (CSS) is a fully hosted distributed search engine service based on the cloud infrastructure and platform. It provides structured and unstructured text search, statistics, and report capabilities.
- With CTS, you can record operations associated with CSS for later query, audit, and backtracking.
-
- Table 1 CSS operations that can be recorded by CTSOperation
- |
-Resource Type
- |
-Trace Name
- |
-
|---|
-
-Creating a cluster
- |
-Cluster
- |
-createCluster
- |
-
-Deleting a cluster
- |
-Cluster
- |
-deleteCluster
- |
-
-Expanding the cluster capacity
- |
-Cluster
- |
-growCluster
- |
-
-Restarting a cluster
- |
-Cluster
- |
-rebootCluster
- |
-
-Performing basic configurations for a cluster snapshot
- |
-cluster
- |
-updateSnapshotPolicy
- |
-
-Setting the automatic snapshot creation policy
- |
-cluster
- |
-updateAutoSnapshotPolicy
- |
-
-Creating a snapshot
- |
-snapshot
- |
-createSnapshot
- |
-
-Restarting a snapshot
- |
-snapshot
- |
-restoreSnapshot
- |
-
-Deleting a snapshot
- |
-snapshot
- |
-deleteSnapshot
- |
-
-
-
-
- Computing
-
-
-
diff --git a/docs/cts/umn/en-us_topic_0127139647.html b/docs/cts/umn/en-us_topic_0127139647.html
deleted file mode 100644
index e1f79b9a..00000000
--- a/docs/cts/umn/en-us_topic_0127139647.html
+++ /dev/null
@@ -1,21 +0,0 @@
-
-
-Storage
-
-
-
diff --git a/docs/cts/umn/en-us_topic_0127139648.html b/docs/cts/umn/en-us_topic_0127139648.html
deleted file mode 100644
index 6542c4fe..00000000
--- a/docs/cts/umn/en-us_topic_0127139648.html
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-Network
-
-
-
diff --git a/docs/cts/umn/en-us_topic_0127139651.html b/docs/cts/umn/en-us_topic_0127139651.html
deleted file mode 100644
index c12a96e4..00000000
--- a/docs/cts/umn/en-us_topic_0127139651.html
+++ /dev/null
@@ -1,25 +0,0 @@
-
-
-
- Management & Deployment
-
-
-
-
-
diff --git a/docs/cts/umn/en-us_topic_0127139652.html b/docs/cts/umn/en-us_topic_0127139652.html
deleted file mode 100644
index 6ba8145f..00000000
--- a/docs/cts/umn/en-us_topic_0127139652.html
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-Application
-
-
-
diff --git a/docs/cts/umn/en-us_topic_0127139653.html b/docs/cts/umn/en-us_topic_0127139653.html
deleted file mode 100644
index 05371f26..00000000
--- a/docs/cts/umn/en-us_topic_0127139653.html
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-Database
-
-
-
diff --git a/docs/cts/umn/en-us_topic_0127139655.html b/docs/cts/umn/en-us_topic_0127139655.html
deleted file mode 100644
index 773dbd06..00000000
--- a/docs/cts/umn/en-us_topic_0127139655.html
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-Security
-
-
-
diff --git a/docs/cts/umn/en-us_topic_0127139658.html b/docs/cts/umn/en-us_topic_0127139658.html
deleted file mode 100644
index 8fb0fa3f..00000000
--- a/docs/cts/umn/en-us_topic_0127139658.html
+++ /dev/null
@@ -1,21 +0,0 @@
-
-
-Data Analysis
-
-
-
diff --git a/docs/cts/umn/en-us_topic_0128329663.html b/docs/cts/umn/en-us_topic_0128329663.html
deleted file mode 100644
index bc3dcbd3..00000000
--- a/docs/cts/umn/en-us_topic_0128329663.html
+++ /dev/null
@@ -1,108 +0,0 @@
-
-
-Key Operations on CDN
-Content Delivery Network (CDN) is an intelligent virtual network layer based on the existing Internet infrastructure. It delivers network content from origin servers to edge node servers distributed across a country, enabling end users to obtain desired content from the proximal node.
- With CTS, you can record operations associated with CDN for future query, audit, and backtrack operations.
- Table 1 CDN operations that can be recorded by CTSOperation
- |
-Resource Type
- |
-Trace Name
- |
-
|---|
-
-Creating an acceleration domain name
- |
-CDN
- |
-createDomain
- |
-
-Updating an acceleration domain name
- |
-CDN
- |
-updateDomain
- |
-
-Deleting an acceleration domain name
- |
-CDN
- |
-deleteDomain
- |
-
-Enabling an acceleration domain name
- |
-CDN
- |
-enableDomain
- |
-
-Disabling an acceleration domain name
- |
-CDN
- |
-disableDomain
- |
-
-Configuring a retrieval host
- |
-CDN
- |
-updateOriginHost
- |
-
-Creating a Referer rule
- |
-CDN
- |
-createRefer
- |
-
-Configuring an acceleration domain name certificate
- |
-CDN
- |
-createCertificate
- |
-
-Creating a cache rule
- |
-CDN
- |
-createCacheRule
- |
-
-Creating a cache refreshing task
- |
-CDN
- |
-createRefreshTask
- |
-
-Creating a preheating task
- |
-CDN
- |
-createPreheatingTask
- |
-
-Enabling CDN
- |
-CDN
- |
-createBillingMode
- |
-
-
-
-
-
- |
|---|
in the upper left corner and choose Management & Deployment > Cloud Trace Service. The CTS console is displayed.
in the upper left corner and choose Management & Deployment > Cloud Trace Service. The CTS console is displayed.
in the upper left corner and choose Management & Deployment > Cloud Trace Service. The CTS console is displayed.
in the upper left corner and choose Management & Deployment > Cloud Trace Service. The CTS console is displayed.
in the upper left corner and choose Management & Deployment > Cloud Trace Service. The CTS console is displayed.
