I have two 160-core windows server and I have to monitor it!
CPU utilization discovery would be very useful.

@Pavel:
I built my own discovery script, just put it somewhere in ZABBIX_HOME/etc/zabbix_agentd.conf/cpu.conf or so:

UserParameter=system.cpu.discovery,for cpu in $(grep processor /proc/cpuinfo  | awk '{print $3}'); do cpulist="$cpulist,"'{"{#CPU}":"'$cpu'"}'; done; echo '{"data":['${cpulist#,}']}'

This should work on any Linux-like operating system.
Note: This list only returns the single cores on a box, use the pre-existing CPU items to monitor the average CPU usage of the system.

@Simon
I don't know VBS, but google helped me and I made this script:

Set oShell = WScript.CreateObject("WScript.Shell")
Set oEnv = oShell.Environment("SYSTEM")
num = oEnv("NUMBER_OF_PROCESSORS")-1

Dim arrCpu()
ReDim arrCpu(num)
Dim i

For i=0 to num
	arrCpu\(i) = "{""{#CPU}"":""" & i & """}"
Next

WScript.Echo "{""data"":["
WScript.Echo (Join(arrCpu,","))
WScript.Echo "]}"

zabbix_agentd.conf:

UserParameter=system.cpu.discovery, cscript //NoLogo C:\zabbix\bin\cpulist.vbs

@Pavel
Thanks! That worked great!

FreeBSD variant:

#!/bin/sh

total=`sysctl -n hw.ncpu`
cpu=0

while [ $cpu -lt $total ]; do
        cpulist="$cpulist,"'{"{#CPU}":"'$cpu'"}'
        cpu=$(($cpu+1))
done

echo '{"data":['${cpulist#,}']}'

Available in the development branch svn://svn.zabbix.com/branches/dev/ZBXNEXT-1300

Aleksej, for which operating systems was this implemented ?

Full support on Linux and FreeBSD, support for online processors only on OpenBSD, NetBSD and Windows. OSx support will be added later.

(1) about freebsd CPU discovery. We should not rely on external utilities (grep) to parse file. I think it should be done manually.

wiper CLOSED as not relevant anymore

Please review my changes in r35134.(which was successfully tested).

Did this improvement make it into 2.2?
I don't see it documented anywhere, nor is it included in the default Linux template.

was not finished/merged; no specific plans as far as i know

Uhm, shouldn't this be re-opened then?

If this isn't merged, it's not resolved. We're trying to stop using SNMP, but with the agent missing functionality like this, it's taking longer than it should.

Please reopen!

Feature implemented at svn://svn.zabbix.com/branches/dev/ZBXNEXT-1300_2

Suggested changes implemented in development branch. Please review r47305.

Successfully tested, please review changes in r47308

jurism Changes reviewed. Looks good. RESOLVED.

Feature implemented in 2.3.3 (trunk) r47314.

(2) The new feature has been documented in What's New for 2.4 at https://www.zabbix.com/documentation/2.4/manual/introduction/whatsnew240#daemon_improvements
Reference regarding platform support for the item can be found at https://www.zabbix.com/documentation/2.4/manual/appendix/items/supported_by_platform
Item description is located at https://www.zabbix.com/documentation/2.4/manual/config/items/itemtypes/zabbix_agent
Notes regarding low-level discovery use can be found here: https://www.zabbix.com/documentation/2.4/manual/discovery/low_level_discovery

<richlv>

• seems to be missing in the overview at https://www.zabbix.com/documentation/2.4/manual/discovery/low_level_discovery
  • was added, but now it says "In Zabbix, three types of item discovery are supported" and lists 4 things
• in https://www.zabbix.com/documentation/2.4/manual/appendix/items/supported_by_platform it's not listed in alphabetic order, should be the first "system.cpu.*" entry

jurism RESOLVED.

wiper CLOSED