Why not provide the same filters as in the web debug toolbar log panel
('sfController', 'sfView', etc) in a config file (probably the
factories.yml) to choose which items we log or, preferably, which
logging level we use for each category? Something like:

categories:
 sfActions: log
 sfView: err
 sfRouting: info
etc...

They would act as 'filters', i.e. any category not defined there would
appear by default with the 'log' level.

François

2008/8/24 Fabien Potencier <[EMAIL PROTECTED]>:
>
> Hi all,
>
> I've refactored the web toolbar to make it more flexible in symfony 1.2
> (http://trac.symfony-project.org/changeset/11041). You can have more
> information in the UPGRADE_TO_1_2 file
> (http://trac.symfony-project.org/browser/branches/1.2/UPGRADE_TO_1_2).
>
> Thanks to the new debug.web.load_panels, the logs panel now only contain
> information that are not available in other panels (db logs, and timer
> logs).
>
> So, the log panel is more readable now. After reading the latest
> François's post
> (http://redotheweb.com/2008/08/19/tip-clean-up-your-symfony-debug-logs/),
> I think we need to think about what we need to log.
>
> I propose to remove some log lines like the "Initalize" lines for
> FrontWebController, Context, and PHPView. They don't give any valuable
> information and pollute the logs. The same goes for the "Dispatch
> request" log.
>
> But perhaps we can log some useful information that are not logged yet.
> Any idea?
>
> Fabien
>
> --
> Fabien Potencier
> Sensio CEO - symfony lead developer
> sensiolabs.com | symfony-project.com | aide-de-camp.org
> Tél: +33 1 40 99 80 80
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"symfony developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/symfony-devs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to