On the CTS console, you can add configurations such as OBS or LTS transfer for the created management tracker.
You can select whether to send recorded traces to an OBS bucket for long-term storage.
After the tracker configuration is complete, CTS will immediately start recording operations under the new settings.
This section describes how to configure the management tracker.
You have enabled CTS.
in the upper left corner to select the desired region and project.
in the upper left corner and choose Management & Deployment > Cloud Trace Service. The CTS console is displayed.Parameter | Description |
|---|---|
Tracker Name | The default value is system and cannot be changed. |
Enterprise Project | Select an enterprise project. NOTE: Enterprise projects allow you to manage cloud resources and users by project. For details about how to enable the enterprise project function, see Creating an Enterprise Project. |
Excluding DEW traces | Deselected by default. If this option is selected, the createDataKey and decryptDatakey operations on DEW will not be transferred to OBS/LTS. |
Parameter | Description |
|---|---|
Transfer to OBS | Select an existing OBS bucket or create one on this page and set File Prefix if Transfer to OBS is enabled. When Transfer to OBS is disabled, no operation is required. |
Create a cloud service agency. | (Mandatory) If you select this check box, CTS automatically creates a cloud service agency when you create a tracker. The agency authorizes you to use OBS. |
OBS Bucket Account | CTS allows you to transfer traces to OBS buckets of other users for unified management.
|
OBS Bucket | New: An OBS bucket will be created automatically with the name you enter. NOTE: The OBS bucket created on this page is a single-AZ private bucket with Standard storage. If you need other configurations, create the bucket on OBS Console in advance and choose Existing to select it. Existing: Select an existing OBS bucket in the current region. |
Select Bucket | If you select New for OBS Bucket, enter a name for the new OBS bucket. The bucket name cannot be empty. Enter 3 to 63 characters, including only lowercase letters, digits, hyphens (-), and periods (.). It cannot contain two consecutive periods (for example, my..bucket). A period (.) and a hyphen (-) cannot be adjacent to each other (for example, my-.bucket and my.-bucket). Do not use an IP address as a bucket name. If you select Existing for OBS Bucket, select an existing OBS bucket. |
Retention Period | For the management tracker, the retention period configured on the OBS console is used by default and cannot be changed. |
File Prefix | A file prefix is used to mark transferred trace files. The prefix you set will be automatically added to the beginning of the file names, facilitating file filtering. Enter 0 to 64 characters. Only letters, digits, underscores (_), hyphens (-), and periods (.) are allowed. |
Compression | The usage of object storage space can be reduced.
|
Sort by Cloud Service |
|
Transfer Path | Log transfer path is automatically set by the system. |
Parameter | Description |
|---|---|
Transfer to LTS | When Transfer to LTS is enabled, traces are transferred to the log stream. |
Log Group | When Transfer to LTS is enabled, the default log group name CTS is set. When Transfer to LTS is disabled, no operation is required. |
You can then view the tracker details on the Tracker List page.
Traces recorded by CTS are delivered periodically to the OBS bucket for storage. If you configure an OBS bucket for a tracker, traces generated during the current cycle (usually several minutes) will be delivered to the configured OBS bucket. For example, if the current cycle is from 12:00:00 to 12:05:00 and you configure an OBS bucket for a tracker at 12:02:00, traces received from 12:00:00 to 12:02:00 will also be delivered to the configured OBS bucket for storage at 12:05:00.
in the Tag column to add tags to the tracker.Tags are key-value pairs, which are used to identify, classify, and search for trackers. Tracker tags are used to filter and manage trackers only. A maximum of 20 tags can be added to a tracker.
If your organization has configured tag policies for CTS, add tags to trackers based on the policies.
Parameter | Description | Example |
|---|---|---|
Tag key | A tag key of a tracker must be unique. You can customize a key or select the key of an existing tag created in Tag Management Service (TMS). A tag key:
| Key_0001 |
Tag value | A tag value can be repetitive or left blank. A tag value:
| Value_0001 |