On 19 March 2010 14:31, C. Bensend <be...@bennyvision.com> wrote: > > Hey folks, > > I have been beating my head against various and sundry walls, > tables, and desks for quite some time now, and my brain is starting > to get very, VERY mushy.
I agree, it's not easy. If it's any help, the best I've been able or bothered to get for monitoring any errors from MS SQL Server is to put this in the NSClient++ .ini file: Event_MSSQL=inject CheckEventLog filter=new file=application MaxWarn=1 MaxCrit=2 filter+generated=<30m filter+eventSource=substr:MSSQL filter+eventType==error truncate=64 This means all the command options are kept in the NSClient++ config which means you don't have to worry so much about escaping various non-alphanumeric characters. To run the nrpe check (for example from the command line on your nagios server), all you need to do is: /usr/local/nagios/libexec/check_nrpe -H xxx.xxx.xxx.xxx -c Event_MSSQL An alternative is to configure the Windows server to send events as SNMP traps and use snmptrapd and snmptt to push these through to Nagios as passive checks. I wrote a section in the Nagios Wiki on it at: http://wiki.nagios.org/index.php/Howtos:snmp-windows I confess I never actually got to use this method in anger (which is a shame because I think it works pretty well) because our Windows admins wouldn't let me enable the SNMP service on our production Windows servers. hth, Jim ------------------------------------------------------------------------------ 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
