Nagios Support Forum

I'm trying to pull windows counters from our skype frontend servers from several paths (as seen below):

PS C:\Windows\system32> Get-Counter -ListSet "LS:SIP - Load*"


CounterSetName : LS:SIP - Load Management
MachineName : .
CounterSetType : SingleInstance
Description : This object includes global counters that apply to the load management component of Skype for
Business Server.
Paths : {\LS:SIP - Load Management\SIP - Average Holding Time For Incoming Messages, \LS:SIP - Load
Management\SIP - Incoming Messages Held, \LS:SIP - Load Management\SIP - Incoming Messages Held
Above Low Watermark, \LS:SIP - Load Management\SIP - Incoming Messages Held Above High
Watermark...}
PathsWithInstances : {}
Counter : {\LS:SIP - Load Management\SIP - Average Holding Time For Incoming Messages, \LS:SIP - Load
Management\SIP - Incoming Messages Held, \LS:SIP - Load Management\SIP - Incoming Messages Held
Above Low Watermark, \LS:SIP - Load Management\SIP - Incoming Messages Held Above High
Watermark...}

When trying to access these via NCPA we get the following error (hostname and token have been replaced):

check_ncpa.py -H 'HOSTNAME' -t 'TOKEN' -P 5693 -M 'windowscounters/LS:SIP - Load Management/SIP - Average Holding Time For Incoming Messages'

The specified object was not found on the computer.

On the windows machine, we can pull these counters up in Perf Mon just fine. I've pulled counters before for other monitor tasks with NCPA and it works fine. Am I missing something here? Thanks!

I think this KB article has the answer:
https://support.nagios.com/kb/article.php?id=126

There is a space between Available and MBytes, you will need to use %20 to emulate the space
'windowscounters/Memory/Available%20MBytes'

Thanks for the suggestion - I was not able to get this to work. I moved on to working with the NCPA plugin on the host directly and I can't get a consistent read from the api endpoint for any of these paths.

Do you have any command line examples of what you were typing and what the output was? Would be good to see if we can find a native solution.

Could you please run this in the CMD prompt: This way we can see the exact name of the counter.

That is of course if you want to keep troubleshooting this.

Hello @wafox,

As Troy (box293) mentioned, getting the exact name of the counter would help us further troubleshoot this issue.

Let us know if you need any additional instructions.