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 GuideData consumption and shippingShip logs to TOSOverview of shipping logs to TOS
Copy page
Download PDFShip logs to TOS
Overview of shipping logs to TOS
Copy pageDownload PDFOverview of shipping logs to TOS
TLS supports periodically shipping collected server-side log data to TOS for long-term storage. This topic introduces the basic concepts and billing information for shipping logs to TOS.
Features overview
Torch Object Storage(TOS) is a distributed cloud storage service provided by Volcengine, offering massive storage capacity, strong security, low cost, ease of use, high reliability, and high availability. TLS supports shipping logs to TOS. After enabling this feature, TLS periodically processes, packages and ships log data to TOS buckets for storage. This solution is ideal for massive data long-term storage scenarios, offering low prices and high cost-effectiveness. Additionally, after log data is shipped to TOS, it can be consumed through offline computing or integration with other systems.
When shipping logs, you can configure the following shipping formats.
Data shipping formats | Description | Related documentation |
JSON format | After the data is shipped to TOS, it is saved in JSON format. As a common data format, JSON is suitable for various structured data scenarios. | |
JSONL format | After the data is shipped to TOS, it is saved in JSONL format. The configuration method is the same as that for JSON format. | |
CSV format | After the data is shipped to TOS, it is saved in CSV format. Fields in CSV files are separated by the specified separator. | |
Parquet format | After the data is shipped to TOS, it is saved in Parquet format.
|
In addition, TLS provides service logs with the log shipping feature. Using this, you can view the progress and status of shipping tasks. For more details, see Service log overview.
Billing description
If shipping logs to TOS, fees involve the costs for TLS and data storage costs for TOS.
- Log shipping costs are based on the amount of original logs delivered in JSON, JSONL, CSV, and Parquet formats. For details, see TLS Billing items based on pay-by-feature mode.
- After log data is shipped to TOS, data storage fees are generated. TOS data storage costs depend on storage usage and bucket type.
- If data compression is enabled, charges are based on the size of the compressed files.
- For price details of different bucket types, see Billing overview in TOS.
Limits
Limitations | | Description |
Account | | To deliver logs across Volcengine accounts, cross-account delivery permissions must be configured. |
Region | | Cross-region log delivery is not supported, that is, the log topic and the TOS bucket should be located in the same region. |
Field | | When delivering logs, the JSON format by default delivers all fields, including metadata fields such as __source__, while the CSV format allows you to configure the list of fields to be delivered. |
Resource quotas | Number of delivery configurations | Each log topic can have up to 10 TOS delivery configurations. |
| Query delivery tasks | You can only query delivery tasks triggered within the past 3 days. |
| Delivery intervals | The delivery time interval can be set to 60 to 900 seconds. |
| Size of delivered data | Delivered data packets must be between 5 and 256 MiB in size. |
Last updated: 2026.04.21 17:05:55
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
