TLS supports shipping collected server-side log data to the Volcanoengine Message Queue for Kafka. This allows various client applications to consume log data. This topic explains the basic concepts and billing rules for the ship logs to Kafka feature.

Background information

The Volcanoengine Message Queue for Kafka is a distributed message middleware service built on Apache Kafka. TLS supports shipping logs to Message Queue for Kafka, making it suitable for big data consumption, real-time stream processing, and related scenarios. Once you enable this feature, TLS sends the log data from the specified log topic to Message Queue for Kafka in the chosen format. The ship logs to Kafka feature supports shipping historical log data, which means all logs retained within the specified period can be sent to the Kafka instance.

In addition, TLS provides service logs with the log shipping feature. With service logs, you can view the progress and status of shipping tasks. For more details, see Service log overview.

Limits

Limit items

Description

Limit items	Description
Account	Cross-account shipping logs for VolcanoEngine require cross-account shipping permissions.
Region	Cross-region log shipping is not supported. That is to say, log topic and Kafka instance must be in the same region.
Resource quota	Each log topic can create 10 Kafka shipping configurations.
Log size	The log size of a single shipping task can not exceed 10MB; otherwise the shipping may fail.

Billing description

Shipping logs to Kafka involves TLS log shipping fees, as well as Kafka instance specifications and storage costs.

Log shipping costs are calculated based on the amount of logs delivered. For details, see TLS Billing items based on pay-by-feature mode.

For the fees of each Volcanoengine Kafka instance type, see Billing items.

Last updated: 2026.05.06 11:10:34

Public security network record in Beijing: No. 11010802032137