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 overview
Copy page
Download PDFProduct Billing
Billing overview
Copy pageDownload PDFBilling overview
This topic introduces the main billing information for Torch Log Service(TLS), including billing methods and billing cycles.
Billing method
TLS adopts pay-as-you-go billing method. You can use it first and pay later. That is to say, TLS charges based on your actual usage. There is no refund involved.
The billing model for TLS calculates charges at the topic level and supports pay by feature and pay by ingested data.
Billing method | Basic concepts | Comparison of advantages |
Billing method | Basic concepts | Comparison of advantages |
Pay by feature | Charges are based on product feature module. The billing items are divided into three categories: storage space, traffic, and other items. These include 14 subcategories such as internal network read traffic, data transformation traffic, log storage space, and log shard count. | The billing items are more detailed and flexible. You can pay separately for needed functions to optimize cost control. It is suitable for scenarios with diverse business and flexible functions. |
Pay by ingested data | Charges are based solely on the amount of data that is written. Billing items are classified into three types: ingested data fees for uploaded data, storage fees for stored data, and traffic fees for public network data reads. | No index traffic, intra-region data delivery/processing, shards count, or other billing items. Billing items are fewer and billing method is simpler. Plus, a 30-day free storage quota is included. It is suitable for scenarios with dynamic business data fluctuations, temporary resource surges, data processing, long-term data retention, and data circulation. |
Billing cycle
The TLS calculates the usage of all resources on a daily basis and settles the fees based on resource usage. The fees generated on the current day will be settled at 00:00 the next day.
Billing item
Each billing item in TLS is charged separately. For example, if you choose pay-by-feature mode, TLS charges based on the billing item for number of log shards after you configure shards. For detailed billing item descriptions, seeBilling items based on pay-by-feature mode.
Price details
Usage query
You can view the usage of billing resources in the following two ways.
- View the total usage of billing resources from the previous calendar day on the Overview page on Torch log service console.
- View billable resource usage through CloudMonitor. For details, see the documentation.View cloud monitoring data.
Bill query
Billing type | Description |
Billing type | Description |
Bill details | On Bill management > Bill details page, you can view specific bill information. For detailed steps, see Bill management. Description The extra specs column in the billing detail table displays the topic name and ID of the project to which the billing item belongs. It can be used to analyze all billing items generated by the target log topic. |
Split bills | On Bill management > Split bills page, you can select TLS in Product filter to view TLS split bills. For detailed steps, see Split bills. The split bills table records detailed information such as billing units, instance ID/name, extended fields, split item ID, split item name, usage, and price. |
Bills at project dimension | On Split bills page, you can use split item ID and split item name in the table to analyze the billing details of the target log project dimension.
|
Bills at topic dimension | Through the extra specs fields in the table on Spill bills, you can view and analyze billing details of the target log topic dimension. Extra specs: Displays the topic name and ID of the project to which the billing item belongs. |
FAQs
Last updated: 2026.07.21 17:50:26
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
