Have a look at some of the content here :
1) Develop using Splunk
2) Integrate Splunk data
3) Build Big Data applications
Walk through the stack traces from Java applications to do root cause analysis on nested exceptions. Observe "home grown" classes, and their place in the stack trace. This can help ascertain whether the observed issue is new or a regression.
Have a look at some of the content here :
1) Develop using Splunk
2) Integrate Splunk data
3) Build Big Data applications
A few presentations you might like to read / watch :
Splunk your applications logs, the build logs. Track the error/warn/exceptions and debug messages for your features. Allow the developers to correlate system performance of the builds with QA tests...