As we recently discussed, many of us are still lost in the darkness, grasping for a log line to shed some light on the issue we are trying to troubleshoot. Many of our customers and colleagues have shared the following challenges with us: But what if we didn’t have to make such a choice? What if we could easily and efficiently switch on exactly the logs we needed, without hurting our application?

We have recently launched our disruptive Live Debugger on the Azure Marketplace, making it easier than ever before for teams on the Microsoft stack to slash the time they invest in debugging. We are excited about this, as we have been working closely with Microsoft to make sure that both large international enterprises as well as smaller and scaling startups have direct access to Rookout, to make the most out of our dynamic observability solutions.

To paraphrase a popular Chinese proverb: “It is better to light a log line than to curse the darkness”. And yet it’s 2021, and many of us are still lost in the dark, struggling to find a match, praying for that one missing log line that would have pointed us in the right direction. How did things get this bad? Since time immemorial, we have relied on logging as the first trustworthy, intuitive, and straightforward debugging method.

The rise in digital transformation over the past few years means that more and more companies are adopting cloud native technologies. While these distributed architectures provide scalability and agility, they also increase complexity. As Arnal Dayaratna, research director in software development for IDC, writes, “One of the challenges faced by contemporary developers is the task of understanding applications that they may not have even developed or used .”