Here are some articles I've written.
With a few minor configuration changes, and a fresh perspective on your logging practices, your Spring Boot application can easily benefit from the latest logging analysis tools.
You have fully embraced the world of Docker hosted containers, and no longer have the patience for local installations of "Enterprise" software that requires a developer account to download. Fortunately, there's a Splunk Enterprise Docker Image just for you. It even comes preconfigured with a 500M per day developer license. No account required!
Using Logstash Logback JSON Encoder with Maven: Search the JSON output by your Maven builds using Splunk.
Using Logstash Logback JSON Encoder with Maven: There are many benefits to logging the output of your Maven build to JSON.
You will have no doubt read about aspects and join points and pointcuts, and probably a lot more about AspectJ weaving vs Spring CGLIB Proxies and how to configure one or the other in Spring. It turns out that Aspect Oriented Programming is a very deep subject and that Java and Spring are a great place to make use of these concepts.
If you are using Splunk for logfile analysis, you should also be using a properly formatted output format that allows for the reliable transmission of key/value pairs from your application. JSON is perfect for this and Logstash has created a convenient Logback encoder for us to use.
What can I learn about my Spring MVC application by logging the Spring Framework? You have probably noticed that a lot of stuff goes scrolling by when you startup your Spring Boot application, including some decent looking ASCII art.
Simple Logging Facade for Java (SLF4J) is an easy to use framework that provides a "Simple" API layer between available logging APIs and your code. This provides a consistent way for your code to focus on providing the logging message, and not the details of how it is actually logged.