LIVE Webinar: Dec. 19, 1pm CSTLearn how to overcome the challenges posed by containerized microservices in highly dynamic IT environments.
451 Research: Key Trends in Machine Learning, AI & Cloud
Zenoss is the only enterprise monitoring solution certified Nutanix Ready - Integrated.
Zenoss Partner Portal
Become a Partner
Learn. Discuss. Participate.Join thousands of Zenoss users and experts to learn, discuss and participate in the Zenoss Community.
Customer Support Portal
Zenoss Learning Center
Forrester Insights:Powering Digital Transformation With Intelligent Monitoring & Analytics
Customers for LifeAt Zenoss, our customers are at the core of everything we do.
Request A Demo
This is an Open Source ZenPack developed by Zenoss, Inc. Enterprise support for this ZenPack is available to commercial customers with an active subscription.
Monitoring for Apache CloudStack and by extension, Citrix CloudPlatform.
The easiest way to start monitoring CloudStack is to navigate to the Infrastructure page, click the *+* menu to add a device and choose Add CloudStack. Fill out the Device to Create, URL, API Key, and Secret Key fields, select a collector, then click OK. The URL should only include the protocol, host and port (i.e. http://cloudstack.example.com/). You can find or create the keys by logging into the CloudStack web interface and navigate to Accounts and users.
Zenoss will then add the CloudStack device to the system. For root administrator users, the associated zones, pods, clusters, hosts, routers, system VMs and VMs will also be added; zones, routers and VMs for domain administrator users; zones and VMs for all non administrator users. Monitoring will also start after the discovery is complete.
If you are upgrading from a version earlier than 1.1.3 you will need to perform the following manual steps after upgrading to fix the collection of network throughput metrics. These steps must be performed on any Zenoss collector server monitoring CloudStack. These steps will remove all historical performance data collected for network throughput, but that matters less because the historical data is completely wrong. If you do not perform these steps, the network data collected after upgrading will continue to be wrong.
Note: These steps are only necessary on Zenoss versions earlier than 5.0.
su - zenoss
find . -name cloudstack_network\*.rrd -delete
Once you've successfully added a CloudStack cloud to Zenoss you will begin to see the following metrics available for the entire cloud to root administrator users. These numbers are aggregated from all zones, pods, clusters and hosts.
The same list of metrics are available for each zone to root administrator users. The same metrics with the exception of public IPs and secondary storage are also available for each pod.
The following metrics are available aggregated to each cluster, and for each host.
The following list of metrics for VMs is available to non root administrator users.
CloudStack has both alerts and events. Once you've successfully added a CloudStack cloud to Zenoss you will automatically receive all CloudStack alerts as events in Zenoss. You will also automatically receive all CloudStack events. However, the events will go straight into your event history by default.
To avoid overloading CloudStack and Zenoss, only the last one (1) hour of events will be checked. This allows for timezone discrepancy between the Zenoss and CloudStack servers as well as some downtime without missing events. There is no real-time event collection mechanism with the CloudStack API, so alerts and events will only be polled once per minute.
Installing the ZenPack will add the following items to your Zenoss system.
View the discussion thread.
This ZenPack is developed and supported by Zenoss Inc. Contact Zenoss to request more information regarding this or any other ZenPacks. Click here to view all available Zenoss Open Source ZenPacks.