We like to monitor if the performance counter is working or not.
Few weeks ago we mentioned some problems with the BE Engine perf counter. The counter was running but don't capturing data.
Part of the counter .xml logfile (dont look at the date :) just an example what happend):
"(PDH-CSV 4.0) (W. Europe Daylight Time)(-120)","\\SBS2011\BE Engine\Failed Jobs"
"04/11/2012 12:36:16.066","0""04/11/2012 13:36:16.536","0""04/11/2012 14:36:17.071"," ""04/11/2012 15:36:17.552"," ""04/11/2012 16:36:17.932"," "
You see the BE Engine dont put any data in the file anymore. And thats what we want to know when that happend.
Is there a way to monitor when a perf counter entered that state?
You're not alone with monitoring problems! I've had some proper fun and games with them.
This problem sounds like one i had a year or two ago and the solution was to have a .BAT file which had a series of STOP START commands to restart each counter once a week, typically on a Sunday.
The .BAT file is simply like the example below:
NET STOP SYSMONLOG
NET STOP PLA
NET START SYSMONLOG
NET START PLA
logman KCTR$1000 start
logman KCTR$1001 start
logman KCTR$1002 start
logman KCTR$1016 start
Hope this helps you get your counters going again!