TLSExporter reports span data to the Volcengine TLS log service over OTLP (HTTP). Data is organized by TLS topic, which suits centralized storage, long-term retention, and cross-service trace analysis.
When to use
- You want your agent’s execution traces stored centrally in the Volcengine TLS log service;
- You need long-term retention and compliance/audit trails for trace data;
- You want to observe traces with TLS alerting and analysis capabilities.
Usage
Connecting to TLS is usually two steps: create a log project and tracing instance with theVeTLS client, then report data with TLSExporter.
config is omitted, topic_id fetches the tracing topic ID automatically by default:
Parameters
Constructor parameters
TLSExporter carries its connection parameters in the config field of type TLSExporterConfig; when omitted, each field is read automatically from the corresponding environment variable.
TLS connection config
config is a TLSExporterConfig; each field defaults from TLSConfig and Volcengine credentials, with the following environment variables:
When
topic_id is not provided via OBSERVABILITY_OPENTELEMETRY_TLS_SERVICE_NAME, the exporter calls VeTLS to fetch the tracing topic ID automatically, so valid Volcengine credentials (VOLCENGINE_ACCESS_KEY and VOLCENGINE_SECRET_KEY) are required.Environment variables
Agent attach the TLS exporter automatically from an environment variable, without constructing it explicitly: