I wasn't the one who set up Zenoss Service Dynamics, in particular, the entire vendor system. It's a little bit complex, but in terms of setting up the agent to monitor devices, it's pretty easy. It took a week or so to set up the entire vendor system.

I wasn't familiar with the implementation strategy for Zenoss Service Dynamics because it was implemented before I joined the company.

The initial setup is not overly complex or difficult. 

The length of the deployment depends on the size of the infrastructure. It can go from three days to three months, something like that. The bigger the environment, the longer it takes. 

You only need one person to deploy and maintain the solution. We use an
IT expert and he delegates the smaller task to engineers, to junior engineers.

The setup is not straightforward because Zenoss is more like building-blocks that are given to you. They will give you all the features that are available in the technology. If you want to build something, you use your own hands, use your own brain, and build it. That is more the approach. The more you get your hands on it, the more you can mold it into anything that you want. I've seen customers — whenever Zenoss does yearly forums for the product — who are using it more efficiently than I do because they have more programming skills. 

On the other hand, that is one of the advantages that Zenoss has. They give it to you in a format so you can do anything that you decide. That is one advantage of Zenoss.

The initial setup was easy but complex. I made some investigations because of life. We were looking for other options. 

It was kind of a little challenge to configure it. It had plenty of configuration flaws. Zenoss Service Dynamics needs to define automation. It was relatively hard to manage this part.

The deployment usually is not that hard, maybe a day. The customization will take most of the time, i.e. the number of plug-ins available. In total, it's probably a month or more to install.

It is straightforward.

The complexity of the initial setup depends on which version is being implemented. For the versions that I have seen, the complexity is somewhere in the middle.

I've used the solution for about a year now, and therefore I don't find the implementation to be complex. It's very straightforward, actually.

The cloud solution can be a little hard if you don't know Zenoss. However, for me, it's very simple, and I can deploy a Zenoss environment in a couple of hours. When I first started about three years ago, it could take me as long as three days.

The first step was to deploy the virtual machine.  Then you need to deploy the software, and then you need to deploy all the dashboards and all features that you need. That is a little complicated as you need to understand how Zenoss works.

Now, however, in the cloud solutions and hybrid models on cloud nodes or in side nodes, it's a little different due to the fact that you have a controller and you have the client's deployment in certain parts. Still, it's very, very easy to deploy as you put the controller software in one machine and you put the nodes in the other machines. Then, you only need to select your features. The features now are also all-inclusive.

The ZenPacks, the backup servers, are for also perfect all kinds of devices that I use.

Setup is very complicated; pruning to desired monitors is very easy and efficient.