Ad Widget

Collapse

Problem monitoring Vmware 6.7

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • aros
    Junior Member
    • Sep 2018
    • 4

    #1

    Problem monitoring Vmware 6.7

    Hello

    I've Vmware infrastructure with 50Esxi 6.0 and 6.5 and a VCENTER 6.7.

    When I want to monitor datastore with default template I have this error :

    1530:20181206:151551.685 error reason for "0c8c51b3-6b8f-4dc1-972b-2a717b6b0c8c:vmware.hv.datastore.size[{$URL},{HOST.HOST},VMWarelun10]" changed: Performance counter data is not available.

    On vcenter 6.0 I dont have this problem.
    Maybe API 6.7 has changed and is not compatible with Zabbix template. Do you have information about that ?

    Thanks
  • dimir
    Zabbix developer
    • Apr 2011
    • 1080

    #2
    If it's possible for you to enable LogLevel=5 you will be able to get more information with XML requests/responses to get the idea what is causing that. But it'll be looooots of log information, you need to have big enough log file. Also you can change log levels on the fly:

    Code:
    zabbix_server -Rlog_level_increase="vmware collector"
    zabbix_server -Rlog_level_increase="vmware collector"
    and when done with it, get it back:
    Code:
    zabbix_server -Rlog_level_decrease="vmware collector"
    zabbix_server -Rlog_level_decrease="vmware collector"

    Comment

    • aros
      Junior Member
      • Sep 2018
      • 4

      #3
      I dont have more information about json with high log level but I find another log. Is not a Vmware API problem but a timeout :


      1533:20181206:160605.216 item "0469e5e2-b675-4e6e-b931-8cda9cc9d76f:vmware.hv.datastore.size[{$URL},{HOST.HOST},lun0]" became supported
      1533:20181206:161605.034 item "0469e5e2-b675-4e6e-b931-8cda9cc9d76f:vmware.hv.datastore.size[{$URL},{HOST.HOST},lun0]" became not supported: Timeout was reached
      1528:20181206:162604.907 error reason for "0469e5e2-b675-4e6e-b931-8cda9cc9d76f:vmware.hv.datastore.size[{$URL},{HOST.HOST},lun0]" changed: Performance counter data is not available.

      Maybe with 50esxi and 40 datastores generate too many API request ?


      Comment

      • dimir
        Zabbix developer
        • Apr 2011
        • 1080

        #4
        Interesting, perhaps report it as a bug in our bug tracker https://support.zabbix.com and post here the issue number.

        Comment

        • sfl
          Junior Member
          • Jun 2016
          • 26

          #5
          Same here with vmware 6.5.0

          Code:
          182239:20190718:161638.987 item "5014014b-a8ca-5047-655a-0be73791565a:vmware.vm.cpu.ready[{$URL},{HOST.HOST}]" became supported
          182239:20190718:164621.908 item "5014bf70-88d8-f85a-6e74-0955c220c6e5:vmware.vm.cpu.ready[{$URL},{HOST.HOST}]" became not supported: Performance counter data is not available.

          Comment

          • johansenfa
            Junior Member
            • Nov 2020
            • 11

            #6
            Did someone already find a solution on this?

            Comment

            Working...