Operations | Monitoring | ITSM | DevOps | Cloud

Maybe you’ve been there. You’re a VP of engineering, or a product owner. There was a critical outage in one of your apps, and it took your team an entire week to track down and fix the issue. Customers and revenue were lost. Now you’re sitting in a review meeting with a consultant hired to figure out what happened and why.

The recent COVID-19 outbreak is stressing healthcare systems worldwide. Most countries are looking to “flatten the curve” of new cases in order to allow the sick to be treated without swamping hospitals.

Over the last few years, more developers have taken Ruby as their staple programming language. Who can blame them? It certainly has a lot of appealing features. For one, the syntax is easy to read and debug. A default MVC architecture within most Ruby frameworks is another alluring factor that may have had you using it as well.

In this release, we’re bringing an all-new section to Real User Monitoring to provide another way for you to monitor application health; the Response Codes tab. Real User Monitoring now tracks the response codes from XHR/AJAX calls made in your web application using the JavaScript provider. You can now: Stacked view of your application’s response codes This feature brings vital insight into the health of your applications so you can deliver the software experiences your customers deserve.

As many of us are rediscovering an interest in board games, it feels relevant to make reference to Hasbro’s classic Clue. Understanding what’s going right or wrong in your sprawling digital business can feel a lot like a murder mystery: it was the authentication service in the east region with the memory exhaustion error. This analogy has a weakness when applied to modern operations. The Clue board game had 6 weapons, 6 suspects, and 9 rooms. That’s 324 combinations.

With a huge number of employees around the globe working remotely during the COVID-19 pandemic, delivering uninterrupted business services to customers has become a major challenge. This requires strict monitoring of all critical business applications in order to accommodate an increased amount of requests, which can cause a critical downtime if not monitored appropriately.