Thanks Bernhard... Looks like the plugin is available only for 1.1 ...whereas we are using 1.0 ... :|
On Dec 12, 2:17 pm, "Bernhard Schussek" <bschus...@gmail.com> wrote: > Hello, > > Maybe you should have a look for the sfErrorLoggerPlugin (or > sfDoctrineErrorLoggerPlugin, if using Doctrine). This plugin logs all > 404 and 500 errors into the database and offers a backend view for > looking through the errors. It is very helpful to find out about > recurring errors, linked pages that do not exist anymore etc. > > If the plugin doesn't collect enough data for you, you can well > override the schema and collect some more. I personally am very fond > of it. > > Bernhard > > On Fri, Dec 12, 2008 at 7:21 AM, Sumedh <sumedh.inam...@gmail.com> wrote: > > > Hi Friends, > > > Need guidance about logging in production environment. > > > Symfony 1.0 log logs a word [sfException] whenever there is some wrong > > query etc...the details can be seen on screen in DEV environment... > > > But how can I trace the root of the problem in production environment > > (I'll just see 500 internal error message on screen)? If I enable > > logs, I'll just see the word sfException in the log, and the Action > > that created the problem, but not the actual culprit query... > > > How do you guys trace the problems that occur in production? > > > Can we write some simple piece of code that asynchronously mails > > details of a problem occurred in production to a given mail id? > > > Thanks in advance... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
