Using Jaeger Collector with Kafka
when embarking on a journey to build cloud native applications and/or decomposing a monolithic application into microservices one of the issues you will encounter at one point in time is the issue of getting a good insight in what the system is actually doing. The benefit of monolithic applications is that logging and monitoring can be done in one place, or at least a limited number of places.
Building a distributed solution, holding multiple services in a multitude of containers who are distributed over multiple cloud regions provide the issue that a single user interaction will trigger actions on multiple environments. When invoking an action on a monolithic application all logging will be on that specific server, doing the same the logging showcasing the entire chain of events will be distributed over all kinds of different systems (containers / serverless functions / virtual machines).
To help you tackle this issue Jaeger provides a part of this solution. Jaeger, an open source, end-to-end distributed tracing solution to Monitor and troubleshoot transactions in complex distributed systems. As on-the-ground microservice practitioners are quickly realizing, the majority of operational problems that arise when moving to a distributed architecture are ultimately grounded in two areas: networking and observability. It is simply an orders of magnitude larger…
