Application Performance Monitoring (APM) means many things to many people. At its core, it enables developers to diagnose why their applications are slow and helps them provide a better experience to their users. Traditionally, this is accomplished by collecting a lot of data and displaying it in the form of dashboards and request traces. The problems you’re trying to solve are generally known up front. For example, N+1 queries are a common issue in many web applications, so many APMs offer purpose-built tools to address them. Third-party HTTP requests are another common culprit, and so they provide instrumentation to track slow external API calls, timeouts, and retry patterns that slow down your response times. This cookie-cutter approach is common across legacy APM solutions. The data they collect and the interfaces they provide are glued together to solve a specific problem: application performance. Too much data, too few answers Modern applications fail in ways that developers…
No comments yet. Log in to reply on the Fediverse. Comments will appear here.