0

We use Proxmox VE as our virtualization environment, and recently upgraded from 2.X -> 3.X. We also made the change from a single host to a dual host cluster. And, last but not least, we moved our VMs from a LVM backend to a GlusterFS one.

Here is a graph from just before the migration. Notice the clean, clear lines:

Before

Now, here is the same graph from right now:

After

My first thought was that virt1 wasn't responding quickly, so I used zabbix_get to test that theory, and here's the result:

[root@monit ~]# for i in {1..10}; do (time zabbix_get -s virt1 -k system.cpu.load[,avg1]) 2>&1 | grep -i real | awk '{print $2}'; sleep 1; done
0m0.011s
0m0.015s
0m0.010s
0m0.010s
0m0.010s
0m0.010s
0m0.010s
0m0.011s
0m0.011s
0m0.011s

The result is very quick, and certainly no where near the limit of three whole seconds.

Also, this doesn't happen on all hosts, for example, it happens on virt1, virt2, and a VM called nas, but not on any of the other VMs.

Hopefully, there's a Zabbix guru here who can help.

Thanks!

ETA:

Here are the stats that asaveljevs was talking about:

Timestamp               Value
2014.Aug.14 09:13:56    17
2014.Aug.14 09:13:27    18
2014.Aug.14 09:12:56    17
14
  • Are there any network errors regarding these hosts in the server log? Also, how busy your pollers are? Zabbix internal process load can be monitored using zabbix[process,poller,avg,busy] and other similar items.
    – asaveljevs
    Aug 12, 2014 at 6:41
  • @asaveljevs I'm running Zabbix 1.8.20, and I don't think those keys exist: [root@monit ~]# zabbix_get -s localhost -k zabbix[process,poller,avg,busy] | wc -l: 0
    – Soviero
    Aug 12, 2014 at 14:26
  • These keys do exist since Zabbix 1.8.5 (see zabbix.com/documentation/1.8/manual/config/…), but they are not agent checks. Rather, they are of type "Simple check" and are processed by the server itself.
    – asaveljevs
    Aug 13, 2014 at 6:15
  • @asaveljevs How do you run the checks manually then?
    – Soviero
    Aug 13, 2014 at 13:21
  • Items of type "Zabbix internal" (the reference to "Simple check" above is a typo) are processed by the server itself and they cannot be run manually, i.e. they cannot be queried using zabbix_get. Instead, in Zabbix frontend they should be created on a host monitored by Zabbix server: create an item like you usually do, but select "Type" to be "Zabbix internal" and use "zabbix[process,poller,avg,busy]" as the "Key".
    – asaveljevs
    Aug 14, 2014 at 10:54

0

You must log in to answer this question.

Browse other questions tagged .