Performance counters don't work in Zabbix

[Gijs007]

I'm using the Processor Counter Monitor to add extra performance counters in Windows, which are specific for CPU's.

These performance counters show up in perfmon.
However every time I add them I get the following error:

Invalid performance counter format

After some time this error changes to:

Cannot obtain performance information from collector

According to TypePerf the name of the performance counter I want to use is:

\PCM Core Counters(total_)\Clockticks

I've tried the following performance counters in Zabbix, but I keep getting the errors explained above:

perf_counter["\PCM Core Counters(total_)\Clockticks"]
perf_counter["\PCM Core Counters(total_)\Clockticks/sec"]
perf_counter["\PCM Core Counters(total_)\Clockticks/sec", 60]

Can anyone tell me what I'm doing wrong? I have the same problem with a couple of other performance counters, but some work fine..

[LenR]

I don't know windows well enough to explain it, but it's like services add to the perf counter schema after boot. Those added after the zabbix agent stats aren't viable to thee zabbix agent until it restarts.

[kloczek]

If you are looking for examples of how to use perf counters you can peak on

https://github.com/kloczek/zabbix-templates/tree/master/OS%20Windows

PS. If you want more details about this template you need to contact my friend Scott Simoons as he spend recently most of the time polishing this template

[Gijs007]

The problem was resolved by simply restarting the Zabbig Agent. Very confusing

[LenR]

I don't know windows well enough to explain it, but it's like services add to the perf counter schema after boot. Those added after the zabbix agent stats aren't viable to thee zabbix agent until it restarts.

[Gijs007]

I don't know windows well enough to explain it, but it's like services add to the perf counter schema after boot. Those added after the zabbix agent stats aren't viable to thee zabbix agent until it restarts.

That would be a logical and plausible explanation for the problem.

[LenR]

We encountered this on either AD or Exchange, we picked one item that would fail after reboot and created a "nodata" trigger that restarts the zabbix agent on the host. The action has to call a script, the windows guys worked for some time to get it working, I think it has to "start" another process outside the agent to restart the agent. I think powershell was involved, which I avoid as much as I can...

[Chewbakka-Wakka]

What are those perf counters used for? Do you have any links to documents for them?