log::log4perl::appender::rrds(3pm) [debian man page]

Appender::RRDs(3pm)					User Contributed Perl Documentation				       Appender::RRDs(3pm)

NAME

       Log::Log4perl::Appender::RRDs - Log to a RRDtool Archive

SYNOPSIS

	   use Log::Log4perl qw(get_logger);
	   use RRDs;

	   my $DB = "myrrddb.dat";

	   RRDs::create(
	     $DB, "--step=1",
	     "DS:myvalue:GAUGE:2:U:U",
	     "RRA:MAX:0.5:1:120");

	   print time(), "
";

	   Log::Log4perl->init(qq{
	     log4perl.category = INFO, RRDapp
	     log4perl.appender.RRDapp = Log::Log4perl::Appender::RRDs
	     log4perl.appender.RRDapp.dbname = $DB
	     log4perl.appender.RRDapp.layout = Log::Log4perl::Layout::PatternLayout
	     log4perl.appender.RRDapp.layout.ConversionPattern = N:%m
	   });

	   my $logger = get_logger();

	   for(10, 15, 20, 25) {
	       $logger->info($_);
	       sleep 1;
	   }

DESCRIPTION

       "Log::Log4perl::Appender::RRDs" appenders facilitate writing data to RRDtool round-robin archives via Log4perl. For documentation on RRD
       and its Perl interface "RRDs" (which comes with the distribution), check out <http://rrdtool.org>.

       Messages sent to Log4perl's RRDs appender are expected to be numerical values (ints or floats), which then are used to run a "rrdtool
       update" command on an existing round-robin database. The name of this database needs to be set in the appender's "dbname" configuration
       parameter.

       If there's more parameters you wish to pass to the "update" method, use the "rrdupd_params" configuration parameter:

	   log4perl.appender.RRDapp.rrdupd_params = --template=in:out

       To read out the round robin database later on, use "rrdtool fetch" or "rrdtool graph" for graphic displays.

COPYRIGHT AND LICENSE

       Copyright 2002-2009 by Mike Schilli <m@perlmeister.com> and Kevin Goess <cpan@goess.org>.

       This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

perl v5.10.1							    2010-07-21						       Appender::RRDs(3pm)

Appender::Limit(3)					User Contributed Perl Documentation					Appender::Limit(3)

NAME

	   Log::Log4perl::Appender::Limit - Limit message delivery via block period

SYNOPSIS

	   use Log::Log4perl qw(:easy);

	   my $conf = qq(
	     log4perl.category = WARN, Limiter

		 # Email appender
	     log4perl.appender.Mailer	       = Log::Dispatch::Email::MailSend
	     log4perl.appender.Mailer.to       = drone@pageme.com
	     log4perl.appender.Mailer.subject  = Something's broken!
	     log4perl.appender.Mailer.buffered = 0
	     log4perl.appender.Mailer.layout   = PatternLayout
	     log4perl.appender.Mailer.layout.ConversionPattern=%d %m %n

		 # Limiting appender, using the email appender above
	     log4perl.appender.Limiter		    = Log::Log4perl::Appender::Limit
	     log4perl.appender.Limiter.appender     = Mailer
	     log4perl.appender.Limiter.block_period = 3600
	   );

	   Log::Log4perl->init($conf);
	   WARN("This message will be sent immediately");
	   WARN("This message will be delayed by one hour.");
	   sleep(3601);
	   WARN("This message plus the last one will be sent now");

DESCRIPTION

       "appender"
	   Specifies the name of the appender used by the limiter. The appender specified must be defined somewhere in the configuration file, not
	   necessarily before the definition of "Log::Log4perl::Appender::Limit".

       "block_period"
	   Period in seconds between delivery of messages. If messages arrive in between, they will be either saved (if "accumulate" is set to a
	   true value) or discarded (if "accumulate" isn't set).

       "persistent"
	   File name in which "Log::Log4perl::Appender::Limit" persistently stores delivery times. If omitted, the appender will have no
	   recollection of what happened when the program restarts.

       "max_until_flushed"
	   Maximum number of accumulated messages. If exceeded, the appender flushes all messages, regardless if the interval set in
	   "block_period" has passed or not. Don't mix with "max_until_discarded".

       "max_until_discarded"
	   Maximum number of accumulated messages. If exceeded, the appender will simply discard additional messages, waiting for "block_period"
	   to expire to flush all accumulated messages. Don't mix with "max_until_flushed".

       If the appender attached to "Limit" uses "PatternLayout" with a timestamp specifier, you will notice that the message timestamps are
       reflecting the original log event, not the time of the message rendering in the attached appender. Major trickery has been applied to
       accomplish this (Cough!).

DEVELOPMENT NOTES

       "Log::Log4perl::Appender::Limit" is a composite appender.  Unlike other appenders, it doesn't log any messages, it just passes them on to
       its attached sub-appender.  For this reason, it doesn't need a layout (contrary to regular appenders).  If it defines none, messages are
       passed on unaltered.

       Custom filters are also applied to the composite appender only.	They are not applied to the sub-appender. Same applies to appender
       thresholds. This behaviour might change in the future.

COPYRIGHT AND LICENSE

       Copyright 2002-2009 by Mike Schilli <m@perlmeister.com> and Kevin Goess <cpan@goess.org>.

       This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

perl v5.12.1							    2010-02-16							Appender::Limit(3)