Full Observability for Application Monitoring
summary
APMs stop where database visibility begins so the session claims 70% of performance problems trace back to the database and argues for instrumenting queries, capturing query execution plans, and correlating them with CPU/memory and network metrics. It shows practical debugging: tracing a slow request down to a specific SQL, spotting a sudden jump in query volume post-deploy, and using staging to compare pre/post deployment query profiles to catch regressions before they reach production.
AI-written summary · about
chapters (7)
- 0:00Start
- 3:20Challenges of Observability
- 10:30Troubleshoot and Diagnose Outages
- 14:49Tuning Query Performance
- 18:41Infrastructure and Its Impact on Database Health
- 20:19Deploy Code with Confidence
- 22:03Full Observability for Application Monitoring
related talks
47mUsing APM to Give Businesses a Competitive Edge
39mPanel Discussion: Application Monitoring
58mObserving Applications in Production
17mOpen Source Database Operations in the Age of AI
45mDeveloping Observable Applications for Production
27mOpenAPM – Application Performance Management tailored to your needs
42mUnified observability, AIOps, and incident response for AWS
52mNot on Our Watch: an Introduction to Application Performance Monitoring