Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-21391

VMware monitoring timeouts

    XMLWordPrintable

Details

    • Incident report
    • Status: Closed
    • Trivial
    • Resolution: Commercial support required
    • 5.0.26
    • None
    • Server (S)
    • Ubuntu 20.04.41
      vSphere/vCenter 7.0.3.00700 and 6.5.0.40000

    Description

      Steps to reproduce:

      1. Add vCenter host to zabbix via built-in template
      2. Start monitoring huge production
      3. See hundred of logs/unsupported items per day

      Result:
        1671:20220726:125532.755 item "[id-id-id-id]:vmware.vm.vfs.dev.read[\{$VMWARE.URL},\{HOST.HOST},scsi0:11,ops]" became not supported: Timeout was reached

      1674:20220726:125517.722 item "dc-vcenter:vmware.datastore.read[\{$VMWARE.URL},DS-01,latency]" became not supported: Counter datastore/totalReadLatency[average] for datastore DS-01 is not available for hypervisor hypervisor.corp: timeout was reached
      (many times, many items)

      Expected:

      no timeouts or unsupported items

       

      Problem occurred on 2 different environments virtual and physical zabbix server and different vcenter version. To reproduce problem you need to monitor ~2000 items, update interval is 1 minute.

       

      It occurs periodically, and restored too:

        1671:20220726:134932.535 item "id-id-id-id:vmware.vm.cpu.ready[\{$VMWARE.URL},\{HOST.HOST}]" became supported

       

      cat /var/log/zabbix/zabbix_server.log | grep vmware | grep -c 'became supported'
      118938

      config:

          1. Option: StartVMwareCollectors
      1.       Number of pre-forked vmware collector instances.
        #
      2. Mandatory: no
      3. Range: 0-250
      4. Default:
        StartVMwareCollectors=8
          1. Option: VMwareFrequency
      1.       How often Zabbix will connect to VMware service to obtain a new data.
        #
      2. Mandatory: no
      3. Range: 10-86400
      4. Default:
        VMwareFrequency=60
          1. Option: VMwarePerfFrequency
      1.       How often Zabbix will connect to VMware service to obtain performance data.
        #
      2. Mandatory: no
      3. Range: 10-86400
      4. Default:
        VMwarePerfFrequency=60
          1. Option: VMwareCacheSize
      1.       Size of VMware cache, in bytes.
      2.       Shared memory size for storing VMware data.
      3.       Only used if VMware collectors are started.
        #
      4. Mandatory: no
      5. Range: 256K-2G
      6. Default:
        VMwareCacheSize=32M
          1. Option: VMwareTimeout
      1.       Specifies how many seconds vmware collector waits for response from VMware service.
        #
      2. Mandatory: no
      3. Range: 1-300
      4. Default:
        VMwareTimeout=300

      Attachments

        Activity

          People

            zabbix.support Zabbix Support Team
            who0ps Taras
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: