Operations | Monitoring | ITSM | DevOps | Cloud

In the era of technology defined by cloud computing, features evolve at the blinding speed of continuous deployment. When large software development organizations like Microsoft deliver semi-annual releases of products, like SQL Server, the volume of new features can be so large they can be hard to grasp. Microsoft continues to push the boundaries on what’s possible, both in on-premises and cloud data platforms, and they aim to make the life of data professionals much more manageable.

Distributed systems open us up to myriad complexities due to their microservices architecture. There are always little problems that arise in the system. Therefore, engineering teams must be able to determine how to prioritize the challenges. Viewing logs and metrics of such systems enables engineers to know the shared state of the system components, thereby informing the decision-making on what challenge needs to be solved most immediately.

While developing the ecosystem around the elmah.io API and App Store, we see an increasing interest and adoption of GitHub and the services around it. We have a range of integrations with GitHub that I’ll introduce you to later in this document. But first of all, I’m happy to announce that elmah.io has been chosen as a GitHub Technology Partner to build integrations in the Marketplace and extend developer capabilities. elmah.io integrates with GitHub in two ways.

SCOM has incredible powers, but it’s not always easy to find the root cause of issues fast. And you definitely don’t get one-click SCOM root cause analysis. We’ve all been there. A business-critical server goes down and you don’t know why. Let’s imagine you had a dashboard showing the health statuses of all your server groups and you notice that the United States is showing as critical.