 Okay, in this video we're going to talk about logging configuration for consolidated logging. So we have a couple things at play here and in my course on the Spring Boot microservices I do cover this in a lot more detail. The Spring Boot microservices are using are already configured to support this. So I'm just going to do a quick code review to show you the key pieces of the puzzle. So one thing here to get the JSON logging, we have this log stash by default Spring Boot uses log back for logging. So this is a log stash log back encoder basically takes the log data and creates JSON output. So that is one piece of the puzzle. Another important piece is Spring Cloud starter sleuth. Sleuth is a project that is going to add tracing elements. So you'll get a correlation ID passed through your services. So if service a call service B Spring Cloud sleuth is going to provide data in those logging calls so that we can see a trace ID to help us trace a call through multiple services. And I'm not going to get too far down that rabbit hole just wanted to point out these two components. Then finally the other piece that we need to be looking at is under resources. We have this log back Spring.XML a lot going on in this, but this is going to be setting up our logger specifically. We want a console appender and the encoder we're going to be using this logging event composite JSON encoder. So this is the primary piece that is going to be taking the log data and making a JSON object out of it. And that is important because we're going to be posting JSON to the console and then file beat is going to be picking up the console logs and shipping those two elastic search. So that's how everything fits together. I'm not going to be able to go through all of what's going on in here, but very important to have this. And then remember I mentioned the Spring Cloud sleuth component that is going to be this piece right here where we have the trace ID and the span ID and parent span ID. This is all going to be coming from data in the logging. So we'll be able to see those trace and span IDs of requests going across multiple services. So very, very important piece to work with as far as seeing the consolidated logging if we have multiple services involved, specifically what Spring Cloud sleuth is for us to see. So just to recap the two things that we need as far as dependencies is the log back encoder to get the JSON output and then the sleuth component that is going to give us the trace IDs. And then finally having this log back Spring.xml on the class path. So this is already built into the Spring Boot microservices and configured. So the services are doing effectively JSON logging. We can also see here the Spring property context, Spring app name. So each microservice has a unique Spring application name and that is included in the log as well.