While developing an application, we always incorporate a feature in our code that can direct us what went wrong if the application fails to run normally. This feature is nothing but logging. The more work you do with logging, the less work you have to do with fixing the application issue. We keep all logging information in a text format file, called a log file. This file captures all the details such as startup of a server, all user activities, names of classes, methods, timestamp, occurred exceptions with stack trace etc. Moreover, it depends on us what all information we require in the log file. Sometimes, these log files become larger in size and finding the exact issue manually becomes
Tag: microservices logging
How to Implement Distributed Logging Tracing using Sleuth Zipkin
In Microservices Architecture based Applications, there are multiple services which interact with each other. In order to serve a client request, one request may involve multiple microservices call to get the response. If any exception occurs or any latency issue appears during such calls, then how will we identify the root cause of the issue? Of course, we will make use of Spring Cloud Sleuth & Zipkin to support distributed logging & Tracing. Therefore, we are going to learn about 'How to implement Distributed Logging Tracing using Sleuth Zipkin' and related concepts accordingly. If we are working on a Standard application, we can implement logging by adding one log file to identify any exception or other issues like response timings or
