Presentation section from Splunk Live content

1. SplunkJavaLogging
Damien Dallimore
Developer Evangelist

2. Copyright©2013,SplunkInc.
Background
2
• Sometimes you can’t deploy a Splunk Forwarder to collect logs,
although this is certainly a best practice
• Sometimes you have disk constraints for writing logs
• Wouldn’t it be nice to send your log events from your code directly to
Splunk ?
• Sure , Splunk can eat any text logs , but we should be educating our
developers about the value in best practice semantic logging

3. Copyright©2013,SplunkInc.
SplunkJavaLogging
3
• A logging framework to allow developers to as seamlessly as possible
integrate Splunk best practice logging semantics into their code
• Transport log events to Splunk directly from your code
• Custom handler/appender implementations(REST and Raw TCP) for
common Java logging frameworks .
• LogBack
• Log4j (Log4j2 coming also)
• java.util.logging
• Utility classes for formatting log events
• Configurable in memory buffer to handle network outages

4. Copyright©2013,SplunkInc.
Developers just log as they are used to
4
2012-08-07 15:54:06:644+1200 name="Failed Login" event_id="someID" app="myapp" user="jane" somefieldname="foobar"
Better
A-HA

5. Copyright©2013,SplunkInc.
Logging Framework takes care of the Splunk transport
, REST or Raw TCP
5

6. Copyright©2013,SplunkInc.
<barf>Typical Java Stacktraces in logs</barf>
6

7. Copyright©2013,SplunkInc.
SplunkJavaLogging is your friend
7

8. Copyright©2013,SplunkInc.
Java Stacktraces in Splunk
8

9. Demo

10. Copyright©2013,SplunkInc.
Contact me
10
Email : ddallimore@splunk.com
Twitter : @damiendallimore
Skype : damien.dallimore
Github : damiendallimore
Splunkbase : damiend
Slideshare : http://www.slideshare.net/damiendallimore
Blogs : http://blogs.splunk.com/dev
Web : http://dev.splunk.com