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.
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.
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.