Yes, that would work. My issue with that approach is that "info" is a fairly low error level, and symfony generates a lot of these per request, so finding my custom events in those files would be tricky methinks. Ideally I want nothing but my custom info in the log files, and since I know what I want to log, I wouldn't even need a "level" parameter, but for some reason all loggers out there seem to have that..
Thanks for the help, Daniel On Apr 28, 1:31 am, Lee Bolding <[EMAIL PROTECTED]> wrote: > Not sure about a separate log file, but isn't this what log level INFO > is for? > > eg. sfContext::getInstance()->getLogger()->info($message); > > On 28 Apr 2008, at 06:15, Richtermeister wrote: > > > > > Hi all, > > > I'm looking to log some events in my ecommerce application, mainly to > > have some data on the data that goes into the order placement (3rd > > party responses etc..), so technically this information doesn't > > qualify as "errors", and to me it seems that the logging is pretty > > strictly for "unuasualities" such as errors (hence the error level > > setting). > > So my question is, how would you recommend I implement logging in such > > a way that only my custom logging events appear in a specific log > > file? > > > Thank you for your help, > > Daniel --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
