Welcome!

Martin Etmajer

Subscribe to Martin Etmajer: eMailAlertsEmail Alerts
Get Martin Etmajer via: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Top Stories by Martin Etmajer

Let me ask you a question: would you say that you have implemented logging correctly for your application? Correct in the sense that it will provide you with all the insights you require to keep your business going once your users are struck by errors? And in a way that does not adversely impact your application performance? Honestly, I bet you have not. Today I will explain why you should turn off logging completely in production because of its limitations: Relies on Developers Lacks Context Impacts Performance Intrigued? Bear with me and I will show you how you can still establish and maintain a healthy and useful logging strategy for your deployment pipeline, from development to production, guided by metrics. What Logging Can Do for You Developers, including myself, often write log messages because they are lazy. Why should I set a breakpoint and fire up a debugge... (more)

Application Failures in Production | @DevOpsSummit [DevOps]

How to Approach Application Failures in Production In my recent article, "Software Quality Metrics for your Continuous Delivery Pipeline - Part III - Logging," I wrote about the good parts and the not-so-good parts of logging and concluded that logging usually fails to deliver what it is so often mistakenly used for: as a mechanism for analyzing application failures in production. In response to the heated debates on reddit.com/r/devops and reddit.com/r/programing, I want to demonstrate the wealth of out-of-the-box insights you could obtain from a single urgent, albeit unspecifi... (more)