Windows agent : Items not supported

[Seb]

Hi,

I installed Windows agents on a XP, a 2000 Server and a 2003 Server computers (agent version : 1.1 beta 7).
In the Host menu, the computers are monitored and available. However, if I check their items, there are only 3 items which are supported (Host status, number of running processes apache and size of $1), the others are not supported.

I have also a Linux agent (Ubuntu) and it works perfectly.

How to explain this situation ?

Thanks

[Valerie]

Hi Seb,

Keys for Linux and Windows parameters are not the same.
See : http://www.zabbix.com/doku/doku.php?...types_of_items

[RussB]

I have the same issue. I had no problems monitoring Windows servers under beta 6. The 'Not supported' problems have arisen since installing beta 7.

[eric.butler]

Same problem here

I am also seeing the same behavior in 1.1b8 when I do the following
-Do a clean installation (on SUSE 10)
-Install 1.1b8 win32agent on a winxp machine
-Add the winxp machine to the host list in zabbix
-Link the host to the win32 template and activate all the items
-After the first polling cycle, they all state "not supported" except for the 3 mentioned in the beginning of the thread.

I tried version 1.0 of the win32agent and the status of the items never changed from Active to Not Supported but no data was ever retreived successfully from the agent. I also tried 1.1b3 of the agent and the results were the same as for 1.1b7.

The wiki document that describes the items has a section called ZABBIX AGENT. I have tested a few of these and they turn to not supported after a polling cycle. I am new to zabbix, so this may be the intended behavior. However the items under the heading WIN32-SPECIFIC PARAMETERS do seem to work fine on 1.1b8.

Are the ZABBIX AGENT keys supposed to be supported on the win32 agent platform or is it only the WIN32-SPECIFIC PARAMETERS that should work?

[pasci]

I've the same problem - I'm using the last version shipped with the beta9 release of w32 agent

per example:
the parameter to get cpu usage is cpu_util. But the item is everytime switching to "not supported". I've tried also the "linux" format (only to find an "answer") and report also "not supported" (of course).

I'm monitoring also a linux system (zabbix is running on it). There everything I want works fine (cpu, disk, ethernet and so on). Is there a bug within the windows agent? the logs doesn't show any error. but I try now the "debug" log level.

[erisan500]

These are comming from the "included" readme file and ARE working.

Parameters supported by Zabbix Win32 Agent
------------------------------------------

I. Zabbix standard parameters

check_port[<port>]
check_port[<host>,<port>]
cksum[<path>] <path> can be normal Windows path, like C:\, or UNC.
Agent will return UNSUPPORTED if file is larger than
64MB.
diskfree[<path>] <path> can be normal Windows path, like C:\, or UNC
disktotal[<path>] <path> can be normal Windows path, like C:\, or UNC
filesize[<path>] <path> can be normal Windows path, like C:\, or UNC
memory[free]
memory[total]
memory[cached] Only on Windows XP and Windows Server 2003
ping
proc_cnt[<process_name>]
swap[free]
swap[total]
system[hostname]
system[proccount]
system[procload]
system[procload5]
system[procload15]
system[uname]
system[uptime]
version[zabbix_agent]


II. Win32-specific parameters

agent[avg_collector_time]
Average time spent by collector thread on each sample processing for
last minute (in milliseconds)

agent[max_collector_time]
Maximum time spent by collector thread on sample processing (in milliseconds)

agent[accepted_requests]
Total number of requests accepted by agent for processing.

agent[rejected_requests]
Total number of requests rejected by agent because they was coming from
unallowed source.

agent[timed_out_requests]
Total number of requests timed out in processing.

agent[accept_errors]
Total number of accept() syscall errors.

agent[processed_requests]
Total number of requests successfully processed by agent.

agent[failed_requests]
Total number of requests with errors in processing (requests generated
ZBX_ERROR return code).

agent[unsupported_requests]
Total number of requests for unsupported parameters (requests generated
ZBX_UNSUPPORTED return code).

cpu_util
Average CPU(s) utilization (in percents) for last minute

cpu_util5
Average CPU(s) utilization (in percents) for last 5 minutes

cpu_util15
Average CPU(s) utilization (in percents) for last 15 minutes

cpu_util[<instance>]
Average specific CPU utilization (in percents) for last minute, where
<instance> is zero-based CPU number

cpu_util5[<instance>]
Average specific CPU utilization (in percents) for last 5 minutes, where
<instance> is zero-based CPU number

cpu_util15[<instance>]
Average specific CPU utilization (in percents) for last 15 minutes, where
<instance> is zero-based CPU number

diskused[<instance>]
Number of used bytes on specific drive.

md5_hash[<file name>]
MD5 hash of specified file (returned as string). Agent will return UNSUPPORTED
if file is larger than 64MB.

perf_counter[<path>]
Value of any performance counter, where <path> is the counter path (you can use
Performance Monitor to obtain list of available counters). Please note that
this parameter will return correct value only for counters which requires just
one sample (like "\System\Threads"). It will not work as expected for counters
that requires more than one sample - like CPU utilization.

proc_info[<process>:<attribute>:<type>]
Different information about specific process(es).
<process> - process name (same as in proc_cnt[] parameter)
<attribute> - requested process attribute. The following attributes are
currenty supported:
vmsize - Size of process virtual memory in Kbytes
wkset - Size of process working set (amount of physical memory
used by process) in Kbytes
pf - Number of page faults
ktime - Process kernel time in milliseconds
utime - Process user time in milliseconds
io_read_b - Number of bytes read by process during I/O operations
io_read_op - Number of read operation performed by process
io_write_b - Number of bytes written by process during I/O operations
io_write_op - Number of write operation performed by process
io_other_b - Number of bytes transferred by process during operations
other than read and write operations
io_other_op - Number of I/O operations performed by process, other
than read and write operations
gdiobj - Number of GDI objects used by process
userobj - Number of USER objects used by process
<type> - representation type (meaningful when more than one process
with the same name exists). Valid values are:
min - minimal value among all processes named <process>
max - maximal value among all processes named <process>
avg - average value for all processes named <process>
sum - sum of values for all processes named <process>
Examples:
1. To get amount of physical memory taken by all Internet Explorer processes,
use the following parameter:
proc_info[iexplore.exe:wkset:sum]
2. To get average number of page faults for Internet Explorer processes,
use the following parameter:
proc_info[iexplore.exef:avg]
Notes:
1. All io_xxx,gdiobj and userobj attributes available only on Windows 2000
and later versions of Windows, not on Windows NT 4.0.

[pasci]

These are comming from the "included" readme file and ARE working.

Parameters supported by Zabbix Win32 Agent
------------------------------------------
...

Thanks for your feedback, but... I doesn't work. I have tried with

- WinXP Pro SP2: cpu_util -> not supported
but: I get per example used Bytes of Drive C: (so, agent run)
- Windows Server 2003 Std: cpu_util -> not supported
but: I get also per example used Byte of Drive C: (so, agent run)
and: system[proccount] returns also valid values

Any ideas? I want primary monitor w2k3 servers (winxp is only for testing).

[gedp]

I'm just looking for the first time at zabbix and wanted to test the agent on a windows platform. Seems the only items working are diskfree and memory.
Is there an exhaustive list of the items that can be used on windows and that should be working with the 1.9 beta?

[pasci]

Thanks for your feedback, but... I doesn't work. I have tried with

- WinXP Pro SP2: cpu_util -> not supported
but: I get per example used Bytes of Drive C: (so, agent run)
- Windows Server 2003 Std: cpu_util -> not supported
but: I get also per example used Byte of Drive C: (so, agent run)
and: system[proccount] returns also valid values

Any ideas? I want primary monitor w2k3 servers (winxp is only for testing).

I don't know why, but if I use value type "numeric (float)" instead "numeric integer", cpu_util works now fine?! On the WinXP and also on the w2k3 machine.

[mary nancy]

Hi all,

I have used both:
system.cpu.util[all,user,avg5]
system.cpu.load[,avg1]

and also tested by changing the type of infomation to numeric(Float), but it still shows as not supported.

Can somebody help me in identifying which could be the right parameter to monitor CPU utilization on Windows 200, windows 2003, windows NT servers.

Thanks and regards
Nancy

[qix]

I use the following:

Key: system.cpu.util[]
Type of Info : Numeric (float)
Units: %
update: 300
history: 90

Key: system.cpu.load[]
Type of Info : Numeric (float)
Units: %
update: 300
history: 90

Good luck!