Torch Log Service
Torch Log Service
Torch Log Service
Document
Product News
Product Overview
Product Billing
User Guide
TLS Agent
AgentLoop
Resource management
Host group
Data collection
LogCollector collection
Introduction to LogCollector
Installation and upgrade
Collect host logs
Collect container logs
LogCollector plugins
Manage LogCollector
general reference
Data import
Cloud product log collection
TOS log collection
DBW log collection
VPN Log collection
VKE log collection
CLB log collection
CloudTrail log collection
CFW log collection
NTA log collection
ALB log collection
APMPlus log collection
veFaaS log collection
VPC log collection
veImageX log collection
TrafficRoute DNS log collection
DDoS log collection
WAF log collection
DCDN log collection
Multi-cloud security platform log collection
APIG log collection
Machine learning task log collection
CR log collection
Volcano Ark application lab log collection
FileNAS log collection
LLM Application Firewall Service log collection
vePFS log collection
Cloud security center log collection
EFS log collection
Data storage
Query and analysis
Configure log indexes
Query log
Analyze logs
Query and analyze logs using third-party tools
Associate external data source for log query
SQL function
SQL syntax
Visualization
Query and analysis charts
Summaries of query and analysis charts
Create dashboard
Use dashboard
Add dashboard filters and variables
Use other systems to analyze logs
Log application
Log applications for product observability
Log applications for large models observability
Coding Agent log app
ModelProvider log app
No-coding Agent log app
Log applications for basic service monitoring
Data processing
Data transformation
Syntax and functions
Global operation function
expression function
Data processing best practices
general reference
Data write processor
Data consumer processor
Data consumption and shipping
Ship logs to TOS
Ship logs to Kafka
Ship logs to Splunk
Alarm
Alarm policy
Alarm notification content
Alarm notification content template
alarm notification channel
Tracing service
Monitor Log Service
API reference
Project management API
Topic management API
Shard management API
Index management API
Log management API
Host group management API
Collection configuration management API
Data import API
Data processor API
Data transformation API
Data backflow API
SQL analysis API
Alarm management API
Consumer group management API
Kafka protocol consumption API
Tag management API
Trace storage API
Account management API
SDK reference
Go SDK
Java SDK
Python SDK
iOS SDK
C++ SDK
CLI reference
Best practices
Data collection
Query and analysis
permission management
Consumption and delivery
Visualization
Alarm
FAQs
Billing and cost FAQ
Data collection FAQ
Data storage FAQ
Index configuration FAQ
Query and analysis FAQ
Scheduled SQL tasks FAQ
Alarm FAQ
- Documentation
Torch Log ServiceSDK referenceJava SDKUse TLS SDK for Java to write logs
Copy page
Download PDFJava SDK
Use TLS SDK for Java to write logs
Copy pageDownload PDFUse TLS SDK for Java to write logs
Java Producer sends log data quickly in massive data scenarios. This topic offers sample code that demonstrates how to use Java Producer to collect log data.
Before you begin
- Install TLS SDK for Java. For more information, refer to Install TLS SDK for Java.
- Add environment variables such as VOLCENGINE_ACCESS_KEY_ID. For information on how to configure environment variables, refer to Configure identity authentication.
warning
We recommend that you use environment variables to dynamically get identity authentication information such as Volcano Engine AccessKey. Otherwise, hard-coded AccessKey information leads to data security risks.
Writing log data
Scenario description
This topic offers sample code that demonstrates how to write log data to TLS using the SDK. TLS SDK for Java supports the following methods to write logs:
Method | Description |
Method | Description |
PutLogs | Not recommended. TLS allows you to call PutLogs to upload logs using synchronous requests. If you use PutLogs to upload logs, we recommend that you aggregate multiple log entries and call PutLogs once. Compared with uploading log entries one by one, log aggregation can improve throughput and avoid rate limiting. |
Producer | Recommended. In the actual production environment, use Java Producer to write log data to improve efficiency. Java Producer sends log data quickly in massive data and high-concurrency scenarios. Go Producer features asynchronous sending, high performance, retry on failure, and graceful shutdown. |
Sample code
The following sample code demonstrates how to use Java Producer to collect log data.
package com.volcengine.example.tls.demo;
import com.volcengine.model.tls.LogItem;
import com.volcengine.model.tls.exception.LogException;
import com.volcengine.model.tls.producer.CallBack;
import com.volcengine.model.tls.producer.ProducerConfig;
import com.volcengine.model.tls.producer.Result;
import com.volcengine.service.tls.Producer;
import com.volcengine.service.tls.ProducerImpl;
import java.util.ArrayList;
import java.util.List;
public class Demo {
public static void main(String[] args) throws LogException, InterruptedException {
// When you initialize the client, we recommend that you use environment variables to dynamically get identity authentication information such as Volcano Engine AccessKey. Otherwise, hard-coded AccessKey information leads to data security risks.
// If you use Security Token Service (STS), use a temporary AccessKey ID and AccessKey secret, and set VOLCENGINE_TOKEN. If you do not use STS, leave VOLCENGINE_TOKEN empty.
ProducerConfig producerConfig = new ProducerConfig(System.getenv("VOLCENGINE_ENDPOINT"), System.getenv("VOLCENGINE_REGION"),
System.getenv("VOLCENGINE_ACCESS_KEY_ID"), System.getenv("VOLCENGINE_ACCESS_KEY_SECRET"), System.getenv("VOLCENGINE_TOKEN"));
// Instantiate and start the producer.
Producer producer = new ProducerImpl(producerConfig);
producer.start();
// Specify topicId, source, and filename as needed.
String topicID = "your-topic-id";
String source = "your-log-source";
String filename = "your-log-filename";
// If a callback is not required, pass null for the callback in sendLogV2 and sendLogsV2 offered by Java Producer.
CallBack callBack = new CallBack() {
@Override
public void onComplete(Result result) {
System.out.println("producer result:" + result);
}
};
LogItem item;
// Call sendLogV2 offered by Java Producer to submit one log entry at a time.
item = new LogItem();
item.setTime(System.currentTimeMillis());
item.addContent("key1", "value1");
item.addContent("key2", "value2");
producer.sendLogV2("", topicID, source, filename, item, callBack);
// Call sendLogsV2 offered by Java Producer to submit multiple log entries at a time.
List<LogItem> items = new ArrayList<>();
for (int i = 1; i <= 1000; i++) {
item = new LogItem();
item.setTime(System.currentTimeMillis());
item.addContent("key1", "value1-" + i);
item.addContent("key2", "value2-" + i);
items.add(item);
}
producer.sendLogsV2("", topicID, source, filename, items, callBack);
// Close the producer.
producer.close();
}
}
Related documents
- After you use the SDK to send an API request, the server returns a response. If the response contains a non-200 status code, the API call fails. To view the error code and error message, refer to API reference.
- For more information on Java Producer, refer to Java Producer.
- To get the complete sample code of uploading logs using Java Producer, refer to TLS Java SDK Demo on GitHub.
Last updated: 2025.10.11 16:44:07
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
