This module provides a Logback appender which forwards Logback log events to the OpenTelemetry Log SDK.
Replace OPENTELEMETRY_VERSION
with the latest
release.
For Maven, add to your pom.xml
dependencies:
<dependencies>
<dependency>
<groupId>io.opentelemetry.instrumentation</groupId>
<artifactId>opentelemetry-logback-appender-1.0</artifactId>
<version>OPENTELEMETRY_VERSION</version>
</dependency>
</dependencies>
For Gradle, add to your dependencies:
implementation("io.opentelemetry.instrumentation:opentelemetry-logback-appender-1.0:OPENTELEMETRY_VERSION")
The following demonstrates how you might configure the appender in your logback.xml
configuration:
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<appender name="console" class="ch.qos.logback.core.ConsoleAppender">
<encoder>
<pattern>
%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n
</pattern>
</encoder>
</appender>
<appender name="OpenTelemetry"
class="io.opentelemetry.instrumentation.logback.appender.v1_0.OpenTelemetryAppender">
</appender>
<root level="INFO">
<appender-ref ref="console"/>
<appender-ref ref="OpenTelemetry"/>
</root>
</configuration>
In this example Logback log events will be sent to both the console appender and
the OpenTelemetryAppender
.
In order to function, OpenTelemetryAppender
needs access to an OpenTelemetry
instance. This must
be set programmatically during application startup as follows:
import io.opentelemetry.instrumentation.logback.appender.v1_0.OpenTelemetryAppender;
import io.opentelemetry.sdk.OpenTelemetrySdk;
public class Application {
public static void main(String[] args) {
OpenTelemetrySdk openTelemetrySdk = // Configure OpenTelemetrySdk
// Find OpenTelemetryAppender in logback configuration and install openTelemetrySdk
OpenTelemetryAppender.install(openTelemetrySdk);
// ... proceed with application
}
}
Settings can be configured in logback.xml
, for example:
<appender name="OpenTelemetry" class="io.opentelemetry.instrumentation.logback.appender.v1_0.OpenTelemetryAppender">
<captureExperimentalAttributes>true</captureExperimentalAttributes>
<captureMdcAttributes>*</captureMdcAttributes>
</appender>
The available settings are:
XML Element | Type | Default | Description |
---|---|---|---|
captureExperimentalAttributes |
Boolean | false |
Enable the capture of experimental log attributes thread.name and thread.id . |
captureCodeAttributes |
Boolean | false |
Enable the capture of source code attributes. Note that capturing source code attributes at logging sites might add a performance overhead. |
captureMarkerAttribute |
Boolean | false |
Enable the capture of Logback markers as attributes. |
captureKeyValuePairAttributes |
Boolean | false |
Enable the capture of Logback key value pairs as attributes. |
captureLoggerContext |
Boolean | false |
Enable the capture of Logback logger context properties as attributes. |
captureMdcAttributes |
String | Comma separated list of MDC attributes to capture. Use the wildcard character * to capture all attributes. |
|
numLogsCapturedBeforeOtelInstall |
Integer | 1000 | Log telemetry is emitted after the initialization of the OpenTelemetry Logback appender with an OpenTelemetry object. This setting allows you to modify the size of the cache used to replay the first logs. thread.id attribute is not captured. |