Tracing Micro Service Logs in Spring Boot

Last updated on May 30 2022
Amarjit Malik

Table of Contents

Tracing Micro Service Logs in Spring Boot

Most developers face difficulty of tracing logs if any issue occurred. This can be solved by Spring Cloud Sleuth and ZipKin server for Spring Boot application.

Spring Cloud Sleuth

Spring cloud Sleuth logs are printed in the following format −

[application-name,traceid,spanid,zipkin-export]

Where,

  • Application-name = Name of the application
  • Traceid = each request and response traceid is same when calling same service or one service to another service.
  • Spanid = Span Id is printed along with Trace Id. Span Id is different every request and response calling one service to another service.
  • Zipkin-export = By default it is false. If it is true, logs will be exported to the Zipkin server.

Now, add the Spring Cloud Starter Sleuth dependency in your build configuration file as follows −

Maven users can add the following dependency in your pom.xml file −

<dependency>   <groupId>org.springframework.cloud</groupId>   <artifactId>spring-cloud-starter-sleuth</artifactId></dependency>

Gradle users can add the following dependency in your build.gradle file −

compile(‘org.springframework.cloud:spring-cloud-starter-sleuth’)

Now, add the Logs into your Spring Boot application Rest Controller class file as shown here −

package com.tecklearn.sleuthapp; import java.util.logging.Level;import java.util.logging.Logger; import org.springframework.boot.SpringApplication;import org.springframework.boot.autoconfigure.SpringBootApplication;import org.springframework.web.bind.annotation.RequestMapping;import org.springframework.web.bind.annotation.RestController; @SpringBootApplication@RestControllerpublic class SleuthappApplication {   private static final Logger LOG = Logger.getLogger(SleuthappApplication.class.getName());   public static void main(String[] args) {      SpringApplication.run(SleuthappApplication.class, args);   }   @RequestMapping(“/”)   public String index() {      LOG.log(Level.INFO, “Index API is calling”);      return “Welcome Sleuth!”;   }}

Now, add the application name in application.properties file as shown −

spring.application.name = tracinglogs

The complete code for build configuration file is given below −

Maven – pom.xml

<?xml version = “1.0” encoding = “UTF-8”?><project xmlns = “http://maven.apache.org/POM/4.0.0”    xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”   xsi:schemaLocation = “http://maven.apache.org/POM/4.0.0    http://maven.apache.org/xsd/maven-4.0.0.xsd”>      <modelVersion>4.0.0</modelVersion>   <groupId>com.tecklearn</groupId>   <artifactId>sleuthapp</artifactId>   <version>0.0.1-SNAPSHOT</version>   <packaging>jar</packaging>    <name>sleuthapp</name>   <description>Demo project for Spring Boot</description>    <parent>      <groupId>org.springframework.boot</groupId>      <artifactId>spring-boot-starter-parent</artifactId>      <version>1.5.9.RELEASE</version>      <relativePath/> <!– lookup parent from repository –>   </parent>    <properties>      <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>      <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>      <java.version>1.8</java.version>      <spring-cloud.version>Edgware.RELEASE</spring-cloud.version>   </properties>    <dependencies>      <dependency>         <groupId>org.springframework.cloud</groupId>         <artifactId>spring-cloud-starter-sleuth</artifactId>      </dependency>      <dependency>         <groupId>org.springframework.boot</groupId>         <artifactId>spring-boot-starter-web</artifactId>      </dependency>      <dependency>         <groupId>org.springframework.boot</groupId>         <artifactId>spring-boot-starter-test</artifactId>         <scope>test</scope>      </dependency>   </dependencies>    <dependencyManagement>      <dependencies>         <dependency>            <groupId>org.springframework.cloud</groupId>            <artifactId>spring-cloud-dependencies</artifactId>            <version>${spring-cloud.version}</version>            <type>pom</type>            <scope>import</scope>         </dependency>      </dependencies>   </dependencyManagement>    <build>      <plugins>         <plugin>            <groupId>org.springframework.boot</groupId>            <artifactId>spring-boot-maven-plugin</artifactId>         </plugin>      </plugins>   </build>   </project>

Gradle – build.gradle

buildscript {   ext {      springBootVersion = ‘1.5.9.RELEASE’   }   repositories {      mavenCentral()   }   dependencies {      classpath(“org.springframework.boot:spring-boot-gradle-plugin:${springBootVersion}”)   }} apply plugin: ‘java’apply plugin: ‘eclipse’apply plugin: ‘org.springframework.boot’ group = ‘com.tecklearn’version = ‘0.0.1-SNAPSHOT’sourceCompatibility = 1.8 repositories {   mavenCentral()}ext {   springCloudVersion = ‘Edgware.RELEASE’}dependencies {   compile(‘org.springframework.cloud:spring-cloud-starter-sleuth’)   compile(‘org.springframework.boot:spring-boot-starter-web’)   testCompile(‘org.springframework.boot:spring-boot-starter-test’)}dependencyManagement {   imports {      mavenBom “org.springframework.cloud:spring-cloud-dependencies:${springCloudVersion}”   }}

You can create an executable JAR file, and run the Spring Boot application by using the following Maven or Gradle commands.

For Maven, you can use the following command −

mvn clean install

After “BUILD SUCCESS”, you can find the JAR file under the target directory.

For Gradle, you can use the following command −

gradle clean build

After “BUILD SUCCESSFUL”, you can find the JAR file under the build/libs directory.

Now, run the JAR file by using the command shown here −

java –jar <JARFILE>

Now, the application has started on the Tomcat port 8080.

Now, hit the URL in your web browser and see the output in console log.

http://localhost:8080/

Page 5 Image 1 2
consolelog

You can see the following logs in the console window. Observe that log is printed in the following format [application-name, traceid, spanid, zipkin-export]

Page 5 Image 2 3
log

Zipkin Server

Zipkin is an application that monitors and manages the Spring Cloud Sleuth logs of your Spring Boot application. To build a Zipkin server, we need to add the Zipkin UI and Zipkin Server dependencies in our build configuration file.

Maven users can add the following dependency in your pom.xml file −

<dependency>   <groupId>io.zipkin.java</groupId>   <artifactId>zipkin-server</artifactId></dependency><dependency>   <groupId>io.zipkin.java</groupId>   <artifactId>zipkin-autoconfigure-ui</artifactId></dependency>

Gradle users can add the below dependency in your build.gradle file −

compile(‘io.zipkin.java:zipkin-autoconfigure-ui’)compile(‘io.zipkin.java:zipkin-server’)

Now, configure the server.port = 9411 in application properties file.

For properties file users, add the below property in application.properties file.

server.port = 9411

For YAML users, add the below property in application.yml file.

server:   port: 9411

Add the @EnableZipkinServer annotation in your main Spring Boot application class fie. The @EnableZipkinServer annotation is used to enable your application act as a Zipkin server.

package com.tecklearn.zipkinapp; import org.springframework.boot.SpringApplication;import org.springframework.boot.autoconfigure.SpringBootApplication;import zipkin.server.EnableZipkinServer; @SpringBootApplication@EnableZipkinServerpublic class ZipkinappApplication {   public static void main(String[] args) {      SpringApplication.run(ZipkinappApplication.class, args);   }}

The code for complete build configuration file is given below.

Maven – pom.xml

<?xml version = “1.0” encoding = “UTF-8”?><project xmlns = “http://maven.apache.org/POM/4.0.0”    xmlns:xsi = “http://www.w3.org/2001/XMLSchema-instance”   xsi:schemaLocation = “http://maven.apache.org/POM/4.0.0    http://maven.apache.org/xsd/maven-4.0.0.xsd”>      <modelVersion>4.0.0</modelVersion>   <groupId>com.tecklearn</groupId>   <artifactId>zipkinapp</artifactId>   <version>0.0.1-SNAPSHOT</version>   <packaging>jar</packaging>   <name>zipkinapp</name>   <description>Demo project for Spring Boot</description>    <parent>      <groupId>org.springframework.boot</groupId>      <artifactId>spring-boot-starter-parent</artifactId>      <version>1.5.9.RELEASE</version>      <relativePath /> <!– lookup parent from repository –>   </parent>    <properties>      <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>      <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>      <java.version>1.8</java.version>      <spring-cloud.version>Edgware.RELEASE</spring-cloud.version>   </properties>    <dependencies>      <dependency>         <groupId>io.zipkin.java</groupId>         <artifactId>zipkin-server</artifactId>      </dependency>      <dependency>         <groupId>io.zipkin.java</groupId>         <artifactId>zipkin-autoconfigure-ui</artifactId>      </dependency>      <dependency>         <groupId>org.springframework.boot</groupId>         <artifactId>spring-boot-starter-test</artifactId>         <scope>test</scope>      </dependency>   </dependencies>    <dependencyManagement>      <dependencies>         <dependency>            <groupId>org.springframework.cloud</groupId>            <artifactId>spring-cloud-dependencies</artifactId>            <version>${spring-cloud.version}</version>            <type>pom</type>            <scope>import</scope>         </dependency>      </dependencies>   </dependencyManagement>    <build>      <plugins>         <plugin>            <groupId>org.springframework.boot</groupId>            <artifactId>spring-boot-maven-plugin</artifactId>         </plugin>      </plugins>   </build>   </project>

Gradle – build.gradle

buildscript {   ext {      springBootVersion = ‘1.5.9.RELEASE’   }   repositories {      mavenCentral()   }   dependencies {      classpath(“org.springframework.boot:spring-boot-gradle-plugin:${springBootVersion}”)   }}apply plugin: ‘java’apply plugin: ‘eclipse’apply plugin: ‘org.springframework.boot’ group = ‘com.tecklearn’version = ‘0.0.1-SNAPSHOT’sourceCompatibility = 1.8 repositories {   mavenCentral()}ext {   springCloudVersion = ‘Edgware.RELEASE’}dependencies {   compile(‘io.zipkin.java:zipkin-autoconfigure-ui’)   compile(‘io.zipkin.java:zipkin-server’)   testCompile(‘org.springframework.boot:spring-boot-starter-test’)}dependencyManagement {   imports {      mavenBom “org.springframework.cloud:spring-cloud-dependencies:${springCloudVersion}”   }}

You can create an executable JAR file, and run the Spring Boot application by using the below Maven or Gradle commands −

For Maven, use the command given below −

mvn clean install

After “BUILD SUCCESS”, you can find the JAR file under the target directory.

For Gradle, use the command given below −

gradle clean build

After “BUILD SUCCESSFUL”, you can find the JAR file under the build/libs directory.

Run the JAR file by using the command shown −

java –jar <JARFILE>

Now, the application has started on the Tomcat port 9411 as shown below −

Page 9 Image 3
app started

Now, hit the below URL and see the Zipkin server UI.

http://localhost:9411/zipkin/

Page 9 Image 4 1
zipkin

Then, add the following dependency in your client service application and point out the Zipkin Server URL to trace the microservice logs via Zipkin UI.

Now, add the Spring Cloud Starter Zipkin dependency in your build configuration file as shown −

Maven users can add the following dependency in pom.xml file −

<dependency>   <groupId>org.springframework.cloud</groupId>   <artifactId>spring-cloud-sleuth-zipkin</artifactId></dependency>

Gradle users can add the below dependency in build.gradle file −

compile(‘org.springframework.cloud:spring-cloud-sleuth-zipkin’)

Now, add the Always Sampler Bean in your Spring Boot application to export the logs into Zipkin server.

@Beanpublic AlwaysSampler defaultSampler() {   return new AlwaysSampler();}

If you add the AlwaysSampler Bean, then automatically Spring Sleuth Zipkin Export option will change from false to true.

Next, configure your Zipkin Server base URL in client service application.properties file.

spring.zipkin.baseUrl = http://localhost:9411/zipkin/

Then, provide the trace id and find the traces in Zipkin UI.

http://localhost:9411/zipkin/traces/{traceid}/

So, this brings us to the end of blog. This Tecklearn ‘Tracing Micro Service Logs in Spring Boot’ blog helps you with commonly asked questions if you are looking out for a job in Java Programming. If you wish to learn Spring Boot and build a career Java Programming domain, then check out our interactive, Java and JEE Training, that comes with 24*7 support to guide you throughout your learning period. Please find the link for course details:

https://www.tecklearn.com/course/java-and-jee-training/

Java and JEE Training

About the Course

Java and JEE Certification Training is designed by professionals as per the industrial requirements and demands. This training encompasses comprehensive knowledge on basic and advanced concepts of core Java & J2EE along with popular frameworks like Hibernate, Spring & SOA. In this course, you will gain expertise in concepts like Java Array, Java OOPs, Java Function, Java Loops, Java Collections, Java Thread, Java Servlet, and Web Services using industry use-cases and this will help you to become a certified Java expert.

Why Should you take Java and JEE Training?

  • Java developers are in great demand in the job market. With average pay going between $90,000/- to $120,000/- depending on your experience and the employers.
  • Used by more than 10 Million developers worldwide to develop applications for 15 Billion devices.
  • Java is one of the most popular programming languages in the software world. Rated #1 in TIOBE Popular programming languages index (15th Consecutive Year)

What you will Learn in this Course?

Introduction to Java

  • Java Fundamentals
  • Introduction to Java Basics
  • Features of Java
  • Various components of Java language
  • Benefits of Java over other programming languages
  • Key Benefits of Java

Installation and IDE’s for Java Programming Language

  • Installation of Java
  • Setting up of Eclipse IDE
  • Components of Java Program
  • Editors and IDEs used for Java Programming
  • Writing a Simple Java Program

Data Handling and Functions

  • Data types, Operations, Compilation process, Class files, Loops, Conditions
  • Using Loop Constructs
  • Arrays- Single Dimensional and Multi-Dimensional
  • Functions
  • Functions with Arguments

OOPS in Java: Concept of Object Orientation

  • Object Oriented Programming in Java
  • Implement classes and objects in Java
  • Create Class Constructors
  • Overload Constructors
  • Inheritance
  • Inherit Classes and create sub-classes
  • Implement abstract classes and methods
  • Use static keyword
  • Implement Interfaces and use it

Polymorphism, Packages and String Handling

  • Concept of Static and Run time Polymorphism
  • Function Overloading
  • String Handling –String Class
  • Java Packages

Exception Handling and Multi-Threading

  • Exception handling
  • Various Types of Exception Handling
  • Introduction to multi-threading in Java
  • Extending the thread class
  • Synchronizing the thread

File Handling in Java

  • Input Output Streams
  • io Package
  • File Handling in Java

Java Collections

  • Wrapper Classes and Inner Classes: Integer, Character, Boolean, Float etc
  • Applet Programs: How to write UI programs with Applet, Java.lang, Java.io, Java.util
  • Collections: ArrayList, Vector, HashSet, TreeSet, HashMap, HashTable

Java Database Connectivity (JDBC)

  • Introduction to SQL: Connect, Insert, Update, Delete, Select
  • Introduction to JDBC and Architecture of JDBC
  • Insert/Update/Delete/Select Operations using JDBC
  • Batch Processing Transaction
  • Management: Commit and Rollback

Java Enterprise Edition – Servlets

  • Introduction to J2EE
  • Client Server architecture
  • URL, Port Number, Request, Response
  • Need for servlets
  • Servlet fundamentals
  • Setting up a web project in Eclipse
  • Configuring and running the web app with servlets
  • GET and POST request in web application with demo
  • Servlet lifecycle
  • Servlets Continued
  • Session tracking and filter
  • Forward and include Servlet request dispatchers

Java Server Pages (JSP)

  • Fundamentals of Java Server Page
  • Writing a code using JSP
  • The architecture of JSP
  • JSP Continued
  • JSP elements: Scriptlets, expressions, declaration
  • JSP standard actions
  • JSP directives
  • Introduction to JavaBeans
  • ServletConfig and ServletContext
  • Servlet Chaining
  • Cookies Management
  • Session Management

Hibernate

  • Introduction to Hibernate
  • Introduction to ORM
  • ORM features
  • Hibernate as an ORM framework
  • Hibernate features
  • Setting up a project with Hibernate framework
  • Basic APIs needed to do CRUD operations with Hibernate
  • Hibernate Architecture

POJO (Plain Old Java Object)

  • POJO (Plain Old Java Object)
  • Persistent Objects
  • Lifecycle of Persistent Object

Spring

  • Introduction to Spring
  • Spring Fundamentals
  • Advanced Spring

Got a question for us? Please mention it in the comments section and we will get back to you.

 

 

 

0 responses on "Tracing Micro Service Logs in Spring Boot"

Leave a Message

Your email address will not be published. Required fields are marked *