[Tickets #7829] Re: Improve / standarize / clean up log messages

bugs at horde.org bugs at horde.org
Wed Jan 7 19:06:27 UTC 2009


DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7829
------------------------------------------------------------------------------
  Ticket             | 7829
  Updated By         | thomas at gelf.net
  Summary            | Improve / standarize / clean up log messages
  Queue              | Horde Groupware Webmail Edition
  Version            | 1.2.1
  Type               | Enhancement
  State              | New
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


thomas at gelf.net (2009-01-07 14:06) wrote:

Hmmm... After grepping around through Horde 4 code (GIT repository) I  
discovered that some mentioned issues are already going to be  
addressed there :-)

It's also great to see that Horde logger is going to look like ZF's  
one! Will it be possible to configure multiple  
observers/listeners/handlers with different filters in Horde's config  
files? And to add other handlers at runtime / using hooks?

I also had a quick look at Horde_Log_Handler_Syslog - if interested  
you could add some improvements from my Zend_Log_Writer_Syslog proposal:
http://framework.zend.com/wiki/display/ZFPROP/Zend_Log_Writer_Syslog+-+Thomas+Gelf
It is able to handle multiple parallel syslog handler instances with  
different facilities and ident's and currently to be found in ZF's  
Standard Incubator (class skeleton on the proposal's site could be  
outdated).

Btw: PHP docs are not correct (I gave a quick look at PHP's source  
code), syslog, openlog and closelog will never fail and return  
"false", even if you completely remove your log device.

Cheers,
Thomas







More information about the bugs mailing list