Deze pagina is nog niet beschikbaar in uw eigen taal. We werken er hard aan om meer taalversies toe te voegen. Bedankt voor uw steun.
Anti-DDoS
Anti-DDoS
- What's New
- Function Overview
- Service Overview
- Getting Started
- User Guide
- Best Practices
-
API Reference
- API Usage Guidelines
- Before You Start
- API Overview
- API Calling
-
API
-
Anti-DDoS Management
- Querying the List of Defense Statuses of EIPs
- Querying Optional Anti-DDoS Defense Policies
- Querying Weekly Defense Statistics
- Querying Configured Anti-DDoS Defense Policies
- Updating Anti-DDoS Defense Policies
- Querying the Traffic of a Specified EIP
- Querying Events of a Specified EIP
- Querying Configured Anti-DDoS Defense Policies
- Anti-DDoS Task Management
- Alarm configuration management
-
Anti-DDoS Management
- Examples
- Appendix
- Out-of-Date APIs
- SDK Reference
-
FAQs
-
General FAQs
- What Are Regions and AZs?
- What Is the Black Hole Policy of HUAWEI CLOUD?
- What Are a SYN Flood Attack and an ACK Flood Attack?
- What Is a CC Attack?
- What Is a Slow HTTP Attack?
- What Are a UDP Attack and a TCP Attack?
- What Are the Differences Between DDoS Attacks and Challenge Collapsar Attacks?
- Does Anti-DDoS Provide SDKs and APIs?
- CNAD Basic (Anti-DDoS) FAQs
-
General FAQs
- Videos
On this page
Show all
Viewing CTS Traces
Updated on 2024-11-29 GMT+08:00
After you enable CTS, the system starts recording operations performed to Anti-DDoS resources. Operation records generated during the last seven days can be viewed 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 Anti-DDoS, 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: Audit
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.