Ad Widget

Collapse

Struggling with esxi host monitoring

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • mzimm88
    Junior Member
    • Oct 2016
    • 5

    #1

    Struggling with esxi host monitoring

    Hi everyone!

    I have taken over an environment and I am trying to monitor my VMware hosts with Zabbix. I don't need VM discovery. I am looking to monitor the basic cpu, memory, and bandwidth metrics on my Esxi 5.1 host. I have been searching google/forum search for a few days with nothing that seems to address my issue.

    Steps I have taken.

    1) Opened Zabbix ports on the host firewall. I can curl the Host from my Zabbix box and get what I believe to be the correct response

    HTTP/1.1 400 Bad Request
    Date: Fri, 7 Oct 2016 16:23:41 GMT
    Connection: close
    Content-Type: text; charset=plain
    X-Frame-Options: DENY
    Content-Length: 0


    2) confirmed that I am using the correct username/password/ip for the Host machine. Connected directly to the Esxi host with the same user/pass that I am providing Zabbix.

    3) Added the three credentials to my Hosts "macro" page

    {$PASSWORD} => <my password>
    {$USERNAME} => <my username>
    {$URL} => https:/<MY IP>/sdk


    4) Applied the "Template Virt VMware" to the configured host entry in Zabbix.


    I get the following in my Zabbix_server.conf and see some possible issues.

    In substitute_key_macros() data:'vmware.cluster.discovery[{$URL}]'
    End of substitute_key_macros():SUCCEED data:'vmware.cluster.discovery[https:/<MY IP ADDR>/sdk]'
    In get_value() key:'vmware.cluster.discovery[{$URL}]'
    In get_value_simple() key_orig:'vmware.cluster.discovery[{$URL}]' addr:'<MY IP ADDR>'
    In get_vmware_service() 'root'@'https:/<MY IP ADDR>/sdk'
    In zbx_vmware_get_service() root@https:/<MY IP ADDR>/sdk
    End of zbx_vmware_get_service():FAIL
    End of get_vmware_service()nil)
    In substitute_key_macros() data:'vmware.hv.discovery[{$URL}]'
    End of substitute_key_macros():SUCCEED data:'vmware.hv.discovery[https:/<MY IP ADDR>/sdk]'
    In get_value() key:'vmware.hv.discovery[{$URL}]'
    In get_value_simple() key_orig:'vmware.hv.discovery[{$URL}]' addr:'<MY IP ADDR>'
    In get_vmware_service() 'root'@'https:/<MY IP ADDR>/sdk'
    In zbx_vmware_get_service() root@https:/<MY IP ADDR>/sdk
    End of zbx_vmware_get_service():FAIL
    End of get_vmware_service()nil)
    __zbx_zbx_setproctitle() title:'vmware collector #1 [updated 0, removed 0 VMware services in 0.000003 sec, querying VMware services]'
    In vmware_service_update() root@https:/<MY IP ADDR>/sdk
    In vmware_service_authenticate() 'root'@'https:/<MY IP ADDR>/sdk'
    End of vmware_service_authenticate():FAIL
    In vmware_service_update_perf_entities()
    End of vmware_service_update_perf_entities() entities:0
    End of vmware_service_update():FAIL


    In get_value() key:'vmware.eventlog[{$URL}]'
    In get_value_simple() key_orig:'vmware.eventlog[{$URL}]' addr:'<MY IP ADDR>'
    In get_vmware_service() 'root'@'https:/<MY IP ADDR>/sdk'
    In zbx_vmware_get_service() root@https:/<MY IP ADDR>/sdk
    End of zbx_vmware_get_service():SUCCEED
    End of get_vmware_service()nil)
    Item [<MY IP ADDR>:vmware.eventlog[{$URL}]] error: Couldn't resolve host name
    In substitute_key_macros() data:'vmware.fullname[{$URL}]'
    End of substitute_key_macros():SUCCEED data:'vmware.fullname[https:/<MY IP ADDR>/sdk]'


    1) End of zbx_vmware_get_service():FAIL
    I feel like this might be one of two things. My password could be wrong or Zabbix is unable to connect to try and authenticate. This issue is annoying because I can confirm that my user/pass will allow me to connect directly to the host with the esxi client with root permissions, I also cannot see any deny attempts in the /var/logs/ on the host machine. As for connectivity, my curl is returning what people have reported as being a correct response. I also cannot find any logging in vmware to confirm if something was blocked.


    2)Item [<MY IP ADDR>:vmware.eventlog[{$URL}]] error: Couldn't resolve host name

    I feel like this is probably due to Zabbix running more modern queries against my old Esxi 5.1 machine. Since some do appear to resolve and some do not. Also, it is not using any fqdn (talking directly to the ip instead).


    Any thoughts? I have been working on this for a few days and I am seriously annoyed that something so simple is beating me up. (I wish snmp still provided good information).
  • mzimm88
    Junior Member
    • Oct 2016
    • 5

    #2
    just a small update. I am on Zabbix 3.0

    Comment

    • Atsushi
      Senior Member
      • Aug 2013
      • 2028

      #3
      Do you have two slash to the after of the https: in the value of the URL?

      ex.
      Code:
      {$URL} => https://<MY IP>/sdk

      Comment

      • mzimm88
        Junior Member
        • Oct 2016
        • 5

        #4
        Originally posted by Atsushi
        Do you have two slash to the after of the https: in the value of the URL?

        ex.
        Code:
        {$URL} => https://<MY IP>/sdk

        **sigh** I just came here to update with my resolution. This was indeed to the issue (and thank you for taking the time to actually look at this). The amount of work I did on this was absurd. Packet capturing and the works...

        Comment

        • mzimm88
          Junior Member
          • Oct 2016
          • 5

          #5
          Just a follow up question. Discovery is working great now!

          I do not see any graphs or triggers once a machine is discovered though. I'm thinking either

          1) I am missing a step with discovery. Maybe the process is not completed? I do not see an option to "keep this discovered node"

          2) I buggered up my templates while trying to get discovery working.

          thoughts?

          Comment

          • burn1024
            Member
            • Jun 2012
            • 52

            #6
            Didn't you say you don't need discovery?
            For discovery actions, go to configuration > actions > event source: discovery

            Comment

            Working...