NCPA windowcounters unable to pull Skype SIP counters.

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Locked
wafox
Posts: 5
Joined: Fri Feb 08, 2019 1:52 pm

NCPA windowcounters unable to pull Skype SIP counters.

Post by wafox »

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!
User avatar
Box293
Too Basu
Posts: 5126
Joined: Sun Feb 07, 2010 10:55 pm
Location: Deniliquin, Australia
Contact:

Re: NCPA windowcounters unable to pull Skype SIP counters.

Post by Box293 »

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'
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
wafox
Posts: 5
Joined: Fri Feb 08, 2019 1:52 pm

Re: NCPA windowcounters unable to pull Skype SIP counters.

Post by wafox »

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.
User avatar
Box293
Too Basu
Posts: 5126
Joined: Sun Feb 07, 2010 10:55 pm
Location: Deniliquin, Australia
Contact:

Re: NCPA windowcounters unable to pull Skype SIP counters.

Post by Box293 »

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.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
User avatar
Box293
Too Basu
Posts: 5126
Joined: Sun Feb 07, 2010 10:55 pm
Location: Deniliquin, Australia
Contact:

Re: NCPA windowcounters unable to pull Skype SIP counters.

Post by Box293 »

Could you please run this in the CMD prompt:

Code: Select all

TypePerf.exe -q | findstr "SIP"
This way we can see the exact name of the counter.

That is of course if you want to keep troubleshooting this.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
benjaminsmith
Posts: 5324
Joined: Wed Aug 22, 2018 4:39 pm
Location: saint paul

Re: NCPA windowcounters unable to pull Skype SIP counters.

Post by benjaminsmith »

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.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.

Be sure to check out our Knowledgebase for helpful articles and solutions!
Locked