Jaeger integration in Kiali

Jaeger integration in Kiali

  • January 27, 2019
Table of Contents

Jaeger integration in Kiali

Kiali has the ability to show traces obtained from Istio. Jaeger collects traces for monitoring and troubleshooting microservices-based distributed systems, and both Istio and Kiali use the data that Jaeger provides. Originally this was done via a separate tab in the UI.

But that turned out to be impractical. So the Kiali team has been working with the Jaeger team on the Jaeger integration. By improving the Jaeger UI components to make them embeddable, there is better integration between a Kiali selection and a Jaeger selection, making it easier to enrich Jaeger with Kiali information.

This enhancement consists of changes in the URL API to personalize the component to be presented from Jaeger UI similar to the Google Maps API. You can view this enhancement in Jaeger in the version 1.8.2 of the project and the related documentation is available here. This enhanced integration between Jaeger and Kiali should be available in the next release of Istio, when Jaeger is updated to version 1.9.

In the meantime we would like to show you what it will look like in future versions.

Source: medium.com

Share :
comments powered by Disqus

Related Posts

Deployment strategies for the Jaeger Agent

Deployment strategies for the Jaeger Agent

If you’ve been following the evolution of the Kubernetes templates for Jaeger, you might have noticed an important change recently: the Jaeger Agent is not being deployed as a DaemonSet anymore. Instead, instructions are now being provided on how to deploy it as a “Sidecar”. The Agent component was developed to act as a “buffer” between the tracer and the collector.

Read More
Sidestepping Dependency Ordering with AppSwitch

Sidestepping Dependency Ordering with AppSwitch

We are going through an interesting cycle of application decomposition and recomposition. While the microservice paradigm is driving monolithic applications to be broken into separate individual services, the service mesh approach is helping them to be connected back together into well-structured applications. As such, microservices are logically separate but not independent.

Read More