Accelerate Your Path to Full-Stack Monitoring and Alerting
Register for this live webinar featuring Zenoss and VictorOps today!
Why Customers Choose Us
Discover why the largest companies in the world choose Zenoss.
Customer Support Portal
Zenoss Learning Center
Zenoss Partner Portal
Become a Partner
Top 5 Focus Areas to Succeed With DevOps
Forrester shares the tools, technologies and best practices to meet the challenges of today's modern IT environments.
Learn. Discuss. Participate.
Join thousands of Zenoss users and experts to learn, discuss and participate in the Zenoss Community.
Hybrid IT Monitoring
Zenoss provides complete visibility into physical, virtual, cloud and converged environments.
Request A Demo
This ZenPack is included with commercial versions of Zenoss and enterprise support for this ZenPack is provided to Zenoss customers with an active subscription.
This ZenPack provides support for monitoring the Hyper-V role running on Windows 8, Windows 8.1, Server 2008 or Server 2012. Monitoring for the following Hyper-V entities is provided using txwinrm Async Python WinRM Client. See the Prerequisites section for details.
Note: Please restart zenoss after installing this ZenPack. Note that the commercial zenoss version requires ZenPacks.zenoss.Impact, otherwise the DynamicServices panel will be missing.
The features added by this ZenPack can be summarized as follows. They are each detailed further below.
The following entities will be discovered through an IP address, user name and password you provide. The attributes, tags and collections will be updated on Zenoss' normal remodeling interval which defaults to every 12 hours.
Note that all the discovered values for the attributes above are shown as of the last modeling time.
The following metrics will be collected every 5 minutes by default. The Average statistic is collected, and the graphed value is per second for anything that resembles a rate.
According to the following Hyper-V states this ZenPack will trigger events with an appropriate summary message.
You can optionally configure each monitored Hyper-V server to attempt to discover and monitor the guest operating systems running within each Hyper-V virtual machine. This requires that your Zenoss system has the network and server access it needs to monitor the guest operating system.
When combined with the Zenoss Service Dynamics product, this ZenPack adds built-in service impact capability for services running on Microsoft Hyper-V. The following service impact relationships are automatically added. These will be included in any services that contain one or more of the explicitly mentioned entities.
Use the following steps to start monitoring Hyper-V with Basic Authentication using the Zenoss web interface. Please check the Prerequisites section before adding device to ensure the Hyper-V target server has the correct WinRM setting.
Note: When adding a device, please make sure that you choose a correct Windows version. Otherwise the device modeling and monitoring may result in an error.
Use the following steps to start monitoring Hyper-V with Kerberos Authentication using the Zenoss web interface. Please check the Prerequisites section before adding device to ensure the Hyper-V target server has the correct WinRM setting.
Note: HyperV and MicrosoftWindows ZenPacks share krb5.conf file as well as tools for sending/receiving data. Therefore if either HyperV or Windows device has a correct zWinKDC setting, it will be used for another device as well.
It is possible to have Hyper-V server in both /Server/Microsoft/HyperV and /Server/Microsoft/Windows. Navigate to the Infrastructure page and use Add a single device... from the add device button. Enter the Device Name, your Hyper-V server's IP address and select /Server/Microsoft/Windows device class. For more specific cases please read Microsoft Windows ZenPack documentation.
Use the following steps to configure Hyper-V device to use WinRM HTTPS using the Zenoss web interface. Please check the Prerequisites section before adding device to ensure the Hyper-V target server has the correct WinRM setting.
Alternatively you can use zenbatchload to add Hyper-V servers from the command line. To do this, you must create a text file with hostname, username and password of all the servers you want to add. Multiple endpoints can be added under the same /Devices/Server/Microsoft/HyperV section. Here is an example:
'/Devices/Server/Microsoft/HyperV' loader='hyperv', loader_arg_keys=['device_name', 'host', 'version', 'zWinRMUser', 'zWinRMPassword', 'zWinKDC','collector']
<HOST NAME> host='<HOST NAME or IP>', version='<WINDOWS VERSION>', zWinRMUser='<USER>', zWinRMPassword='<PASSWORD>', zWinKDC='<KDC>',collector='<COLLECTOR>', device_name='<HOST NAME>'
You can then load the Hyper-V servers into Zenoss Core or Resource Manager as devices with the following command.
$ zenbatchload <filename>
Use the following steps to configure virtual machine guest device discovery. Guest device discovery must be configured individually for each Hyper-V server.
Note: The above instructions use the max values for MaxConcurrentOperationsPerUser and WinRS MaxShellsPerUser. If you do not want to set these to the max, then a value of 50 should be adequate. The default is 5 on both, which will cause problems because Zenoss will open up concurrent requests for each WQL query and set of Perfmon counters.
Note: If you choose to use Basic authentication it is highly recommended that you also configure HTTPS. If you do not use the HTTPS protocol your user name and password will be sent over in clear text. If you have challenges setting up HTTPS on the Windows clients and you don't mind sending the payload in clear text but require the user name and password to be encrypted then using the Kerberos authentication is the best option. HTTPS is not required for Kerberos but is recommended.
Note: If you choose to take the WinRM default configurations you must supply Kerberos authentication settings in the zProperties. The Kerberos authentication process requires a ticket granting server. In the Microsoft Active Directory environment the AD Server is also the KDC. The zWinKDC value must be set to the IP address of the AD Server and the collector must be able to sent TCP/IP packets to this server. Once this is set your zWinRMUser must be a FQDN such as jsmith@Zenoss.com and the zWinRMPassword must be set correctly for this user account.
Note: The HTTPS setup must be completed on each client. At this time we do not have notes on automating this task but are currently in the process of testing several options. To successfully encrypt your payload between the Zenoss server and the Windows client you must install a Server Authentication certificate on tbe client machine. The process for requesting and installing the appropriate certificate can be found at the following URL. http://blogs.technet.com/b/meamcs/archive/2012/02/25/how-to-force-winrm-to-listen-interfaces-over-https.aspx Once the client has the correct certificate installed you only need to change the zWinScheme to HTTPS and zWinRMPort to 5986. If you are still having challenges setting up HTTPS on the client you can execute the following command on any AD server to verify the appropriate SPN record exists for Kerberos authentication.
setspn -l hostname1
If you do not see a record with HTTPS/ at the beginning of the hostname you will need to create the record. example: setspn -s HTTPS/hostname1.zenoss.com hostname1
setspn -s HTTPS/hostname1.zenoss.com hostname1
yum -y install krb5-workstation
Please refer the the Zenoss Service Dynamics documentation if you run into any of the following problems:
If you cannot find the answer in the documentation, then Resource Manager (Service Dynamics) users should contact Zenoss Customer Support. Core users can use the #zenoss IRC channel or the community.zenoss.org forums.
This ZenPack provides additional support for Zenoss Analytics. Perform the following steps to install extra reporting resources into Zenoss Analytics after installing the ZenPack.
You can now navigate back to the HyperV ZenPack folder in the repository to see the HyperV Domain added by the bundle.
Domains can be used to create Ad Hoc views using the following steps.
Installing this ZenPack will add the following items to your Zenoss system.
View the discussion thread.
This ZenPack is developed and supported by Zenoss Inc. Commercial ZenPacks are available to Zenoss commercial customers only. Contact Zenoss to request more information regarding this or any other ZenPacks. Click here to view all available Zenoss Commercial ZenPacks.