Depends on the DSLAM brand, but we support any SNMPv2-MIBs out of the box.
We have 2 Ubiquiti ZenPacks submitted by the community, and you can extend
Zenoss further using Nagios plugins, or by writing your own ZenPacks.

If you have further questions feel free to contact me on my work e-mail
aki...@zenoss.com, as I'm pretty sure this isn't the Zenoss-Advertising
mailing list, and I don't want to overstep :)

Andrew

On Sun, Oct 18, 2015 at 12:04 PM, Jeremy Peterson <jpeter...@acentek.net>
wrote:

> Currently we are 4 hypervisors
> With about 30 VM's  between 18 VR's
>
> We are upgrading the corporate esx servers this year still so four more
> servers will be moving to the CloudStack enviroment.
>
> CloudStack + XS = 0 licensing
> ESX = $$$
>
> Like I mentioned before the VM's may or may not need monitoring as that
> will only apply to us offering management to those customers.
>
> SaltStack is amazing and will do a lot of the deployment and automation
> for us but yes Zenoss does look decent but I also need something that can
> check multiple DSLAM's, Valere's, even custom SNMP checks for Ubinquity
> AP's being down.
>
> Jeremy
> ________________________________________
> From: Andrew Kirch <trel...@trelane.net>
> Sent: Sunday, October 18, 2015 1:32 AM
> To: users@cloudstack.apache.org
> Subject: Re: Cloudstack - Monitoring
>
> I'm going to shamelessly plug Zenoss, we have ZenPacks for both CloudStack,
> and Xenserver which should give you deep monitoring of both.
>
> I say shameless, because I am the Zenoss Community Manager.
>
> On Fri, Oct 16, 2015 at 5:25 PM, Jeremy Peterson <jpeter...@acentek.net>
> wrote:
>
> > We are looking at a new monitoring software for our corporate
> > environment.  Management has requested that CloudStack and XenServer be
> > added to that monitoring software.  One of the software titles we are
> > looking at is DataDogHQ.
> >
> > https://bigpanda.io/monitoringscape/
> >
> > Does anyone use a 3rd party software to monitor process's in your
> > cloudstack server farm and hypervisor?
> >
> > jeremy
> >
>

Reply via email to