Page 3 of 3
Re: Distributed Monitoring with Windows Environments
Posted: Tue Mar 06, 2018 4:42 am
by domsch1988
kyang wrote:Interesting, I'll have to try and reproduce it that way our NCPA developer can fix it if possible.
I would like to mention there is a new NCPA release 2.1.3.
Were there any more questions on this or are we all set?
No questions anymore. I know how it should work but it doesn't for me. I appreciate you taking the time to help me with this.
I'll make sure to test 2.1.3 later today and will report back. Getting Windows Counters to work would help me massively achieve certain tasks (Exchange and Backup Monitoring for example).
Re: Distributed Monitoring with Windows Environments
Posted: Wed Mar 07, 2018 5:42 pm
by scottwilkerson
Let us know how 2.1.3 goes.
I can also mention that there is also counter support in NSClient++ agent using the Windows Server Wizard as well.
Re: Distributed Monitoring with Windows Environments
Posted: Mon Mar 12, 2018 5:48 am
by domsch1988
It's not getting better with 2.1.3
I installed that on a new Server i wanted to add. All i get in the Log is:
Code: Select all
2018-03-12 11:45:06,982:WARNING:ncpacheck:Unable to parse all arguments from instruction. Mis-paired option: avg
2018-03-12 11:45:07,638:WARNING:ncpacheck:Unable to parse all arguments from instruction. Mis-paired option: Gi
2018-03-12 11:45:07,904:WARNING:ncpacheck:Unable to parse all arguments from instruction. Mis-paired option: Gi
2018-03-12 11:45:08,700:ERROR:nrdp:junk after document element: line 1, column 40
Traceback (most recent call last):
File "C:\ncpa\agent\passive\nrdp.py", line 198, in submit_to_nagios
File "C:\ncpa\agent\passive\nrdp.py", line 145, in log_result
File "C:\Python27\lib\xml\dom\minidom.py", line 1928, in parseString
File "C:\Python27\lib\xml\dom\expatbuilder.py", line 940, in parseString
File "C:\Python27\lib\xml\dom\expatbuilder.py", line 223, in parseString
ExpatError: junk after document element: line 1, column 40
No Checks are processed. Configs where copied from the Server that is already working (minus the spaces). Any tips?
EDIT: I'm dumb, had the wrong URL (http instead of https)
Re: Distributed Monitoring with Windows Environments
Posted: Mon Mar 12, 2018 6:45 am
by domsch1988
So, quick test shows that even with 2.1.3 i can't use any names that contain spaces. Same error.
Re: Distributed Monitoring with Windows Environments
Posted: Mon Mar 12, 2018 5:02 pm
by kyang
I'm gonna have to replicate this myself. It looks like it can be true, and we will have to see what the NCPA developer says.
Re: Distributed Monitoring with Windows Environments
Posted: Thu Mar 29, 2018 2:07 am
by domsch1988
kyang wrote:I'm gonna have to replicate this myself. It looks like it can be true, and we will have to see what the NCPA developer says.
Any News on that Problem?
Re: Distributed Monitoring with Windows Environments
Posted: Thu Mar 29, 2018 10:35 am
by kyang
Hello,
I'm sorry for not following up again.
Yes, I was able to reproduce this and will be forwarding this to our NCPA developer.
Please look at my screenshots. For this example I used the interface card also, against an object with spaces in its name.
ncpa1.PNG
ncpa2.PNG
ncpa3.PNG
Re: Distributed Monitoring with Windows Environments
Posted: Thu Mar 29, 2018 3:28 pm
by kyang
UPDATE:
@domsch1988, I found out there is a way around this that has already been put into the github issues.
https://github.com/NagiosEnterprises/ncpa/issues/336
If a host/service has spaces in its name, for example. -->
I am a host --> (You would use the
%20 to get past that) -->
I%20am%20a%20host
I tested this, and confirmed because my interface now works correctly!
Code: Select all
%HOSTNAME%|Interface Check = /interface/VMware%20Network%20Adapter%20VMnet1/bytes_recv
ncpa4.PNG