Use this appender to log messages with logback to a Graylog2 server via GELF messages. Supports Additional Fields and chunking.
If you don't know what Graylog2 is, jump on the band wagon!
Simply add logback-gelf to your classpath. Either download the jar or if you're in maven land, the dependency details are below.
<dependencies>
...
<dependency>
<groupId>me.moocar</groupId>
<artifactId>logback-gelf</artifactId>
<version>0.12</version>
</dependency>
...
</dependencies>
Add the following to your logback.xml configuration file.
src/main/resources/logback.xml
<configuration>
<appender name="GELF" class="me.moocar.logbackgelf.GelfAppender">
<facility>logback-gelf-test</facility>
<graylog2ServerHost>localhost</graylog2ServerHost>
<graylog2ServerPort>12201</graylog2ServerPort>
<useLoggerName>true</useLoggerName>
<hostName>sendinghost</hostName>
<useThreadName>true</useThreadName>
<useMarker>true</useMarker>
<graylog2ServerVersion>0.9.6</graylog2ServerVersion>
<chunkThreshold>1000</chunkThreshold>
<messagePattern>%m%rEx</messagePattern>
<shortMessagePattern>%.-100(%m%rEx)</shortMessagePattern>
<additionalField>ipAddress:_ip_address</additionalField>
<additionalField>requestId:_request_id</additionalField>
<fieldType>_request_id:long</fieldType>
<staticAdditionalField>_node_name:www013</staticAdditionalField>
<includeFullMDC>true</includeFullMDC>
</appender>
<root level="debug">
<appender-ref ref="GELF" />
</root>
</configuration>
If you're using groovy configuration, checkout the logback.groovy example.
- facility: The name of your service. Appears in facility column in graylog2-web-interface. Defaults to "GELF"
- graylog2ServerHost: The hostname of the graylog2 server to send messages to. Defaults to "localhost"
- graylog2ServerPort: The graylog2ServerPort of the graylog2 server to send messages to. Defaults to 12201
- useLoggerName: If true, an additional field call "_loggerName" will be added to each gelf message. Its contents will be the fully qualified name of the logger. e.g: com.company.Thingo. Defaults to false;
- useThreadName: If true, an additional field call "_threadName" will be added to each gelf message. Its contents will be the name of the thread. Defaults to false;
- graylog2ServerVersion: Specify which version the graylog2-server is. This is important because the GELF headers changed from 0.9.5 -> 0.9.6. Allowed values = 0.9.5 and 0.9.6. Defaults to "0.9.6"
- chunkThreshold: The maximum number of bytes allowed by the payload before the message should be chunked into smaller packets. Defaults to 1000
- hostName The hostname of the sending host. Defaults to getLocalHostName()
- useMarker: If true, and the user has used an slf4j marker (http://slf4j.org/api/org/slf4j/Marker.html) in their log message by using one of the marker-overloaded log methods (http://slf4j.org/api/org/slf4j/Logger.html), then the marker.toString() will be added to the gelf message as the field "_marker". Defaults to false;
- messagePattern: The layout of the actual message according to PatternLayout. Defaults to "%m%rEx"
- shortMessagePattern: The layout of the short message according to PatternLayout. Defaults to none which means the message will be truncated to create the short message
- additionalFields: See additional fields below. Defaults to empty
- fieldType: See field type conversion below. Defaults to empty (fields sent as string)
- staticAdditionalFields: See static additional fields below. Defaults to empty
- includeFullMDC: See additional fields below. Defaults to false
Additional Fields can be added very easily. Let's take an example of adding the ip address of the client to every logged message. To do this we add the ip address as a key/value to the slf4j MDC (Mapped Diagnostic Context) so that the information persists for the length of the request, and then we inform logback-gelf to look out for this mapping every time a message is logged.
-
Store IP address in MDC
// Somewhere in server code that wraps every request ... org.slf4j.MDC.put("ipAddress", getClientIpAddress()); ... -
Inform logback-gelf of MDC mapping
... <appender name="GELF" class="me.moocar.logbackgelf.GelfAppender"> ... <additionalField>ipAddress:_ip_address</additionalField> ... </appender> ...
The syntax for the additionalFields in logback.groovy is the following
additionalFields = [<MDC Key>:<GELF Additional field name>, ...]
where <MDC Key> is unquoted and <GELF Additional field name> is quoted. It should also begin with an underscore (GELF standard)
If the property includeFullMDC is set to true, all fields from the MDC will be added to the gelf message. Any key, which is not
listed as additionalField will be prefixed with an underscore. Otherwise the field name will be obtained from the
corresponding additionalField mapping.
If the property includeFullMDC is set to false (default value) then only the keys listed as additionalField will be
added to a gelf message.
Use static additional fields when you want to add a static key value pair to every GELF message. Key is the additional field key (and should thus begin with an underscore). The value is a static string.
E.g in the appender configuration:
<appender name="GELF" class="me.moocar.logbackgelf.GelfAppender">
...
<staticAdditionalField>_node_name:www013</staticAdditionalField>
...
</appender>
...
You can configure a specific field to be converted to a numeric type. Key is the additional field key (and should thus
begin with an underscore), value is the type to convert to. Currently supported types are int, long, float
and double.
<appender name="GELF" class="me.moocar.logbackgelf.GelfAppender">
...
<fieldType>_request_id:long</fieldType>
...
</appender>
...
logback-gelf will leave the field value alone (i.e.: send it as String) and print the stacktrace if the conversion fails.
- Development version 0.13-SNAPSHOT (current Git
master) - Release [0.12] on 2014-Nov-04
- Explicitly set Zipper string encoding to UTF-8 #41
- Release [0.11] on 2014-May-18
- Release [0.10p2] on 2014-Jan-12