perf_counter not supported

[norms]

I have searched all the forums and have found no solution to this. I have windows counters which are visible on the server but zabbix reports them as not supported. Is there any issue with characters (-) or is it that zabbix can not monitor all counters. See example below.

C:\zabbix>zabbix_agentd.exe -t perf_counter["\HP EVA Storage Array(5000-1FE1-5011-51D0)\Total host KB/s"]
perf_counter[\HP EVA Storage Array(5000-1FE1-5011-51D0)\Total host KB/s] [m|ZBX_NOTSUPPORTED]



However Windows reports values for the same counters.

C:\zabbix>typeperf "\HP EVA Storage Array(5000-1FE1-5011-51D0)\Total host KB/s"

"(PDH-CSV 4.0)","\\2UX82401EF-\HP EVA Storage Array(5000-1FE1-5011-51D0)\Total host KB/s"
"08/30/2011 12:12:06.687","0.000000"
"08/30/2011 12:12:07.687","0.000000"
"08/30/2011 12:12:08.687","0.000000"
"08/30/2011 12:12:09.687","0.000000"
"08/30/2011 12:12:10.687","0.000000"
"08/30/2011 12:12:11.687","0.000000"
"08/30/2011 12:12:12.687","0.000000"
"08/30/2011 12:12:13.687","0.000000"
"08/30/2011 12:12:14.687","0.000000"

[ghoz]

set your Debuglevel to 4 on the agent side, and check the logs... for errors or translation problems...

however, it may not be enough, I've had a situation on a localized windows 2008, when a perfcounter would'nt be recognized by the agent. I resorted to translating the perfcounter to it's ID (using the registry 'Perflib' trick).

unfortunately, for non core perfcounters, the IDs are guaranteed unique... by machine only : depending on the order on which the perf counters are registered , you have different IDs on different servers...
in order to use the templating system, you have to put an alias at the agent level for each and every server :-/

[naveen28187]

shakti

Yes,this is quite possible

[norms]

perf_counter

The logs says it can't find object on system, if the values can be obtained from the prompt why would zabbix have an issue, should it not just pass the exact counter given to it.



10764:20110831:083836.062 Processing request.
10764:20110831:083836.234 Requested [perf_counter[\HP EVA Storage Array(5000-1FE1-5011-51D0)\Total host KB/s]]
10764:20110831:083836.234 In PERF_COUNTER()
10764:20110831:083836.234 PERF_COUNTER(): unable to add PerfCounter '\HP EVA Storage Array(5000-1FE1-5011-51D0)\Total host KB/s': [0xC0000BB8] The specified object is not found on the system.
10764:20110831:083836.234 End of PERF_COUNTER()
10764:20110831:083836.234 Sending back [ZBX_NOTSUPPORTED]

[norms]

solved

Ok. I found the issue, system was a 64bit machine. Apparently some counters do not work for zabbix when you install a 32bit version unto a 64bit machine.

Thanks for all the help.

[frater]

unfortunately, for non core perfcounters, the IDs are guaranteed unique... by machine only : depending on the order on which the perf counters are registered , you have different IDs on different servers...
in order to use the templating system, you have to put an alias at the agent level for each and every server :-/

What a bunch of losers at Microsoft...
What were they thinking?

I now moved the perf_counter items out of "Template Windows" and moved them to "Template Windows English". I cloned this template to "Template Windows Dutch" and replaced all the English keys with their Dutch counterparts.

Depending on the Language I need to add the appropriate Template....

[ghoz]

I now moved the perf_counter items out of "Template Windows" and moved them to "Template Windows English". I cloned this template to "Template Windows Dutch" and replaced all the English keys with their Dutch counterparts.

Be careful with that, I had problems with translation changing from one version to another, some counters in english in one version , translated in the next ...

If you have multiple OS version, you may need a 'template_Windows_2003_SP4_dutch_god_i_hate_ms" :-)

in order to avoid that, I deploy a .conf with the agent that depends on OS version with aliases... that way I have one template, one set of graphs and triggers...

on the other had I have to maintain configuration on the agent... oh well..

[frater]

I can advice everyone using Zabbix to create the item:

zabbix[items_unsupported]
zabbix internal
Decimal (unsigned)
interval: 300 seconds

and these triggers:

Unsupported items increased
{Zabbix server:zabbix[items_unsupported].last(0)}>{Zabbix server:zabbix[items_unsupported].last(#2)}>0
High

Unsupported items decreased ({ITEM.LASTVALUE1} items)
{Zabbix server:zabbix[items_unsupported].last(0)}<{Zabbix server:zabbix[items_unsupported].last(#2)}>0
Informational

Unsupported items exist ({ITEM.LASTVALUE1} items)
{Zabbix server:zabbix[items_unsupported].last(0)}>0
Average
dependency: Unsupported items increased
dependency: Unsupported items decreased

If the situation you describe occurs, you can take appropriate action.....