Usually you call the plugin with the –config option which gets the name of a configuration file: Windows - The plugin works with Unix as well as with Windows (e.g.Performance data - The number of lines scanned and the number of warnings/criticals is output.Macros - Pattern definitions and logfile names may contain macros, which are resolved at runtime.Protocol - The matching lines can be written to a protocol file the name of which will be included in the plugin’s output.Thresholds - You can define the number of matching lines which are necessary to activate an alert.You can define exception patterns which are more specific versions of your critical/warning patterns. Exceptions - If a pattern matches, the matched line could be a very special case which should not be counted as an error.
Check_logfiles lets you call scripts either after every hit or at the beginning or the end of it’s runtime.
Perl file monitor detect file change code#
Sometimes, however, you want to run some code during the scan every time you got a hit. Triggered actions - Usually nagios plugins return just an exit code and a line of text, describing the result of the check.More than one pattern can be defined which again can be classified as warning patterns and critical patterns.The most common rotation schemes are predefined but you can describe any strategy (shortly: where and under which name is a logfile archived).
Perl file monitor detect file change archive#
If this rotation is done between two runs of check_logfiles also the rotated archive has to be scanned to avoid gaps. Each operating system or company has it’s own naming scheme.
0 kommentar(er)
