Rob on 3:55am, Tuesday, 2011-01-04log4php was pretty easy to get started with but I think it's made for people who already understand Log4J. The configuration page is pretty clear for a basic set up but there are a ton of more advanced options.
In my case I've been using something like
require_once "log4php/Logger.php";
class Foo {
public function __construct($cid = 0) {
Logger::configure(dirname(__FILE__).'/log4php.properties');
$this->logger = Logger::getLogger('Foo');
...
$this->logger->debug('made a foo ' . $someVal);
}
}
And in my log4php.properties file I have a line that I think defines the logger named Foo (which I use exclusively in the class named Foo).
log4php.appender.Message = LoggerAppenderFile
log4php.appender.Message.file = /path/to/my/project.log
log4php.appender.Message.layout = LoggerLayoutTTCC
...
I have other loggers defined in there as well, including a root logger. And things seem to work. Mostly. I haven't been able to shut off logging from a class, which I think I should be able to do with a line like
This part doesn't behave as I'd expect. Outside of that though, I've used log4php to get a lot of diagnostic info. It was also really easy to spit out log lines over plain TCP/IP using LoggerAppenderSocket and catch it on another machine with netcat (nc).
Overall using log4php has been well worth the little time it took to figure it out. One of these days I'll sort out that last kink & figure out how to toggle logging by class too.