This topic describes the systematic instructions to troubleshoot the errors using the Zipkin Traces.

1. Launch the Zipkin URL.

   Note:

   The basic layout of Zipkin displays.

   Figure 1-5 Layout of Zipkin

   
   

   
   Description of "Figure 1-5 Layout of Zipkin"

   
   
2. Use Search to find the traces of required API calls and services.

   Note:

   The search options given in the user interface are self-explanatory, and there is another UI option (Try Lens UI). It is given a different user interface with the same functionality.

   Some error API calls are made to showcase how to track errors. The blue listing shows the successful API hits, and the red listing indicates the errors. Each block indicates a single trace in the listing. The below figure shows the list of traces.

   Figure 1-6 List of Traces

   
   

   
   Description of "Figure 1-6 List of Traces"

   
   
3. Open the individual trace.
   It describes the time taken for each block. As the two custom spans are created inside two service calls, user can find a total of four blocks.
   The time taken for an individual block is shown below.
   The details of an individual trace displays.

   Figure 1-7 Individual Trace

   
   

   
   Description of "Figure 1-7 Individual Trace"

   
   
4. Click on the individual block to display the details.

   Figure 1-8 Details of Individual Block

   
   

   
   Description of "Figure 1-8 Details of Individual Block"

   
   

   The user can also view the logging events in the Zipkin UI as small circular blocks. An example of an error log is shown below.

   Figure 1-9 Sample Error Log

   
   

   
   Description of "Figure 1-9 Sample Error Log"

   
   
5. Click the error to get clear details and place of the error.

   Figure 1-10 Details of Error

   
   

   
   Description of "Figure 1-10 Details of Error"

   
   

   Note:

   If the Lens UI is used in Zipkin, the above figures are not applicable but are relatable to the Lens UI as well. Traces of the application can be found using TraceId. The TraceId can be found in the debug logs of the deployment when spring-cloud-sleuth is included in the dependencies (included in spring-cloud-starter-zipkin dependency).
6. Click the Dependencies to get the dependency graph information between micro-services.

   Figure 1-11 Sample Dependency Graph

   
   

   
   Description of "Figure 1-11 Sample Dependency Graph"