JarCastingSpring Boot Contextual Logging
This project allows to configure Spring Boot logging on a per-request basis. Currently this project only supports Logback, the default logging framework in Spring Boot.
Versions
Multiple branches are maintained to support multiple Spring Boot versions. The following tables show the relation between the Spring Boot version and the Spring Boot Contextual Logging version.
| Spring Boot | Spring Boot Contextual Logging | Branch |
|---|---|---|
| 1.5.x | 1.0.x | 1.0.x |
| 2.0.x | 2.0.x | 2.0.x |
| 2.1.x | 2.1.x | 2.1.x |
| 2.2.x | 2.2.x | master |
Installation
- Add the following Maven dependency.
<dependency>
<groupId>com.github.timpeeters</groupId>
<artifactId>spring-boot-contextual-logging</artifactId>
<version>X.X.X</version>
</dependency>
Implementation details
ContextualLoggingLogbackFilter
The implementation relies on the use of a Logback TurboFilter.
TurboFilters are called every time a logging request is issued. They are called before the LoggingEvent is created. As such, TurboFilters are intended for high performance filtering of logging events.
This projects ContextualLoggingLogbackFilter extends the Logback TurboFilter abstract class and checks for the presence of a ContextualLoggingContext in the ContextualLoggingContextHolder. If a ContextualLoggingContext is present, it will use the state in the context to decide whether a log statement should be filtered or not. If no ContextualLoggingContext is present, the filter will return a FilterReply.NEUTRAL resulting in default Logback behavior.
RequestEvaluator
The RequestEvaluator interface is responsible for deciding whether contextual logging should be enabled for a given request or not.
The interface takes only one input parameter HttpServletRequest and returns a boolean indicating whether contextual logging should be enabled or not.
boolean shouldEnable(HttpServletRequest request);
By default a HeaderRequestEvaluator is created that looks for the presence of a request header with the name Contextual-Logging. If the header is present, contextual logging is enabled.
@Bean
@ConditionalOnMissingBean
@ConditionalOnWebApplication
public RequestEvaluator requestEvaluator() {
return new HeaderRequestEvaluator();
}
It is possible to register you own RequestEvaluator using different logic. E.g. evaluating the presence of a request parameter.
@Bean
public RequestEvaluator requestEvaluator() {
return request -> request.getParameter("debug") != null;
}
LogLevelSource
When contextual logging is enabled for a request, the LogLevelSource interface will determine what log levels should be applied.
The interface takes only one input parameter HttpServletRequest and returns a map with the logger name as key and the log level as value.
Map<String, LogLevel> getLogLevels(HttpServletRequest request);
By default two implementations of the interface are shipped: HeaderLogLevelSource and PropertiesLogLevelSource.
HeaderLogLevelSource
Retrieves the log levels from the HTTP headers of the request. This implementation is enabled by default.
Configuration:
contextual.logging.enabled=true
contextual.logging.log-level-source=header
E.g. the following headers will result in info level for all loggers and debug level for the com.github logger.
GET / HTTP/1.1
Host: localhost
ContextualLogging: root=info
ContextualLogging: com.github=debug
PropertiesLogLevelSource
Retrieves the log levels from the Spring Environment.
Enabled using the following configuration:
contextual.logging.enabled=true
contextual.logging.log-level-source=properties
contextual.logging.level.root=info
contextual.logging.level.com.github=debug