Querying Archived Traces¶
Scenarios¶
CTS periodically sends trace files to OBS buckets. A trace file is a collection of traces. CTS generates trace files based on services and transfer cycle, and adjusts the number of traces contained in each trace file as needed.
This section describes how to obtain historical operation records from trace files downloaded from the OBS bucket.
Prerequisites¶
You have configured a tracker. For details, see Configuring a Tracker.
Procedure¶
Log in to the management console.
Click
in the upper left corner and choose Management & Deployment > Cloud Trace Service. The CTS console is displayed.Choose Tracker List in the navigation pane on the left.
Click a bucket in the OBS Bucket column.
Figure 1 Selecting an OBS bucket¶
In the OBS bucket, select the trace to be viewed based on the trace file storage path, and download the file to the default download path of the browser. If you need to save the event file to a custom path, click Download As on the right.
The trace file storage path is as follows:
OBS bucket name > CloudTraces > Region > Year > Month > Day > Tracker name > Service directory
An example is User-defined name > CloudTraces > region > 2016 > 5 > 19 > system > ECS.
The trace file naming format is as follows:
Trace file prefix_CloudTrace_Region/Region-project_Time when the trace file was uploaded to OBS: Year-Month-DayTHour-Minute-SecondZ_Random characters.json.gz
An example is File Prefix_CloudTrace_region-project_2016-05-30T16-20-56Z_21d36ced8c8af71e.json.gz.
Note
The OBS bucket name and trace file prefix are user-defined, and other parameters are automatically generated.
For details about key fields in the CTS trace structure, see Trace Structure and Example Traces.
Figure 2 Viewing trace file content¶
Decompress the downloaded package to obtain a JSON file with the same name as the package. Open the JSON file using a text file editor to view traces.
Figure 3 JSON file¶