Ad Widget

Collapse

VMware vSphere monitoring with vPoller 0.5.1

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • noeand
    Junior Member
    • Apr 2014
    • 24

    #1

    VMware vSphere monitoring with vPoller 0.5.1

    vPoller (Distributed vSphere API Proxy) version 0.5.1 has been released.

    This release of vPoller comes with lots of new features and bug fixes and with even more Zabbix items for your VMware vSphere environment!

    The changes that made it into vPoller since I last posted about it in this forum are a lot, so I will try to summarize some of the highlights:

    * vPoller can now use caching of vSphere managed objects, which speeds polling of metrics a lot and reduces the number of API calls to the vSphere host
    * Support for VMware vSphere Alarms for Datacenters, Clusters, Hypervisors, Virtual Machines and Datastores.
    * Support for VMware vSphere Performance Metrics - both real-time and historical ones
    * You can now even monitor the vSphere Sessions with vPoller and Zabbix
    * Support for agent-less process monitoring inside Virtual Machines
    * vPoller now comes with native loadable module for Zabbix
    * vPoller templates for Zabbix versions 2.2.x and 2.4.x
    * Python 3.2.x support and later
    * Lots of documentation updates
    * and more ...

    The vPoller documentation can be found in the link below where you can learn more about vPoller and how it works.

    * http://vpoller.readthedocs.org/en/latest/index.html

    This page provides some examples about using vPoller in your vSphere environment:

    * http://vpoller.readthedocs.org/en/latest/examples.html

    And here you can read more about the vPoller integration with Zabbix.

    * http://vpoller.readthedocs.org/en/la...er-zabbix.html

    In the above link you can also find some example screenshots of vPoller and Zabbix monitoring a VMware vSphere environment.
  • pc99096
    Senior Member
    • Oct 2011
    • 193

    #2
    is it possible to use vpoller directly with a free esxi host without vcenter?
    datastore.discover seems to be working, but datastore.get on the same platform returns "Cannot find object":

    Code:
    # vpoller-client -m datastore.discover -V ESXI
    {"msg": "Successfully discovered objects", "result": [{"name": "datastore1"}], "success": 0}
    # vpoller-client -m datastore.discover -V VCENTER
    {"msg": "Successfully discovered objects", "result": [{"name": "datastore1"}], "success": 0}
    Code:
    # vpoller-client -V ESXI  -m datastore.get -p summary.capacity -n ds:///vmfs/volumes/54f4a608-2c2592dc-4e51-001e6745ce74/
    {"msg": "Cannot find object ds:///vmfs/volumes/54f4a608-2c2592dc-4e51-001e6745ce74/", "success": 1}
    
    # vpoller-client -V VCENTER  -m datastore.get -p summary.capacity -n ds:///vmfs/volumes/54f4a608-2c2592dc-4e51-001e6745ce74/
    {"msg": "Successfully retrieved object properties", "result": [{"summary.capacity": 949993078784, "info.url": "ds:///vmfs/volumes/54f4a608-2c2592dc-4e51-001e6745ce74/", "name": "datastore1"}], "success": 0}

    Comment

    • oitss
      Member
      • Dec 2013
      • 62

      #3
      Please, try this way

      Code:
      # vpoller-client -V ESXI  -m datastore.get -p summary.capacity -n /vmfs/volumes/54f4a608-2c2592dc-4e51-001e6745ce74/

      Comment

      • pc99096
        Senior Member
        • Oct 2011
        • 193

        #4
        no, it does not work either:

        Code:
        {"msg": "Cannot find object /vmfs/volumes/54f4a608-2c2592dc-4e51-001e6745ce74/", "success": 1}

        Comment

        • oitss
          Member
          • Dec 2013
          • 62

          #5
          Even without ending / ?

          Code:
          vpoller-client -V ESXI  -m datastore.get -p summary.capacity -n /vmfs/volumes/54f4a608-2c2592dc-4e51-001e6745ce74

          Comment

          • pc99096
            Senior Member
            • Oct 2011
            • 193

            #6
            actually it is working without /
            good catch, thanks!
            Code:
            # vpoller-client -V ESXI  -m datastore.get -p summary.capacity -n /vmfs/volumes/datastore1
            {"msg": "Successfully retrieved object properties", "result": [{"summary.capacity": 949993078784, "info.url": "/vmfs/volumes/54f4a608-2c2592dc-4e51-001e6745ce74", "name": "datastore1"}], "success": 0}

            Comment

            Working...