>
> Yeah, I was combing the Armstrong book (or was it the OReilly book)
> and came up with very little... Ill check the Armstrong book again.
The Armstrong book doesn't say much about logging.
The subject is somewhat delicate, because loggers sometimes act as
concurrency bottlenecks in a system.
Most people are content with the standard logger (error_logger module)
and with saving logs to a file and/or the console.
The SASL application adds a couple of different logger backends,
particularly one that saves log items to a buffered file as binary
erlang terms. This is probably the fastest you can get, but it will
require special tools to read and search.
Anyway, error_logger is just a gen_event instance so anybody can hook
up to it and redirect log items to any other target. Some people,
including myself have designed specific logger implementations based
on it, that do all sorts of log formatting and filtering. Log4erl is
one of the freely available implementations, I'm sure there are others.
Bottom line is I don't think there's a clear answer. It all depends on
your logging requirements.
Mihai