> Likewise please ask again if you're still stuck. I don't mind having > another bash at some of these issues when I have a minute. > > I just read your thread on the NSClient++ forum too. I have found > that whenever I try to combine too many matches in one check it simply > doesn't work right (can't remember the precise details). So I > normally try to match on as few things as possible for each check even > if that means I'm casting the net maybe a little wider than I'd really > like.
Thanks everyone for your suggestions... In the end, I gave up on using either NSClient++ or the Nagios EventLog Agent to check my windows event logs. While I certainly will admit the problem still may have been with me, I have come to the conclusion that either they're not designed to do what I needed (to find a single event ID) or they're inconsistent/under-documented. I ended up going with check_logfiles from ConSol: http://labs.consol.de/lang/en/nagios/check_logfiles/ Not only are the developers responsive, but it *works*. I use it with a very flexible definition via NSClient++, and so far it's performing *exactly* like I need. :) Thanks again, everyone! Benny -- Whoever said that hell hath no fury like a women scorned never owned a cat. -- bash.org ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null