Operations | Monitoring | ITSM | DevOps | Cloud

What’s the point of observability? Surely if you write good code, maintain it, handle tech debt, and administer its resources correctly, it’ll run great? Why would you need to keep a close eye on services that have already been tested and are working great? In this article I want to show how continuous monitoring of your systems closely, with tools like Checkly and Coralogix, can find problems that would have been impossible to predict or pre-optimize.

We’ve had a fantastic month celebrating 20 years of Nexthink and taking time to reflect on the people, products, and innovations that have shaped the company. Today, Nexthink is a category creator, an industry defining brand reshaping how IT teams manage the digital workplace. But that wasn’t always the case. Let's take a moment to recap some of our favourite content from the month celebrating the last 20 years of Nexthink.

Ensuring smooth transitions during application upgrades are important. Maintaining system consistency and stability with a database upgrade is paramount. Databases are complex systems with numerous stored procedures, each intricately linked to critical functionalities. Changes to these procedures during an upgrade could potentially disrupt overall system performance and negatively impact thousands of customers.

System monitoring can be viewed as being closely related to infrastructure monitoring, but there are differences between the two concepts, particularly with their scopes within the realm of IT monitoring. Infrastructure monitoring concentrates on monitoring the physical and virtual components of an IT environment, such as servers, networks, storage systems, and cloud services.

While spring is traditionally the time for tidying up for most folks, IT and Security teams know it is important always to maintain a clean, streamlined environment. However, we understand that doesn’t always happen with growing data volumes, stagnant budgets, and changing organizational priorities. This blog is to help you understand if you are properly overdue for a clean-up.

An oft-forgotten component of robust, production-ready code is testing. The moat protects us from costly service interruptions and fortifies trust in our product with our customers. Simply put, it’s in the critical path of damn good software. However, as we scale a cloud product to serve a rapidly growing user base, our test case scenarios scale correspondingly. As far as testing goes, end-to-end (E2E) testing most closely mirrors the end-user experience.