We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda Managed Workplace

Setting Up Monitoring for VMware

  • Last updated on

The VMware service module includes three policy modules that you can set up to monitor VMware hosts:

VMware ESXi Host Policy Module for Service Module (Default) This is the default policy module for the VMware service module. This policy module has automatic application rules pre-configured to automatically monitor any device in which the OS name starts with VMware ESXi 5.5, VMware ESXi 5.1, or VMkernel.

VMWare ESXi Host Policy Module for Service Module (Optional 1) This is a copy of the default VMware ESXi Host Policy Module for Service Module. You can modify the monitor and alert configurations in this policy module to monitor hosts for which you have unique monitoring requirements.

VMWare ESXi Host Policy Module for Service Module (Optional 2) This is a second copy of the default VMWare ESXi Host Policy Module for Service Module, which you can also modify by setting lower thresholds for monitoring and alerting.

It is recommended that you use the default policy module to monitor host machines with typical monitoring requirements. The optional policy modules should be used when monitoring for a single host or a group of hosts falls outside the monitoring and alerting thresholds that are provided with the default VMware policy module.

For example, you can change the alerting thresholds to one of the optional policy modules, then apply the policy module to hosts that require a different alert threshold for memory or CPU usage. The optional policy modules are also useful if you have a group of hosts connected to a specific external storage array in which you want to monitor the total disk latency so that you are alerted to poor performance.

Understanding VMWare Monitors

The VMware policy modules contain four VMware monitor types.

Note: These four monitor types are only available for the VMware ESXi service module policy modules. They are not available when adding monitors to other policy modules in Barracuda Managed Workplace.

VMware Events This monitor type pulls events logged on a VMware ESXi host with a severity level of Warning, Error, or Critical.

VMware Guest Performance Performance counters related to the virtual guest. Note that these performance counters are pulled from the host directly and do not necessarily match performance metrics pulled directly from the virtual guest operating system. Note that you cannot alert on guest performance data.

VMware Inventory Collection Used to pull hardware/software inventory objects from both the virtual guests and the host.

VMware Performance Pulls performance counters relating to the host.

Note: Windows and VMware performance monitors are collected using different methods. VMware allows historical data collection, whereas Windows does not. In rare cases, alerts may generate on the initial application of the service module, resulting in what appears to be the alert not following its set configuration because it was generated based on historical data.

Viewing and Changing the Alert Thresholds on a Policy Module
  1. In Service Center, click Configuration > Service Modules.
  2. From the list of service modules, select VMware.
  3. Click the name of a VMware policy module.
  4. Click the Monitors tab.
  5. Click the name of a monitor.
  6. Click the Alerts tab.
  7. Do any of the following:
    • To view or modify an existing alert configuration, click the name of the alert configuration.
    • To add an alert configuration, click Add Alert Configuration.
Applying the VMware Policy Modules

To begin monitoring with the VMware ESXi service module, you must either add the policy modules to a policy set, or manually apply it to a site, group, or device.

Note: The two optional policy modules have automatic application rules applied by default that prevent these policy modules from monitoring; the default rules state that a VMware host operating system must start with VMware ESXi 5.5, VMkernel, and VMware ESXi 5.1. If you plan to use one of these policy modules in a policy set, you must remove two of these rules for automatic monitoring to function.

  1. in Service Center, click Configuration > Service Modules.
  2. From the list of service modules, select VMware.
  3. To select a policy set to associate with the policy modules in the VMware service module, do the following:
    1. In the Policy Set Membership area, click Add.
    2. Select the checkbox beside the name of the policy set to which you want to associate with this service module.
    3. Click Add.
    Tip: After adding the policy set, you can click the policy set name to view and modify the sites, groups, and devices within its scope.
  4. To manually apply monitoring, do any of the following:
    1. To apply the policy module to a group, click a policy module name. Click the Manual Application tab, and then under Applied Groups, click Add. Filter on the Group Type, if desired. Select the group and click Add.
    2. To apply the policy module to a device, click a policy module name. Click the Manual Application tab, and then under Applied Devices, click Add. Filter the list of devices. Select the device and click Add.

Note: When applying the policy module, you must ensure that the devices to which it is applied, whether through policy sets, groups, or manually added devices, are valid host devices. If the policy module is applied to non-host devices, then some of the monitors will collect data for these devices and present it in the service module dashboards. For example, memory available, memory page faults, etc.

 

 

Last updated on