Example below: Everything for 2 seconds to < 14999 ms will be log.warn. 15s+ will be log.error (and I get an email :-) )
#########################################################################
# ERXAdaptorChannelDelegate
#########################################################################
## Enable delegate to emit SQL debugging info. The Logger used is
## log4j.category.er.extensions.ERXAdaptorChannelDelegate.sqlLogging
er.extensions.ERXAdaptorChannelDelegate.enabled=true
## How long a statement must run to cause a log message. Messages with longer than
## error also emit a stack-trace
er.extensions.ERXAdaptorChannelDelegate.trace.milliSeconds.debug=0
er.extensions.ERXAdaptorChannelDelegate.trace.milliSeconds.info=100
er.extensions.ERXAdaptorChannelDelegate.trace.milliSeconds.warn=2000
er.extensions.ERXAdaptorChannelDelegate.trace.milliSeconds.error=15000
## MaxLength of the message
er.extensions.ERXAdaptorChannelDelegate.trace.maxLength = 3000
## What entities to watch
er.extensions.ERXAdaptorChannelDelegate.trace.entityMatchPattern = .*
## Actually set the log level
log4j.logger.er.extensions.ERXAdaptorChannelDelegate.sqlLogging=WARN
On Apr 21, 2010, at 1:12 PM, Ricardo J. Parada wrote:
> Hi All,
>
> I'm trying to display SQL taking longer than x millisecs but I'm not sure if I'm doing it right because so far nothing displays. My properties are set as follows:
>
> er.extensions.ERXSQLExpressionTracker.trace.milliSeconds.debug=300
> er.extensions.ERXSQLExpressionTracker.trace.entityMatchPattern=.*
>
> Here x = 300 millisecs.
>
> Also, what is the difference between debug/info/error/etc. in the property? An example would go a long way!
>
> Thanks,
> Ricardo
>
This archive was generated by hypermail 2.0.0 : Wed Apr 21 2010 - 13:18:28 EDT