Blog

Using Propel 1.4 detailed logging

Symfony Live 2010 Paris Conference

« Back to the Blog

Categories

Feeds

feed Posts feed

comments feed Comments feed

symfony training
Be trained by symfony experts
Dec 16: Paris (1.3 + Doctrine - Français)
Jan 20: Paris (1.3 + Doctrine - Français)
Feb 24: Paris (1.3 + Doctrine - Français)
Mar 24: Paris (1.3 + Doctrine - Français)
and more...

Archives

Creative Commons License This work is licensed under a Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 Unported License.

Today Propel 1.4 was released and it contains some debugging goodies. We can use the DebugPDO class to get the nifty logging into the Web Debug Panel. However some more interesting information is turned off by default by Propel. It includes:

Using this is very easy as of today / symfony 1.3 beta 2:

dev:
  propel:
    param:
      classname: DebugPDO
      debug:
        realmemoryusage: true
        details:
          time:
            enabled: true
          slow:
            enabled: true
            threshold: 0.001
          memdelta:
            enabled: true
          mempeak:
            enabled: true
          method:
            enabled: true
          mem:
            enabled: true
          querycount:
            enabled: true

The whole list can be found in the Propel Documentation. The prefix debugpdo.logging is taken care of by the key debug. Simply put the remaining path below it, creating a new nesting level each dot.

Because Propel takes the order into account, the above configuration results into something like this:

Propel 1.4 detailed logging

Add a Comment

(will not be published - gravatar enabled)

Comments comments feed

The Sensio Labs Network

Since 1998, Sensio Labs has been promoting the Open-Source software movement by providing quality web application development, training, consulting, and supporting several large Open-Source projects.