Parameters | Type | Example value | Description |
Total | Integer | 100 | Total number of eligible Trace instances, used to calculate the total number of pages for pagination. |
TraceInstances | - | Returns a list of Trace instances that meet the criteria. Each instance includes project ID, creation time, modification time, description, and project name. |
Parameters | Type | Example value | Description |
ProjectId | String | c7e0e442-19bf-4fb3-b547-5992fb8b**** | The project ID that the Trace instance belongs to. |
CreateTime | String | 2023-01-15T10:30:00Z | Creation time of the Trace instance, representing when the instance was created in the system |
ModifyTime | String | 2023-01-15T14:45:00Z | Trace instance last modified time, indicating the latest update time in the system for this instance. |
Description | String | This is a test trace ins. | Description of the trace instance |
ProjectName | String | my-log-project | The name of the log project identifies which Trace instance belongs to which project. |
TraceTopicId | String | ca0c7da2-313e-4729-a66f-85f40380**** | Log topic ID associated with the Trace instance, identifying the log topic for the instance. |
BackendConfig | {"Ttl":97,"EnableHotTtl":true,"HotTtl":7,"ColdTtl":30,"ArchiveTtl":60,"AutoSplit":true,"MaxSplitPartitions":10} | Trace instance backend configuration for setting log storage tiering strategies, auto split, and more | |
TraceTopicName | String | my-trace-topic | Name of the log topic associated with Trace instances, used to identify the corresponding log topic for the instance. |
TraceInstanceId | String | 0fdaa6b6-3c9f-424c-8664-fc0d222c**** | Trace instance ID. |
CsAccountChannel | String | cs-channel-1234567890ab**** | The customer service account channel for the Trace instance, which identifies the channel to which the instance belongs. |
DependencyTopicId | String | c1c28228-627a-476b-98b4-2914225d**** | The Trace instance relies on the log topic ID, which identifies other log topics required by this instance. |
TraceInstanceName | String | my-trace-instance | Trace instance name. |
TraceInstanceStatus | String | CREATED | Status of Trace instance. |
DependencyTopicTopicName | String | dependency-topic-name | The name of the log topic that Trace instances depend on, used to identify other log topics referenced by the instance. |
Parameters | Type | Example value | Description |
Ttl | Integer | 97 | The total retention period of logs in TLS. When logs in the topic exceed the specified Log storage period, expired logs will be automatically deleted. The unit is days. The default value is 30 days. The value ranges from 1 to 3650. If it is set to 3650, the storage time becomes permanent storage. tip After setting EnableHotTtl to true, the Ttl duration must equal the total value of HotTtl, ColdTtl, and ArchiveTtl |
EnableHotTtl | Boolean | true | Enable tiered storage Once enabled, TLS supports standard storage, infrequent access storage, and archive storage When HotTtl, ArchiveTtl, and ColdTtl are configured, if the data storage time exceeds the set duration, the data will automatically migrate to infrequent access and archive storage for further retention. Data will be automatically deleted by the backend service when the total log collection duration reaches Ttl tip The Ttl duration must equal the total value of HotTtl, ColdTtl, and ArchiveTtl |
HotTtl | Integer | 7 | Standard storage duration. The default duration is 30 days, and the valid range is 7 to 3650 days. This parameter is only effective when EnableHotTtl is set to true. |
ColdTtl | Integer | 30 | Low-frequency storage duration. The valid range for this duration is 30 to 3650. Low-frequency storage can be enabled when the standard storage period is 7 days or longer. This parameter takes effect only when EnableHotTtl is set to true. |
ArchiveTtl | Integer | 60 | Archive storage period. The period must range from 60 to 3650. Archive storage is available when any of the following conditions are met.
This parameter is only effective when EnableHotTtl is set to true |
AutoSplit | Boolean | true | Automatic sharding can be enabled or disabled. Once enabled, if data volume exceeds existing shard capacity for 5 consecutive minutes, TLS will automatically split shards based on data volume to meet business needs. The number of shards after splitting cannot exceed the maximum split count. New shard created within the last 15 minutes will not split automatically.
|
MaxSplitPartitions | Integer | 10 | Maximum number of shard splits |