vm.memory.size and system.cpu.load unsupported after migration to Zabbix Agent2

[zaicnupagadi]

Hey all,

Just recently I've migrated all of our zabbix agents to version 2, unfortunately noticed as well that these two

vm.vmemory.size
system.cpu.load



became unsupported on all of the endpoints

Is somoene familiar with such behaviour?

J

[zaicnupagadi]

What's displayed if hover over that red i...?

Hi cyber, do not know why I didn't think to put that here, sorry. Well after an upgrade, for:

"vm.vmemory.size[pavailable]" it returns me:

"Unknown metric vm.vmemory.size"

and for:

"system.cpu.load[percpu,avg1]"
"system.cpu.load[percpu,avg5]"
"system.cpu.load[percpu,avg15" it returns me:

"Invalid first parameter."

Surprisingly it works with the default parameter - all:

xxx@yyyxxx0:~$ zabbix_get -s xxxxhv6 -k system.cpu.load[all,avg5]
0.000000
xxx@yyyxxx0:~$ zabbix_get -s xxxxhv6 -k system.cpu.load[percpu,avg5]
ZBX_NOTSUPPORTED: Invalid first parameter.

Hmm... maybe this is something known with zabbix agent 2?

[cyber]

What's displayed if hover over that red i...?...