#2391: Integrate CherryPy logging with Turbogears's logging configuration
-------------------------+--------------------------------------------------
Reporter: Chris Arndt | Owner:
Type: defect | Status: new
Priority: high | Milestone: 1.5
Component: TurboGears | Version: 1.5 HEAD
Severity: normal | Keywords: needs patch, logging, cherrypy
-------------------------+--------------------------------------------------
!CherryPy 3 sets up the following loggers:
- `cherrypy.access`
- `cherrypy.error`
- `cherrypy.access.<appid>`
- `cherrypy.error.<appid>`
In !TurboGears 1.1 requests were logged via the special '_cp_log_access'
method of the `controllers.RootController` class to 'turbogears.access'
with level INFO, but with !CherryPy 3 this is not supported anymore,
AFAICS.
We need to sort out how to log requests. Do we use CP's logger or do we
set up our own? In the former case, we should drop the `_cp_log_access`
method.
How do we make it easy to set up ogging destinations for the CP loggers in
the application configuration?
See also:
[http://groups.google.com/group/turbogears-
trunk/browse_frm/thread/d3e1e668956bbf60 Logging in the TG 1.5 branch]
(Mailing list thread)
--
Ticket URL: <http://trac.turbogears.org/ticket/2391>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "TurboGears Tickets" group.
This group is read-only. No posting by normal members allowed.
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/turbogears-tickets?hl=en?hl=en
-~----------~----~----~----~------~----~------~--~---
