If you work in IT, especially on the decision-making side, then you should be aware of how vital logging is. When things go wrong with software in production, a solid logging approach often is the difference between hours of fruitless troubleshooting and an easy fix. Today, we’re here to talk about logging by covering a specific angle. Namely, we’ll answer the question, “What is log collection?”
Cloud computing, mobile devices, and IoT technologies continue to evolve and proliferate. As a result, businesses are generating and collecting more data than ever before. Data is generated and stored every time a customer interacts with a website or device. Savvy companies understand the importance of capitalizing on that data. It enables them to enhance customer experiences and increase profitability, among other countless benefits.
Before the need for log correlation, there was a time not so long ago when reading software application logs was simple. Your application would output log files in sequential order, and you’d read through them. In the event of a bug, software outage, or security incident, you could easily parse what happened and when. It was a tedious process, but it was simple.
Time for another installment in the series where we explain in detail yet another important metric for tech organizations. After covering MTTD and MTTF, today we answer the question, “What is MTBF?” As the post title makes clear, MTBF stands for “Mean time between failures.” The acronym refers—like the others that came before it—to an important DevOps KPI. But what actually is it? What is it good for? How do I implement it?
