As we announced at the end of last year, more and more new customers are choosing to deploy the Zenoss unified monitoring platform as a service via our Zenoss-as-a-Service (ZaaS) offering, but we’re also seeing an increase in the number of existing on-premises customers, like Vassar College, who are choosing to migrate their existing Zenoss installation to ZaaS. In fact, as of this writing, fully one-third of our ZaaS customers had previous on-premises installations.
The top three reasons customers are choosing to migrate to ZaaS:
1. They are looking to upgrade to our latest platform but not wanting to increase their hardware footprint for the migration.
2. They want to remove the administrative overhead of managing, patching and upgrading an on-premises software installation.
3. They want to take advantage of the redundancy benefits of an external solution and keep their monitoring platform from being impacted by internal issues.
Choosing to Migrate to ZaaS
Of all the ZaaS customers who have migrated over from an on-premises installation, a little more than half were running version 4.x of our platform. When evaluating the hardware requirements for 5.x as well as the resource scope to migrate from 4.x to 5.x, these customers realized this was a perfect opportunity to consider an alternative approach to implementation. Choosing to migrate to ZaaS drastically decreases the time, cost and level of effort of getting onto the latest and greatest version of our platform.
Once customers migrate to ZaaS they get the benefit of being on the latest version of Zenoss Service Dynamics and getting the latest ZenPacks installed either on demand, monthly or quarterly. They no longer have to be concerned with patching servers running Zenoss, updating Zenoss software, or managing the scaling of resources to monitor a growing and changing infrastructure. Instead, they get to focus on the task of effectively and efficiently monitoring the health and performance of their infrastructure and providing service assurance to the business.
Lastly, what happens when the hardware running your monitoring software has an issue and takes down the product? To paraphrase the Roman poet Juvenal, “Who monitors the monitoring?” Having your monitoring software run in the cloud and being monitored for health and stability by Zenoss ensures that your monitoring is available when you need it and that issues within your infrastructure don’t actually impair your monitoring or ability to see those issues.
As detailed above, there are many benefits to running your monitoring with ZaaS. From reduced financial and administrative overhead to having a reliable and protected deployment, it’s really not surprising that more and more Zenoss customers are choosing ZaaS as their preferred deployment of Zenoss.
