Operations | Monitoring | ITSM | DevOps | Cloud

I often have discussions with N-able partners who need help capturing data for either regular reporting or just to have when a customer asks for it. Often people will use a tool like BrightGauge to pull data from their RMM platform and generate dashboards and reports. However, these can be overly complex if you only need to capture the data so you have it and can act upon it. What I regularly recommend is that you create a monitoring script to capture just the data that is needed.

For many years, system uptime was the primary measure of reliability, especially when the most popular method of running software was on bare metal, on-premises servers. If a server was shutdown, rebooted, or otherwise became unavailable, downtime was expected until a system administrator could manually restart it.

After the global pandemic and lockdowns, most businesses look onward to online solutions for their applications. They want to take their business online by creating mobile or web applications. Companies are looking to monitor every aspect of the application, including deployment, bugs, API failures, etc. But the most important thing is how the application behaves when it goes into the hands of the end-users.

With hybrid work environments on the rise, enterprise networks are dealing with multiple remote connections, increasing the risk of breaches and other attacks. One way to mitigate these risks is by implementing Zero Trust Architecture (ZTA) into the enterprise network. Unfortunately however this does not address the full set of threats to the enterprise, as many of the zero-trust service providers and on-premises network solutions do not address the voice network.