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 BillingBilling itemsBilling items based on pay-by-ingested-data mode
Copy page
Download PDFBilling items
Billing items based on pay-by-ingested-data mode
Copy pageDownload PDFBilling items based on pay-by-ingested-data mode
This topic introduces the billing items and calculation formulas for pay-by-ingested-data billing mode of Torch Log Service (TLS).
Price details
Notes
- TLS supports changing the billing mode. However, only the change from pay-by-ingested-data mode to pay-by-feature mode is supported.
- Under pay-by-ingested-data mode, data transformation (cross-region data transformation incurs cross-region transfer fees) and log shipping do not generate extra fees but have quota limits. If the data exceeds the quota, fees are generated based on pay-by-feature mode.
- Quota limitsQuota requirementsQuota limitsQuota requirementsData transformation volumeThe free data transforming volume that each topic supports per month is 100TiB.Data shipping volume
- Basic edition: The free data shipping volume supported for each topic per month is 100 TiB.
- Advanced edition: The free data shipping volume supported for each topic per month is 10 TiB.
Data consumption volumeThe free data consumption volume that each topic supports per month is 100 TiB.
Billing item
Storage space
TLS calculates the storage volume at every full hour (UTC+8). The daily storage volume is the average of the hourly storage volumes that are recorded over 24 hours of the day.
The retention period of log data and index data is the log storage period that you set in log topic. Log data that exceeds retention period is no longer counted in storage volume. TLS deletes expired data at the next full hour.
TLS automatically compresses data once the data is collected. The compression ratio is 20%~30%.
Billing by data write volume only considers data stored for more than 30 days. Storage volume is calculated daily. For details, see Storage billing scenario.
Data volume calculation methods are categorized into the following two types:
- Calculated based on compressed raw data volume: log storage space, infrequent access-log storage space, archive-log storage space.
- Calculated based on uncompressed raw data volume: index storage space, infrequent access-index storage space, archive-index storage space.
Billing item | Description | Formula |
Billing item | Description | Formula |
Log storage space | After TLS collects data, the corresponding data volume (compressed) occupies standard storage space and generates accordingly. For example, if the collected raw data volume is 10 GiB with a compression rate of 20%, the daily storage volume for this data is 2 GiB. | Daily storage volume (GiB) × price per GiB |
Infrequent access-log storage space | The data volume (compressed) occupies IAS storage space and generates fees accordingly. When IAS storage is enabled, log storage converts to IAS storage if log storage time exceeds the standard storage period. Accordingly, fees are calculated based on IAS billing standard. | Daily storage volume (GiB) × price per GiB |
Archive-log storage space | The data volume (compressed) occupies archive storage space and generates fees accordingly. When archive storage is enabled, log storage converts to archive storage if log storage time exceeds the standard storage period or IAS storage period. Accordingly, fees are calculated based on archive billing standards. | Daily storage volume (GiB) × price per GiB |
Index storage space | After the data is indexed, index data volume (uncompressed) occupies standard storage space and generates fees accordingly. For example, if the original collected data volume is 10 GiB and only full-text indexing is enabled, the daily index storage size for this data is 10 GiB. | Daily storage volume (GiB) × price per GiB |
IAS-index storage space | After data is indexed, indexed data volume (uncompressed) occupies infrequent access storage(IAS) space and generates fees. When IAS storage is enabled, log storage converts to IAS storage if log storage time exceeds the standard storage period. Accordingly, fees are calculated based on IAS billing standard. | Daily storage volume (GiB) × price per GiB |
Archive - index storage space | After data is indexed, indexed data volume (uncompressed) occupies archive storage space and generates fees. When archive storage is enabled, log storage converts to archive storage if log storage time exceeds the standard storage period or IAS storage period. Accordingly, fees are calculated based on archive billing standards. | Daily storage volume (GiB) × price per GiB |
Traffic
Data volume calculation methods are categorized into the following two types:
- Calculates based on compressed raw data volume: public network read traffic and cross-region transmission traffic.
- Calculates based on uncompressed raw data volume: raw write traffic.
Billing item | Description | Formula |
Billing item | Description | Formula |
Raw write traffic | When uploading data to TLS, the raw write data is calculated based on the amount of data transmitted (uncompressed). | Daily total raw write traffic (GiB) × unit price per GiB |
Public network read traffic | When the data are collected through TLS public network domain name, the corresponding data volume generates downstream traffic fees.
| Daily total public network read traffic (GiB) × unit price per GiB |
Cross-region data transmission traffic | Traffic fees generated by the volume of data transformed (compressed) during cross-region transfer in data transformation. | Daily cumulative transmission data volume (GiB) × unit price per GiB |
Last updated: 2026.08.24 11:43:35
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
