Uploaded image for project: 'Observium'
  1. Observium
  2. OBS-3618

VMWare ESXi Volume/Datastore Names/Symlinks

Details

    • Bug
    • Resolution: Unresolved
    • Minor
    • None
    • Community Edition
    • Discovery
    • Debian Buster

    Description

      Hi, 

      Wondering if it is possible when polling an ESXi server to bring back the Datastore names that have been set in VMware, as opposed to the Volume ID strings that are returned.

       

      Would make it easier when monitoring to know which Datastore is which without having to manually link the two together.

       

      Unless I am missing something here.

       

      Many thanks, 

       

      Liam

      Attachments

        Activity

          [OBS-3618] VMWare ESXi Volume/Datastore Names/Symlinks

          Hi Liam Hughes, we have not received the additional information requested earlier from you in this issue 'Hi, 

          Wondering if it is possible when polling an ESXi server to bring back the Datastore names that have been set in VMware, as opposed to the Volume ID strings that are returned.

           

          Would make it easier when monitoring to know which Datastore is which without having to manually link the two together.

           

          Unless I am missing something here.

           

          Many thanks, 

           

          Liam'!

          Issues without your response will be closed within 2 weeks.

          landy Mike Stupalov added a comment - Hi Liam Hughes, we have not received the additional information requested earlier from you in this issue 'Hi,  Wondering if it is possible when polling an ESXi server to bring back the Datastore names that have been set in VMware, as opposed to the Volume ID strings that are returned.   Would make it easier when monitoring to know which Datastore is which without having to manually link the two together.   Unless I am missing something here.   Many thanks,    Liam'! Issues without your response will be closed within 2 weeks.

          I don't think VMWare exposes this information in SNMP. There doesn't seem to be any place for it in their MIBs.

          adama Adam Armstrong added a comment - I don't think VMWare exposes this information in SNMP. There doesn't seem to be any place for it in their MIBs.

          Please make and attach additional information about the device:

          • full snmp dump from device:

            snmpwalk -v2c -c <community>  --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk
            snmpwalk -v2c -c <community>  --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk

            If device not support SNMP version 2c, replace -v2c with -v1.

          • If you have problems with discovery or poller processes, please do and attach these debugs:

            ./discovery.php -d -h <device>
            ./poller.php -d -h <device>

          • additionally attach device and/or vendor specific MIB files

          Note, this comment is added automatically.

          bot Observium Bot added a comment - Please make and attach additional information about the device: full snmp dump from device: snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk If device not support SNMP version 2c, replace -v2c with -v1. If you have problems with discovery or poller processes, please do and attach these debugs: ./discovery.php -d -h <device> ./poller.php -d -h <device> additionally attach device and/or vendor specific MIB files Note, this comment is added automatically.

          People

            landy Mike Stupalov
            lhughes Liam Hughes
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated: