Help Center/
Anti-DDoS Service/
User Guide/
Advanced Anti-DDoS User Guide/
Auditing/
Viewing CTS Traces
Updated on 2024-01-31 GMT+08:00
Viewing CTS Traces
After you enable CTS, the system starts recording operations on Anti-DDoS Service. You can view the operation records of the last 7 days on the CTS console.
Procedure
- Log in to the management console.
- Click on the left of the page and choose Cloud Trace Service under Management & Deployment.
- Choose Trace List in the navigation pane on the left.
- Select Trace Source from the drop-down list, enter AAD, and press Enter.
- Click a trace name in the query result to view the event details.
You can use the advanced search function to combine one or more filter criteria in the filter box.
- Enter Trace Name, Resource Name, Resource ID, and Trace ID.
- Resource Name: If the cloud resource involved in the trace does not have a name or the corresponding API operation does not involve resource names, this field is left empty.
- Resource ID: If the resource does not have a resource ID or the resource fails to be created, this field is left empty.
- Trace Source and Resource Type: Select the corresponding cloud service name or resource type from the drop-down list.
- Operator: Select one or more operators from the drop-down list.
- Trace Status: The value can be normal, warning, or incident. You can select only one of them.
- normal: indicates that the operation is successful.
- warning: indicates that the operation failed.
- incident: indicates a situation that is more serious than an operation failure, for example, other faults are caused.
- Time range: You can query traces generated in the last hour, day, or week, or customize traces generated in any time period of the last week.
- Enter Trace Name, Resource Name, Resource ID, and Trace ID.
Parent topic: Auditing
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.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot