Yo, questions wrt logging: -) What are the plans to improve the rather primitive logging facilities in zope ? I couldn't find anything in the plan for 2.6, nor on the 3.0 homepage. I think we need at least an extendibl framework with following types of components: - Loggers (fi, file logger, db loggers, remote logger, nulllogger,...) - Filters (fi on severity, on subsystem, ...) - LogBus (central accesspoint for the logging framework, where you can (dynamically) hook your loggers, filters etc... if time is an issue, we could just copy the design of fi Log4J which is a good logging framework for apache. -) If there are no such plans, can we hack something up ourselves and add/donate it to the product ? I hate writing stuff that gets replaced by something else afterwards .... input appreciated. Sloot.
http://freshmeat.net/projects/log4py/ Romain Slootmaekers wrote:
Yo, questions wrt logging:
-) What are the plans to improve the rather primitive logging facilities in zope ? I couldn't find anything in the plan for 2.6, nor on the 3.0 homepage. I think we need at least an extendibl framework with following types of components:
- Loggers (fi, file logger, db loggers, remote logger, nulllogger,...) - Filters (fi on severity, on subsystem, ...) - LogBus (central accesspoint for the logging framework, where you can (dynamically) hook your loggers, filters etc...
if time is an issue, we could just copy the design of fi Log4J which is a good logging framework for apache.
-) If there are no such plans, can we hack something up ourselves and add/donate it to the product ? I hate writing stuff that gets replaced by something else afterwards ....
input appreciated.
Sloot.
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Romain Slootmaekers wrote:
- Loggers (fi, file logger, db loggers, remote logger, nulllogger,...)
Zope already has a filer logger, I dunno what you mean by db, remote and null loggers, perhaps you can explain?
- Filters (fi on severity, on subsystem, ...)
zLOG already provides this. Set STUPID_LOG_SEVERITY to the level you want Dunno about subsystem. subsystem is passed to zLOG, so maybe you could do a patch which lets subsystem also be controlled by an environment.
- LogBus (central accesspoint for the logging framework, where you can (dynamically) hook your loggers, filters etc...
This is prettymuch what zLOG is. Take a look at my MailingLogger product for an example. It emails log messages with the specified parameters to an address you specify and provides an example for rolling your own loggers. cheers, Chris
On Fri, 1 Mar 2002, Chris Withers wrote:
Romain Slootmaekers wrote:
- Loggers (fi, file logger, db loggers, remote logger, nulllogger,...)
Zope already has a filer logger, I dunno what you mean by db, remote and null loggers, perhaps you can explain?
db= log to database... remote:what if you want your logs to be put on another machine.... null logger does nothing.
- Filters (fi on severity, on subsystem, ...)
zLOG already provides this.
Set STUPID_LOG_SEVERITY to the level you want Dunno about subsystem. subsystem is passed to zLOG, so maybe you could do a patch which lets subsystem also be controlled by an environment.
- LogBus (central accesspoint for the logging framework, where you can (dynamically) hook your loggers, filters etc...
This is prettymuch what zLOG is. Take a look at my MailingLogger product for an example. It emails log messages with the specified parameters to an address you specify and provides an example for rolling your own loggers.
I can write my own stuff. but I need to restart zope if I want to change the zLOG configuration, or hack it in zope and patch every next release. if I'm fi trying to figure out what's happening with a possible bug on a production machine, I'd like fi to temporarily reroute all ERROR logs from BuggyProduct to file dump.txt so that we don't have to wade through the log output the 300 other users visiting websites on the server, produce, since they are not using the BuggyProduct. what if I want to split the logs based on some condition.... I have to change code in Zope, and restart the server ... that's not the way something like this should be done. Romain.
Romain Slootmaekers <romain@zzict.com> writes:
db= log to database...
remote:what if you want your logs to be put on another machine....
null logger does nothing.
Handling the log output should be _completely_ separated from Zope. On the fly changes to log levels and separating ouput to different output "channels" would be good. Regards, Frank
Have you looked at EventLogManager? http://www.zope.org/Members/mcdonc/Products/EventLogManager If I had it to do over again, I'd change lots, but it does do what you're asking for.
what if I want to split the logs based on some condition.... I have to change code in Zope, and restart the server ... that's not the way something like this should be done.
See PEP 282 [1]. If this PEP is accepted, work should probably follow its course. It would be nice to have a single logging mechanism for Python, and for Zope to use and/or extend it. Granted, if it is accepted, it won't be in Python until Python 2.3 which I believe is due in August. ..[1] http://python.sourceforge.net/peps/pep-0282.html On 2/28/02 3:34 PM, "Romain Slootmaekers" <romain@zzict.com> wrote:
Yo, questions wrt logging:
-) What are the plans to improve the rather primitive logging facilities in zope ? I couldn't find anything in the plan for 2.6, nor on the 3.0 homepage. I think we need at least an extendibl framework with following types of components:
- Loggers (fi, file logger, db loggers, remote logger, nulllogger,...) - Filters (fi on severity, on subsystem, ...) - LogBus (central accesspoint for the logging framework, where you can (dynamically) hook your loggers, filters etc...
if time is an issue, we could just copy the design of fi Log4J which is a good logging framework for apache.
-) If there are no such plans, can we hack something up ourselves and add/donate it to the product ? I hate writing stuff that gets replaced by something else afterwards ....
input appreciated.
Sloot.
-- Jeffrey P Shell www.cuemedia.com
participants (6)
-
Chris McDonough -
Chris Withers -
Frank Tegtmeyer -
Jeffrey P Shell -
John Ziniti -
Romain Slootmaekers