Open Source Summit Europe 2022

In the past few years, we have seen rapid development in system designing where multiple services coordinate with each other to form a whole end-to-end architecture. Along with this, our testing methodologies have also improved by using end-to-end tests. What about observability though? End-to-end observability is still a dream for many organizations. How do we know which application is underperforming? What causes it to underperform? Is it taking other applications down with it? Which users are getting affected? It’s high time that we stop tailing logs or worse, deriving metrics out of these logs to understand our system’s bottlenecks. Application Performance Monitoring (APM) can help us here. It can not only provide you with the necessary metrics but also other benefits like understanding your application’s transactional behaviour via traces, visualising how your application communicates with external entities, etc. Do you want to know how your users are reacting to your application’s performance? Yes, that’s possible. In Prashansa’s experience of working with APM for the past year, she has done enough mistakes so that you don’t have to repeat them. With this talk, she wants to share how APM along with OpenTelemetry can help to debug problems before they occur.