Consider the scenario – You are an SRE (Site Reliability Engineer) joining a team to take charge of their Java applications. It has been reported that a Java application is very flaky in terms of memory issues.

A few months ago, I wrote an article about a serious outage of Azure and how eG Enterprise enabled us and our customers to understand the issue long before Microsoft had confirmed the issue and updated their service status pages.

The observability landscape - specifically your traditional Application Performance Monitoring (APM) offerings are failing modern-day developers. These legacy tools are made for ops and infra teams to keep their infrastructure and services up and running. But when it comes to helping the people that actually write the code to find and fix latency issues, these tools - which often come with massive price tags - leave developers hunting for issues causing slowdowns.

At Raygun, we’re a pretty polyglot group of developers. Various parts of our code base are written in different languages and frameworks — whatever is best for the job. That said, large parts of Raygun written with.NET, and we’re big.NET fans. Given the prevalence of C# applications (C# has been in the top 5 on the TIOBE index for about 10 years!) and the massive scale of data Raygun deals with, we’re often called on to do C# optimization work.