Microservice architecture comes with many benefits but implies additional complexity especially in the context of deployment, monitoring and observability.
When your monitoring system is warning you that your application is failing frequently or simply getting slower and slower, it may be difficult to figure out where the actual problem is. Sure, you may be using some tools to aggregate logs and, provided that your logs have the appropriate granularity, you could start investigating there. But when the anomaly is related to a funcionality that is implemented through a chain of invocations of different microservices it may be very difficult to identify the actual culprit.
Wouldn't it be great if your application produced complete telemetry information across all the layers and provided effective means of chaining the traces of all the involved microservices? Even better, wouldn't it be great if you could add this capability to your application without having to write a single line of code? Here is where OpenTelemetry shines! Thanks to OpenTelemetry you can make your existing Java application fully observable and easily enable tracing and trace propagation via simple configuration without any code modification.
The session will first introduce the OpenTelemetry concepts and working principles and will then demonstrate usage of OpenTelemetry with a sample application.
