Скачать или смотреть Export Data from a Remote System to Your Local Zipkin Using Spring Cloud Sleuth

Learn how to export tracing data from your customers' remote systems to your local Zipkin server using Spring Cloud Sleuth. This guide provides step-by-step instructions and code examples to help you streamline your application monitoring.
---
This video is based on the question https://stackoverflow.com/q/66383029/ asked by the user 'Rokko_11' ( https://stackoverflow.com/u/2432030/ ) and on the answer https://stackoverflow.com/a/66384663/ provided by the user 'Marcin Grzejszczak' ( https://stackoverflow.com/u/1773866/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Spring Cloud Sleuth: Export data from remote system to local Zipkin

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
How to Export Data from a Remote System to Your Local Zipkin Using Spring Cloud Sleuth

In a modern software development landscape, monitoring and tracing requests in your applications is crucial for performance and debugging. Spring Cloud Sleuth provides a powerful way to trace requests through microservices with the help of the @ NewSpan annotation. However, many developers face challenges when working in environments where access to a Zipkin server is restricted or impossible. If you're using Spring Cloud Sleuth with your monolithic application and want to export tracing data to your local Zipkin server, you're in the right place!

The Problem at Hand

You’re developing a Spring Boot application that leverages Spring Cloud Sleuth for distributed tracing. You've integrated the spring-cloud-starter-zipkin in your development environment without issues. However, when deploying to customer servers, you find yourself unable to access or install a Zipkin server. The crux of the problem is: How can you save the tracing data that Spring is sending to Zipkin and later import it into your local Zipkin instance?

The Solution: Saving and Exporting Spans

Thanks to inspiration from the community, there is a neat solution to this problem that involves creating a custom ZipkinSender. Here's a breakdown of the steps you'll need to follow:

Step 1: Create a Custom Sleuth Configuration

To redirect your span data to a local file instead of a remote Zipkin server, you need to define a configuration class. Below is the code that sets up a custom ZipkinSender:

[[See Video to Reveal this Text or Code Snippet]]

Step 2: Implement the Utility Methods

Within this custom sender, you'll need to implement the convertByteArrayToList and saveToFile methods yourself. They should handle the conversion of the byte array containing your spans into a JSON format and save that JSON data to a file.

convertByteArrayToList(List<byte[]> list): This method should convert the obtained list of byte arrays into a JSON string representation of your tracing spans.

saveToFile(String result): Next, create a method that saves the resulting JSON string to a designated file on the local system.

Step 3: Uploading to Zipkin

After collecting all the span data in JSON format, you can upload those JSON files to your local Zipkin server at your convenience. You can iterate through the saved JSON files and post them to your Zipkin server, enabling you to view trace information just as if it were sent directly.

Conclusion

By implementing the above solution, you can effectively export trace data from a customer's remote system to your local Zipkin server, even when direct access to the Zipkin server isn't viable.

This approach not only enables you to maintain visibility into your application's performance across different environments but also allows you to leverage the powerful features of Spring Cloud Sleuth for tracing.

Takeaways

Spring Cloud Sleuth provides powerful tracing capabilities.

You can create a custom Sender to save trace data locally instead of sending it directly to Zipkin.

This solution alleviates access issues on production environments while still allowing for trace data analysis.

With this guide, you should be well-equipped to handle tracing and data exporting in your monolithic Spring Boot application. Happy coding!