Torch Log Service
Torch Log Service
Torch Log Service
Document
Product News
Product Overview
Product Billing
User Guide
TLS Agent
AgentLoop
Resource management
Host group
Data collection
LogCollector collection
Introduction to LogCollector
Installation and upgrade
Collect host logs
Collect container logs
LogCollector plugins
Manage LogCollector
general reference
Data import
Cloud product log collection
TOS log collection
DBW log collection
VPN Log collection
VKE log collection
CLB log collection
CloudTrail log collection
CFW log collection
NTA log collection
ALB log collection
APMPlus log collection
veFaaS log collection
VPC log collection
veImageX log collection
TrafficRoute DNS log collection
DDoS log collection
WAF log collection
DCDN log collection
Multi-cloud security platform log collection
APIG log collection
Machine learning task log collection
CR log collection
Volcano Ark application lab log collection
FileNAS log collection
LLM Application Firewall Service log collection
vePFS log collection
Cloud security center log collection
EFS log collection
Data storage
Query and analysis
Configure log indexes
Query log
Analyze logs
Query and analyze logs using third-party tools
Associate external data source for log query
SQL function
SQL syntax
Visualization
Query and analysis charts
Summaries of query and analysis charts
Create dashboard
Use dashboard
Add dashboard filters and variables
Use other systems to analyze logs
Log application
Log applications for product observability
Log applications for large models observability
Coding Agent log app
ModelProvider log app
No-coding Agent log app
Log applications for basic service monitoring
Data processing
Data transformation
Syntax and functions
Global operation function
expression function
Data processing best practices
general reference
Data write processor
Data consumer processor
Data consumption and shipping
Ship logs to TOS
Ship logs to Kafka
Ship logs to Splunk
Alarm
Alarm policy
Alarm notification content
Alarm notification content template
alarm notification channel
Tracing service
Monitor Log Service
API reference
Project management API
Topic management API
Shard management API
Index management API
Log management API
Host group management API
Collection configuration management API
Data import API
Data processor API
Data transformation API
Data backflow API
SQL analysis API
Alarm management API
Consumer group management API
Kafka protocol consumption API
Tag management API
Trace storage API
Account management API
SDK reference
Go SDK
Java SDK
Python SDK
iOS SDK
C++ SDK
CLI reference
Best practices
Data collection
Query and analysis
permission management
Consumption and delivery
Visualization
Alarm
FAQs
Billing and cost FAQ
Data collection FAQ
Data storage FAQ
Index configuration FAQ
Query and analysis FAQ
Scheduled SQL tasks FAQ
Alarm FAQ
- Documentation
Torch Log ServiceUser GuideTracing serviceCreate a universal trace instance
Copy page
Download PDFTracing service
Create a universal trace instance
Copy pageDownload PDFCreate a universal trace instance
Before accessing trace storage, you need to create a trace instance in TLS to manage collected trace data.
Background information
A trace instance is a trace data computing resource provided by TLS. It is used to manage collected trace data. You can view and analyze collected trace data from the dimension of trace instance in the TLS console.
Tip
- Before using trace storage for the first time, you must authorize access to cloud resources. That is to say, you need to grant the ServiceRoleForTls role permission for TLS to access and write resources. If you have not authorized yet, TLS will guide you through the authorization process when you create a trace instance in the console. We recommend using Volcanoengine main account. For details, see Cross-service access authorization.
- After you create a trace instance, TLS automatically creates a corresponding topic to store related trace data. This topic occupies the quota of the Volcanoengine account. For the default configuration of this log topic, see Notice.
Steps
- Log in to TLS console.
- Select the region where log service is located from the top navigation bar.
- In the left navigation bar, select Legacy log application > Trace storage.
- On the Trace storage page, click Create trace instance.
- In the Create trace instance dialog box, configure the following parameters, and then click Create.
- ParametersDescriptionParametersDescriptionFile system nameIt is the name of the trace instance. After creation, the instance name can not be modified.Instance descriptionDescription of the trace instance The following requirements must be met:
- Unsupported characters: <>, ', \\, \\\\ and all emoji symbols.
- Length must be between 0 and 64 characters.
Log projectThe project is used for storing data related to the trace instance.Advanced settings switchWhen enabled, you can set up advanced configurations such as auto-splitting and log storage period.- Auto split:
- Once enabled, if data volume exceeds existing shard capacity for 5 consecutive minutes, shards split automatically to increase the number of shards.
- After enabling auto-splitting, you need to set maximum shards. The supported shard number ranges from 1 to 256. If the maximum number of splits is less than or equal to the number of log shards, auto-splitting is not available.
- Log storage time configuration:
- Set log storage period as you need. For log storage types and period requirements, see Storage types.
Next steps
Based on your business needs, you can see Access methods to select appropriate access solution for trace data.
Last updated: 2026.04.24 16:21:39
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
