Page 2 of 2
Re: Passive Windows monitoring advice!
Posted: Thu Mar 27, 2014 9:03 am
by BanditBBS
Scott,
The vbs script is not the issue. It is NCPA that is kicking off the error saying it can not find kickNRDS.vbs, but only after it does find and run it once.
Re: Passive Windows monitoring advice!
Posted: Thu Mar 27, 2014 3:32 pm
by lmiltchev
Nick just told me that he found a couple of bugs in ncpa, which should be fixed in the next release of ncpa.
FYI, while testing the *.vbs script, I got the same error:
Code: Select all
Input Error: Can not find script file "C:\Windows\system32\plugins\kickNRDS.vbs
Re: Passive Windows monitoring advice!
Posted: Fri Mar 28, 2014 8:16 am
by BanditBBS
Ok, I have to be the pain in the butt user and ask these couple questions:
1.) Is this one of the bugs being fixed? So that i can execute a vbs more that one time?
2.) Any chance on earth this next version is coming very soon(i.e. 2-3 business days)?
As mentioned in my opening post, i am trying to find the best way to move forward and away from WMI for my 1000+ windows servers and I need to make a decision and plant my feet for a battle here in the next few days, I can't wait much longer for than that. So if the answer to #2 is no, then I'll have to take NCPA out of the running for my environment.
Re: Passive Windows monitoring advice!
Posted: Fri Mar 28, 2014 11:06 am
by lmiltchev
I understand that you need to make an important decision, and you don't have much time, however the only person who knows if this could be done in timely manner is Nick. He should be in today (around noon), so you should hear from him by the end of the day.
Re: Passive Windows monitoring advice!
Posted: Sun Mar 30, 2014 10:51 pm
by BanditBBS
lmiltchev wrote:I understand that you need to make an important decision, and you don't have much time, however the only person who knows if this could be done in timely manner is Nick. He should be in today (around noon), so you should hear from him by the end of the day.
Hey Ludmil, just bringing this up again to make sure it is on someone's list
Any chance Nick can let me know if the fix for running passive scripts with NCPA is going to be fixed soon? I hate asking for a date, but until I"m told to stop...well...I'm going to ask, LOL. I've tried it with a .bat file as well and it gives a similar error after the 1st successful run, so it's definitely something in NCPA that needs resolved.
Re: Passive Windows monitoring advice!
Posted: Mon Mar 31, 2014 10:36 am
by sreinhardt
Ludmil is actually out for the week, I will check with nick though. I'll shoot him an email since he is not in today, otherwise will discuss tomorrow when he is in.
Re: Passive Windows monitoring advice!
Posted: Tue Apr 01, 2014 2:45 pm
by BanditBBS
Ok Nagios folks...here is a document I'm putting together to go over all the options with my boss and what the pros and cons are. Please read and let me know if you can think of another pro or con to add to any of them and also if I am completely off base on one that I have put down.
Windows monitoring options:
Agentless with ssh
• Pros
o Can run any windows app/script as a check and/or event handler
• Cons
o ssh would need installed on all servers
o No method to automatically update agent configuration, would need scripted
o No method to automatically distribute updated plugins, would need scripted
Agentless with WMI
• Pros
o Reads information directly from the OS(performance counters)
• Cons
o No method to automatically update agent configuration, would need scripted
o WMI can easily stop working or timeout in responding to requests making Nagios percentages be off
o Large overhead and requires extra Nagios Workers
Active Agent - NSClient
• Pros
o Can run any windows app/script as a check and/or event handler
o The most used and stable Windows agent
• Cons
o No method to automatically distribute updated plugins, would need scripted. This is for adding new command definitions. There is a work around for this developed by me
o Enterprise apps team seems to believe this cause major overhead on the servers. I was never approached with the stats that show this and have a hard time believing it
Passive Agent – NRDS
• Pros
o Can run any windows app/script as a check and/or event handler
o Remote host only needs to be able to hit port 443 or 80 on the Nagios server
o Can automatically configure the agent and deploy updated check scripts centrally from Nagios
• Cons
o Uses scheduled tasks to kick off the agent every X minutes. Control-M can be used but with a massive rollout that means Control-M on every server
Passive or Active Agent – NCPA
• Pros
o Built in API to handle most common checks
o Can run any windows app/script as a check and/or event handler
o Creates a web page on server to view live data(can be disabled)
o Runs NRDS, no need to scheduled task and has all pros of NRDS
• Cons
o Currently the passive checks outside of the API are not functioning
o Currently no method to automatically distribute updated plugins, would need scripted
o Currently no method to automatically update agent configuration, would need scripted
o Not very mature, still active bugs being fixed regularly
The two I am leaning towards are NRDS and NCPA. NCPA though is 2nd due to the amount of bug/issues I am having with it and not knowing the level of development being done to it.
Re: Passive Windows monitoring advice!
Posted: Tue Apr 01, 2014 3:09 pm
by sreinhardt
I think you have hit just about every pro\con that I could think of and just about every way of monitoring windows short of snmp(buhhh (please don't consider this)). I was actually just looking for this page to update you after talking with Nick. He is aware of the present issues with external passive checks, and is planning a patch for the next version, which is likely about 2 weeks away.
Obviously the maturity level or somewhat lack there of, of NCPA is a potential issue. However I think that can largely be worked around aside from current passive check issues, by using an event handler or something else to restart the service if there is an issue, and possibly a check that purely looks for the service(s) to be running and responding, and if not executes the event handler to restart them. I think it would be a pretty easy thing to setup, but that also depends on if this is something you want to have to do.(ideally not with a more stable agent)
Otherwise despite my tendencies towards NCPA, the only two I consider real options here are NCPA\nrds and WMI monitoring, and I know you would like to move away from wmi if possible.
Re: Passive Windows monitoring advice!
Posted: Wed Apr 02, 2014 10:36 am
by BanditBBS
Thanks for the input. i think you can consider this thread closed. Going with NRDS/Conrol-M for now until NCPA passive check issues are resolved.