Docs

Torch Log Service

veFaaS log collection

Collect veFaaS logs

This topic describes the features and collection methods related to veFaaS logs.

Features overview

veFaaS (Volcano Engine Function as a Service, veFaaS) is an event-driven, fully managed serverless computing platform. You can quickly create and deploy functions, integrating cloud middleware and database products as needed. It shields underlying resources and operational details, ensuring elastic and highly reliable business operations. This helps enterprises significantly reduce development and maintenance costs, maximizing the benefits of cloud computing.

The function service veFaaS integrates with Volcano Engine TLS to provide log management features. Simply enable the log feature when creating a function, and you can view function runtime logs in the function service console.

The related configuration is as follows:

Configuration	Description
Log type	Function invocation logs (stdout, stderr).
Log storage location	After enabling the log function in veFaaS, TLS automatically creates projects and log topics. For details on managing log resources, see Manage veFaaS log resources. Project: tls-vefaas or custom project Log topic: tls-vefaas-logstore or custom topic
Log storage period	The default period is 7 days.
Log shards	One shard is preset. Auto split for log topic shards can be enabled. When write traffic increases, shards will split to meet data write requirements.
Index settings	Configure indexes are automatically configured.
Log fields	For a detailed list of log fields, see veFaaS log fields.

Collect veFaaS logs

For usage limits and steps to enable veFaaS log collection in TLS, see Enable log delivery.

veFaaS log fields

The veFaaS logs are written to TLS individually, with each log record using a fixed key:value format.

Field name	Field description
__path__	The file name collected for logs. For internal-system use only and may be ignored by users.
__source__	The source IP address collected for logs. For internal-system use only and may be ignored by users.
content	Log content.
function_id	The unique identifier for the function, which is shown as Function ID on the configuration tab.
function_name	Function name.
log_type	Log output types, including stdout and stderr. The function service collects log information from the stdout and stderr fields in your code.
pod_name	The function instance (Pod) name. For internal-system use only and may be ignored by users.
revision_number	Function version number.

Last updated: 2026.08.12 18:45:18