1.3.6 Windows agents issues

[JonB]

I am trying to monitor my Network Interfaces. I first tried setting a perf_counter parameter

perf_counter[\Network Interface(VIA Compatable Fast Ethernet Adapter - Packet Scheduler Miniport)\Bytes Received/sec]

The following error message was recived in the server logs

Parameter [perf_counter[\Network Interface(VIA Compatable Fast Ethernet Ada] is not supported by agent on host [ctshowick1] Old status [0]

It appears the the Parameter is truncated to 64 characters.

I then tried to set up an Alias

Alias=NetIn,perf_counter[\Network Interface(VIA Compatable Fast Ethernet Adapter - Packet Scheduler Miniport)\Bytes Received/sec]

but the windows agent refused to restart until I removed the Alias parameter so it appears the Windows agent does not support the parameter Alias.

The last try was to set up an active parameter

PerfCounter=netin,"\Network Interface(VIA Compatable Fast Ethernet Adapter - Packet Scheduler Miniport)\Bytes Received/sec",30

Item was setup as

agent(active)
netin
Numeric(float)
Bps
Delta(speed per second)

This errors with the following errors on the server

24385:20070507:150941 Active parameter [netin] is not supported by agent on host [hostname]
24385:20070507:150941 Type of received value [ZBX_NOTSUPPORTED] is not suitable for [netin@hostname]

Jon

[JonB]

Further to this I tried another test.

I set a perf_counter item less than 64 characters

perf_counter[\TCP\Segments/sec]

This works as expected and returns results.

I then removed it and set up an active agent item tcp.segments

PerfCounter=tcp.segments, "\TCP\Segments/sec",5

This does not work and returns ZBX_UNSUPPORTED so it also appears that the Windows agent does not support the parameter PerfCounter correctly.

UserParameter works as expected.

I thinks it has already been reported but the latest Windows Agent reports as version 1.3.5.

Jon

[NOB]

Hi,

there is a problem (already fixed, but not included in 1.3.6) with changing
items to active.
The agent will not get the new items until you restart it.

Did you restart the agent ?

I think so, otherwise the agentd.conf will not be read, anyway,
and changes will not take effect, AFAIK.

Regards,

Norbert.

[JonB]

Nob,

I am aware of the issue of having to restart the agent. I restarted the agent every time I made a change.

Jon