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 consumer groups to consume logs
Copy page
Download PDFJava SDK
Use TLS SDK for Java consumer groups to consume logs
Copy pageDownload PDFUse TLS SDK for Java consumer groups to consume logs
Torch Log Service (TLS) SDKs offer the ConsumerGroup feature that allows you to consume log data using consumer groups. This topic describes how to use TLS SDK for Java consumer groups to consume logs.
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.
Configuration description
When you use consumer groups to consume data, TLS automatically allocates shards to balance the consumption capability and progress of each consumer group. Therefore, you do not need to consider internal scheduling, load balancing among consumers, or failovers that may occur. Just focus on your business logic.
tip
TLS SDK consumer groups support automatically retrying failed requests and reporting the checkpoints. Therefore, you only need to focus on the business logic of handling LogGroupList generated after log data is consumed each time.
In TLS SDK for Java, the ConsumerConfig constructor returns the default config of a consumer group. In the config, specify basic information such as the endpoint, Region, AccessKey ID, and AccessKey secret, as well as the project ID, topic ID list, consumer group name, and consumer name.
In addition, you can use the setter method to set other ConsumerConfig parameters as needed. The following table describes the ConsumerConfig parameters:
Parameter | Type | Example | Description |
Parameter | Type | Example | Description |
maxFetchLogGroupCount | int | 100 | The maximum number of log groups when the consumer consumes log data each time. Default value: 100. Maximum value: 1000. |
heartbeatIntervalInSecond | int | 20 | The interval at which the consumer reports a heartbeat. Unit: seconds. |
dataFetchIntervalInMillisecond | int | 200 | The interval at which the consumer consumes log data. Unit: milliseconds. |
flushCheckpointIntervalInSecond | int | 5 | The interval at which the consumer uploads the consumption progress. Unit: seconds. |
consumeFrom | String | begin | The default consumer offset when the consumption starts. The value is consistent with that of From in the DescribeCursor API action. The parameter takes effect only when the consumer has not uploaded consumer offsets. |
orderedConsume | boolean | false | Whether to enable consumption in sequence. If enabled, the consumer consumes log data based on the parent-child relationship of shard splitting. For example, Shard 0 is split into Shard 1 and Shard 2, while Shard 1 is then split into Shard 3 and Shard 4. If the feature is enabled, log data is consumed in the sequence of (Shard 0) > (Shard 1, Shard 2) > (Shard 2, Shard 3, Shard 4). |
Sample code
The following sample code demonstrates how to use TLS SDK for Java to create a consumer group and consumers to consume logs.
package com.volcengine.example.tls.demo;
import java.util.ArrayList;
import java.util.List;
import com.volcengine.model.tls.consumer.ConsumerConfig;
import com.volcengine.model.tls.exception.LogException;
import com.volcengine.model.tls.pb.PutLogRequest;
import com.volcengine.service.tls.consumer.Consumer;
import com.volcengine.service.tls.consumer.ConsumerImpl;
import com.volcengine.service.tls.consumer.LogProcessor;
// Define a class to implement LogProcessor.
public class ConsumerDemo implements LogProcessor {
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.
ConsumerConfig config = new ConsumerConfig(System.getenv("VOLCENGINE_ENDPOINT"), System.getenv("VOLCENGINE_REGION"),
System.getenv("VOLCENGINE_ACCESS_KEY_ID"), System.getenv("VOLCENGINE_ACCESS_KEY_SECRET"), System.getenv("VOLCENGINE_TOKEN"));
// Specify your project ID.
config.setProjectID("your-project-id");
// Specify the topic ID list for consumption.
config.setTopicIDList(new ArrayList<String>(){{
add("your-topic-id");
}});
// Specify the name of the consumer group.
config.setConsumerGroupName("java-consumer-group");
// Specify the name of the consumer.
config.setConsumerName("java-consumer");
// Instantiate ConsumerImpl, and call consumer.start() to continuously consume log data.
Consumer consumer = new ConsumerImpl(config, new ConsumerDemo());
consumer.start();
// Call consumer.stop() to end consumption by the consumer group.
Thread.sleep(10000);
consumer.stop();
}
/**
Implement a process method to handle LogGroupList generated after log data is consumed each time as needed.
The following sample code prints each log entry that is consumed.
*/
@Override
public void process(String topicID, int shardID, PutLogRequest.LogGroupList logGroupList) {
System.out.println(topicID + " --- " + shardID);
System.out.println(logGroupList.getLogGroupsCount());
int count = 0;
List<PutLogRequest.LogGroup> logGroups = logGroupList.getLogGroupsList();
for (PutLogRequest.LogGroup logGroup: logGroups) {
List<PutLogRequest.Log> logs = logGroup.getLogsList();
for (PutLogRequest.Log log: logs) {
count++;
System.out.println("*** Count = " + count + " ***");
List<PutLogRequest.LogContent> logContents = log.getContentsList();
for (PutLogRequest.LogContent logContent: logContents) {
System.out.println(logContent.getKey() + ": " + logContent.getValue());
}
System.out.println();
}
}
}
}
Last updated: 2025.10.11 16:44:07
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
