Cette page n'est pas encore disponible dans votre langue. Nous nous efforçons d'ajouter d'autres langues. Nous vous remercions de votre compréhension.
- What's New
- Function Overview
- Service Overview
- Getting Started
- User Guide
- Best Practices
- API Reference
- SDK Reference
-
FAQs
- Must I Use an IAM User (Sub Account) to Configure Transfer on CTS and Perform Operations on an OBS Bucket?
- How Will CTS Be Affected If My Account Is in Arrears?
- What Are the Recommended Users of CTS?
- What Will Happen If I Have Enabled Trace Transfer But Have Not Configured an Appropriate Policy for an OBS Bucket?
- Does CTS Support Integrity Verification of Trace Files?
- Why Are There Some Null Fields on the View Trace Page?
- Why Is an Operation Recorded Twice in the Trace List?
- What Services Are Supported by Key Event Notifications?
- How Can I Store Trace Files for a Long Time?
- Why Are user and source_ip Null for Some Traces with trace_type as SystemAction?
- How Can I Find Out Who Created a Specific ECS?
- How Can I Find Out the Login IP Address of an IAM User?
- Why Are Two deleteMetadata Traces Generated When I Buy an ECS in Pay-per-Use or Yearly/Monthly?
- What Can I Do If I Cannot Query Traces?
- Can I Disable CTS?
- How Do I Configure the Storage Duration of CTS Audit Logs to 180 Days?
- What Should I Do If I Cannot Enable CTS as an IAM User?
- How Do I Enable Alarm Notifications for EVS?
- Videos
Show all
API Overview
With the extension APIs provided by CTS, you can use all CTS functions, such as querying API versions and the trace list, or creating a tracker.
Table 1 lists CTS APIs.
|
Subtype |
Description |
|---|---|
|
API versions |
API for querying versions of all or specified CTS APIs |
|
Trackers |
APIs for creating, modifying, querying, and deleting a tracker |
|
Traces |
API for querying traces recorded in the last seven days |
|
Key event notifications |
APIs for creating, modifying, querying, and deleting a key event notification |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
