This is the one post I hope you’ll never need. However, should you ever need it, this is your one-stop shop for understanding how to proceed with DevOps incident management. Have you just been attacked? Did the commit go wrong? A CI pipeline went haywire? Don’t worry. I got you.

Measuring the maturity of your DevOps team might sound difficult, but it isn’t at all. Simple key performance indicators (KPIs), such as the deployment success rate or mean time between failure, give a good indication of the maturity of your DevOps team. By “mature,” I mean that your team consistently and smoothly operates at a high level and can deploy several times a day with very little risk.

Today’s post covers yet another log-related concept: log forensics. What’s this, and why should your organization care about it? Well, this is a topic related to logs, which are ubiquitous in the technology field. An IT organization that doesn’t generate many MBs worth of logs each day would be a rare occurrence nowadays. Even though logs are omnipresent, specific terms might not be so well-known. Not long ago, we covered log analytics, and today it’s log forensics time.