Docs

Volcano Engine Function as a Service

Trigger management

Creating TLS triggers

veFaaS can be integrated with TLS of Volcano Engine. You can create a TLS trigger. In this way, veFaaS will consume messages from the corresponding log topic as a consumer and pass the messages to the user function. This triggers code execution. This topic describes how to create TLS triggers.

Background information

Application scenarios

Perform ETL processing on massive log data. Through an event-driven mechanism and simple configuration, you can process event source data. This enriches the one-stop TLS capabilities of collection, processing, analysis, alert visualization, and delivery, and provides end-to-end solutions across cloud services.

Consumption rules

If a log topic has multiple shards, consumption order is not guaranteed. We recommend uploading logs in load-balancing mode.

The first consumption starts from the latest position by default.

Subsequent consumption starts from the offset by default.

Log data generated during a brief restart of the TLS trigger can still be consumed, but log data collected more than 2 hours after consumption interruption cannot be consumed.

Log data is retained on the TLS server side for 2 hours. It will be deleted after 2 hours or when the Kafka protocol consumption feature is disabled on the TLS side.

Prerequisites

TLS has been activated. A log project and log topic have been created in the region where the function resides, and log data has been collected. For detailed descriptions, see Getting started.

The Kafka consumption feature has been enabled for the specified log topic. For detailed instructions, see Enabling the Kafka consumption feature.

The access keys of Volcano Engine have been obtained: AccessKey ID (AK) and Secret Access Key (SK). We recommend using the access keys of an IAM user for authentication. Before you use an IAM user, make sure that an IAM user has been created under the Volcano Engine root user and permissions for consuming TLS resources (at least the tls:ConsumeLogs permission) have been granted to it. For detailed descriptions, see Access key usage guide and Permissions that can be granted to TLS.

The function must have completed at least one full release. For details, see Releasing functions.

Limits

You can create up to 20 triggers for each function.

After a TLS trigger is created, you cannot change the consumed log project and log topic.

Procedure

In the top navigation bar, select the target region.

In the function list, find the function for which you want to create a trigger and click its name.

On the function details page, click Create trigger on the Trigger tab.

In the Create trigger panel, specify the parameters as required.

Parameter	Description
Trigger type	In this scenario, select TLS.
Trigger name	Specify a custom name for the trigger. Trigger names cannot be repeated under the same function. The trigger name cannot be modified after being created.
Log project and Log topic	Select the Log project and Log topic to be consumed.
Number of retries	The maximum number of retries when a function has run errors, including user code errors and runtime errors. The default value is 100. Valid values: 0 to 100. The retry policy triggers retries at a fixed interval of 5 seconds.
Activate now	Whether to enable the Trigger while creating it. Only Trigger enabled will work properly.
Authentication	Enter the access keys of Volcano Engine (AK and SK) described in the prerequisites. warning We recommend using the access keys of an IAM user. The keys must include permissions related to TLS consumption (at least the tls:ConsumeLogs permission). The access key is used only for authentication. veFaaS does not store your key.
Description	Enter remarks as needed.

Click Confirm to create the TLS trigger.

After the trigger is created, you can view the information about the created TLS trigger on the Trigger tab of the current function.

What to do next

For the method of modifying the configurations of the TLS trigger, see Managing triggers.

For the method of monitoring the running status of the function, see Monitoring and logging.

TLS provides a visual O&M interface for Kafka protocol consumption, which enables you to view consumer group information, reset consumer offsets, and observe consumption progress. You can monitor the consumption details of the TLS trigger in the TLS console. For more details, see Consuming logs by using the Kafka protocol.

Last updated: 2026.08.19 14:06:06