Uploaded image for project: 'OpenNMS'
  1. OpenNMS
  2. NMS-5845

VMware integration not gathering statistics on VM host hardware collections such as vmware4Disk or vmware4Cpu

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.11.90
    • Fix Version/s: 1.11.91, 1.13.0
    • Security Level: Default (Default Security Scheme)
    • Labels:
      None
    • Environment:
      1.11.90 tested with VMware 4.0 Update 2 vSphere Server
      1.11.91-0.20130422.3 snapshot tested with VMware 5.1 vSphere Server

      Description

      Hello,

      I am particularly interested in getting OpenNMS to record disk device latency statistics as VMware itself seems to only allow these to be viewed in real-time and does not record them for later analysis.

      The particular data points I would like are already configured to be recorded in the default config files:

      e.g. for VMware 5

      <vmware-group name="vmware5Disk" resourceType="vmware5Disk">
      ...
      <attrib name="disk.deviceReadLatency.average" alias="DiskDeRdLyAvg" type="Gauge"/>
      <attrib name="disk.deviceWriteLatency.average" alias="DiskDeWeLyAvg" type="Gauge"/>
      ...
      </vmware-group>

      VMware host performance data (and CIM server hardware data) at the node level is being collected as expected. However, the data points that are part of a collection are being correctly enumerated but no data is being collected afterwards (no .jrb files are created in these subfolders, though .jrb files area created for the same node's node-level data fine).

      If anyone has gotten this to work, any tips would be appreciated!

      This is the resource type for which I am not seeing data collection happen.

      <resourceType name="vmware5Disk" label="VMware v5 Disk" resourceLabel="$

      {DiskName}

      ">
      <persistenceSelectorStrategy class="org.opennms.netmgt.collectd.PersistAllSelectorStrategy"/>
      <storageStrategy class="org.opennms.netmgt.dao.support.IndexStorageStrategy"/>
      </resourceType>

      Devices are found correctly.

      /var/lib/opennms/rrd/snmp/1/vmware5Disk# ls -la
      total 32
      drwxrwxr-x 6 root root 4096 Apr 23 10:00 .
      drwxrwxr-x 13 root root 12288 Apr 23 10:05 ..
      drwxrwxr-x 2 root root 4096 Apr 23 10:00 naa.600508b1001c592f0e725819fca959cc
      drwxrwxr-x 2 root root 4096 Apr 23 10:00 naa.600508b1001c925e7bc47896a06b3049
      drwxrwxr-x 2 root root 4096 Apr 23 10:00 naa.600508b1001ce44d44d48212698a1b64
      drwxrwxr-x 2 root root 4096 Apr 23 10:00 naa.600508b1001ce60f7da35ed283eb29ea

      root@wwlhinMonitor02:/var/lib/opennms/rrd/snmp/1/vmware5Disk# ls -la *
      naa.600508b1001c592f0e725819fca959cc:
      total 12
      drwxrwxr-x 2 root root 4096 Apr 23 10:00 .
      drwxrwxr-x 6 root root 4096 Apr 23 10:00 ..
      rw-rw-r- 1 root root 83 Apr 23 10:00 strings.properties

      naa.600508b1001c925e7bc47896a06b3049:
      total 12
      drwxrwxr-x 2 root root 4096 Apr 23 10:00 .
      drwxrwxr-x 6 root root 4096 Apr 23 10:00 ..
      rw-rw-r- 1 root root 83 Apr 23 10:00 strings.properties

      naa.600508b1001ce44d44d48212698a1b64:
      total 12
      drwxrwxr-x 2 root root 4096 Apr 23 10:00 .
      drwxrwxr-x 6 root root 4096 Apr 23 10:00 ..
      rw-rw-r- 1 root root 83 Apr 23 10:00 strings.properties

      naa.600508b1001ce60f7da35ed283eb29ea:
      total 12
      drwxrwxr-x 2 root root 4096 Apr 23 10:00 .
      drwxrwxr-x 6 root root 4096 Apr 23 10:00 ..
      rw-rw-r- 1 root root 83 Apr 23 10:00 strings.properties

      Looking at collectd.log:

      1. look for updates in .rrd files expected in vmware5... folders:
        grep "updating RRD" collectd.log | grep vmware5
        (returns no found lines)

      However, there are many updates of jrb files for node-level data:
      collectd.log:2013-04-23 20:29:49,773 INFO [LegacyScheduler-Thread-44-of-50] RrdUtils: updateRRD: updating RRD file /var/lib/opennms/rrd/snmp/1/ResCpuMaxLd5Lat.jrb with values '1366763390:0'
      collectd.log:2013-04-23 20:29:49,774 INFO [LegacyScheduler-Thread-44-of-50] RrdUtils: updateRRD: updating RRD file /var/lib/opennms/rrd/snmp/1/ResCpuActav15Lat.jrb with values '1366763390:9300'

      Looking for a specific disk device shows collection attempts but no data seems to be retrieved or stored:

      grep naa.600508b1001ce60f7da35ed283eb29ea collectd.log

      2013-04-23 20:29:49,665 DEBUG [LegacyScheduler-Thread-44-of-50] VmwareMultiInstanceCollectionResource: Adding attribute org.opennms.netmgt.collectd.vmware.vijava.VmwareCollectionAttribute: VmwareCollectionAttribute vmware5DiskName=naa.600508b1001ce60f7da35ed283eb29ea to group AttrGroupType[name=vmware5Disk, ifType=all] for naa.600508b1001ce60f7da35ed283eb29ea@1
      2013-04-23 20:29:49,665 DEBUG [LegacyScheduler-Thread-44-of-50] VmwareMultiInstanceCollectionResource: Adding attribute org.opennms.netmgt.collectd.vmware.vijava.VmwareCollectionAttribute: VmwareCollectionAttribute vmware5StPthName=sas.50014380225a8940-sas.14380225a8940-naa.600508b1001ce60f7da35ed283eb29ea to group AttrGroupType[name=vmware5StPth, ifType=all] for sas.50014380225a8940-sas.14380225a8940-naa.600508b1001ce60f7da35ed283eb29ea@1
      2013-04-23 20:29:49,780 INFO [LegacyScheduler-Thread-44-of-50] OneToOnePersister: Persisting data for resource Node[1]/type[vmware5Disk]/instance[naa.600508b1001ce60f7da35ed283eb29ea]
      2013-04-23 20:29:49,780 DEBUG [LegacyScheduler-Thread-44-of-50] AttributeGroup: Visiting Group AttrGroupType[name=vmware5Disk, ifType=all] for naa.600508b1001ce60f7da35ed283eb29ea@1
      2013-04-23 20:29:49,781 DEBUG [LegacyScheduler-Thread-44-of-50] AttributeGroup: AttrGroupType[name=vmware5Disk, ifType=all] for naa.600508b1001ce60f7da35ed283eb29ea@1.shouldPersist = true
      2013-04-23 20:29:49,781 DEBUG [LegacyScheduler-Thread-44-of-50] VmwareCollectionAttribute: Visiting attribute VmwareCollectionAttribute vmware5DiskName=naa.600508b1001ce60f7da35ed283eb29ea
      2013-04-23 20:29:49,781 DEBUG [LegacyScheduler-Thread-44-of-50] OneToOnePersister: Persisting VmwareCollectionAttribute vmware5DiskName=naa.600508b1001ce60f7da35ed283eb29ea
      2013-04-23 20:29:49,781 DEBUG [LegacyScheduler-Thread-44-of-50] OneToOnePersister: Storing attribute VmwareCollectionAttribute vmware5DiskName=naa.600508b1001ce60f7da35ed283eb29ea
      2013-04-23 20:29:49,782 INFO [LegacyScheduler-Thread-44-of-50] OneToOnePersister: Persisting data for resource Node[1]/type[vmware5StPth]/instance[sas.50014380225a8940-sas.14380225a8940-naa.600508b1001ce60f7da35ed283eb29ea]
      2013-04-23 20:29:49,782 DEBUG [LegacyScheduler-Thread-44-of-50] AttributeGroup: Visiting Group AttrGroupType[name=vmware5StPth, ifType=all] for sas.50014380225a8940-sas.14380225a8940-naa.600508b1001ce60f7da35ed283eb29ea@1
      2013-04-23 20:29:49,782 DEBUG [LegacyScheduler-Thread-44-of-50] AttributeGroup: AttrGroupType[name=vmware5StPth, ifType=all] for sas.50014380225a8940-sas.14380225a8940-naa.600508b1001ce60f7da35ed283eb29ea@1.shouldPersist = true
      2013-04-23 20:29:49,782 DEBUG [LegacyScheduler-Thread-44-of-50] VmwareCollectionAttribute: Visiting attribute VmwareCollectionAttribute vmware5StPthName=sas.50014380225a8940-sas.14380225a8940-naa.600508b1001ce60f7da35ed283eb29ea
      2013-04-23 20:29:49,782 DEBUG [LegacyScheduler-Thread-44-of-50] OneToOnePersister: Persisting VmwareCollectionAttribute vmware5StPthName=sas.50014380225a8940-sas.14380225a8940-naa.600508b1001ce60f7da35ed283eb29ea
      2013-04-23 20:29:49,782 DEBUG [LegacyScheduler-Thread-44-of-50] OneToOnePersister: Storing attribute VmwareCollectionAttribute vmware5StPthName=sas.50014380225a8940-sas.14380225a8940-naa.600508b1001ce60f7da35ed283eb29ea

      I also tested 1.11.90 with VMware 4.0 Update 2 vSphere Server, but the same behavior occurred – vmware4Disk directory has all disk devices created as subfolders with a strings.properties file for each, but no .rrd files.

      Please see the wiki at http://www.opennms.org/wiki/Featurebranch/feature-vmware for the tested procedure using VMware 4.0.

      Regards,
      Tim Miller Dyck

        Attachments

          Activity

            People

            • Assignee:
              indigo Ronny Trommer
              Reporter:
              timmillerdyck Tim Miller Dyck
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: