Introducing Zipkin-Azure


Today in Build 2017, we released Microsoft’s contribution to the Open Source Community by extending Zipkin with the power of Application Insights (AppInsights) calling it “Zipkin-Azure”.

Zipkin is a tracing tool for distributed systems to log events related to each individual activity (also known as job, transaction, or trace, depending on the context) in a way that allows the path of the activity through the system to be reconstructed. It offers correlation across multiple services within a customer’s application. With AppInsights integration, Zipkin now gains the ability to log data to an Application Insights store and to trace activities through multiple services including non-logging systems using impersonation. It provides application performance management features from AppInsights along with tracing capabilities provided by Zipkin.

AppInsights users would also be able to leverage the distributed tracing offered through Zipkin by instrumenting their services using existing libraries. To use the AppInsights back-end store, configure your Zipkin server instance to use the AppInsights plug-in. This integration makes monitoring and debugging your overall end-to-end applications much easier.

Azure-based systems may already have one or more associated Application Insights instances. If so, you can use any one of them. Otherwise, you can create a new Application Insights instance by logging in to the Azure Portal, and then navigate to the Application Insights blade, either by typing “Application Insights” into the search bar or by choosing “Application Insights” from the service list.

Zipkin-Application Insights Integration Architecture

Zipkin-Application Insights Integration Architecture

You can also view our offerings through this short video –

Comments (3)

  1. Avishek Roy says:

    Great Arijit. Our application is also using Azure but I did not know that you are a part of it. Proud to hear from you.

    1. Thanks a lot.

      Nice to know. Please let me know if you need any help on instrumenting your library with this plugin.

  2. Are you able to share any more on “trace activities through multiple services including non-logging systems using impersonation” (with the emphasis on the non-logging systems)? I’m interested in how to propagate the trace through systems that can’t directly be instrumented. Thanks

Skip to main content