Docs

Torch Log Service

LogCollector collection

Create anonymous identifiers to collect logs without AKSK

VolcanoEngine Torch Log Service (TLS) provides multiple log collection methods, such as LogCollector and SDK. When using LogCollector to collect logs, you can generate anonymous identifiers in the TLS console and add them to LogCollector startup parameters to enable AK/SK-free log collection.

An anonymous identifier is unique within each account and can be viewed multiple times after generation. To replace this identifier, contact customer support.

If the anonymous identifier is leaked, unauthorized write access may occur. To deactivate this identifier, contact customer for support.

Notice

This feature is currently available for invitation testing. To apply for the allowlist, contact technical support via the ticketing system.

This section describes how to generate an anonymous identifier in the TLS console and add it to LogCollector startup parameters.

Prerequisites

The LogCollector version must be V2.2.7 or later version.

Steps

1 Generate an anonymous identifier

Select the region where torch log service is located from the top navigation bar.

In the left navigation bar, select Resource management > Authentication management.

Click Generate anonymous identifier, check the confirmation prompt, and then click Confirm to obtain the anonymous identifier.

2 Start LogCollector and add the anonymous identifier

Download the LogCollector installation script. For details, see .

Run the following command to install and start LogCollector.

For example, join the host group with LogCollector using the Host identification type.

sudo ./logcollector.sh install --region {region} --endpoint {endpoint} --endpoint_strategy {endpoint_strategy} --anonymous_identities {anonymous_identities} --label {label}

Partial parameter descriptions:

Parameters	Required	Example value	Description
endpoint	Yes	https://tls-cn-shanghai.volces.com	Connection domain name for TLS. For supported domain names, see Service regions. If endpoint_strategy is specified, then endpoint must be the public address.
endpoint_strategy	No	private_first	Priority order for TLS service address connections. public_first: Access the public network address first. If the public network is not available, try the private network and internal network addresses in order. private_first: Access the private network address first. If the private network is not available, try the internal and public network addresses in order. inner_first: Access the internal network address first. If the internal network is unreachable, try the private and public network addresses in order. Empty: Only access the specified connection domain name. If the specified connection domain name is not available, an error will be reported.
anonymous_identities	Yes	2100685862@AA******tU=	Anonymous identifier for TLS, see 1 Generate an anonymous identifier.

3 Log collection

Once LogCollector is configured, you can collect logs without AK/SK. For log collection instructions, see Collection overview.

Last updated: 2026.03.25 18:13:42