Using Foglight to monitor Hyper-v environment

Using Foglight to monitor Hyper-v environment

Using Foglight to monitor Hyper-v environment

 Lately, I have been asked multiple times about using Foglight for Virtual Environments to monitor Microsoft hyper-v servers. Some of our large customers and many small ones too are either experimenting with Hyper-v or have adopted it in production environment.

Foglight (FVE) is platform agnostic. It supports VMware as well as Microsoft (and many more to come as market matures). One of the key advantages of using the performance monitoring solution from a large, independent software vendor like Dell is that it has the best partnerships with all vendors in the market and has resources to deliver.

Foglight’s hyper-v cartridge works a little differently than the VMware cartridge. This is due mainly to the platform limitations and typical solution architecture in customer environment. For example, vCenter is very prevalent whereas System Center not so in hyper-v environments. Also vCenter captures and saves configuration as well as performance data on VMware objects, whereas no such centralization is available in hyper-v environments.

So how do you install and configure the Foglight hyper-v cartridge?

Installation and Configuration

 In order to monitor hyper-v hosts and VMs, users would need to do two (2) main tasks:

-          Configure hyper-v hosts: setup and configure windows monitoring framework, provide secure access and configure appropriate security policy

-          Configure the agent: using Foglight hyper-v administration

 Configuring Hyper-v hosts

Foglight cartridge for hyper-v uses Windows Management Instrumentation (WMI) methods to connect to remote hosts and collect performance data. There are essentially two ways to connect to WMI from a remote computer (Foglight ‘agent’ runs on the Foglight Agent Manager server and connects remotely to the hyper-v hosts to collect the performance information).

You can either use Windows Remote Management (WinRM) or Distributed Common Object Model (DCOM) transports to connect to WMI infrastructure.

Let’s look at WinRM method of connecting to the WMI infrastructure. WinRM service is included with all windows servers and enabled by default.

Configure WinRM on monitored hosts to listen for remote connections. These can be accessed using HTTP or HTTPS. (We will use HTTP method as illustration).

  1. Login as Administrator (Domain Admin with local admin access) to be able to set security policies and ACLs.
    1. Run Command using command-line: winrm enumerate winrm/config/listener

  2. If no listener exists, create one using  winrm create winrm/config/listener?Address=*+Transport=HTTP
  3. Set WinRM to accept Basic authentication using: winrm set winrm/config/service/auth @{Basic="true"}
  4. If you are going to use HTTPS with WinRM, you will also need to configure Root Certificates for the Agent manager.
  5. Once the listeners are set for remote access, you can go to Foglight console and proceed to add the agent.

Configuring the Agent

 

 

  1. From Home screen, you can go directly to Hyper-v dashboard’s administration tab by clicking “Add Hyper-v” button.
  2. The configuration wizard is able to discover servers with hyper-v roles using Active Directory. If you wish, you can also manually enter the IP address/name of the server.

  1. You will also be asked to enter credentials that the server/agent should use. This credential could be server specific or Active Directory-wide.
  2. One the information is provided, the configuration is complete. It usually takes about 5 to 10 minutes for the first observations to get polled and dashboard updated.
  3. Once configured, the dashboard would look similar to this:

0