Share

check_logfiles

Code

Programming Languages: Perl

License: GNU General Public License (GPL)

Repositories

browse code, statistics svn co https://check-logfiles.svn.sourceforge.net/svnroot/check-logfiles check-logfiles

browse code, statistics, last commit on 2006-03-03 cvs -d:pserver:anonymous@check-logfiles.cvs.sourceforge.net:/cvsroot/check-logfiles login

cvs -z3 -d:pserver:anonymous@check-logfiles.cvs.sourceforge.net:/cvsroot/check-logfiles co -P modulename

Show:

What's happening?

  • 2.3.1.2 come and get it

    Handles logfiles of > 1GB size. More options migrated from the config file to the command line. New macros $CL_PROTOCOLFILE$ and $CL_SERVICEPERFDATA$.

    2007-12-28 12:57:35 UTC by lausser

  • Followup: RE: Many log files, wildcard filename matching?

    Simply add the following as last line to your config file: 1; The require expects the code in the "required" file to return a true value. The rotation 'Archive\..*log' would match too many files in my opinion. The pattern must only match those filenames which are derived from the $logfile name.

    2007-11-03 11:44:49 UTC by lausser

  • Followup: RE: Many log files, wildcard filename matchin

    I realize that "rotation" line in the config file above is not right. I have taken it out. Why am I getting this error? Is the for loop the problem? Am I missing some syntactical punctuation? (I tried to match up brackets, braces and parenthesis properly.) Also, the filenames that are globbed will have square brackets in the filename (NOT my choice, not my files). Could this...

    2007-11-02 18:04:48 UTC by adodson

  • Followup: RE: Many log files, wildcard filename matchin

    Gerhard, I tried this on my testing system, but I must be missing something. I get this error when check_logfiles runs: UNKNOWN - syntax error C:\temp\check_logfiles.conf did not return a true value at C:\temp\check_logfiles line 140. Line 140 in check_logfiles is: require $fullcfgfile; My config file must be missing something, but it seems to have everything I had before...

    2007-10-29 13:39:40 UTC by adodson

  • Followup: RE: Many log files, wildcard filename matchin

    Gerhard, Yes, the log files come and go, and the file names are predictable, but a bit dynamic. I think the first option is exactly what I need. Thank you very much. Anthony.

    2007-10-27 14:31:37 UTC by adodson

  • Followup: RE: Many log files, wildcard filename matching?

    Hi Anthony, do these logfiles change or appear and disappear? The config file is just a piece of perl code. You can do the following: @searches = (); foreach my $logfile (glob 'C:\path\*.log') { push(@searches, { tag => basename($logfile), logfile => $logfile, options => 'noperfdata', criticalpatterns => ..... }); } If your logfiles don't change,

    2007-10-26 23:26:16 UTC by lausser

  • Many log files, wildcard filename matching?

    I need to check many log files (perhaps 200). They are all in one directory, and all filenames end with ".log". I need to make the same searches on every log file. I imagine a check_logfiles.conf file with a search tag for EVERY log file would work. Is there a way that within the conf file I could loop over the list of filenames and substitute the loop index in a variable for the...

    2007-10-23 18:18:08 UTC by adodson

  • Release 2.3.1 is out

    Smaller changes: Templates, bzip2 archives, scriptparam bugfix, threshold counters are inherited. See the examples. I made it easier to scan a logfile which contains the forwarded eventlogs of windows clients.

    2007-10-17 09:51:20 UTC by lausser

  • Release 2.3 is out

    2.3 adds support for AIX errpt output instead of logfiles. Performance data have now a correct format. Logfiles can be prefiltered with syslogclient.

    2007-09-12 08:52:53 UTC by lausser

  • please use release 2.2.4.1

    everything else is crap ;-)

    2007-06-10 20:29:49 UTC by lausser

Our Numbers