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.
- 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
Function Overview
-
Cloud Trace Service
-
Cloud Trace Service (CTS) is a log audit service, which allows you to collect, store, and query cloud resource operation records (traces). You can use these traces to perform security analysis, track resource changes, audit compliance, and locate faults.
- Trace recording: CTS records operations performed on the management console, API calls, and system-triggered operations.
- Trace query: Traces of the last seven days can be queried on the CTS console by multiple dimensions, such as trace type, 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.
- Trace file encryption: Trace files can be encrypted using keys provided by Data Encryption Workshop (DEW) during transfer.
All regions
-
-
Tracker
-
Before using CTS, you need to enable it, and a tracker will be automatically created. The tracker identifies and associates with all cloud services you are using, and records all operations on the services.
-
-
Trace
-
Traces are cloud resource operation records captured and stored by CTS. You can view traces to identify when operations were performed by which users.
There are two types of traces. Management traces are operation records reported by cloud services, whereas data traces are read/write operation records reported by OBS.
All regions
-
-
Trace file
-
A trace file is a collection of traces. CTS generates trace files based on services and transfer cycle and sends these files to your specified OBS bucket. 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.
All regions
-
-
Trace file integrity verification
-
During a security audit, operation records will not be able to serve as effective and authentic evidence if they have been deleted or otherwise tampered with. You can enable the integrity verification in CTS to ensure the authenticity of trace files.
-
-
Supported services
-
CTS connects with many cloud services to track and save their traces.
-
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.