I haven't seen you mention the xdebug extension? I use it all the time for performance profiling, prettier and more informative error/exception messages, and it does tons of other stuff if you dig around it's settings and functions.
Paddy Philip G wrote: > > Currently, the debug implementation looks pretty ... bleak. Is there more > to > this not documented? Or would I be using something else in combination? > > What I'm trying to do is build an integrated debugging system that can be > extremely informative in dev/staging and informative enough within our > live > environment (if something happens to go boom-boom). > > I love the Zend_Db_Profiler, but I fear I might not be able to get its > detailed information when it's disabled (on live) in case something blows > up > for some unknown reason. So, I need a new system, to work along side this, > to gather other bits of data to shot off an informative email with a > nuclear > bomb does decide to hit our production sites. > > Any suggestions? Zend_Log looks to be purely a logger, not exactly an > internal debugging logger which sits ideal until called upon. > > What does everybody else use? How do you gain detailed enough information > from a production site, without degrating performance, when something > unexpected happens? > > -- > Philip > [EMAIL PROTECTED] > http://www.gpcentre.net/ > > ----- Pádraic Brady http://blog.astrumfutura.com http://www.patternsforphp.com OpenID Europe Foundation - Irish Representative -- View this message in context: http://www.nabble.com/Zend_Debug----or-better--tp17494670p17494760.html Sent from the Zend Framework mailing list archive at Nabble.com.
