Hi -
Someone asked me the question "Why not use syslog for the logging protocol?"
So, I've spent some time looking at syslog, as well as syslog-ng, which
is an open source
implementation. I had not done any detailed research on this myself, so
I thought it would be
a good idea to do so.
Fundamentally, the requirements for the logging framework that I'm
developing a design
doc for has the following requirements:
* Be agnostic to data format and input.
* Be able to provide multiple streams of output simultaneously in
multiple formats
* Be able to provide data for diverse purposes.
* Provide a remote, logging capability.
* Provide a standardized format.
* Allow the user to modify logging level from the command line for a
particular component of an application
* Provide notification upon completion of the logged process.
I think that the syslog protocol (both syslog and syslog-ng) can fulfill
most of these requirements.
There would be some risk with remote logging and using syslog because
syslog uses UDP which can drop
transmissions. Syslog-ng uses TCP so that wouldn't carry the same level
of risk. But another cost with syslog-ng is
that it is not included as part of Solaris.
The other issue that neither of the syslog facilities can meet is the
need to log at more granular levels in components
within applications. Syslog defines the level of logging at the
application level, and that can't be modified within
components of the application, which is something we want to be able to
do within the installer.
If anyone has any comments or questions about this, please let me know.
--
Ginnie
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/caiman-discuss/attachments/20100224/683515cd/attachment.html>
