We use Zenoss Service Dynamics to monitor our customers. We use it to monitor the devices we manage, and also use it to generate reports, and alerts, and also use it for larger assets.

As a Zenoss partner, the use cases have varied, based on the requirements. When I started using it in 2012, we were asked to migrate a set of technologies, like Windows and Linux monitoring, infrastructure monitoring, from different tools like SolarWinds and Tivoli to Zenoss, so that we would have a single pane for unified monitoring; a global operations manager. That, in turn, was integrated with ITSM tools like ServiceNow or CA. 

When I joined a different organization, it was used mostly for direct monitoring of vSphere and NetApp, with Windows and Linux of course, and some integration with SolarWinds and trap-based integrations. Internally we integrated it with ServiceNow. I implement that, integrate it, and hand it over to the daily support team.

We implement some customers on-prem and some customers we do using AWS or Azure cloud. It varies.

Our environment for Zenoss Service Dynamics is custom-made. We have connected to a cloud system. On the other hand, they are more service-oriented than our data center.

We are a system integrator and this is one of the solutions that we provide for our customers.

We have experience with several versions of this software, and the one we are using depends on our clients. 

We are using a lot of modules in a hybrid cloud deployment. We have used this solution in both a classical data center and a private cloud. Amazon is normally the cloud provider that we use.

I primarily use the solution for monitoring the network infrastructure and the operator platforms. The last implementation I did was for the user experience. 

It can also be used as a data center, similar to a virtual machine. Some users use Zenoss only for seeing everything on specific types of devices. They see only certain devices like operating systems and network communications, for example.