Ad Widget

Collapse

Zabbix Proxy 2.2 + VMware

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • ccesario
    Junior Member
    • Dec 2013
    • 11
    #1

    Zabbix Proxy 2.2 + VMware

    Hello!

    I'd like to know if Zabbix Proxy 2.2 can support monitoring VMware, because I don't having success. But if I try monitoring Vmware by Zabbix (without proxy), it's work perfect.


    I see any messages like this in zabbix proxy log

    Code:
     1740:20131201:003124.599 In vmware_service_create_vm() vmid:'vm-39'
  1740:20131201:003124.600 In vmware_service_get_vm_data() vmid:'vm-39'
  1740:20131201:003124.605 End of vmware_service_get_vm_data():SUCCEED
  1740:20131201:003124.608 In vmware_service_get_vm_stats()
  1740:20131201:003124.608 In vmware_service_get_perfcounter_refreshrate()
  1740:20131201:003124.610 vmware_service_get_perfcounter_refreshrate() refresh_rate:20
  1740:20131201:003124.610 End of vmware_service_get_perfcounter_refreshrate():SUCCEED
  1740:20131201:003125.621 End of vmware_service_get_vm_stats():SUCCEED
  1740:20131201:003125.621 End of vmware_service_create_vm():SUCCEED
  1740:20131201:003125.622 End of vmware_service_create_hv():SUCCEED
  1740:20131201:003125.622 In vmware_service_get_event_data() event_session:'(null)'
  1740:20131201:003125.622 In vmware_service_get_event_session()
  1738:20131201:003126.998 vmware collector #1 [updated 0, removed 0 VMware services in 0.000003 sec, querying VMware services]
  1738:20131201:003126.999 vmware collector #1 [updated 0, removed 0 VMware services in 0.000003 sec, idle 5 sec]
  1739:20131201:003127.002 vmware collector #2 [updated 0, removed 0 VMware services in 0.000003 sec, querying VMware services]
  1739:20131201:003127.003 vmware collector #2 [updated 0, removed 0 VMware services in 0.000003 sec, idle 5 sec]
  1738:20131201:003131.999 vmware collector #1 [updated 0, removed 0 VMware services in 0.000003 sec, querying VMware services]
  1738:20131201:003131.999 vmware collector #1 [updated 0, removed 0 VMware services in 0.000003 sec, idle 5 sec]
  1739:20131201:003132.003 vmware collector #2 [updated 0, removed 0 VMware services in 0.000003 sec, querying VMware services]
  1739:20131201:003132.003 vmware collector #2 [updated 0, removed 0 VMware services in 0.000002 sec, idle 5 sec]
  1740:20131201:003135.628 End of vmware_service_get_event_session():FAIL
  1740:20131201:003135.628 End of vmware_service_get_event_data():FAIL
  1740:20131201:003135.631 End of vmware_service_update():FAIL
    Thanks

    Carlos
    Tags: None
    • a.shpak
      Junior Member
      • Feb 2013
      • 7
      #2
      I am using proxy to vmware monitoring.
      You need to update proxy to 2.2 and include new settings in zabbix_proxy.conf file.

      Here is ps aux in one of our proxies:

      Code:
      [root@m17zabbixproxy ~]# ps aux |grep zabbix
zabbix    1604  0.0  0.0  76492  1292 ?        S    Nov28   0:00 /usr/sbin/zabbix_agentd
zabbix    1613  0.0  0.0  76492  1332 ?        S    Nov28   0:36 /usr/sbin/zabbix_agentd: collector [idle 1 sec]
zabbix    1614  0.0  0.3  81120  6208 ?        S    Nov28   0:47 /usr/sbin/zabbix_agentd: active checks #1 [idle 1 sec]
zabbix    1858  0.0  0.1 149348  3668 ?        S    17:28   0:00 zabbix_proxy -c /etc/zabbix/zabbix_proxy.conf
zabbix    1862  0.0  0.2 150188  4388 ?        S    17:28   0:00 zabbix_proxy: configuration syncer [synced config 301810 bytes in 0.108011 sec, idle 180 sec]
zabbix    1863  0.0  0.1 149348  2408 ?        S    17:28   0:00 zabbix_proxy: heartbeat sender [sending heartbeat message success in 0.021404 sec, idle 60 sec]
zabbix    1865  0.0  0.1 149840  3664 ?        S    17:28   0:01 zabbix_proxy: data sender [sent 0 values in 0.001028 sec, idle 1 sec]
zabbix    1866  0.0  0.3 246908  7328 ?        S    17:28   0:00 zabbix_proxy: poller #1 [got 0 values in 0.000002 sec, idle 2 sec]
zabbix    1867  0.0  0.3 246564  6968 ?        S    17:28   0:00 zabbix_proxy: poller #2 [got 1 values in 0.003744 sec, idle 2 sec]
zabbix    1868  0.0  0.3 246616  6828 ?        S    17:28   0:00 zabbix_proxy: poller #3 [got 0 values in 0.000002 sec, idle 2 sec]
zabbix    1869  0.0  0.3 246860  7100 ?        S    17:28   0:00 zabbix_proxy: poller #4 [got 0 values in 0.000002 sec, idle 2 sec]
zabbix    1870  0.0  0.3 246540  6708 ?        S    17:28   0:00 zabbix_proxy: poller #5 [got 0 values in 0.000003 sec, idle 2 sec]
zabbix    1871  0.0  0.3 246908  7384 ?        S    17:28   0:01 zabbix_proxy: poller #6 [got 0 values in 0.000003 sec, idle 2 sec]
zabbix    1872  0.0  0.3 246664  7100 ?        S    17:28   0:00 zabbix_proxy: poller #7 [got 0 values in 0.000003 sec, idle 2 sec]
zabbix    1873  0.0  0.3 246540  6832 ?        S    17:28   0:00 zabbix_proxy: poller #8 [got 0 values in 0.000003 sec, idle 2 sec]
zabbix    1874  0.0  0.3 246560  6888 ?        S    17:28   0:00 zabbix_proxy: poller #9 [got 1 values in 0.002277 sec, idle 2 sec]
zabbix    1875  0.0  0.3 246880  7188 ?        S    17:28   0:00 zabbix_proxy: poller #10 [got 1 values in 0.005036 sec, idle 2 sec]
zabbix    1876  0.0  0.3 246860  7096 ?        S    17:28   0:00 zabbix_proxy: poller #11 [got 0 values in 0.000002 sec, idle 2 sec]
zabbix    1877  0.0  0.3 246540  7064 ?        S    17:28   0:00 zabbix_proxy: poller #12 [got 0 values in 0.000003 sec, idle 2 sec]
zabbix    1878  0.0  0.3 246540  6804 ?        S    17:28   0:00 zabbix_proxy: poller #13 [got 1 values in 0.005791 sec, idle 2 sec]
zabbix    1879  0.0  0.3 246860  7236 ?        S    17:28   0:00 zabbix_proxy: poller #14 [got 0 values in 0.000002 sec, idle 2 sec]
zabbix    1881  0.0  0.3 246540  6632 ?        S    17:28   0:00 zabbix_proxy: poller #15 [got 0 values in 0.000003 sec, idle 2 sec]
zabbix    1882  0.0  0.3 246536  6928 ?        S    17:28   0:00 zabbix_proxy: poller #16 [got 0 values in 0.000002 sec, idle 2 sec]
zabbix    1883  0.0  0.3 246552  6788 ?        S    17:28   0:00 zabbix_proxy: poller #17 [got 0 values in 0.000002 sec, idle 2 sec]
zabbix    1884  0.0  0.3 246536  6768 ?        S    17:28   0:00 zabbix_proxy: poller #18 [got 0 values in 0.000002 sec, idle 2 sec]
zabbix    1885  0.0  0.3 246588  6924 ?        S    17:28   0:00 zabbix_proxy: poller #19 [got 0 values in 0.000002 sec, idle 2 sec]
zabbix    1886  0.0  0.3 246564  6964 ?        S    17:28   0:00 zabbix_proxy: poller #20 [got 0 values in 0.000002 sec, idle 2 sec]
zabbix    1887  0.0  0.1 246484  3544 ?        S    17:28   0:00 zabbix_proxy: unreachable poller #1 [got 0 values in 0.000004 sec, idle 5 sec]
zabbix    1888  0.0  0.2 149712  4528 ?        S    17:28   0:00 zabbix_proxy: trapper #1 [processed data in 0.000284 sec, waiting for connection]
zabbix    1889  0.0  0.2 149712  4464 ?        S    17:28   0:00 zabbix_proxy: trapper #2 [processed data in 0.000344 sec, waiting for connection]
zabbix    1890  0.0  0.2 149672  4612 ?        S    17:28   0:00 zabbix_proxy: trapper #3 [processed data in 0.000646 sec, waiting for connection]
zabbix    1891  0.0  0.2 149712  4572 ?        S    17:28   0:00 zabbix_proxy: trapper #4 [processed data in 0.000895 sec, waiting for connection]
zabbix    1892  0.0  0.2 149700  4564 ?        S    17:28   0:00 zabbix_proxy: trapper #5 [processed data in 0.000330 sec, waiting for connection]
zabbix    1893  0.0  0.1 149704  3288 ?        S    17:28   0:00 zabbix_proxy: icmp pinger #1 [got 0 values in 0.000003 sec, idle 1 sec]
zabbix    1894  0.0  0.1 149704  3244 ?        S    17:28   0:00 zabbix_proxy: icmp pinger #2 [got 0 values in 0.000003 sec, idle 1 sec]
zabbix    1895  0.0  0.1 149704  3176 ?        S    17:28   0:00 zabbix_proxy: icmp pinger #3 [got 0 values in 0.000004 sec, idle 1 sec]
zabbix    1896  0.0  0.1 149704  3388 ?        S    17:28   0:00 zabbix_proxy: icmp pinger #4 [got 0 values in 0.000003 sec, idle 1 sec]
zabbix    1897  0.0  0.1 149708  3324 ?        S    17:28   0:00 zabbix_proxy: icmp pinger #5 [pinging hosts]
zabbix    1898  0.0  0.1 149704  3308 ?        S    17:28   0:00 zabbix_proxy: icmp pinger #6 [got 0 values in 0.000003 sec, idle 1 sec]
zabbix    1899  0.0  0.1 149704  3388 ?        S    17:28   0:00 zabbix_proxy: icmp pinger #7 [got 0 values in 0.000003 sec, idle 1 sec]
zabbix    1900  0.0  0.1 149704  3356 ?        S    17:28   0:00 zabbix_proxy: icmp pinger #8 [got 0 values in 0.000003 sec, idle 1 sec]
zabbix    1901  0.0  0.1 149704  3464 ?        S    17:28   0:00 zabbix_proxy: icmp pinger #9 [got 0 values in 0.000004 sec, idle 1 sec]
zabbix    1907  0.0  0.1 149708  3212 ?        S    17:28   0:00 zabbix_proxy: icmp pinger #10 [pinging hosts]
zabbix    1908  0.0  0.1 149704  3348 ?        S    17:28   0:00 zabbix_proxy: icmp pinger #11 [got 0 values in 0.000002 sec, idle 1 sec]
zabbix    1909  0.0  0.1 149704  3268 ?        S    17:28   0:00 zabbix_proxy: icmp pinger #12 [got 0 values in 0.000003 sec, idle 1 sec]
zabbix    1910  0.0  0.1 149704  3388 ?        S    17:28   0:00 zabbix_proxy: icmp pinger #13 [got 0 values in 0.000002 sec, idle 1 sec]
zabbix    1911  0.0  0.1 149708  3232 ?        S    17:28   0:00 zabbix_proxy: icmp pinger #14 [pinging hosts]
zabbix    1912  0.0  0.1 149708  3280 ?        S    17:28   0:00 zabbix_proxy: icmp pinger #15 [pinging hosts]
zabbix    1913  0.0  0.1 149704  3260 ?        S    17:28   0:00 zabbix_proxy: icmp pinger #16 [got 2 values in 6.055926 sec, idle 1 sec]
zabbix    1914  0.0  0.1 149708  3444 ?        S    17:28   0:00 zabbix_proxy: icmp pinger #17 [pinging hosts]
zabbix    1915  0.0  0.1 149708  3452 ?        S    17:28   0:00 zabbix_proxy: icmp pinger #18 [pinging hosts]
zabbix    1916  0.0  0.1 149704  3268 ?        S    17:28   0:00 zabbix_proxy: icmp pinger #19 [got 0 values in 0.000003 sec, idle 1 sec]
zabbix    1917  0.0  0.1 149704  3088 ?        S    17:28   0:00 zabbix_proxy: icmp pinger #20 [got 0 values in 0.000003 sec, idle 1 sec]
zabbix    1918  0.0  0.1 149348  2444 ?        S    17:28   0:00 zabbix_proxy: housekeeper [deleted 24354 records in 0.608383 sec, idle 3600 sec]
zabbix    1919  0.0  0.1 149348  2428 ?        S    17:28   0:00 zabbix_proxy: http poller #1 [got 0 values in 0.000380 sec, idle 5 sec]
zabbix    1920  0.0  0.1 246448  3544 ?        S    17:28   0:00 zabbix_proxy: discoverer #1 [processed 0 rules in 0.000742 sec, idle 60 sec]
zabbix    1921  0.0  0.1 246448  3544 ?        S    17:28   0:00 zabbix_proxy: discoverer #2 [processed 0 rules in 0.000196 sec, idle 60 sec]
zabbix    1922  0.0  0.2 248520  4172 ?        S    17:28   0:00 zabbix_proxy: discoverer #3 [processed 0 rules in 0.000376 sec, idle 60 sec]
zabbix    1923  0.0  0.1 246448  3544 ?        S    17:28   0:00 zabbix_proxy: discoverer #4 [processed 0 rules in 0.000386 sec, idle 60 sec]
zabbix    1924  0.0  0.1 246448  3544 ?        S    17:28   0:00 zabbix_proxy: discoverer #5 [processed 0 rules in 0.000209 sec, idle 60 sec]
zabbix    1925  0.0  0.1 246448  3544 ?        S    17:28   0:00 zabbix_proxy: discoverer #6 [processed 0 rules in 0.000335 sec, idle 60 sec]
zabbix    1926  0.0  0.1 149348  3724 ?        S    17:28   0:00 zabbix_proxy: history syncer #1 [synced 0 items in 0.000001 sec, idle 5 sec]
zabbix    1927  0.0  0.1 149348  3816 ?        S    17:28   0:00 zabbix_proxy: history syncer #2 [synced 0 items in 0.000001 sec, idle 5 sec]
zabbix    1928  0.0  0.1 149348  3828 ?        S    17:28   0:00 zabbix_proxy: history syncer #3 [synced 34 items in 0.034685 sec, idle 5 sec]
zabbix    1929  0.0  0.1 149348  3828 ?        S    17:28   0:00 zabbix_proxy: history syncer #4 [synced 0 items in 0.000001 sec, idle 5 sec]
zabbix    1930  0.0  0.1 149348  2452 ?        S    17:28   0:00 zabbix_proxy: snmp trapper [processed data in 0.000014 sec, idle 1 sec]
zabbix    1931  0.0  0.1 149348  2280 ?        S    17:28   0:00 zabbix_proxy: self-monitoring [processed data in 0.000004 sec, idle 1 sec]
zabbix    1939  0.1  0.4 160444  7732 ?        S    17:28   0:03 zabbix_proxy: vmware collector #1 [updated 0, removed 0 VMware services in 0.000002 sec, idle 5 sec]
zabbix    1940  0.0  0.3 159440  6820 ?        S    17:28   0:00 zabbix_proxy: vmware collector #2 [updated 0, removed 0 VMware services in 0.000002 sec, idle 5 sec]
zabbix    1941  0.0  0.3 159368  6748 ?        S    17:28   0:00 zabbix_proxy: vmware collector #3 [updated 0, removed 0 VMware services in 0.000002 sec, idle 5 sec]
zabbix    1942  0.0  0.3 159844  7312 ?        S    17:28   0:00 zabbix_proxy: vmware collector #4 [updated 0, removed 0 VMware services in 0.000002 sec, idle 5 sec]
zabbix    1943  0.0  0.3 159404  6784 ?        S    17:28   0:00 zabbix_proxy: vmware collector #5 [updated 0, removed 0 VMware services in 0.000001 sec, idle 5 sec]
zabbix   12082  0.0  0.0 108160  1396 ?        S    18:21   0:00 sh -c /usr/sbin/fping -q -C4 2>&1 </tmp/zabbix_proxy_1915.pinger;/usr/sbin/fping6 -q -C4 2>&1 </tmp/zabbix_proxy_1915.pinger;
zabbix   12084  0.0  0.0 108160  1396 ?        S    18:21   0:00 sh -c /usr/sbin/fping -q -C4 2>&1 </tmp/zabbix_proxy_1897.pinger;/usr/sbin/fping6 -q -C4 2>&1 </tmp/zabbix_proxy_1897.pinger;
zabbix   12088  0.0  0.0 108160  1388 ?        S    18:21   0:00 sh -c /usr/sbin/fping -q -C4 2>&1 </tmp/zabbix_proxy_1907.pinger;/usr/sbin/fping6 -q -C4 2>&1 </tmp/zabbix_proxy_1907.pinger;
zabbix   12090  0.0  0.0 108160  1396 ?        S    18:21   0:00 sh -c /usr/sbin/fping -q -C4 2>&1 </tmp/zabbix_proxy_1914.pinger;/usr/sbin/fping6 -q -C4 2>&1 </tmp/zabbix_proxy_1914.pinger;
zabbix   12092  0.0  0.0   7716   736 ?        S    18:21   0:00 /usr/sbin/fping6 -q -C4
zabbix   12093  0.0  0.0   7716   696 ?        S    18:21   0:00 /usr/sbin/fping6 -q -C4
zabbix   12094  0.0  0.0 108160  1392 ?        S    18:21   0:00 sh -c /usr/sbin/fping -q -C4 2>&1 </tmp/zabbix_proxy_1912.pinger;/usr/sbin/fping6 -q -C4 2>&1 </tmp/zabbix_proxy_1912.pinger;
zabbix   12095  0.0  0.0   7716   696 ?        S    18:21   0:00 /usr/sbin/fping -q -C4
zabbix   12096  0.0  0.0 108160  1388 ?        S    18:21   0:00 sh -c /usr/sbin/fping -q -C4 2>&1 </tmp/zabbix_proxy_1911.pinger;/usr/sbin/fping6 -q -C4 2>&1 </tmp/zabbix_proxy_1911.pinger;
zabbix   12097  0.0  0.0   7716   700 ?        S    18:21   0:00 /usr/sbin/fping -q -C4
zabbix   12098  0.0  0.0   7716   700 ?        S    18:21   0:00 /usr/sbin/fping6 -q -C4
zabbix   12099  0.0  0.0   7716   696 ?        S    18:21   0:00 /usr/sbin/fping6 -q -C4
root     12101  0.0  0.0 103240   868 pts/0    S+   18:21   0:00 grep zabbix
[root@m17zabbixproxy ~]#
      Here is conf file vmware part:
      Code:
      ### Option: StartVMwareCollectors
#       Number of pre-forked vmware collector instances.
#
# Mandatory: no
# Range: 0-250
# Default:
StartVMwareCollectors=1

### Option: VMwareFrequency
#       How often Zabbix will connect to VMware service to obtain a new data.
#
# Mandatory: no
# Range: 10-86400
# Default:
VMwareFrequency=30

### Option: VMwareCacheSize
#       Size of VMware cache, in bytes.
#       Shared memory size for storing VMware data.
#       Only used if VMware collectors are started.
#
# Mandatory: no
# Range: 256K-2G
# Default:
VMwareCacheSize=8M

        Comment

        • ccesario
          Junior Member
          • Dec 2013
          • 11
          #3
          Yes, I know.

          My proxy server has bee updated to 2.2 version, and configured to start vmware collector. See below.


          Version
          # zabbix_proxy -V
          Zabbix proxy v2.2.0 (revision 40163) (12 November 2013)
          Compilation time: Nov 12 2013 12:25:44

          proxy conf
          Code:
          ProxyMode=1
Server=zabbixserver.domain
Hostname=ZBProxy
LogFile=/var/log/zabbix/zabbix_proxy.log
LogFileSize=0
DebugLevel=4
PidFile=/var/run/zabbix/zabbix_proxy.pid
DBHost=localhost
DBName=/var/lib/zabbix/zabbix_proxy.db
DBUser=zabbix
StartVMwareCollectors=3
VMwareFrequency=60
VMwareCacheSize=16M
ExternalScripts=/usr/lib/zabbix/externalscripts
FpingLocation=/usr/bin/fping
Fping6Location=/usr/bin/fping6

          Zabbix Process

          Code:
          zabbix    2964  0.0  0.1 166176  2224 ?        S    11:17   0:01 /usr/sbin/zabbix_proxy: self-monitoring [processed data in 0.000089 sec, idle 1 sec]
zabbix    2965  0.1  0.5 170792 10444 ?        S    11:17   0:06 /usr/sbin/zabbix_proxy: vmware collector #1 [updated 0, removed 0 VMware services in 0.000002 sec, querying VMware services]
zabbix    2966  0.0  0.4 170548 10200 ?        S    11:17   0:02 /usr/sbin/zabbix_proxy: vmware collector #2 [updated 0, removed 0 VMware services in 0.000002 sec, idle 5 sec]
zabbix    2967  0.2  0.5 171240 10808 ?        S    11:17   0:12 /usr/sbin/zabbix_proxy: vmware collector #3 [updated 0, removed 0 VMware services in 0.000003 sec, idle 5 sec]


          Its attached a debug piece too


          Thanks

          Carlos
          Attached Files

            Comment

            • a.shpak
              Junior Member
              • Feb 2013
              • 7
              #4
              I think it can be some template problem. For example too frequently data gathering.
              I had big problems with default template and rewrite it. I will post detailed post about my template on first half of the week.

              I also checked my debug log on proxy. I am not programmer but i have the same string in my debug log like:
              Code:
              2853:20131201:111317.577 In zbx_vmware_get_service() xxxxusername@https://192.168.0.1/sdk
              But I am still get any information from VMHOST:

                Comment

                • ccesario
                  Junior Member
                  • Dec 2013
                  • 11
                  #5
                  Exploring the debug log, I saw that the collector get the data, but proxy mark as NOT SUPPORTED.

                  See attached
                  Attached Files

                    Comment

                    • ccesario
                      Junior Member
                      • Dec 2013
                      • 11
                      #6
                      More debug data. (attached)

                      error: Timeout was reached


                      5253:20131201:213224.354 Item [192.168.0.1:vmware.version[{$URL}]] error: Timeout was reached


                      5251:20131201:211219.594 Item [192.168.0.1:vmware.hv.discovery[{$URL}]] error: Cannot set cURL option [10015]: Timeout was reached
                      Attached Files

                        Comment

                        • mikkelrobin
                          Junior Member
                          • Aug 2013
                          • 12
                          #7
                          Zabbix 2.2.1

                          Im getting this error on my zabbix server too.

                          My installation is an upgrade from 2.1, so i have exported the templates and created the value mappings from an other new 2.2.1 installation.

                            Comment

                            • Vengant
                              Junior Member
                              • Dec 2013
                              • 22
                              #8
                              Hi all, I have the same error on Zabbix 2.2.1.

                              I monitor 1 vSphere 5.1 site directly from server, and 2 vSphere 5.1 sites via proxies. There are over 200 VMs and over 10 hosts.

                              In period with ~1 hours i see that count of unsupported items for vmware hosts increasing very much. This looks in 5-10 minutes and then decrease back. When it increasing, CURL error shown in sever log like that: "Cannot set cURL option [10015]: Timeout was reached".

                              My server works on CentOS installed in VMWare VM that running on BL460c G8 server. VM have 8GB of RAM, 2 vCPU and storage on SAN SAS10K disks. DB is MySQL, running on the same server. I has been done DB optimization as shown in this article.

                              Proxies runs on the same hardware configuration, but have 2GB of RAM.

                              I don't see that CPU, memory or disk I/O overloaded on server or proxies when error appears.

                              I confused that error shown in Zabbix Server log, not in Proxy log.

                              Maybe it can be related to housekeeper processes?

                              Any ideas?
                              Last edited by Vengant; 29-01-2014, 12:36.

                                Comment

                                • gavind
                                  Member
                                  • Mar 2013
                                  • 59
                                  #9
                                  Hi Vengant, looks like you're on a dead end here. But any updates on this so far for you?

                                    Comment

                                    • Chalmo
                                      Junior Member
                                      • Jan 2014
                                      • 8
                                      #10
                                      I've had this same issue, resolved by setting the following configuration in /etc/zabbix/zabbix_proxy.conf -

                                      ### Option: StartVMwareCollectors
                                      # Number of pre-forked vmware collector instances.
                                      #
                                      # Mandatory: no
                                      # Range: 0-250
                                      # Default:
                                      StartVMwareCollectors=6

                                      ### Option: VMwareFrequency
                                      # How often Zabbix will connect to VMware service to obtain a new data.
                                      #
                                      # Mandatory: no
                                      # Range: 10-86400
                                      # Default:
                                      VMwareFrequency=15

                                      ### Option: VMwareCacheSize
                                      # Size of VMware cache, in bytes.
                                      # Shared memory size for storing VMware data.
                                      # Only used if VMware collectors are started.
                                      #
                                      # Mandatory: no
                                      # Range: 256K-2G
                                      # Default:
                                      VMwareCacheSize=256M

                                      We are running Zabbix 2.2.0.

                                      The change took affect immediately.

                                      I think we were seeing the issue because on certain VMware items I had it set to check every 15 secs but VMwareFrequency= was previously 60.
                                      Last edited by Chalmo; 26-03-2014, 17:23.

                                        Comment

                                        • leferocha
                                          Junior Member
                                          • Mar 2012
                                          • 3
                                          #11
                                          Hi there!

                                          To enable monitoring of VMware environments from Zabbix Proxies, you must also compile the Zabbix Proxy with --with-libxml2 and --with-libcurl and set the StartVMwareCollectors option in Zabbix Proxy configuration file to 1 or more.

                                          I was facing similar problem and that's what solved in my case.

                                          Hope this helps!

                                            Comment

                                            Previous template Next
                                            Working...