Ideally, you should be using distributed tracing to trace requests through your system, but event-based systems such as Kafka decouple producers and consumers, which means there are no direct transactions to trace between them. Event-based architectures also use asynchronous processes, which have implicit, not explicit, dependencies. That makes it challenging to understand how your microservices are working together.
However, it is possible to monitor your event-based systems with distributed tracing and OpenTelemetry. You can then analyze and visualize your traces in open source distributed tracing tools or full observability platforms like New Relic. In this talk I will leverage a simple application to show how you can achieve this in various different configuration options.
However, it is possible to monitor your event-based systems with distributed tracing and OpenTelemetry. You can then analyze and visualize your traces in open source distributed tracing tools or full observability platforms like New Relic. In this talk I will leverage a simple application to show how you can achieve this in various different configuration options.
Harry Kimpel
New Relic
Passionate software craftsman with 28+ years experience in a broad spectrum of development technologies and platforms. Main focus on cloud-native software architectures and all major cloud environments. Passion for model-driven development, application modernization and Dapr. Observing and securing these environments are key aspects.
As a Developer Relations Engineer at New Relic, Harry helps software engineers, DevOps, SREs and operations experts to understand and implement proactive and scalable observability practices by leveraging open source technologies and the New Relic platform.
As a Developer Relations Engineer at New Relic, Harry helps software engineers, DevOps, SREs and operations experts to understand and implement proactive and scalable observability practices by leveraging open source technologies and the New Relic platform.