This is an intro to Application Performance Monitoring (APM). We'll talk a bit about the history of APM, look through a quick case study and walk through a simple vendor-agnostic approach to choosing an APM solution. It has been a busy several years in monitoring and observability. Logging solutions are widely deployed, from scp+grep to proper federated logging. Collecting centralised server environment and resources metrics has also matured. In this talk we'll introduce the next layer in this onion - in-depth Application Performance Monitoring (APM). While other parts of the monitoring stack could be described as watchpeople, APM plays much more of a detective role, bringing ever more metrics into increasingly complex UIs to suss out performance bottlenecks. We'll talk a bit about the history of APM and show an example Python app being monitored with a free APM system (made by Elastic). We'll reflect on a case study of 2 of the speaker's old clients, 2 small web technology-driven organisations which could have gotten more out of their APM systems. We will look at why that might be and how you could do better. We'll end with a simple vendor-agnostic approach to choosing an APM solution.
YOU MAY ALSO LIKE:
Hiring a Personal Investigator for Your App
Emanuil is a Community Engineer with Elastic. He used to be a freelance web developer and ran a small open science web dev consultancy with partners for several years. Interested in mentorship, inclusion, small businesses, archery and always curious about how the world works in detail.