ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/AnyEvent/lib/AnyEvent/Log.pm
(Generate patch)

Comparing AnyEvent/lib/AnyEvent/Log.pm (file contents):
Revision 1.2 by root, Tue Aug 16 14:47:27 2011 UTC vs.
Revision 1.23 by root, Sun Aug 21 03:20:52 2011 UTC

2 2
3AnyEvent::Log - simple logging "framework" 3AnyEvent::Log - simple logging "framework"
4 4
5=head1 SYNOPSIS 5=head1 SYNOPSIS
6 6
7 # simple use
8 use AnyEvent;
9
10 AE::log debug => "hit my knee";
11 AE::log warn => "it's a bit too hot";
12 AE::log error => "the flag was false!";
13 AE::log fatal => "the bit toggled! run!"; # never returns
14
15 # "complex" use (for speed sensitive code)
7 use AnyEvent::Log; 16 use AnyEvent::Log;
17
18 my $tracer = AnyEvent::Log::logger trace => \$my $trace;
19
20 $tracer->("i am here") if $trace;
21 $tracer->(sub { "lots of data: " . Dumper $self }) if $trace;
22
23 # configuration
24
25 # set logging for the current package to errors and higher only
26 AnyEvent::Log::ctx->level ("error");
27
28 # set logging level to suppress anything below "notice"
29 $AnyEvent::Log::FILTER->level ("notice");
30
31 # send all critical and higher priority messages to syslog,
32 # regardless of (most) other settings
33 $AnyEvent::Log::COLLECT->attach (new AnyEvent::Log::Ctx
34 level => "critical",
35 log_to_syslog => 0,
36 );
37
38 # see also EXAMPLES, below
8 39
9=head1 DESCRIPTION 40=head1 DESCRIPTION
10 41
11This module implements a relatively simple "logging framework". It doesn't 42This module implements a relatively simple "logging framework". It doesn't
12attempt to be "the" logging solution or even "a" logging solution for 43attempt to be "the" logging solution or even "a" logging solution for
13AnyEvent - AnyEvent simply creates logging messages internally, and this 44AnyEvent - AnyEvent simply creates logging messages internally, and this
14module more or less exposes the mechanism, with some extra spiff to allow 45module more or less exposes the mechanism, with some extra spiff to allow
15using it from other modules as well. 46using it from other modules as well.
16 47
17Remember that the default verbosity level is C<0>, so nothing 48Remember that the default verbosity level is C<0> (C<off>), so nothing
18will be logged, ever, unless you set C<$Anyvent::VERBOSE> or 49will be logged, unless you set C<PERL_ANYEVENT_VERBOSE> to a higher number
19C<PERL_ANYEVENT_VERBOSE> to a higher number. 50before starting your program, or change the logging level at runtime with
51something like:
20 52
21Possible future extensions are to allow custom log targets (where the 53 use AnyEvent::Log;
22level is an object), log filtering based on package, formatting, aliasing 54 AnyEvent::Log::FILTER->level ("info");
23or package groups.
24 55
56The design goal behind this module was to keep it simple (and small),
57but make it powerful enough to be potentially useful for any module, and
58extensive enough for the most common tasks, such as logging to multiple
59targets, or being able to log into a database.
60
61The amount of documentation might indicate otherwise, but the module is
62still just below 300 lines of code.
63
64=head1 LOGGING LEVELS
65
66Logging levels in this module range from C<1> (highest priority) to C<9>
67(lowest priority). Note that the lowest numerical value is the highest
68priority, so when this document says "higher priority" it means "lower
69numerical value".
70
71Instead of specifying levels by name you can also specify them by aliases:
72
73 LVL NAME SYSLOG PERL NOTE
74 1 fatal emerg exit aborts program!
75 2 alert
76 3 critical crit
77 4 error err die
78 5 warn warning
79 6 note notice
80 7 info
81 8 debug
82 9 trace
83
84As you can see, some logging levels have multiple aliases - the first one
85is the "official" name, the second one the "syslog" name (if it differs)
86and the third one the "perl" name, suggesting that you log C<die> messages
87at C<error> priority.
88
89You can normally only log a single message at highest priority level
90(C<1>, C<fatal>), because logging a fatal message will also quit the
91program - so use it sparingly :)
92
93Some methods also offer some extra levels, such as C<0>, C<off>, C<none>
94or C<all> - these are only valid in the methods they are documented for.
95
25=head1 LOG FUNCTIONS 96=head1 LOGGING FUNCTIONS
26 97
27These functions allow you to log messages. They always use the caller's 98These functions allow you to log messages. They always use the caller's
28package as a "logging module/source". Also, The main logging function is 99package as a "logging context". Also, the main logging function C<log> is
29easily available as C<AnyEvent::log> or C<AE::log> when the C<AnyEvent> 100callable as C<AnyEvent::log> or C<AE::log> when the C<AnyEvent> module is
30module is loaded. 101loaded.
31 102
32=over 4 103=over 4
33 104
34=cut 105=cut
35 106
37 108
38use Carp (); 109use Carp ();
39use POSIX (); 110use POSIX ();
40 111
41use AnyEvent (); BEGIN { AnyEvent::common_sense } 112use AnyEvent (); BEGIN { AnyEvent::common_sense }
113use AnyEvent::Util ();
114
115our $VERSION = $AnyEvent::VERSION;
116
117our ($COLLECT, $FILTER, $LOG);
42 118
43our ($now_int, $now_str1, $now_str2); 119our ($now_int, $now_str1, $now_str2);
44 120
45# Format Time, not public - yet? 121# Format Time, not public - yet?
46sub ft($) { 122sub ft($) {
51 if $now_int != $i; 127 if $now_int != $i;
52 128
53 "$now_str1$f$now_str2" 129 "$now_str1$f$now_str2"
54} 130}
55 131
132our %CTX; # all package contexts
133
134# creates a default package context object for the given package
135sub _pkg_ctx($) {
136 my $ctx = bless [$_[0], (1 << 10) - 1 - 1, {}], "AnyEvent::Log::Ctx";
137
138 # link "parent" package
139 my $parent = $_[0] =~ /^(.+)::/
140 ? $CTX{$1} ||= &_pkg_ctx ("$1")
141 : $COLLECT;
142
143 $ctx->[2]{$parent+0} = $parent;
144
145 $ctx
146}
147
56=item AnyEvent::Log::log $level, $msg[, @args] 148=item AnyEvent::Log::log $level, $msg[, @args]
57 149
58Requests logging of the given C<$msg> with the given log level (1..9). 150Requests logging of the given C<$msg> with the given log level, and
59You can also use the following strings as log level: C<fatal> (1), 151returns true if the message was logged I<somewhere>.
60C<alert> (2), C<critical> (3), C<error> (4), C<warn> (5), C<note> (6),
61C<info> (7), C<debug> (8), C<trace> (9).
62 152
63For C<fatal> log levels, the program will abort. 153For C<fatal> log levels, the program will abort.
64 154
65If only a C<$msg> is given, it is logged as-is. With extra C<@args>, the 155If only a C<$msg> is given, it is logged as-is. With extra C<@args>, the
66C<$msg> is interpreted as an sprintf format string. 156C<$msg> is interpreted as an sprintf format string.
67 157
68The C<$msg> should not end with C<\n>, but may if that is convenient for 158The C<$msg> should not end with C<\n>, but may if that is convenient for
69you. Also, multiline messages are handled properly. 159you. Also, multiline messages are handled properly.
70 160
71In addition, for possible future expansion, C<$msg> must not start with an 161Last not least, C<$msg> might be a code reference, in which case it is
72angle bracket (C<< < >>). 162supposed to return the message. It will be called only then the message
163actually gets logged, which is useful if it is costly to create the
164message in the first place.
73 165
74Whether the given message will be logged depends on the maximum log level 166Whether the given message will be logged depends on the maximum log level
75and the caller's package. 167and the caller's package. The return value can be used to ensure that
168messages or not "lost" - for example, when L<AnyEvent::Debug> detects a
169runtime error it tries to log it at C<die> level, but if that message is
170lost it simply uses warn.
76 171
77Note that you can (and should) call this function as C<AnyEvent::log> or 172Note that you can (and should) call this function as C<AnyEvent::log> or
78C<AE::log>, without C<use>-ing this module if possible, as those functions 173C<AE::log>, without C<use>-ing this module if possible (i.e. you don't
79will laod the logging module on demand only. 174need any additional functionality), as those functions will load the
175logging module on demand only. They are also much shorter to write.
176
177Also, if you optionally generate a lot of debug messages (such as when
178tracing some code), you should look into using a logger callback and a
179boolean enabler (see C<logger>, below).
180
181Example: log something at error level.
182
183 AE::log error => "something";
184
185Example: use printf-formatting.
186
187 AE::log info => "%5d %-10.10s %s", $index, $category, $msg;
188
189Example: only generate a costly dump when the message is actually being logged.
190
191 AE::log debug => sub { require Data::Dump; Data::Dump::dump \%cache };
80 192
81=cut 193=cut
82 194
83# also allow syslog equivalent names 195# also allow syslog equivalent names
84our %STR2LEVEL = ( 196our %STR2LEVEL = (
85 fatal => 1, emerg => 1, 197 fatal => 1, emerg => 1, exit => 1,
86 alert => 2, 198 alert => 2,
87 critical => 3, crit => 3, 199 critical => 3, crit => 3,
88 error => 4, err => 4, 200 error => 4, err => 4, die => 4,
89 warn => 5, warning => 5, 201 warn => 5, warning => 5,
90 note => 6, notice => 6, 202 note => 6, notice => 6,
91 info => 7, 203 info => 7,
92 debug => 8, 204 debug => 8,
93 trace => 9, 205 trace => 9,
94); 206);
95 207
208sub now () { time }
209
210AnyEvent::post_detect {
211 *now = \&AE::now;
212};
213
96our @LEVEL2STR = qw(0 fatal alert crit error warn note info debug trace); 214our @LEVEL2STR = qw(0 fatal alert crit error warn note info debug trace);
97 215
216# time, ctx, level, msg
217sub _format($$$$) {
218 my $ts = ft $_[0];
219 my $ct = " ";
220
221 my @res;
222
223 for (split /\n/, sprintf "%-5s %s: %s", $LEVEL2STR[$_[2]], $_[1][0], $_[3]) {
224 push @res, "$ts$ct$_\n";
225 $ct = " + ";
226 }
227
228 join "", @res
229}
230
231sub _log {
232 my ($ctx, $level, $format, @args) = @_;
233
234 $level = $level > 0 && $level <= 9
235 ? $level+0
236 : $STR2LEVEL{$level} || Carp::croak "$level: not a valid logging level, caught";
237
238 my $mask = 1 << $level;
239
240 my ($success, %seen, @ctx, $now, $fmt);
241
242 do
243 {
244 # skip if masked
245 if ($ctx->[1] & $mask && !$seen{$ctx+0}++) {
246 if ($ctx->[3]) {
247 # logging target found
248
249 # now get raw message, unless we have it already
250 unless ($now) {
251 $format = $format->() if ref $format;
252 $format = sprintf $format, @args if @args;
253 $format =~ s/\n$//;
254 $now = AE::now;
255 };
256
257 # format msg
258 my $str = $ctx->[4]
259 ? $ctx->[4]($now, $_[0], $level, $format)
260 : ($fmt ||= _format $now, $_[0], $level, $format);
261
262 $success = 1;
263
264 $ctx->[3]($str)
265 or push @ctx, values %{ $ctx->[2] }; # not consumed - propagate
266 } else {
267 push @ctx, values %{ $ctx->[2] }; # not masked - propagate
268 }
269 }
270 }
271 while $ctx = pop @ctx;
272
273 exit 1 if $level <= 1;
274
275 $success
276}
277
98sub log($$;@) { 278sub log($$;@) {
99 my ($targ, $msg, @args) = @_; 279 _log
280 $CTX{ (caller)[0] } ||= _pkg_ctx +(caller)[0],
281 @_;
282}
100 283
101 my $level = ref $targ ? die "Can't use reference as logging level (yet)" 284*AnyEvent::log = *AE::log = \&log;
102 : $targ > 0 && $targ <= 9 ? $targ+0
103 : $STR2LEVEL{$targ} || Carp::croak "$targ: not a valid logging level, caught";
104 285
105 return if $level > $AnyEvent::VERBOSE; 286=item $logger = AnyEvent::Log::logger $level[, \$enabled]
106 287
107 my $pkg = (caller)[0]; 288Creates a code reference that, when called, acts as if the
289C<AnyEvent::Log::log> function was called at this point with the given
290level. C<$logger> is passed a C<$msg> and optional C<@args>, just as with
291the C<AnyEvent::Log::log> function:
108 292
109 $msg = sprintf $msg, @args if @args; 293 my $debug_log = AnyEvent::Log::logger "debug";
110 $msg =~ s/\n$//;
111 294
112 # now we have a message, log it 295 $debug_log->("debug here");
113 #TODO: could do LOTS of stuff here, and should, at least in some later version 296 $debug_log->("%06d emails processed", 12345);
297 $debug_log->(sub { $obj->as_string });
114 298
115 $msg = sprintf "%5s (%s) %s", $LEVEL2STR[$level], $pkg, $msg; 299The idea behind this function is to decide whether to log before actually
116 my $pfx = ft AE::now; 300logging - when the C<logger> function is called once, but the returned
301logger callback often, then this can be a tremendous speed win.
117 302
118 for (split /\n/, $msg) { 303Despite this speed advantage, changes in logging configuration will
119 printf STDERR "$pfx $_\n"; 304still be reflected by the logger callback, even if configuration changes
120 $pfx = "\t"; 305I<after> it was created.
306
307To further speed up logging, you can bind a scalar variable to the logger,
308which contains true if the logger should be called or not - if it is
309false, calling the logger can be safely skipped. This variable will be
310updated as long as C<$logger> is alive.
311
312Full example:
313
314 # near the init section
315 use AnyEvent::Log;
316
317 my $debug_log = AnyEvent:Log::logger debug => \my $debug;
318
319 # and later in your program
320 $debug_log->("yo, stuff here") if $debug;
321
322 $debug and $debug_log->("123");
323
324=cut
325
326our %LOGGER;
327
328# re-assess logging status for all loggers
329sub _reassess {
330 local $SIG{__DIE__};
331 my $die = sub { die };
332
333 for (@_ ? $LOGGER{$_[0]} : values %LOGGER) {
334 my ($ctx, $level, $renabled) = @$_;
335
336 # to detect whether a message would be logged, we actually
337 # try to log one and die. this isn't fast, but we can be
338 # sure that the logging decision is correct :)
339
340 $$renabled = !eval {
341 _log $ctx, $level, $die;
342
343 1
344 };
121 } 345 }
122
123 exit 1 if $level <= 1;
124} 346}
125 347
126*AnyEvent::log = *AE::log = \&log; 348sub _logger {
349 my ($ctx, $level, $renabled) = @_;
127 350
128#TODO 351 $$renabled = 1;
352
353 my $logger = [$ctx, $level, $renabled];
354
355 $LOGGER{$logger+0} = $logger;
356
357 _reassess $logger+0;
358
359 my $guard = AnyEvent::Util::guard {
360 # "clean up"
361 delete $LOGGER{$logger+0};
362 };
363
364 sub {
365 $guard if 0; # keep guard alive, but don't cause runtime overhead
366
367 _log $ctx, $level, @_
368 if $$renabled;
369 }
370}
371
372sub logger($;$) {
373 _logger
374 $CTX{ (caller)[0] } ||= _pkg_ctx +(caller)[0],
375 @_
376}
129 377
130=back 378=back
131 379
132=head1 CONFIGURATION FUNCTIONALITY 380=head1 LOGGING CONTEXTS
133 381
134None, yet, except for C<PERL_ANYEVENT_VERBOSE>, described in the L<AnyEvent> manpage. 382This module associates every log message with a so-called I<logging
383context>, based on the package of the caller. Every perl package has its
384own logging context.
385
386A logging context has three major responsibilities: filtering, logging and
387propagating the message.
388
389For the first purpose, filtering, each context has a set of logging
390levels, called the log level mask. Messages not in the set will be ignored
391by this context (masked).
392
393For logging, the context stores a formatting callback (which takes the
394timestamp, context, level and string message and formats it in the way
395it should be logged) and a logging callback (which is responsible for
396actually logging the formatted message and telling C<AnyEvent::Log>
397whether it has consumed the message, or whether it should be propagated).
398
399For propagation, a context can have any number of attached I<slave
400contexts>. Any message that is neither masked by the logging mask nor
401masked by the logging callback returning true will be passed to all slave
402contexts.
403
404Each call to a logging function will log the message at most once per
405context, so it does not matter (much) if there are cycles or if the
406message can arrive at the same context via multiple paths.
407
408=head2 DEFAULTS
409
410By default, all logging contexts have an full set of log levels ("all"), a
411disabled logging callback and the default formatting callback.
412
413Package contexts have the package name as logging title by default.
414
415They have exactly one slave - the context of the "parent" package. The
416parent package is simply defined to be the package name without the last
417component, i.e. C<AnyEvent::Debug::Wrapped> becomes C<AnyEvent::Debug>,
418and C<AnyEvent> becomes ... C<$AnyEvent::Log::COLLECT> which is the
419exception of the rule - just like the "parent" of any single-component
420package name in Perl is C<main>, the default slave of any top-level
421package context is C<$AnyEvent::Log::COLLECT>.
422
423Since perl packages form only an approximate hierarchy, this slave
424context can of course be removed.
425
426All other (anonymous) contexts have no slaves and an empty title by
427default.
428
429When the module is loaded it creates the C<$AnyEvent::Log::LOG> logging
430context that simply logs everything via C<warn>, without propagating
431anything anywhere by default. The purpose of this context is to provide
432a convenient place to override the global logging target or to attach
433additional log targets. It's not meant for filtering.
434
435It then creates the C<$AnyEvent::Log::FILTER> context whose
436purpose is to suppress all messages with priority higher
437than C<$ENV{PERL_ANYEVENT_VERBOSE}>. It then attached the
438C<$AnyEvent::Log::LOG> context to it. The purpose of the filter context
439is to simply provide filtering according to some global log level.
440
441Finally it creates the top-level package context C<$AnyEvent::Log::COLLECT>
442and attaches the C<$AnyEvent::Log::FILTER> context to it, but otherwise
443leaves it at default config. Its purpose is simply to collect all log
444messages system-wide.
445
446The hierarchy is then:
447
448 any package, eventually -> $COLLECT -> $FILTER -> $LOG
449
450The effect of all this is that log messages, by default, wander up to the
451C<$AnyEvent::Log::COLLECT> context where all messages normally end up,
452from there to C<$AnyEvent::Log::FILTER> where log messages with lower
453priority then C<$ENV{PERL_ANYEVENT_VERBOSE}> will be filtered out and then
454to the C<$AnyEvent::Log::LOG> context to be passed to C<warn>.
455
456This makes it easy to set a global logging level (by modifying $FILTER),
457but still allow other contexts to send, for example, their debug and trace
458messages to the $LOG target despite the global logging level, or to attach
459additional log targets that log messages, regardless of the global logging
460level.
461
462It also makes it easy to modify the default warn-logger ($LOG) to
463something that logs to a file, or to attach additional logging targets
464(such as loggign to a file) by attaching it to $FILTER.
465
466=head2 CREATING/FINDING/DESTROYING CONTEXTS
135 467
136=over 4 468=over 4
137 469
470=item $ctx = AnyEvent::Log::ctx [$pkg]
471
472This function creates or returns a logging context (which is an object).
473
474If a package name is given, then the context for that packlage is
475returned. If it is called without any arguments, then the context for the
476callers package is returned (i.e. the same context as a C<AE::log> call
477would use).
478
479If C<undef> is given, then it creates a new anonymous context that is not
480tied to any package and is destroyed when no longer referenced.
481
138=cut 482=cut
483
484sub ctx(;$) {
485 my $pkg = @_ ? shift : (caller)[0];
486
487 ref $pkg
488 ? $pkg
489 : defined $pkg
490 ? $CTX{$pkg} ||= AnyEvent::Log::_pkg_ctx $pkg
491 : bless [undef, (1 << 10) - 1 - 1], "AnyEvent::Log::Ctx"
492}
493
494=item AnyEvent::Log::reset
495
496Resets all package contexts and recreates the default hierarchy if
497necessary, i.e. resets the logging subsystem to defaults, as much as
498possible. This process keeps references to contexts held by other parts of
499the program intact.
500
501This can be used to implement config-file (re-)loading: before loading a
502configuration, reset all contexts.
503
504=cut
505
506sub reset {
507 # hard to kill complex data structures
508 # we "recreate" all package loggers and reset the hierarchy
509 while (my ($k, $v) = each %CTX) {
510 @$v = ($k, (1 << 10) - 1 - 1, { });
511
512 $v->attach ($k =~ /^(.+)::/ ? $CTX{$1} : $AnyEvent::Log::COLLECT);
513 }
514
515 @$_ = ($_->[0], (1 << 10) - 1 - 1)
516 for $LOG, $FILTER, $COLLECT;
517
518 $LOG->slaves;
519 $LOG->title ('$AnyEvent::Log::LOG');
520 $LOG->log_cb (sub {
521 warn shift;
522 0
523 });
524
525 $FILTER->slaves ($LOG);
526 $FILTER->title ('$AnyEvent::Log::FILTER');
527 $FILTER->level ($AnyEvent::VERBOSE);
528
529 $COLLECT->slaves ($FILTER);
530 $COLLECT->title ('$AnyEvent::Log::COLLECT');
531
532 _reassess;
533}
534
535# create the default logger contexts
536$LOG = ctx undef;
537$FILTER = ctx undef;
538$COLLECT = ctx undef;
539
540AnyEvent::Log::reset;
541
542# hello, CPAN, please catch me
543package AnyEvent::Log::LOG;
544package AE::Log::LOG;
545package AnyEvent::Log::FILTER;
546package AE::Log::FILTER;
547package AnyEvent::Log::COLLECT;
548package AE::Log::COLLECT;
549
550package AnyEvent::Log::Ctx;
551
552# 0 1 2 3 4
553# [$title, $level, %$slaves, &$logcb, &$fmtcb]
554
555=item $ctx = new AnyEvent::Log::Ctx methodname => param...
556
557This is a convenience constructor that makes it simpler to construct
558anonymous logging contexts.
559
560Each key-value pair results in an invocation of the method of the same
561name as the key with the value as parameter, unless the value is an
562arrayref, in which case it calls the method with the contents of the
563array. The methods are called in the same order as specified.
564
565Example: create a new logging context and set both the default logging
566level, some slave contexts and a logging callback.
567
568 $ctx = new AnyEvent::Log::Ctx
569 title => "dubious messages",
570 level => "error",
571 log_cb => sub { print STDOUT shift; 0 },
572 slaves => [$ctx1, $ctx, $ctx2],
573 ;
574
575=back
576
577=cut
578
579sub new {
580 my $class = shift;
581
582 my $ctx = AnyEvent::Log::ctx undef;
583
584 while (@_) {
585 my ($k, $v) = splice @_, 0, 2;
586 $ctx->$k (ref $v eq "ARRAY" ? @$v : $v);
587 }
588
589 bless $ctx, $class # do we really support subclassing, hmm?
590}
591
592
593=head2 CONFIGURING A LOG CONTEXT
594
595The following methods can be used to configure the logging context.
596
597=over 4
598
599=item $ctx->title ([$new_title])
600
601Returns the title of the logging context - this is the package name, for
602package contexts, and a user defined string for all others.
603
604If C<$new_title> is given, then it replaces the package name or title.
605
606=cut
607
608sub title {
609 $_[0][0] = $_[1] if @_ > 1;
610 $_[0][0]
611}
612
613=back
614
615=head3 LOGGING LEVELS
616
617The following methods deal with the logging level set associated with the
618log context.
619
620The most common method to use is probably C<< $ctx->level ($level) >>,
621which configures the specified and any higher priority levels.
622
623All functions which accept a list of levels also accept the special string
624C<all> which expands to all logging levels.
625
626=over 4
627
628=item $ctx->levels ($level[, $level...)
629
630Enables logging for the given levels and disables it for all others.
631
632=item $ctx->level ($level)
633
634Enables logging for the given level and all lower level (higher priority)
635ones. In addition to normal logging levels, specifying a level of C<0> or
636C<off> disables all logging for this level.
637
638Example: log warnings, errors and higher priority messages.
639
640 $ctx->level ("warn");
641 $ctx->level (5); # same thing, just numeric
642
643=item $ctx->enable ($level[, $level...])
644
645Enables logging for the given levels, leaving all others unchanged.
646
647=item $ctx->disable ($level[, $level...])
648
649Disables logging for the given levels, leaving all others unchanged.
650
651=cut
652
653sub _lvl_lst {
654 map {
655 $_ > 0 && $_ <= 9 ? $_+0
656 : $_ eq "all" ? (1 .. 9)
657 : $STR2LEVEL{$_} || Carp::croak "$_: not a valid logging level, caught"
658 } @_
659}
660
661our $NOP_CB = sub { 0 };
662
663sub levels {
664 my $ctx = shift;
665 $ctx->[1] = 0;
666 $ctx->[1] |= 1 << $_
667 for &_lvl_lst;
668 AnyEvent::Log::_reassess;
669}
670
671sub level {
672 my $ctx = shift;
673 my $lvl = $_[0] =~ /^(?:0|off|none)$/ ? 0 : (_lvl_lst $_[0])[-1];
674
675 $ctx->[1] = ((1 << $lvl) - 1) << 1;
676 AnyEvent::Log::_reassess;
677}
678
679sub enable {
680 my $ctx = shift;
681 $ctx->[1] |= 1 << $_
682 for &_lvl_lst;
683 AnyEvent::Log::_reassess;
684}
685
686sub disable {
687 my $ctx = shift;
688 $ctx->[1] &= ~(1 << $_)
689 for &_lvl_lst;
690 AnyEvent::Log::_reassess;
691}
692
693=back
694
695=head3 SLAVE CONTEXTS
696
697The following methods attach and detach another logging context to a
698logging context.
699
700Log messages are propagated to all slave contexts, unless the logging
701callback consumes the message.
702
703=over 4
704
705=item $ctx->attach ($ctx2[, $ctx3...])
706
707Attaches the given contexts as slaves to this context. It is not an error
708to add a context twice (the second add will be ignored).
709
710A context can be specified either as package name or as a context object.
711
712=item $ctx->detach ($ctx2[, $ctx3...])
713
714Removes the given slaves from this context - it's not an error to attempt
715to remove a context that hasn't been added.
716
717A context can be specified either as package name or as a context object.
718
719=item $ctx->slaves ($ctx2[, $ctx3...])
720
721Replaces all slaves attached to this context by the ones given.
722
723=cut
724
725sub attach {
726 my $ctx = shift;
727
728 $ctx->[2]{$_+0} = $_
729 for map { AnyEvent::Log::ctx $_ } @_;
730}
731
732sub detach {
733 my $ctx = shift;
734
735 delete $ctx->[2]{$_+0}
736 for map { AnyEvent::Log::ctx $_ } @_;
737}
738
739sub slaves {
740 undef $_[0][2];
741 &attach;
742}
743
744=back
745
746=head3 LOG TARGETS
747
748The following methods configure how the logging context actually does
749the logging (which consists of formatting the message and printing it or
750whatever it wants to do with it).
751
752=over 4
753
754=item $ctx->log_cb ($cb->($str)
755
756Replaces the logging callback on the context (C<undef> disables the
757logging callback).
758
759The logging callback is responsible for handling formatted log messages
760(see C<fmt_cb> below) - normally simple text strings that end with a
761newline (and are possibly multiline themselves).
762
763It also has to return true iff it has consumed the log message, and false
764if it hasn't. Consuming a message means that it will not be sent to any
765slave context. When in doubt, return C<0> from your logging callback.
766
767Example: a very simple logging callback, simply dump the message to STDOUT
768and do not consume it.
769
770 $ctx->log_cb (sub { print STDERR shift; 0 });
771
772You can filter messages by having a log callback that simply returns C<1>
773and does not do anything with the message, but this counts as "message
774being logged" and might not be very efficient.
775
776Example: propagate all messages except for log levels "debug" and
777"trace". The messages will still be generated, though, which can slow down
778your program.
779
780 $ctx->levels ("debug", "trace");
781 $ctx->log_cb (sub { 1 }); # do not log, but eat debug and trace messages
782
783=item $ctx->fmt_cb ($fmt_cb->($timestamp, $orig_ctx, $level, $message))
784
785Replaces the formatting callback on the context (C<undef> restores the
786default formatter).
787
788The callback is passed the (possibly fractional) timestamp, the original
789logging context, the (numeric) logging level and the raw message string
790and needs to return a formatted log message. In most cases this will be a
791string, but it could just as well be an array reference that just stores
792the values.
793
794If, for some reaosn, you want to use C<caller> to find out more baout the
795logger then you should walk up the call stack until you are no longer
796inside the C<AnyEvent::Log> package.
797
798Example: format just the raw message, with numeric log level in angle
799brackets.
800
801 $ctx->fmt_cb (sub {
802 my ($time, $ctx, $lvl, $msg) = @_;
803
804 "<$lvl>$msg\n"
805 });
806
807Example: return an array reference with just the log values, and use
808C<PApp::SQL::sql_exec> to store the emssage in a database.
809
810 $ctx->fmt_cb (sub { \@_ });
811 $ctx->log_cb (sub {
812 my ($msg) = @_;
813
814 sql_exec "insert into log (when, subsys, prio, msg) values (?, ?, ?, ?)",
815 $msg->[0] + 0,
816 "$msg->[1]",
817 $msg->[2] + 0,
818 "$msg->[3]";
819
820 0
821 });
822
823=item $ctx->log_to_file ($path)
824
825Sets the C<log_cb> to log to a file (by appending), unbuffered.
826
827=item $ctx->log_to_path ($path)
828
829Same as C<< ->log_to_file >>, but opens the file for each message. This
830is much slower, but allows you to change/move/rename/delete the file at
831basically any time.
832
833=item $ctx->log_to_syslog ([$log_flags])
834
835Logs all messages via L<Sys::Syslog>, mapping C<trace> to C<debug> and all
836the others in the obvious way. If specified, then the C<$log_flags> are
837simply or'ed onto the priority argument and can contain any C<LOG_xxx>
838flags valid for Sys::Syslog::syslog, except for the priority levels.
839
840Note that this function also sets a C<fmt_cb> - the logging part requires
841an array reference with [$level, $str] as input.
842
843=cut
844
845sub log_cb {
846 my ($ctx, $cb) = @_;
847
848 $ctx->[3] = $cb;
849}
850
851sub fmt_cb {
852 my ($ctx, $cb) = @_;
853
854 $ctx->[4] = $cb;
855}
856
857sub log_to_file {
858 my ($ctx, $path) = @_;
859
860 open my $fh, ">>", $path
861 or die "$path: $!";
862
863 $ctx->log_cb (sub {
864 syswrite $fh, shift;
865 0
866 });
867}
868
869sub log_to_file {
870 my ($ctx, $path) = @_;
871
872 $ctx->log_cb (sub {
873 open my $fh, ">>", $path
874 or die "$path: $!";
875
876 syswrite $fh, shift;
877 0
878 });
879}
880
881sub log_to_syslog {
882 my ($ctx, $flags) = @_;
883
884 require Sys::Syslog;
885
886 $ctx->fmt_cb (sub {
887 my $str = $_[3];
888 $str =~ s/\n(?=.)/\n+ /g;
889
890 [$_[2], "($_[1][0]) $str"]
891 });
892
893 $ctx->log_cb (sub {
894 my $lvl = $_[0][0] < 9 ? $_[0][0] : 8;
895
896 Sys::Syslog::syslog ($flags | ($lvl - 1), $_)
897 for split /\n/, $_[0][1];
898
899 0
900 });
901}
902
903=back
904
905=head3 MESSAGE LOGGING
906
907These methods allow you to log messages directly to a context, without
908going via your package context.
909
910=over 4
911
912=item $ctx->log ($level, $msg[, @params])
913
914Same as C<AnyEvent::Log::log>, but uses the given context as log context.
915
916=item $logger = $ctx->logger ($level[, \$enabled])
917
918Same as C<AnyEvent::Log::logger>, but uses the given context as log
919context.
920
921=cut
922
923*log = \&AnyEvent::Log::_log;
924*logger = \&AnyEvent::Log::_logger;
139 925
1401; 9261;
927
928=back
929
930=head1 EXAMPLES
931
932This section shows some common configurations.
933
934=over 4
935
936=item Setting the global logging level.
937
938Either put PERL_ANYEVENT_VERBOSE=<number> into your environment before
939running your program, or modify the log level of the root context:
940
941 PERL_ANYEVENT_VERBOSE=5 ./myprog
942
943 $AnyEvent::Log::FILTER->level ("warn");
944
945=item Append all messages to a file instead of sending them to STDERR.
946
947This is affected by the global logging level.
948
949 $AnyEvent::Log::LOG->log_to_file ($path); (sub {
950
951=item Write all messages with priority C<error> and higher to a file.
952
953This writes them only when the global logging level allows it, because
954it is attached to the default context which is invoked I<after> global
955filtering.
956
957 $AnyEvent::Log::FILTER->attach
958 new AnyEvent::Log::Ctx log_to_file => $path);
959
960This writes them regardless of the global logging level, because it is
961attached to the toplevel context, which receives all messages I<before>
962the global filtering.
963
964 $AnyEvent::Log::COLLECT->attach (
965 new AnyEvent::Log::Ctx log_to_file => $path);
966
967In both cases, messages are still written to STDERR.
968
969=item Write trace messages (only) from L<AnyEvent::Debug> to the default logging target(s).
970
971Attach the C<$AnyEvent::Log::LOG> context to the C<AnyEvent::Debug>
972context - this simply circumvents the global filtering for trace messages.
973
974 my $debug = AnyEvent::Debug->AnyEvent::Log::ctx;
975 $debug->attach ($AnyEvent::Log::LOG);
976
977This of course works for any package, not just L<AnyEvent::Debug>, but
978assumes the log level for AnyEvent::Debug hasn't been changed from the
979default.
141 980
142=back 981=back
143 982
144=head1 AUTHOR 983=head1 AUTHOR
145 984

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines