https://github.com/aliyun/aliyun-log-logback-appender
https://github.com/aliyun/aliyun-log-logback-appender
Last synced: 6 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/aliyun/aliyun-log-logback-appender
- Owner: aliyun
- License: apache-2.0
- Created: 2018-02-06T09:46:44.000Z (over 8 years ago)
- Default Branch: master
- Last Pushed: 2024-12-25T08:45:57.000Z (over 1 year ago)
- Last Synced: 2025-07-03T22:08:17.764Z (about 1 year ago)
- Language: Java
- Size: 154 KB
- Stars: 194
- Watchers: 15
- Forks: 66
- Open Issues: 39
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
- awesome-java - Aliyun Log Logback Appender
README
# Logback Appender
[](https://travis-ci.org/aliyun/aliyun-log-logback-appender)
[](/LICENSE)
[中文版README](/README_CN.md)
## Aliyun Log Logback Appender
Logback is intended as a successor to the popular log4j project. You can control the destination of the log through logback. It can be console, file, GUI components, socket, NT event log, syslog. You can control the output format for each log as well. You can control the generation process of the log through log level. The most interesting thing is you can complete the above things through a configuration file and without any code modification.
You can set the destination of your log to AliCloud Log Service through `Aliyun Log Logback Appender`, The format of the log in AliCloud Log Service is as follows:
```
level: ERROR
location: com.aliyun.openservices.log.logback.example.LogbackAppenderExample.main(LogbackAppenderExample.java:18)
message: error log
throwable: java.lang.RuntimeException: xxx
thread: main
time: 2018-01-02T03:15+0000
log: 2018-01-02 11:15:29,682 ERROR [main] com.aliyun.openservices.log.logback.example.LogbackAppenderExample: error log
__source__: xxx
__topic__: yyy
```
Field Specifications:
+ `level` stands for log level
+ `location` is logs's output position, can be disabled by configuration
+ `message` is the content of the log
+ `throwable` is exception of the log (this field will appear only if the exception is recorded)
+ `thread` stands for thread name
+ `time` is the log's generation time (you can configure it's format through timeFormat and timeZone)
+ `log` is custom log format (this field will appear only if you configure the encoder)
+ `__source__` is the log's source, you can specify its value in conf file
+ `__topic__` is the log's topic, you can specify its value in conf file
## Advantage
+ `Disk Free`: the generation data will be send to AliCloud Log Service in real time through network.
+ `Without Refactor`: if your application already use logback, you can just add logback appender to your configuration file.
+ `Asynchronous and High Throughput`: the data will be send to AliCloud Log Service asynchronously. It is suitable for high concurrent write.
+ `Context Query`: at server side, in addition to searching log with keywords, you can obtain the context information of original log as well.
## Supported Version
* logback 1.2.3
* aliyun-log-producer 0.3.8
* protobuf-java 2.5.0
## Configuration Steps
### 1. Adding the Dependencies in pom.xml
```
com.google.protobuf
protobuf-java
2.5.0
com.aliyun.openservices
aliyun-log-logback-appender
0.1.28
```
### 2. Modify the Configuration File
Take `logback.xml` as an example, you can configure the appender and logger related to AliCloud Log Services as follows:
```
your project endpoint
your accesskey id
your accesskey
your project
your logStore
your topic
your source
104857600
0
8
524288
4096
2000
10
100
50000
%d %-5level [%thread] %logger{0}: %msg
yyyy-MM-dd'T'HH:mmZ
UTC
true
true
${accessKeyId}
${accessKeySecret}
500
s
```
**Note**：
+ To prevent data loss when the process exits, please remember to add label `DelayingShutdownHook`.
+ The LoghubAppender will catch the exceptions in the process of running and put them into `BasicStatusManager`, you can obtain the exception information through `OnConsoleStatusListener` or other means. Reference: https://logback.qos.ch/access.html
## Parameter Description
The `Aliyun Log Logback Appender` provides following parameters.
```
# Specify the project name of your log services, required
project = [your project]
# Specify the logstore of your log services, required
logStore = [your logStore]
# Specify the HTTP endpoint of your log services, required
endpoint = [your project endpoint]
# Specify the account information of your log services, required
accessKeyId = [your accesskey id]
accessKeySecret = [your accessKeySecret]
# The upper limit log size that a single producer instance can hold, default is 100MB.
totalSizeInBytes=104857600
# If the producer has insufficient free space, the caller's maximum blocking time on the send method, defaults is 60 seconds. In order not to block the log printing thread, it is strongly recommended to set this value to 0.
maxBlockMs=0
# The thread pool size for executing log sending tasks, defaults is the number of processors available.
ioThreadCount=8
# When the size of the cached log in a Producer Batch is greater than or equal batchSizeThresholdInBytes, the batch will be send, default is 512KB, maximum can be set to 5MB.
batchSizeThresholdInBytes=524288
# When the number of log entries cached in a ProducerBatch is greater than or equal to batchCountThreshold, the batch will be send.
batchCountThreshold=4096
# A ProducerBatch has a residence time from creation to sending, defaulting is 2 seconds and a minimum of 100 milliseconds.
lingerMs=2000
# The number of times a Producer Batch can be retried if it fails to send for the first time, default is 10.
retries=10
# The backoff time for the first retry, default 100 milliseconds.
baseRetryBackoffMs=100
# The maximum backoff time for retries, default is 50 seconds.
maxRetryBackoffMs=50000
# Specify the topic of your log, default is "", optional
topic = [your topic]
# Specify the source of your log, default is host ip, optional
source = [your source]
# Specify time format of the field time, default is yyyy-MM-dd'T'HH:mmZ, optional
timeFormat = yyyy-MM-dd'T'HH:mmZ
# Specify timezone of the field time, default is UTC, optional
timeZone = UTC
# Whether to record the Location field, defaults to true, set it false if performance-sensitive
includeLocation = true
# Whether to include field message when encoder exists, defaults to true.
includeMessage = true
# option for maximum exception stack trace recording length. Exceeding this length will result in truncation. Defaults to 500, optional.
maxThrowable=500
# Specify ingest processor, default is "", optional
processor = [ingest processor]
# time precision for log uploaded to log service
timePrecision=s
# MDC fields capture configuration (appender can capture fields from logging MDC context and add them to log fields)
# Format:
# - "*" - capture all fields
# - "KEY1,KEY2" - only capture specified fields KEY1 and KEY2
# - "KEY1=name1,KEY2,KEY3=name3" - capture fields KEY1, KEY2, KEY3; rename KEY1 to log field name1, KEY3 to name3
# - "*,KEY1=name1" - capture all fields by default, rename KEY1 to log field name1
# Example: mdcFields=THREAD_ID=thread_id,MDC_KEY
# Example: mdcFields=*,traceId=trace_id,spanId=span_id
mdcFields = [your mdc fields]
```
## Custom CredentialsProvider
The logback-appender supports custom `CredentialsProvider`. By implementing the `CredentialsProvider` interface, you can implement advanced features yourself, such as dynamic rotation of AccessKey.
> Once a `CredentialsProvider` is provided, it's unnecessary to configure parameter for static credentials (AccessKeyId/AccessKeySecret/SecurityToken); the system will use the credentials fetched through the `CredentialsProvider` provided.
1. Defines a class, eg. `MyCredentialsProvider`, and implements the `CredentialsProvider` interface to support the dynamic updates of credentials. Make sure the implementation is thread-safe.
- For performance, it is recommended that method `getCredentials` caches credentials and refreshes them before expired.
```java
class MyCredentialsProvider implements CredentialsProvider {
@Override
public synchronized Credentials getCredentials() {
// fetch credentials and caches credentials
}
// constructor
MyCredentialsProvider(String param1, long paramField2) {}
}
```
2. Defines a class, eg. `MyBuilder`, and implements the `CredentialsProviderBuilder` interface.
- The method `getCredentialsProvider` should return a new instance of `CredentialsProvider` for each call.
```java
class MyBuilder implements CredentialsProviderBuilder {
@Override
public CredentialsProvider getCredentialsProvider() {
return new MyCredentialsProvider(param1, paramField2);
}
private String param1;
private long paramField2;
public void setParam1(String param1) {
this.param1 = param1;
}
public void setParamField2(long paramField2) {
this.paramField2 = paramField2;
}
}
```
3. Configure logback with xml file, set the class of `credentialsProviderBuilder` with the fully qualified name of your class, eg. `com.example.MyBuilder`, and pass any custom parameters.
```xml
hello
123
```
### Custom parameter
To pass in some custom parameters to the `MyBuilder` class, such as param1, paramField2, define the setter methods setParam1 and setParamField2 in the class first.
```java
class MyBuilder implements CredentialsProviderBuilder {
private String param1;
private long paramField2;
public void setParam1(String param1) {
this.param1 = param1;
}
public void setParamField2(long paramField2) {
this.paramField2 = paramField2;
}
// Omit other codes
}
```
Then configure logback with xml file, set the class of `credentialsProviderBuilder` with the fully qualified name of your class, eg. `com.example.MyBuilder`, and fill with custom parameters.
```xml
hello
123
```
## Sample Code
[LogbackAppenderExample.java](/src/main/java/com/aliyun/openservices/log/logback/example/LogbackAppenderExample.java)
[logback-example.xml](/src/main/resources/logback-example.xml)
## Contributors
[@lionbule](https://github.com/lionbule) [@zzboy](https://github.com/zzboy) made a great contribution to this project.
Thanks for the excellent work by [@lionbule](https://github.com/lionbule) [@zzboy](https://github.com/zzboy).