| Previous Up Next |
From the documentation:
Let me give you an example: You might find out that your system has a problem in the MySystem::Helpers::ScanDir component. Turning on detailed debugging logs all over the system would generate a flood of useless log messages and bog your system down beyond recognition. With Log::Log4perl, however, you can tell the system: ``Continue to log only severe errors to the log file. Open a second log file, turn on full debug logs in the MySystem::Helpers::ScanDir component and dump all messages originating from there into the new log file''. And all this is possible by just changing the parameters in a configuration file, which your system can re-read even while it's running!
Origins: log4j (logging.apache.org)
Siblings: Log4Cxx Log4CPlus Log4Net Log4PHP Log4PLSQL logging.apache.org
Originally designed for flexibility and speed. Perl porters kept this in mind and made a few perlish enhancements.
Features: Remote control, fine tuning, component based, hierarchical.
| www.chelsea.net/~mprewitt/log4perl | Previous Up Next |
Copyright © 2004, Marc Prewitt.
All Rights Reserved.
These slides are free information; you can redistribute them and/or modify them
under the same terms as Perl itself.