APM 4.0 is currently in the RC phase, and GA is right around the corner. In addition to the Virtual Infrastructure Monitoring we released with NPM 10.1, APM 4.0 will also include a new VMware component monitor. Where the Virtual Infrastructure Monitoring in NPM 10.1 gives you basic performance statistics about your virtual infrastructure, the new APM VMware component monitor will allow you to monitor almost any statistic that’s available via the VMware API. Because APM is exposing statistics directly available via the VMware API, this new component monitor will give you tremendous breadth in terms of what you need to monitor in your VMware virtual infrastructure. Let’s take a look.
For those of you familiar with building your own templates using the Process Browser in APM, you’ll find a new component monitor type available for selection. Select VMware Performance Counter Monitor and click Next.
Next, you’ll select a target machine which APM will use to browse the VMware API. The target machine should be a vCenter server or an ESX host. APM will know which one you’ve selected, and expose the appropriate performance counters on the next screen. Select a vCenter or ESX host then click Next.
Next you’ll select whether you want to apply this monitor to a single machine or multiple machines. This selection is necessary to determine which performance counters are available for the monitor. Selecting ‘Multiple Systems’ will expose generic counters that are available on any VMware system; selecting ‘A single system’ will expose counters for a specific virtual machine, host, or vCenter. In this example I’ve selected Multiple systems, which will give me a generic list of counters from which to choose. On this page you’ll also select the VMware Entity type (e.g. VM, ESX host, resource pool, etc.).
Last you’ll select the Performance Object you’d like to monitor. In this example I’ve selected Memory, which exposes the counters in the screenshot above. Select the counters you want to monitor and click Next.
In the next set of steps you’ll confirm the components that will be monitored, and decide if you want to create a new monitor or template, or add these components to an existing monitor or template. Last, you’ll assign the monitor to the appropriate nodes in APM.
For those of you participating in the APM 4.0 RC, the latest build that includes this new component monitor is in your customer portal if you haven’t already downloaded it. Check it out; we’d love to hear your feedback.