Login or Register to Ask a Question and Join Our Community


Infrastructure Monitoring

check_logfiles 2.5.5.1 (Default branch)

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums UNIX and Linux Applications Infrastructure Monitoring check_logfiles 2.5.5.1 (Default branch)
# 1  
Old 02-02-2009
check_logfiles 2.5.5.1 (Default branch)
check_logfiles is a plugin for Nagios which checks logfiles for defined patterns. It is capable of detecting logfile rotation. If you tell it how the rotated archives look, it will also examine these files. Unlike check_logfiles, traditional logfile plugins were not aware of the gap which could occur, so under some circumstances they ignored what had happened between their checks. A configuration file is used to specify where to search, what to search, and what to do if a matching line is found. License: GNU General Public License (GPL) Changes:
Native support for the Windows EventLog was added (which requires the Win32-Perl-Module). Multiline-output was added. Pathnames can now contain blanks. Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. Infrastructure Monitoring

check_logfiles HPUX

Hello, I have to monitoring a log in a machine HPUX B.11.00. I defined config file: $seekfilesdir = '/opt/tools/capmau/log'; @logs = ( { tag => 'sybase', logfile => '/opt/sybase/ASE-12_0/install/errorlog', criticalpatterns =>, }, ); and defined in nrpe.cfg: ... (0 Replies)
Discussion started by: msanbrug
0 Replies
Login or Register to Ask a Question

LEARN ABOUT DEBIAN

mailping-latency

2004-04-16

      mailping

      0.0.4

MAILPING-LATENCY(1)						     Mailping						       MAILPING-LATENCY(1)

NAME

       mailping-latency - Munin plugin to graph latency of mail deliveries

SYNOPSIS

       /usr/share/mailping/munin-plugins/mailping-latency {[config] | ['']}

DESCRIPTION

	mailping-latency is a Munin plugin that monitors the time spent between email submit and it's delivery.

   Configuration output
       When passed config, it outputs Munin configuration information. If there are no circuits defined (no subdirectories in /etc/mailping), it
       specifies that Munin should draw no graph either.

       If configuration files /etc/mailping/circuit/warnlatency and /etc/mailping/circuit/faillatency exist, the values in them are passed on to
       Munin, for use in Nagios alert integration.

   Value output
       When passed an empty string '', mailping-latency outputs latency of last successful probe message, for each configured circuit.

FILES

       /etc/mailping/
	   List of circuits that exist; each subdirectory is a circuit.

       /etc/mailping/circuit/warnlatency
	   If latency is greater than this many seconds, a Nagios warning is triggered by Munin (assuming it has been configured to do that).
	   Default: no warnings.

       /etc/mailping/circuit/faillatency
	   If latency is greater than this many seconds, a Nagios alert is triggered by Munin (assuming it has been configured to do that).
	   Default: no alerts.

       /var/lib/mailping/state/circuit/latency
	   Amount of latency in seconds of the last successful probe for circuit.

ENVIRONMENT

       MAILPING_CONFIGDIR
	   Override the location of the configuration directory. Default: /etc/mailping

       MAILPING_STATEDIR
	   Override the location of the state directory. Circuit states are stored in the state subdirectory of this directory, in subdirectories
	   named after the circuit name. Default: /var/lib/mailping

SEE ALSO

	mailping-success(1), mailping-cron(1), mailping-store(1), munin-run(8), munin-node(8)

AUTHOR

       Tommi Virtanen <tv@havoc.fi>
       Havoc Consulting
	   Author.

COPYRIGHT

       Copyright (C) 2004 Havoc Consulting

mailping 0.							    2004-04-16						       MAILPING-LATENCY(1)