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 ServiceProduct NewsProduct announcementTLS Architecture upgrade notification
Copy page
Download PDFProduct announcement
TLS Architecture upgrade notification
Copy pageDownload PDFTLS Architecture upgrade notification
To enhance service performance and improve product stability, TLS will gradually upgrade the product backend service architecture for all users in the near future.
Upgrade content
The new generation architecture 2.0 of Volcano Engine's self-developed observable storage engine—TLS—has been officially released. After extensive refinement through practical use in multiple ByteDance applications, it delivers enhanced query performance and more comprehensive query analysis capabilities.
- Petabyte-level elastic log writing supports large-scale data storage and efficient data writing.
- Query tens of billions of logs within seconds to enable rapid data processing and analysis.
- Supports more than 200 SQL functions, providing enhanced data analysis and processing capabilities.
- Supports associated queries across multiple data sources, making it easy for you to perform comprehensive analysis.
- More comprehensive query analysis features, including phrase queries, index rebuilding, and more, to improve query efficiency and accuracy.
Upgrade process
Effective immediately, users who enable Volcengine TLS for the first time will, by default, use the new architecture of TLS 2.0. Existing users will gradually be upgraded to the TLS 2.0 new architecture. During the upgrade process, a small amount of data may be consumed more than once in scenarios where the Kafka protocol is used. After the upgrade is completed, you will receive an internal message notification confirming the successful upgrade to the new architecture.
Upgrade impact
The upgrade process is seamless for Volcengine users. However, a very small number of query and analysis syntax incompatibilities may cause the same query and analysis statements to return inconsistent query and analysis results after an upgrade. If you are using syntax such as fuzzy query, it is recommended to consult the product documentation and adjust the query and analysis statements you are using to avoid changes in the meaning of the syntax from affecting log query and analysis results.
If you have any questions or issues, please contact us via the ticketing system. Thank you for your support and understanding of VolcEngine!
Last updated: 2025.10.11 16:12:25
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
