Now we can build the connection between the NSClient++ agent and the check_logfiles.exe plugin on the Windows system.
File monitor windows software#
While it is possible to also call NSClient++ with the Nagios-builtin plugin 'check_nt', the additional plugin 'check_nrpe' is needed to use NSClient++ with external scripts.Īfter installing the NSClient++ software on the Windows system and the NRPE check plugin on the Nagios server, we test the monitoring connection from Nagios and verify network connectivity works: During the installation of NSClient++ we should enable the NRPE server module to listen for check_nrpe service requests. It collects various standard performance data, and in addition it can call external scripts for custom monitoring such as our check_logfiles.exe plugin.
File monitor windows free#
Next comes the NSClient++, which is a free monitoring agent written for Windows (32 and 64bit). |apperror_lines=2 apperror_warnings=0 apperror_criticals=1 apperror_unknowns=0 Part 2: Initiating the log check and transporting the result back to Nagios In the example below, I inserted a test string into the log file to see if the critical pattern filter matches.Ĭ:\logmonitor> check_logfiles.exe -f check_logfiles.cfgĬRITICAL - (1 errors in check_logfiles.protocol-15-02-37) - ERROR timestamp appfailure 1 caused by xxx
Next, we run the check_logfiles.exe on the Windows system over our example logfile to test the configuration we just created. We set our example log file to be in D:\data\logs\log1.log, and we define example warning and critical strings to search for. Next, we create a log parsing configuration file, here I named it check_logfiles.cfg. Either in a directory by itself, or another good place is to place it later into the scripts directory of the NSClient++ home. Simply place it in a good home on your Windows server. It is available as an executable for Windows and integrates with NSclient++. The check_logfiles plugin is needed to parse the log based on freely defined patterns and return a Nagios readable status. Part 1: Custom log parsing under Windows based on Error and Warn criteria, generating Nagios compatible output
check_logfiles from ConSol Labs for actually parsing the log.In this particular example, I will look at building the Windows log monitoring from the following 3 software components: I believe there is no turnkey solution and to solve it we need to break the requirement up into functional parts to combine existing software. Monitoring custom application log files with Nagios is quite a complex task, it deserves a tutorial of its own.
0 kommentar(er)
