Recording AS Resource Operations
Scenarios
AS can use the Cloud Trace Service (CTS) to record resource operations. CTS can record operations performed on the management console, operations performed by calling APIs, and operations triggered within the cloud system.
If you have enabled CTS, when a call is made to the AS API, the operation will be reported to CTS which will then deliver the operation record to a specified OBS bucket for storage. With CTS, you can record operations associated with AS for later query, audit, and backtrack operations.
Obtaining AS Information in CTS
After you enable CTS in the application system, the system logs the API calling operations performed on AS resources. On the Cloud Trace Service console, you can view operation records for the last 7 days. For details, see Querying Real-Time Traces. To obtain more operation records, you can enable the Object Storage Service (OBS) and synchronize operation records to the OBS in real time.
Operation |
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 |
Performing operations on an AS group |
scaling_group |
operateScalingGroup |
Creating an AS configuration |
scaling_configuration |
createScalingConfiguration |
Deleting an AS configuration |
scaling_configuration |
deleteScalingConfiguration |
Deleting AS configurations in a batch |
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 |
Performing operations on an AS policy |
scaling_policy |
operateScalingPolicy |
Enabling AS policies in a batch |
scaling_policy |
batchEnableScalingPolicies |
Disabling AS policies in a batch |
scaling_policy |
batchDisableScalingPolicies |
Removing an instance |
scaling_instance |
removeInstance |
Removing instances in batches |
scaling_instance |
batchRemoveInstances |
Adding instances in batches |
scaling_instance |
batchAddInstances |
Performing operations on instances in batches |
scaling_instance |
batchOperateInstance |
Enabling instance protection in a batch |
scaling_instance |
batchProtectInstances |
Disabling instance protection in a batch |
scaling_instance |
batchUnprotectInstances |
Putting instances into standby in a batch |
scaling_instance |
batchEnterStandbyInstances |
Configuring a notification |
scaling_notification |
putScalingNotification |
Deleting a notification |
scaling_notification |
deleteScalingNotification |
Creating a lifecycle hook |
scaling_lifecycle_hook |
createLifecycleHook |
Modifying a lifecycle hook |
scaling_lifecycle_hook |
modifyLifecycleHook |
Deleting a lifecycle hook |
scaling_lifecycle_hook |
deleteLifecycleHook |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot