• Cloud Trace Service

  1. Help Center
  2. Cloud Trace Service
  3. User Guide
  4. Getting Started
  5. Querying Archived Traces

Querying Archived Traces


CTS periodically compresses the recorded traces into trace files and delivers them to OBS buckets. Trace files are collections of traces that CTS automatically generates by service and dump interval. CTS adjusts the number of traces contained in a trace file as the service load changes.

This section describes how to obtain historical operation records from trace files downloaded from the OBS bucket.


  1. Log in to the management console.
  2. Click in the upper left corner and select a region and project.
  3. Click Service List and choose Management & Deployment > Cloud Trace Service.
  4. Click Tracker in the left pane.
  5. Click the specified bucket in the OBS Bucket column.
    Figure 1 Selecting the OBS bucket
    Figure 2 Selecting the OBS bucket
  6. Select the target trace. Choose OBS bucket name > CloudTraces > Region > Year > Month > Day > Tracker name > Service type directory. Click Download in the Operation column to download the trace file to the default path. To download the trace file to a customized path, click Download As.
    • The trace file storage path is as follows:

      OBS bucket name > CloudTraces > Region > Year > Month > Day > Tracker name > Service type directory

      An example is User Define>CloudTraces>region>2016>5>19>system>ECS.

    • The trace file naming format is as follows:

      Operation trace file prefix_CloudTrace_Region_/Region-projectTime when the log was uploaded to OBS: year-month-dayThour-minute-secondZ_Character randomly generated.json.gz

      An example is File Prefix_CloudTrace_region_2016-05-30T16-20-56Z_21d36ced8c8af71e.json.gz.


    The OBS bucket name and trace file prefix are user-defined, and other parameters are automatically generated.

    For details about key fields in the trace structure, see Trace Structure and Example Traces.

    Figure 3 Viewing trace file content
  7. Extract a JSON file with the same name as the downloaded trace file and open the JSON file using a text file editor to view trace logs.